Key concepts

An organization's ability to continuously move information, decisions, execution and learning through enduring capabilities, so that value gets created for customers and users. Every organization has it to some degree; it is a property you hold a position on, not a state you arrive at, and not a framework or a methodology.

Developed in: What is Organizational Flow? · The Ten-Minute Version

Whatever the structure of an organization adds between a piece of work and its value: unclear ownership, context rebuilt at every boundary, decisions that wait, and outcomes that never travel back to whoever chose. Its real cost is not effort or time but the value those hours would otherwise have created. Organizations become slow when friction accumulates faster than value is created.

Developed in: The Cost of Value Never Created · Reducing Friction

The first of the four indicators: whether responsibility for a capability is unambiguous to the people around it. A quick test is to ask five people, separately, who owns it — and compare the answers.

Developed in: A Meeting Grew Here · Observing Organizations

The second indicator: effort spent rebuilding context that already existed, each time work crosses a boundary between groups. It is a restatement of flow efficiency from Lean, applied to the boundaries an organization draws.

Developed in: You Have to Know a Guy · Observing Organizations

The third indicator: the gap between a decision becoming necessary and being made. It is lead time applied to decisions rather than to work, and in most organizations the deliberation takes minutes while the waiting takes weeks.

Developed in: The Long Way to a Yes · Observing Organizations

The fourth indicator: how long it takes for the outcome of a decision to travel back to whoever made it — if it ever does.

Developed in: We Have Solved This Before · Closing the Loop

An enduring business area — a bounded context that owns an outcome. Enduring, because it outlives the systems, suppliers and reorganizations that deliver it; bounded, because you can say what is inside it and what is not. The nearest relative is the bounded context from Domain-Driven Design.

Developed in: What a Capability Is, and Is Not · What Survives the Reorg

Capability belongs to the organization; competence belongs to people — and, increasingly, to agents. A capability that rests on the competence of a few named people is one resignation away from disappearing.

Developed in: What a Capability Is, and Is Not · The Wait Nobody Logged

The limit on how much a team can hold. The paper borrows the idea from Team Topologies (Skelton and Pais) and applies it as a sizing rule: count the separate domains a team must understand, not the people in it.

Developed in: How Much Can One Team Hold · Drawing the Line Around a Team

Who may decide what without asking. Friction falls when the decision moves to the information rather than the information to the decision — and when delegated authority survives its first bad outcome.

Developed in: Reducing Friction · Leading Without Deciding

The structure people and AI agents both need to act with confidence: a clear outcome, the right context, boundaries, decision rights, tools and feedback. Its purpose is to reduce the cost of navigating the organization — so the useful question is how little context someone needs to make a good decision, and the aim is a thinner harness, not a larger one.

Developed in: The Meter Was Always Running · Owning What AI Can't