Part I — Discovering Flow · Chapter 1 · First Public Draft

Introduction

Why organizations create less value than they could.

Organizations exist to create value.

Everything else — the structure, the systems, the meetings, the operating model, the strategy deck — exists only to help create more of it. It earns its place by helping something reach someone outside the organization who is better off for having received it.

Which makes one question more important than almost any other.

How much more value could this organization create with exactly the resources it already has?

Not with a larger budget. Not after the next hire. Not after the next transformation. With the people, knowledge and capability already in place today.

For most organizations, the answer is considerably more.

The gap is rarely a lack of effort. It is rarely a lack of talent. More often, it is that too much of the organization’s existing capacity never becomes value.

I call the mechanism behind that loss structural friction, and the claim this whole paper rests on is worth stating once, plainly:

Organizations don’t become slow because people work slowly. They become slow because structural friction accumulates faster than value is created.

The next chapter follows one piece of that loss all the way to a number, and names the shapes structural friction most often takes.

Organizational Flow

This paper calls an organization’s ability to continuously create value Organizational Flow.

Every organization has it. Not a framework. Not a maturity model. Not a programme. A property every organization already possesses, whether high or low — and a way of seeing why some organizations consistently convert more of their existing capacity into value than others. What that property actually consists of is what the rest of this paper explains, starting properly in the chapter after next.

One system, not several subjects

This paper is not about separate subjects such as ownership, technology, AI or leadership. It describes one living organizational system, viewed from different angles.

One observation from software development is worth carrying into organizations. We learned that the systems we build are never truly finished — they evolve continuously, and must be cultivated over time. Organizations are no different. If one is designed for continuous evolution while the other is designed for completion, structural friction is inevitable. The systems we build and the organizations that build them must therefore be cultivated together.

That has become even more important as AI lowers the cost of building technology. The constraint is no longer primarily the ability to create software. Increasingly, it is the organization’s ability to create clarity, ownership and sound decisions around what should be created and how it should evolve — a thread this paper picks up properly in Teams and Artificial Intelligence.

What follows

The chapters that follow work out where that loss lives, what it costs, and what Organizational Flow actually is — and then, from there, what to do about it.

Once you begin seeing this, you start noticing it everywhere — in ownership, in meetings, in incentives, in funding, in decisions, in structure. That is rather the point.

You have almost certainly already seen it. You may just not have had words for it.