patrick.belmans@servinomy.be
en

The Lab

In this thought laboratory, Servinomy is questioning everything. From the most obvious to the most bizarre ideas and/or approaches within service management. Limitless and boundless experimentation is the key in this lab.

From a Common Language to Meaning

Why the Future of Organisations Does Not Begin with Technology or Processes

Servinomy: 28/07/2026

Follow-up to: "From Alignment to a Common Language"

Introduction

In the previous article, one central idea emerged: organisations need a common language. An organisation-wide process model can provide that language. It connects areas of expertise, clarifies responsibilities and illustrates how value flows throughout the organisation. But the story does not end there. Because a process model can connect expertise, it cannot inspire people. And that is precisely where the next challenge begins.

The Uncomfortable Insight

Many organisations stop at structure. They document processes. They define roles. They implement technology. They build dashboards. They launch projects. And then they expect human behaviour to follow automatically. It rarely does. Not because people are stubborn. Not because employees dislike change. But because understanding how something works is not the same as understanding why it matters.

A process model may perfectly explain how an organisation creates value. It does not automatically explain why that value is meaningful to the people contributing to it. As a result, a strange situation emerges. The organisation has expertise. The organisation has processes. The organisation has technology. And yet engagement is missing.

The Persistent Myth of the Modern Organisation

When organisations encounter difficulties, they often reach for the same solutions:

  • new technology;
  • optimised processes;
  • additional reporting;
  • more governance;
  • extra controls.

The underlying assumption is straightforward:

If we improve the system, behaviour will naturally follow.

But human behaviour does not work that way.

  • A process is an antecedent.
  • Technology is an antecedent.
  • Training is an antecedent.
  • Communication is an antecedent.

They all exist before behaviour. They may encourage desired behaviour. They can never guarantee it. Ultimately, behaviour emerges from the consequences people experience. People constantly ask themselves the same questions:

  • Why are we doing this?
  • Who does this help?
  • Does this create value?
  • Does my contribution matter?

When these questions remain unanswered, organisations often see exactly the behaviours they are trying to avoid:

  • resistance;
  • cynicism;
  • passivity;
  • minimal compliance;
  • declining engagement.

Not because people fail to understand the process. But because they fail to experience its meaning.

The Missing Layer Above the Process Model

This is where what I call The Meaning begins. Not as a new methodology. Not as a culture programme. Not as a change initiative. But as an additional layer above the process model. The process model connects expertise. Meaning connects people. The process model explains how the organisation works. Meaning reveals why that work matters. Both are necessary. An organisation without a process model creates chaos. An organisation without meaning creates bureaucracy.

People Are Not the Problem

This may be the most important idea of all. Meaning is not about changing people. Quite the opposite. People are not software that can be reprogrammed. Yet many change initiatives start from exactly that assumption. When desired behaviour fails to appear, organisations respond with:

  • more communication;
  • more training;
  • more workshops;
  • more change management.

As though people themselves were the problem. Perhaps the problem lies elsewhere. Perhaps it lies in the environment.

Change the Environment, Not the Person

Behaviour never emerges in a vacuum. Behaviour emerges as a response to an environment. That environment consists of:

  • processes;
  • structures;
  • objectives;
  • language;
  • technology;
  • leadership;
  • culture.

When the environment feels complex, contradictory or meaningless, behaviour often emerges that is misinterpreted as resistance. When the environment is simple, understandable and human-centred, desired behaviour often becomes the most natural choice. Adding meaning does not begin by changing people. It begins by designing a better environment.

Cognitive Simplicity as a Strategic Advantage

Many organisations respond to complexity by adding more complexity.

  • More rules.
  • More processes.
  • More controls.
  • More exceptions.
  • More dashboards.

Yet every additional layer consumes cognitive energy. Energy that can no longer be invested in creating value. This is why I believe the organisations of the future will not necessarily be those with the most processes or the most technology. They will be the organisations that can most clearly explain:

  • why they exist;
  • what value they create;
  • how everyone contributes to that value.

Not simplistic. But simple enough to remain humanly understandable.

But Isn't This a Utopia?

At this point, some will argue:

"The future is technology, not Meaning."

And honestly, that sounds like a reasonable argument. AI is becoming more powerful. Automation continues to expand. Digital transformation is accelerating. But that is precisely why the human dimension becomes more important. AI (technology) is increasingly capable of answering the question: How?

  • How do we analyse data?
  • How do we optimise processes?
  • How do we automate tasks?

Yet organisations will still need people to answer a different question: Why?

  • Why does this organisation exist?
  • Why do we provide this service?
  • Why is this value important?

Technology can accelerate a direction. It cannot determine that direction. An organisation without a shared purpose will produce confusion more efficiently through technology.

A New Order of Priorities

Perhaps organisations have spent years operating in this order:

  1. Technology
  2. Processes
  3. People

Perhaps it is time to reverse it.

  1. Meaning (Humanising)
  2. Process Model
  3. Technology

Not because processes or technology are becoming less important. Quite the opposite. They remain essential. But their role changes.

  • Humanising provides Meaning.
  • Process models facilitate collaboration.
  • Technology supports and accelerates.

Finally: The Future Remains Human

Expertise creates knowledge. A process model connects that knowledge. Humanising gives Meaning to that connection. Only then does something emerge that no technology, process or organisation can create on its own: engagement.

Perhaps the future therefore does not lie in ever better processes or ever smarter technology. Perhaps it lies in organisations that once again understand that value creation remains, ultimately, a human activity.

  • Processes do not create value.
  • Technology does not create value.
  • Even organisations do not create value.

People do.

In Conclusion

This trilogy began with a simple observation: organisations today possess more expertise, processes and technology than ever before, yet many of the same challenges continue to reappear.

  • In the first article, we explored how expertise alone is not enough. Value is only created when different areas of expertise are aligned.
  • In the second article, we discovered that alignment requires a common language. An organisation-wide process model helps make visible how value flows through the organisation and how different areas of expertise contribute to a shared outcome.
  • In this third article, we added a crucial layer. A process model can connect expertise, but only people can give meaning to that connection. Without meaning, organisations achieve compliance. With meaning, they inspire engagement.

Perhaps the future of organisations is not about choosing between people, processes or technology. Perhaps the real challenge is restoring the correct order.

  1. Humanising provides direction.
  2. Processes create coherence.
  3. Technology enables execution.

When these three components reinforce one another, they create an environment in which people understand why their work matters, how they contribute together and how technology supports that effort.

This is not a new methodology. Not a new framework. Not another management trend. Perhaps it is simply an attempt, seen thrue the Servinomy lens, to look at organisations through their most fundamental purpose once again: creating value through people, for people.

From Alignment to a Common Language

Servinomy: 26/07/2026

The process model that everyone understands

Follow-up to: "From Expertise to Alignment"

Alignment Is Lovely. But Aligned to What?

The previous article asked one central question: are organisations sufficiently aligning their expertise? The answer was: far from always, and it costs more than most people realise.

But there is a follow-up question that is at least as important.

What exactly are you aligning to?

Because aligning without a shared starting point is like doing a jigsaw puzzle together without the picture on the box; everyone is busy. Everyone is trying their best. But the pieces do not fit.

This article is about that missing picture. And about why an organisation-wide process model — a shared description of how the organisation delivers value — is the most underestimated solution to the most common organisational problems.

The Uncomfortable Truth: More Investment, Same Problems

Organisations today spend more than ever on technology, digital transformation, and new systems. And yet the same people complain about the same things. Departments working past each other. Decisions that take forever. Employees who do not know what is expected of them. Customers who have to tell their story three times.

The figures are confronting. Nearly nine out of ten major organisational changes fail to achieve their goals. Not because the technology does not work. But because people do not come along — or do not understand what is being asked of them.

And that is not a question of unwillingness. It is a question of understanding.

Research shows that poor collaboration between departments costs organisations twenty to thirty percent of their revenue. Employees waste an average of more than five hours per week searching for information that already exists somewhere else, or recreating something a colleague has already done. That is almost a full working day per week — evaporated into thin air.

The Problem Has a Name: the Silo

A silo is a department, team, or group of people that has become so focused on itself that it barely sees the rest of the organisation. Not because they want to. But because the organisation is built that way.

Think about it. The finance department is measured on costs. Customer service on satisfaction. Sales on revenue. All logical goals. But if nobody looks at the whole — at how all those goals together deliver value to the customer — then people work alongside each other instead of with each other.

The real problem is this: organisations are built vertically, but value flows horizontally. A customer who places an order draws a line straight through procurement, logistics, finance, and customer service. But those departments rarely talk to each other about that one customer. They talk about their own goals.

Two Experts, Two Languages

Imagine a finance manager and a customer service manager sitting down together. Both are sharp. Both want what is best for the organisation. But if the finance manager thinks of "customer" as a cost item on an invoice, and the customer service manager thinks of "customer" as a person with a problem — they are speaking two different languages.

That sounds exaggerated. But research shows this is daily reality in most organisations. People in different departments use the same words but mean fundamentally different things by them. "Priority" for one department is "maybe next month" for another. "Done" in sales means something entirely different from "done" in operations.

And that leads to mistakes, delays, frustration — and ultimately to customers who walk away.

Scientists call this the problem of mental models: the internal map that every person carries of how the world works. When those maps diverge too much, collaboration grinds to a halt. When they resemble each other, collaboration happens almost naturally.

Research conducted with teams running flight simulations showed that teams with a shared understanding of the task and of each other's roles performed significantly better. Not because they were smarter. But because they had the same map.

When team members share the same 'map' of reality, they work faster, make fewer mistakes, and achieve better results.

The Common Language That Is Missing

This is where the process model comes in. Not as a technical document for specialists. But as a common language for the entire organisation.

A good process model answers four simple questions:

  • What do we deliver? — What value do we bring to the customer or citizen?
  • For whom? — Who receives that value?
  • How? — What steps do we go through, from start to finish?
  • Who does what? — Who is responsible for which part?

That sounds simple. And in theory, it is. In practice, most organisations cannot give a clear, shared answer to at least one of these four questions. Not because the answer does not exist. But because the answer lives in ten different heads, in ten different versions.

A process model makes those versions visible. It lays them side by side. And it forces a conversation about what the organisation actually does — and what it should do.

What Happens When You Actually Do It

The municipality of The Hague is a good example. After a major fraud case in 2019 — in which €1.8 million disappeared due to weak internal controls — the city decided to take its processes seriously, not as a paper exercise, but as a foundation for collaboration.

What did they find? Many processes had never been documented at all. And the processes that had been described looked completely different in every department. Nobody had the same picture. Everyone was doing their best, but nobody could see the whole.

The solution was not a new reorganisation or an expensive IT system. The solution was one shared process model, accessible to all 12,000 employees, so everyone could see how work flows, who does what, and where the connections lie.

The lessons the city drew are universal:

  • One language works better than ten dialects. When every department has its own way of describing things, confusion follows.
  • People need to understand why it matters. A process model imposed from above does not work. One that helps people understand their own work does.
  • Technology helps, but does not solve it. The tool is not the solution. The shared language is the solution.

And Then There Is AI

Artificial intelligence makes all of this more urgent. AI is brilliant at answering the question "How?" How do you optimise a route? How do you analyse data? How do you write a text?

But AI cannot answer the question "Why?" on behalf of the organisation. Why does this organisation exist? Why do we deliver value in this way? Why is this process designed as it is?

Those questions require people. People with a shared understanding of the organisation.

And there is another risk. If AI is deployed to automate existing processes — without those processes first being understood and shared — then AI accelerates the inefficiency. You automate the silos. The problem gets faster, not smaller.

A process model is therefore not only useful for today's collaboration. It is the foundation for tomorrow's AI deployment.

Five Things a Good Process Model Does

Based on research and practical experience, five characteristics make a process model effective:

1. It starts with the customer, not the department. Processes describe how value reaches the customer — not how the department organises itself. That is a fundamental difference.

2. It shows the whole picture. A process model that stops at the departmental boundary reproduces the silos it seeks to break down. The power lies in making the complete value stream visible, from start to finish.

3. It uses one language, not ten versions of the same concept. One definition of "customer", "priority", "done", and "responsible". Simple, but powerful.

4. It makes clear who does what. Who owns which process? Who provides input at which moment? Where are the connections between departments? A process model without ownership is a map without a compass.

5. It lives. A process model is not a document that disappears into a drawer. It is a living instrument that grows with the organisation — and that people use every day to understand their work.

What a Process Model Is Not

To be clear: a process model is not a reorganisation plan. It is not an IT architecture diagram for technologists. It is not a bureaucratic document that makes compliance officers happy.

It is an answer to the question every new employee asks on their first day: "How does it actually work here?"

If your organisation has a clear, shared answer to that question — then you have a common language. And then alignment is no longer a challenge, but a matter of course.

In Closing: People Create Value, Not Organisations

Organisations do not create value. People do.

But people can only create value together if they speak the same language. Not only the language of their own discipline. But the language of the organisation as a whole.

An organisation-wide process model is that language. It is the map that orients new employees. The bridge that connects departments. The compass that guides technology and AI. And the foundation upon which genuine collaboration is built.

The question is not whether your organisation needs a process model.

The question is whether your process model is already a common language — or merely a document.

From Expertise to Alignment

Servinomy: 17/07/2026

Lately, I have noticed that organisations are putting substantial resources into technology, digital transformation, processes, expertise, and artificial intelligence. Nonetheless, many continue to face the same common challenges: organisational silos, fragmented responsibilities, complex decision-making, and resistance to change.

This led me to a simple reflection. Perhaps the greatest challenge today is no longer acquiring more knowledge or implementing more technology. Perhaps the real challenge is connecting expertise.

As organisations grow and become more specialised, the need for a shared understanding increases. What value are we creating? How do we collaborate? What service are we trying to deliver?

AI is becoming increasingly capable of answering the question "How?" But organisations will still need people to answer the question: "Why?"

One reflection question I often ask myself is: Could a new employee explain how your organisation creates value within 15 minutes of joining?

If the answer is yes, your organisation probably has a strong and understandable service model. If the answer is no, the greatest opportunity may not be the next tool, process or project. It may be alignment. 

Because, ultimately, organisations do not create value. People do.