Design Determines Power
Why the structure of a system is never neutral — and what that means for organisations trying to grow.
2026-03-10
The System Is Never Neutral
Every organisation is a designed system. The question is rarely whether it was designed — it always was. The question is whether it was designed intentionally.
Revenue processes that were inherited from the previous leadership team. Meeting cadences that reflect who had the most political capital three years ago. Reporting structures that map to the org chart of a company half the current size.
These are design choices. They carry assumptions. And those assumptions determine who has power, who has visibility, and whose work gets counted.
The Hidden Architecture
When we walk into a new engagement, we're rarely looking at the surface layer — the KPIs, the dashboards, the stated strategy. We're looking for the hidden architecture: the implicit rules that govern how decisions actually get made.
These show up in small places. Who gets CC'd on what emails. Which meetings are optional and which are "optional." What gets measured in performance reviews and what doesn't. The gap between the official process and the workaround everyone actually uses.
The hidden architecture is usually more powerful than the stated one.
What This Means for Growth
Here's what we've found: most scaling problems aren't resource problems. They're design problems that have been funded.
Adding headcount to a broken process makes the process faster at producing the wrong outcomes. Building a new sales function on top of a misaligned product-market handoff just creates more friction at higher speed.
Before you scale, you need to understand what you're scaling.
This is the first in a series on systems thinking for founders.