The org chart is not the value stream

An org chart describes who reports to whom. It says nothing about how value is actually created, because value does not flow up and down a hierarchy — it flows sideways, across teams, from a customer’s request to a delivered result.

That mismatch is structural, and it is where value leaks. Every time work crosses a boundary between teams, it waits, it loses context, and someone has to re-establish what the last team already knew. The handoffs are invisible on the org chart and expensive in the value stream.

Manage the flow across the seams

Optimising each department in isolation is a reliable way to make the whole worse. A team can hit every one of its targets while the work passing through it sits in queues, because no one owns the space between the boxes.

The leverage is at the seams. When you manage the flow of work across team boundaries — rather than the productivity of each team in isolation — the queues that quietly dominate lead time finally become someone’s responsibility.

Follow the work, not the reporting line

We start an engagement by following a single piece of work all the way through, ignoring who owns each step. It is uncomfortable, because it cuts across the very lines the organisation uses to manage itself.

But it is the only view that matches how customers experience you. They never see your org chart. They only ever feel your value stream — and the waiting, rework, and dropped context built into its seams.