Functional Design vs. Business Unit Design — Part I
The AI productivity debate above makes one thing clear: technology doesn't create impact on its own — organizations do. A tool that makes high performers 15% better while making low performers 8% worse isn't a technology problem. It's an organizational design problem. This week, we begin a series on the structural choices that determine whether new capabilities — AI or otherwise — actually translate into results.
Your People Are Too Loyal to You
Those who know me know I've long been passionate about one thing: teaching future leaders and entrepreneurs how to scale a business — from the first hire to five hundred people and beyond. For years I've been studying, living, and preaching what it actually takes to scale effectively. And one of the most critical — and most underestimated — levers is this: how you design your organization has to evolve as your company grows.
This is the first in a series of articles exploring exactly that. We start with one of the most consequential design choices a scaling company faces: functional structure versus business unit structure — and the very real trade-offs that come with each.
The Comfort of Clean Reporting Lines
In organizations where data analysts report to the Head of Data, software engineers report to the Head of IT, and content people report to the Head of Marketing — functional leaders build something that feels like excellence. Deep expertise. Strong standards. A team that knows how to do the work properly.
What they sometimes build instead is a silo with good intentions.
The Org Chart Looks Clean. The Work Doesn't.
There's a satisfying logic to functional reporting. Like reports to like. Expertise compounds. Standards hold.
But the moment a product owner needs to bring a new offer to market — or a strategic initiative leader is tasked with entering a new segment, transforming a customer experience, or driving an enterprise-wide change program — they hit the same uncomfortable truth: the work requires ten functions and they control none of them.
Every capability they need lives behind a functional boundary. Every request becomes a conversation, a queue, a negotiation, a prioritization meeting they weren't invited to.
The product owner is asking permission to use your data analyst. The initiative leader is lobbying three functional heads simultaneously just to stand up a working team. Both are spending energy on access that should be spent on execution.
The product doesn't care about reporting lines. The customer doesn't. The strategic deadline definitely doesn't.
What Actually Happens When Functional Walls Are High
Product owners and initiative leaders are resourceful. When functions are hard to access, they adapt — but not always in ways that serve the organization.
They build informal networks — finding the data analyst who's "helpful" and routing everything through them until that person is quietly drowning.
They hire around the gap — a coordinator here, a junior analyst there — creating shadow capability that duplicates what the function already has.
They lower their ambitions — launching with approximate data, good-enough content, and financial models built on assumptions because the right experts were unavailable when the decision couldn't wait.
They lose weeks — not to the complexity of the work, but to the complexity of getting the right people in the room.
None of this shows up on anyone's KPIs. It just quietly degrades the quality and speed of what the organization produces.
Opening the Aperture
The functional leaders who create the most organizational value aren't the ones who protect their teams. They're the ones who deploy them.
Imagine a product launch where the data analyst is embedded with the product team — direction set by the product owner, quality standards held by the Head of Data. Where the content person executes the launch narrative inside the business unit, with Marketing ensuring brand consistency rather than approving every output. Where engineering, finance, and sales show up as genuine contributors, not vendors processing requests from a distance.
Now imagine a strategic initiative — a new market entry, a digital transformation, a major customer experience overhaul — where the initiative leader can assemble the right cross-functional team without a month of stakeholder negotiations. Where functional leaders actively second their best people into the work, confident that their standards travel with them.
The functional leader's job in both models isn't diminished. It's clarified.
You're no longer managing what your people work on. You're ensuring they're excellent wherever they work — developing their capability, holding their standards, building their careers.
That's a harder job. It's also a more valuable one.
The Real Test of Functional Leadership
Any functional leader can build a great team that reports to them.
The harder test is whether you can build people who are trusted and effective across the organization — inside launches they didn't plan, inside initiatives whose outcomes they don't own, solving problems they didn't define.
If a product owner or initiative leader asked tomorrow to direct your data analyst's priorities for the next six weeks, what would your answer be?
If there's hesitation — it's worth asking honestly whether that hesitation is about quality, or something closer to territory.
A function that can't be deployed isn't a capability. It's a department.
Next in this series: when business units move fast and own everything, the organization gains speed — but starts losing consistency, standards, and the deep expertise that made it great in the first place. That's when functional leadership stops being a constraint and becomes the answer.
More on AI Change Management
- The Flattened Middle Is Carrying Your AI Rollout November 16, 2026
- The Fractional CFO, Rebuilt: What AI Changes for SMBs and the Lower Mid-Market November 16, 2026
- Framing AI for Every Stakeholder: A Change-Management Playbook July 5, 2026
- AI ROI Is Still Unclear — So Adoption Cannot Be Tool-Led June 27, 2026
Get the newsletter in your inbox
A weekly, curated digest on AI and organizational design.