Capability 3 · Company System
Design the Org
One founder redrew his org backwards from the next milestone — bottleneck named, squads owning slices of the user journey, every team traffic-lit — and stopped being the org chart himself.
Founders say
“We just closed the round and I know exactly what we need to build. What I don't know is who we need — I keep sketching org charts on napkins and none of them survives a month.”
Where you are today
- The org grew by accretion — every hire solved last quarter's fire; nobody designed the shape.
- You couldn't say which team is the bottleneck between you and the next milestone.
- Structure changes only happen in a crisis, so every one of them feels like a betrayal.
Where you’re headed
- The org is designed backwards from the next milestone: bottleneck named, structure built around it.
- Three layers, simple and consistent — anyone on the team can draw the org from memory.
- Every team has a traffic light, so you know where the founder dives in next — and where to leave well alone.
You've founded the cult, charted the path and named the next big milestone — now it's time to build the capability to actually get there. And the design question is not the one on the napkin. It's not "what does a proper org look like?" It's: what is the bottleneck for the company? You know where you need to go — the next round, the next milestone — so is the blocker your ability to build, your ability to sell, or your ability to operationally deliver what you promised? Structure around that answer, and keep asking it, because today's bottleneck won't be next period's. The napkin org charts fail precisely because they answer the wrong question: they describe a company shape instead of removing a constraint.
The journey itself is boringly deliberate: founder-led team, then first hires, then two layers of management, then maybe three — each step triggered by need, not fashion. At around thirty people that's C-level, heads-of, employees, with each founder or C-level owning one clear area. The failure mode is cleverness: matrix reporting at 25 people, titles nobody can explain, cross-functional squads before roughly 40 people when the coordination machinery costs more than it returns. If the team can't draw the org from memory, it isn't a structure — it's a diagram. And in the age of AI, be conservative with hiring before you add a layer at all: challenge whether the existing team with better tools closes the gap, because investors are reading the efficiency curve, and adding heads where it's comfortable while the real constraint stays starved is doubly expensive.
Scaling the product org: chapters & squads
Credit: Henrik Kniberg & Anders Ivarsson · Scaling Agile @ Spotify (2012) · Adapted for Outstride OS
My favourite way of scaling product, engineering and design: cross-functional squads that own one slice of the user journey, with chapters keeping each craft consistent across them. Teams grow like cells — one big squad at first, and when it passes about seven people it divides: partially split for a while, then fully. You're never done; the squads keep evolving as the company grows.
The founder is the org's roving repair crew. When a team goes red — say customer support is drowning — you dive in and force it, build the system until it's forming, and leave when it flows without you. In the early years you'll bounce around the org like this constantly. The skill is leaving every team more independent than you found it.
What you can do right now
- Name the bottleneck. Between here and the next milestone: is it your ability to build, to sell, or to deliver what you sold? Write it down — it decides your next two or three hires.
- Traffic-light every team. Green, amber or red on delivery, self-improvement and ability to scale. The board tells you where the founder goes next. Team Traffic Lighting →
- Draw the two-year org on one page. Simple, consistent layers, and one owned area per founder or C-level. If it needs a legend, simplify it.
- Hire for two years out. For each open role, ask whether this person is good for at least the next two years — someone who grows into the role and scales with the team. Senior Hire Process →
The toolkit
Work with Ben
Want help installing this?
Outstride OS is the system behind Ben's founder coaching — pre-seed to Series C. If this page names something you are living right now, start a conversation.