The finance team wanted printouts.

Not out of stubbornness. They needed to check the numbers, and checking meant reading them on paper, line by line, against another set of numbers, by hand. That was the control. It had always been the control, and it worked, in the sense that errors were caught.

It also meant that every month a group of capable people spent days doing something a machine could do in seconds, and everyone involved knew it, and it carried on anyway — because the people who understood what the checks were for and the people who could automate them were in different parts of the organization, speaking to each other through requirements documents.

So we tried something small. One person from finance came and sat close to the team building the thing. Not as a stakeholder to be consulted at milestones. Close enough to be asked a question and answer it the same hour.

The printouts went away. Most of the manual validation became automatic. A bonus came with it that nobody had asked for: quality went up. Not because the machine was more careful than the people were, but because once the checks were automatic we could afford to run more of them than anyone would ever have done by hand.

Nobody in that story was doing anything wrong. Finance was protecting the numbers, which is their job. The team was building what was specified, which is theirs — and what was specified is where the whole problem was hiding, because a specification is what you need when the people who understand the work aren’t in the room. The friction wasn’t inside the work. It was between the work.

One person moved. Thousands of hours disappeared — not because anyone worked harder, but because more of the organization’s existing capacity finally became value. That is what structural friction costs. Not effort. Not salaries. Not even time. It costs value that never gets created.

That story has a team building something in it, which makes it easy to file this as a software problem. It isn’t, and the clearest cases have no technology in them anywhere.

A procurement function I worked alongside was genuinely good at its job, measured exactly the way it had been asked to measure it. It negotiated hard, consolidated suppliers, and took real money off the contract every year. Nobody could fault the work, and nobody did.

The consequences landed in a different building. The contract that saved the most had a change-request clause in it, and the department living inside that contract needed changes constantly — each one now priced individually, quoted in weeks, and approved by someone who had never met the person asking. The savings were real, and they were recorded, in the quarter they happened. The cost of those savings was equally real and was recorded nowhere, because it arrived as slowness in someone else’s budget, eighteen months later, where nobody was looking for it.

Nobody was wrong. Procurement optimized what it owned. The department owned the consequences and not the decision. The friction was the distance between those two facts, and there was nothing to buy, nothing to build, and no technology anywhere in the problem.

That’s what makes friction so difficult. It rarely lives inside anyone’s work. It lives in the space between people’s work, which means it belongs to no one, which means nobody is accountable for removing it.

Structural friction is not what organizations lose. It is how they lose it. The loss is the value their existing people, knowledge and capability could have created — but never did.

Every hour spent rebuilding context, waiting for a decision, navigating unclear ownership or crossing an unnecessary boundary consumes capacity the organization has already paid for. The capacity is real. The effort is genuine. The salaries were paid. The value simply never arrived.

That is why friction is so difficult to see. Failure announces itself — a project cancelled, a system down, a customer lost. Structural friction rarely does. Projects continue. Meetings continue. People remain busy. Reports are delivered. Approvals happen. Everything looks productive. The organization simply creates less value than it could have, with exactly the same resources.

Friction takes a small number of recognizable shapes, and they sort into four groups. Those four are the spine of this paper — every chapter from here on works on one of them, and Part IV comes back to measure all four. Learn these and you have the vocabulary for everything that follows.

Ownership clarity — nobody can say whose it is.

Ownership nobody can name. Two teams given the same capability on different time horizons — one building the future, one maintaining the past. It looks efficient on an org chart. In practice both teams are technically right, neither is fully responsible, and every decision between them escalates.

Governance grown to fill the gap. Where ownership is unclear, people don’t stop working — they start compensating. Meetings. Committees. Approval chains. None of it comes from incompetence. It comes from uncertainty, and uncertainty always builds something in its own defense.

Handoff loss — context rebuilt at every boundary.

Handovers, meaning any point where work passes from one group to another. Each looks like a clean transfer on a process diagram. Each is really a small act of forgetting, paid for later by whoever has to reconstruct what the previous team already knew. Sales to delivery. Recruitment to onboarding. Procurement to the department that has to live with what was procured.

Decision latency — the gap between necessary and made.

A decision waiting on a forum. The decision itself takes four minutes. Reaching the forum authorized to make it takes three weeks, and nobody counts the three weeks, because nobody bills for waiting.

Information that arrives correct and late. The report was accurate. It was thorough. It reached the person with authority to act on it after the window to act had closed. This is the most expensive form of friction and the least likely to be treated as a problem, because everyone involved did their job well.

A rhythm mismatch. The work needs a decision this week. The structure around it can produce one in April. Nobody is being obstructive; the two things simply run at different speeds, and the slower one sets the pace.

Learning cycle time — outcomes that never travel back.

Nothing changed as a result. Execution finished, results arrived, and nothing about the next decision was different. The organization didn’t learn. It will now solve this problem again, at full price.

None of those are technology problems. Some of them will be presented to you as technology problems, which is its own kind of friction. And each one is cumulative and invisible at the same time — no single instance is worth escalating, which is exactly why the total never gets escalated either.

Doing the arithmetic

Here is the sum, with the numbers I have most often seen. Replace them with yours — the point is the shape, not my figures.

Handoff loss, the easy one. Ask a receiving team how long it takes before they can act without going back to ask. Four hours is a common answer and a conservative one. Take a boundary crossed weekly:

4 hours × 52 weeks = 208 hours a year, on one boundary.

That is more than five working weeks, spent entirely on reconstructing something somebody already knew. A mid-sized organization has eight or ten such boundaries without trying. At eight, it is:

208 × 8 = 1,664 hours — a full-time role, doing nothing but remembering.

Almost one full-time role, not creating anything. Simply recovering information the organization had already produced once. Nobody is employed to do this. It appears in no budget, and no one has ever been asked to justify it, because at four hours a time it never looks like anything.

Decision latency, the expensive one. This one is not measured in salary, and treating it that way understates it badly. The people waiting are not idle — they move to something else, which is precisely why the wait costs nothing visible and why nobody counts it.

The real cost is delay. Take an initiative worth €50,000 a month once it is live — modest for anything a company bothers to fund at all. It needs eight cross-team decisions, made in sequence, each waiting a median of three weeks:

8 decisions × 3 weeks = 24 weeks of pure waiting, about six months.

6 months × €50,000 = €300,000, in delay alone.

Total deliberation across those eight decisions: perhaps a day. The organization did not lose six months of effort. It lost six months of value creation.

What it isn’t. These numbers are illustrations rather than research. I have not measured this across a sample of companies and neither has anyone else — the figures above are deliberately conservative. Replace them with your own, halve every assumption, and the conclusion rarely changes: small, individually reasonable delays compound into large amounts of value that never reach a customer.

Why it never gets escalated. Both calculations produce large numbers out of small, individually reasonable events. Nobody approves a six-month delay. Everybody approves this particular three-week wait, because this one has a good reason — and so does the next one. The cost is real and the decision to incur it was never made.

This is why structural friction survives being obvious. It rarely appears where it originates. It appears as slower delivery, more meetings, more approvals, more governance, more dependencies. Those are symptoms, and they are often a reasonable response to uncertainty — the friction lies underneath them. Which is why removing a governance forum without resolving unclear ownership rarely creates speed. The symptom disappears. The cause remains.

So here is the frame for everything that follows.

Friction comes off two ways. Clarity — an ownership question settled once, a boundary drawn, a decision moved to where the information already is. Done, and it holds. Cultivation — the conditions that let people decide with confidence, not just without asking. Ownership isn’t only permission. It’s knowing your call was the right one to make, and guardrails are what make that confidence earned rather than just brave.

I spent years doing the second while the first was missing, and called it a culture problem. It wasn’t. You don’t cultivate your way out of one capability split across two departments. You fix that with a decision.

Flow is what an organization does when nothing is in the way. Friction is everything that gets in the way. Every chapter after this one — purpose and ownership, capabilities, teams, people, information, decisions, execution, learning, and later leadership, architecture, technology and AI — removes friction one of those two ways, or helps more value emerge once it’s gone. I’ll say which, whenever it isn’t obvious on its own.

The rest of this paper is about changing that equation. Some changes remove friction directly. Others increase an organization’s ability to create value. Together they increase Organizational Flow — because organizations rarely need dramatically more capacity. They need more of the capacity they already have to actually become value.