The Definition Holding Us Back
Ask most people what a process is, and they will describe a sequence of tasks connected by arrows. Someone draws it, it gets approved and filed.
Not wrong. But dangerously biased.
Reducing process to a flowchart shapes what process work is expected to deliver. And it explains why so many improvement initiatives fail to stick.
Process Is Behavioural Science
A process is not just a description of what happens. It is a description of how people interact with each other, systems, and data.
When we model a process as a technical sequence, we are modelling a world that does not exist. Real processes operate inside organisations with cultures, histories, and accumulated habits. Informal norms shape what gets raised and what gets avoided. The process as documented and the process as lived are often two very different things.
Process is how an organisation breathes. Understanding it fully is not a specialist concern. It is a leadership imperative.
Where the Real Problems Hide
On paper, everything looks fine. The flow is logical. The roles are clear. And yet outcomes are consistently poor or the same failures repeat.
The explanation is rarely in the diagram. It is in the culture surrounding it.
Perhaps certain topics are systematically avoided because raising them has historically been uncomfortable. Perhaps a handoff always degrades because two functions have a long history of mistrust. Perhaps a governance step functioning as quality control is actually a blocking mechanism.
These dynamics are invisible to process work that stops at the technical level.
The Dead Document Problem
A process that does not understand how people within it actually think and behave, is not a process. It is a document. Documents do not transform organisations. Behaviour does.
This applies even more forcefully with AI. An AI agent operating within a process modelled only at the technical level will encounter the same invisible barriers that humans encounter. Only faster and at greater scale.
What Genuine Process Work Requires
It requires asking not just what happens but why people behave the way they do. It requires surfacing informal norms alongside formal ones. It requires examining how legacy, incentives and culture shape choices at every level.
It also requires courage from leadership. The most significant process failures are often visible to people inside the organisation. Surfacing them requires honest inquiry, not just analytical rigour.
Three Questions Worth Asking
Are your process models describing what actually happens, or what is supposed to happen?
The gap between these two is where the most costly opportunities and risks lurk.
Do your improvement efforts examine cultural and behavioural dynamics?
If not, you are working on the surface.
When a process change fails to stick, what explanation is given?
If it is consistently about communication, training or leadership support, ask whether the deeper questions are addressed.
Conclusion
Process development is one of the most demanding leadership disciplines in organisational life, because it requires understanding systems in which human behaviour, culture, and technical architecture are inseparable.
When you understand processes at this level, everything changes. Improvements stick and technology lands.
FAQ
Frequently asked questions
What is a business process, really?
- A business process is the operating logic the organisation actually runs on the living pattern of decisions, handoffs, and conditions that produce a result. It is not a diagram on a wall. The diagram is at best a snapshot; the process is the system that keeps running whether anyone is looking at it or not.
Why aren't process diagrams enough?
- Diagrams capture an idealised sequence of steps, but they miss the conditions under which work actually happens: exceptions, rework loops, informal decisions, and the data that flows alongside. Treating the diagram as the process is what makes process work feel disconnected from reality.
How do you describe a process as a living system?
- By describing it through the behaviour it produces: what triggers it, what decisions are made along the way, who owns each decision, what information is required, what 'done' means, and how it adapts when conditions change. A living-system view treats process as something that has to be observed, not just drawn.
Why do improvements and technology fail to stick?
- Because they are bolted onto a diagram instead of the real system. When the underlying operating logic is not understood, automation and AI lock in the existing dysfunction. Improvements stick and technology lands when the process is understood at the level of how it actually behaves.
Dr. Katariina Kemppainen
One of Finland's sharpest voices on process intelligence and the operational foundations for the AI era. With a PhD in Operations Management from Aalto University and over two decades across academia, global corporations and entrepreneurship, Katariina believes processes are the user interface to AI. Without world-class processes, intelligence lacks the context and direction it needs to create lasting value.
All essays by this authorRead next