Most executives treat org structure as an afterthought — something to adjust when things are clearly broken, or something to inherit from a predecessor. Some treat it as a political artifact, drawing lines around the people they want to keep and the ones they want to move along.
Both approaches waste the most powerful structural tool an executive has.
Org structure is not just a reporting chart. It is the architecture of decision rights, information flow, and accountability. Right structure does not make execution automatic. It reduces friction. Wrong structure creates constant friction that no amount of process or off-site bonding can fix.
---
Structure Is Political
Org design is never a clean exercise in boxes and lines. It touches power, status, budget, revenue ownership, founder favorites, legacy teams, and people's sense of identity. A pricing team moved from Product to Revenue is not just a coordination choice; it changes who controls margin, discounting, packaging, and the story told to customers. Expect resistance. Some of it will be self-interested. Some of it will be legitimate operational concern.
Pretending org design is apolitical produces weak designs because the real power structure keeps operating underneath the formal one.
---
What Structure Actually Does
Structure determines five things:
Who owns what decision. Clear ownership is the foundation of accountability. When decisions have no clear owner, they either don't get made or get made by default by whoever is most persistent. Neither is good.
Who has what information. Where information lives determines who can act on it. If critical information about customer issues lives only in one team's silo, the organization will be systematically slow to respond to what customers are actually telling it.
Where coordination happens. Some coordination is planned — scheduled reviews, project rituals. Some is emergent — the hallway conversation, the Slack thread, the lunch. Structure shapes both. If two teams that need to coordinate are in separate reporting chains with no intersecting forum, coordination will either not happen or happen expensively.
Who gets pulled into what. Bad structure creates cross-functional drag — people pulled into initiatives that aren't theirs, decisions that require sign-off from ten people, approvals that bottleneck on a single point. The org chart is the first draft of your coordination cost.
Where accountability lives. When something goes wrong, who is responsible? Not culpable — responsible. The person who should have seen it coming, raised the flag, and course-corrected. Structure determines whether that person exists.
---
The Common Errors
Designing around personalities rather than decisions. The most common org design error is drawing the chart to fit the people you have, rather than designing the chart that the work requires and then figuring out how to staff it. This is backwards. The structure should serve the strategy.
Leaving gaps and overlaps. Where one person's accountabilities end and another's begins is where things fall through — or where two people duplicate effort and get in each other's way. Precision here prevents a lot of pain.
Creating reporting chains that don't match information flow. The classic problem: the person who has the information isn't the person who has the authority to act on it, and there is no forum to connect them. This is a structural failure, not a communication failure. More meetings will not fix it.
Treating structure as one-time design. Organizations change. Strategy evolves. People grow into roles or outgrow them. A structure that made sense eighteen months ago may be actively harmful today. Treating org design as a one-time event rather than an ongoing calibration is a slow bleed.
---
How to Use It Well
The starting point is to make the implicit explicit. Write down, for each major function and for each significant decision type in the organization: who owns this, who has input, who gets decided. Then compare that to what the org chart says. The gaps are where your friction lives.
Example: churn is rising in enterprise accounts. Sales says Product owns feature gaps. Product says Customer Success owns adoption. Customer Success says pricing created bad-fit customers. Finance says retention targets are missed but no one owns the cross-functional fix. If churn matters, someone must own the number, the decision rights, and the forum where pricing, product gaps, support load, and renewal risk get traded off together. Otherwise everyone owns a piece and no one owns the outcome.
When redesigning structure, work from the decisions outward, not the people inward. What decisions does this part of the organization need to make? What information does it need to make those decisions well? Who does it need to coordinate with? The chart is the last thing you draw, not the first.
Watkins's framework in The First 90 Days is useful: understand the existing decision rights map before you change anything. Find where the real authority lives versus where the formal authority is — those are often not the same person.
Also know when not to reorganize. Do not redraw the chart to avoid a performance conversation, to signal motion to the board, to settle a personality conflict, or because strategy is unclear and structure feels more concrete. Reorgs are expensive. If the work is unclear, clarify the work first. If the leader is wrong, change the leader. If the decision rights are fuzzy, fix the decision rights before moving fifty people.
---
The Test
You can tell whether your structure is working without a formal review: watch where coordination happens. If it happens in the hallways and informal channels rather than in the formal forums the chart implies, your structure is not matching how work actually gets done. That's the signal to look harder at the design.
Structure is not the whole answer. But it is the first answer. Get it right and you reduce a category of problems before they form. Get it wrong and you create a category of problems that no amount of good people can fully solve.
