Part I — Discovering Flow

What is Organizational Flow?

Every field has a word that gets used constantly and understood differently by everyone using it. In this one, that word is “transformation.” Ask ten people what digital transformation means and you’ll get ten answers, and the gap between those answers is where most transformation efforts quietly stall — not from lack of effort, but from lack of a shared destination.

It’s worth being precise, once, about what the surrounding vocabulary actually means, because the rest of this book leans on the distinction. Digitization is the shallowest layer: converting analog into digital, paper into records, nothing about how the work happens actually changes. Digitalization goes one layer deeper — using technology to do the same work better, faster, with less friction, but still recognizably the same work. Digital transformation goes deeper still: rethinking not just how work gets done but where the organization creates value in the first place, letting technology reshape process, product, and culture rather than just accelerate them. And beyond that sits full digital business transformation — the rare case where an organization uses digital capability to become something genuinely new, not a faster version of what it was.

Most organizations aim for the third and settle for the second, and don’t notice the difference until years in, when the tools have all changed and the operating model hasn’t.

Organizational Flow is not a fifth term for that same ladder. It’s the thing underneath all four of them — the property an organization needs regardless of which layer of digitization it’s currently attempting. Here is the definition this whole book keeps returning to:

Organizational Flow is the organization’s ability to continuously move information, decisions and execution through enduring capabilities towards customer and user value — and learn from the outcomes.

Read that slowly, because every word is doing work. Continuously — not a project with an end date, but an ongoing condition, the way a forest doesn’t finish growing. Move — flow is about motion, not position; an organization can have excellent people, excellent technology, and excellent intentions sitting perfectly still. Information, decisions, execution — the three things that actually have to travel, in that order, for anything to happen. Enduring capabilities — the roots from the previous chapter, the what that outlives every how. Customer and user value — the canopy, the only part anyone outside the organization actually experiences. And learn from the outcomes — the part most organizations skip, closing the loop back from canopy to roots so the next season grows a little better than the last.

Everything in Part I has been circling this definition without naming it. A personal journey through twenty years of watching the questions get bigger. A single conversation that reframed technology as engine rather than cost center. A garden tended rather than managed. A forest, not a machine. Flow is the name for what all of that was actually about — not a new methodology to adopt, but a way of noticing whether value is actually moving, or just sitting somewhere, waiting for someone to ask why.

The rest of this book is an attempt to take that definition seriously, one enduring part of an organization at a time — starting, in Part II, with the first and most foundational of them: purpose.