What breaks first when a startup scales headcount before process.

A founder-led company that scales headcount quickly after a funding round almost always hits the same wall, and it's rarely the process documentation everyone assumes is missing. It's decision rights.

Here's the shape of it: the org chart says a department head now owns pricing exceptions, or hiring approvals, or vendor selection. In practice, everyone -- including the department head -- still routes the actual decision through the founder, because that's how it worked when the company was ten people and it never got explicitly renegotiated when the company became sixty. The new manager has the title and the reporting line, but not the decision, and everyone quietly knows it.

This doesn't look like a crisis. It looks like slowness. Decisions queue up waiting for the one person who's now approving things across a dozen departments instead of three. New managers get quietly undermined -- their team learns to route around them for anything that matters, which then reads to leadership as "this hire isn't stepping up," when the real problem is that stepping up was never actually made possible.

The org chart is a hiring plan, not a decision-rights transfer. Redrawing the boxes doesn't move the authority; only an explicit conversation about who decides what, and a founder actually letting a wrong-but-reasonable decision stand without overriding it, does that. This is exactly the gap our Target Operating Model work is built to catch in a growth-stage engagement -- not just documenting who reports to whom, but confirming whether the authority implied by that reporting line has actually been exercised, or just assumed.

The practical test: pick five decisions your org chart says a given manager owns, and ask them honestly whether they've made each of those decisions unilaterally in the last month, or routed it up first "just to check." If it's mostly the second, your structure scaled faster than your decision rights did -- and that's a fixable, specific problem, not a vague culture issue.