Issue #4 March 29, 2026

Shutdowns, Power Struggles, and the Two-Boss Problem

Editor's Take

This week delivered a dose of reality that the AI industry badly needed. OpenAI killed Sora — its flagship video generator — after it burned $15 million a day while generating just $2.1 million in total revenue. Disney pulled their billion-dollar deal. The compute is being redirected toward robotics. I genuinely liked Sora — the video quality was impressive — but the economics were unsustainable. It's a clean case study in the gap between capability and viability. Google Veo 3.1 is now the leading alternative, alongside Chinese options like Kling, but the broader lesson is that not every impressive demo deserves to be a product. Meanwhile, OpenAI started running ads in ChatGPT — currently recommendation-only, with direct purchasing expected in Q2-Q3 — as the pressure to monetize intensifies.

The agent wars escalated. Anthropic launched Claude Computer Use and Dispatch — letting Claude click, type, scroll, and control your Mac remotely, with tasks fired from your phone. They also shipped Claude Code Channels for Discord and Telegram. The market read it as a direct strike at OpenClaw, and it's hard to argue otherwise. One observer noted: "Claude just killed OpenClaw with this update. You no longer need to buy a Mac Mini." Whether that holds remains to be seen, but the competitive dynamic is now firmly about who owns the persistent agent layer on your machine.

Two other stories deserve attention for what they reveal about the gap between AI ambition and institutional reality. The White House released a national AI policy framework pushing federal preemption of state laws and "light-touch" regulation — but the document reads more like a wish list than a strategy, and it's not clear the authors fully grasp the technical landscape they're trying to govern. And the energy question got real: local moratoriums on data centers are proliferating, 230+ environmental groups asked Congress to halt new builds, and Sam Altman stepped down from Helion's board as OpenAI negotiates to buy 5 gigawatts of fusion power by 2030. The infrastructure demands of AI are no longer theoretical — they're political.

This Week's Essay

Functional Design vs. Business Unit Design — Part II: Dual Reporting

Last week we explored how functional structures create silos with good intentions — and how business units need capabilities they don't control. This week, we look at the design that sits between those two poles: dual reporting. It's the most criticized, most misunderstood, and most necessary structure in modern organizations. Here's why it exists, why it's hard, and what makes it work.

Dual Reporting in Modern Organizations

Why Everyone Has Two Bosses — and How to Make It Work

The End of the Single Boss

In modern enterprises, the idea of having one boss is outdated.

As organizations scale and specialize, a more accurate reality emerges: most professionals have two bosses.

This isn't a flaw — it's intentional design.

Matrix structures exist because companies need both: deep expertise, and cross-functional execution. Research backs this up: most large organizations operate with some form of matrix because it's the only way to manage complexity effectively.

The Rise of Dual Reporting

Dual reporting typically means:

A functional leader (e.g., Head of HR), and a business or execution leader (e.g., BU head, client lead).

It's how organizations combine consistency and scale, with speed and responsiveness.

Andy Grove's Classic Illustration

Andy Grove explained this simply:

A security guard in Singapore reports to the Plant Manager (local execution), and the Head of Security in HQ (standards and expertise).

One ensures things get done. The other ensures they're done right.

This is the essence of dual reporting.

Dual Reporting in Practice

This pattern already exists everywhere:

Client Service Associate (CSA): Head of CSA owns training, standards, career path. Advisors own day-to-day execution.

HR Professional: Head of HR owns policies and expertise. Business Unit Leader owns hiring and performance needs.

The pattern is consistent: Functional = how we do things. Business = what we need to get done.

Why Dual Reporting Exists

Dual reporting solves a core tension:

Specialization and consistency → owned by the functional leader.
Speed, coordination, and outcomes → owned by the business leader.

Without it, you get silos (strong functions, weak execution), or chaos (fast execution, inconsistent quality).

As Galbraith put it: the matrix isn't optional — it's necessary for complexity.

The Reality: Dual Reporting Is Hard

This model works — but it's not easy. Common challenges:

Conflicting priorities (speed vs. rigor). Duplicate work (alignment gaps). Role ambiguity ("who's my real boss?"). Power conflicts (resource and decision tension). Complex evaluations (two dimensions of success).

These are not design flaws — they are tradeoffs.

What Makes Dual Reporting Work

High-performing organizations don't remove the matrix — they discipline it.

Clear decision rights: Who decides vs. who contributes.

Strong governance: Alignment forums, escalation paths, shared planning.

Mature leaders: Influence without authority. Resolve conflict constructively.

Aligned incentives: Reward both quality (functional) and outcomes (business).

The Ideal Model: Clear Separation of Roles

Clarity reduces friction.

Functional Leader Owns: Career path and development. Training and specialization. Standards and centers of excellence.

Business Leader Owns: Day-to-day priorities. Execution and client outcomes. Cross-functional coordination. Incentives and bonuses.

Simple rule: Functional = how. Business = what.

Who Is the "Primary" Boss? It Depends.

The natural question: who is the real boss?

The correct answer: it depends.

There is no fixed primary authority — only a context-driven one.

When Functional Should Lead — when stability matters most: integration and standardization, building scalable processes, compliance and risk control, establishing best practices. Here, the functional leader is the anchor.

When Business Should Lead — when speed matters most: strategic initiatives, fast-changing environments, key client or revenue moments, time-sensitive decisions. Here, the business leader is the integrator.

The Deeper Insight: Authority Is Dynamic

The key is not choosing one boss. It's accepting that authority shifts — by project, by phase, by priority.

This is not separate from dual reporting — this is how dual reporting is supposed to work.

The Cultural Imperative: Normalize Change

The real unlock is cultural.

Most organizations struggle not because of structure — but because change feels disruptive.

High-performing organizations operate differently: re-orgs are normal, not dramatic. Roles are reset quickly. People expect priorities to shift.

As Bartlett & Ghoshal argued: matrix management is not just a structure — it's a mindset.

Nimbleness Without the Cost of Friction

True agility isn't just speed. It's speed without friction.

That requires: a clear "why" behind shifts, shared understanding of the model, and systems that adapt without confusion.

When this works: re-org becomes a tool, not a disruption. Dual reporting becomes a strength, not a burden.

Structure, Flexibility, and Discipline

Dual reporting is often criticized as messy. In reality, it is the natural operating system of modern organizations.

The real question is not: who is the boss?

The better question is: what does the organization need most right now — and who should lead?

Organizations that answer this well achieve: specialization without silos, speed without chaos, scale with adaptability.

For leaders navigating dual reporting: The next time you feel the tension of two bosses pulling in different directions, ask: is this a design flaw, or a design feature that needs better governance? The answer almost always points toward clearer decision rights and more mature leadership — not fewer reporting lines.

Further reading: Steven Sinofsky, "Functional versus Unit Organizations" | Kates & Galbraith, Designing Your Organization (Jossey-Bass, 2007) | Kesler & Kates, Leading Organization Design | Gareth Jones, Organizational Theory, Design, and Change | Bartlett & Ghoshal on matrix management as mindset.

Get the newsletter in your inbox

A weekly, curated digest on AI and organizational design.