The Great Flattening - Chapter 3: Your Org Chart Is Lying to You. The Real Company Runs Through Flows.

Chapter 3 of The Great Flattening.

How AI is rewriting power, layers, and leadership at work.

---

Marketing owns demand. Sales owns pipeline. Operations owns delivery. Service owns retention.

But your customer experiences one journey. Your revenue moves through one flow. Your problems do not stop politely at departmental borders.

A lead becomes a conversation. A conversation becomes a proposal. A proposal becomes delivery. Delivery becomes adoption. Adoption becomes renewal. Renewal becomes growth.

So when AI enters the business, it does not ask, "Which department owns this?"

It asks: what is the workflow, where is the friction, and who decides what happens next?

That is where the org chart starts lying.

Not because org charts are useless. They still explain authority. Reporting. Budget. Formal accountability.

But they do not show how work actually moves.

And in an AI environment, that gap becomes expensive.

McKinsey's latest marketing workflow research found that nearly 90% of CMOs are experimenting with AI use cases, but fewer than 10% have captured value across end-to-end workflows. That is the whole problem in one sentence. AI activity is rising. Enterprise value is not.

The Flow Is Not the Function

A campaign launch rarely belongs to one team.

Brand writes the story. Content shapes the assets. Legal checks the claims. Media launches the spend. CRM builds the nurture. Sales enablement translates the message. Analytics reads the signal. Service hears the customer reaction.

The org chart treats those as separate boxes.

The customer sees one experience.

The work itself is one flow with many dependencies.

This is why so many companies feel busy but slow. Each team is working. Each team has dashboards. Each team can defend its own effort.

But no one can explain where the full journey stalls. The org chart tells you who reports to whom. The workflow tells you where performance leaks.

AI as an Operating-Model Stress Test

This is where the Great Flattening gets uncomfortable.

When AI is applied to one task inside a broken flow, the company gets more output without better outcomes.

More content. More reports. More summaries. More dashboards. More "productivity."

But the customer still waits. The proposal still gets rewritten three times. The escalation still bounces between teams. The forecast still depends on five different truths.

McKinsey puts it plainly: value from agentic AI comes from changing workflows, not obsessing over the agent or tool. The starting point is mapping processes, pain points, people, systems, and feedback loops. (McKinsey - One year of agentic AI: Six lessons from the people doing the work)

That is why AI is an operating-model stress test.

It reveals slow handoffs. It reveals unclear decision rights. It reveals duplicate work. It reveals where five teams touch the same issue without shared context. It reveals managers who are coordinating noise instead of improving flow.

What a Flow Actually Is

A flow is not a department. A flow is how value moves.

Lead to opportunity. Brief to campaign live. Customer issue to resolution. Forecast to resource allocation. Invoice to cash. Incident to recovery. Signal to decision to action.

Every flow has the same basic structure:

Trigger: something happens.

Decision: someone or something interprets it.

Action: work moves, escalates, resolves, or stalls.

Feedback: the result teaches the system what to do better next time.

Functions sit inside flows. They do not sit above them.

The org chart organizes functions. The workflow organizes outcomes.

When those two things are misaligned, you get the pattern that is everywhere right now: teams that are individually high-performing and collectively stuck.

What This Means for How You Redesign

Start by mapping flows before moving boxes. Most companies reach for structure too early. Redesign the work first. Then decide whether reporting lines need to change.

Make the handoff the unit of analysis. Most performance loss happens at the boundary between teams - not inside them. AI can surface where handoffs slow, fail, or create rework. That data should drive your redesign.

Attach every AI investment to a named flow. Stop funding tools without flow ownership. Every AI use case should connect to a named workflow, a measurable outcome, a data source, a decision right, and an escalation rule.

Shift manager focus from task supervision to flow stewardship. The manager's job is not to check that tasks are done. It is to ensure the flow is moving, the friction is being removed, the decision rights are clear, and the learning is feeding back into the system.

Three Questions That Come Up Every Time

Does this make managers less important?

No. It makes weak management more visible. The manager's job shifts from supervising tasks to stewarding workflows. Less checkpoint ownership. More friction removal, decision clarity, quality control, and learning loops.

Where should AI sit - IT, operations, marketing, or the business?

AI should sit inside the workflow, with governance around it. The owner of the outcome should own performance. Technology should own standards. Risk should own guardrails. The business should own value.

How do we avoid disconnected pilots?

Stop funding tools without flow ownership. Every AI use case should attach to a named workflow, a measurable outcome, a data source, a decision right, and an escalation rule.

Where Power Moves

Power moves toward the people who can improve outcomes across functions.

HBR recently argued that AI is forcing an organizational reckoning around how decisions get made, especially where consensus slows execution. That is the leadership shift: fewer vague approvals, clearer rights, faster learning.

The leader who owns the flow - who can see where it starts, where it stalls, who decides, what escalates, and how learning loops back into the system - becomes the most valuable person in the organization.

Not the leader with the biggest team. The leader with the clearest flow.

The Org Chart Is Authority. The Flow Is Reality.

The companies that thrive in the Great Flattening will not have the neatest org charts.

They will have the clearest flows.

They will know where work starts, where it stalls, who decides, what escalates, and how learning loops back into the system.

AI does not care about your boxes.

It follows the work.

The leaders who follow it too will build faster, cleaner, more accountable organizations.

Your org chart shows authority. The workflow shows where value moves.

Fix the flow.