Every organisation has a second structure—the one that doesn’t appear on the org chart. It’s the real set of rules, roles, and flows that determine who gets things done and where work stalls. Call it the secret operating system.
In a software development organisation of around 200 people, with a core of seven and a network of about twenty key competencies, the gap between the formal chart and this hidden system is often stark. Bottlenecks sit at specific people: work backs up between concept and implementation not because of process, but because the real decision points and influence live in the shadows. Getting this right is crucial when the goal is to build a product—a platform—for an audience of tens of thousands of developers who will use it to build the future of automotive software. If the organisation can’t discover and shape its secret OS, it can’t move fast or align enough to deliver that platform well.
This talk is about how to discover that system, map and use the competency network, align without centralising, and decentralise decisions so the organisation can move. It covers building the right mindset through habits, rewarding the behaviour that strengthens the network, and addressing the behaviour that undermines it—including when and how to escalate. It introduces the taskforce as both a way to find outthe secret OS—by running a small E2E team you see who gets pulled in, where handoffs break, and who the real decision-makers are—and as an operating mode that works inside a highly functional, organised company once you’ve started to shape it. We also show how to foster and grow the network without recreating bottlenecks.
To steer these decisions we use four lenses: Goldratt’s Theory of Constraints (identify the system’s constraint—the bottleneck—then exploit it, subordinate everything else to it, and elevate it); Wardley mapping (context and evolution: what to own, what to buy, where to align), Team Topologies (who works with whom, how teams are shaped), and value stream analysis (where flow stalls and where to assign ownership). Together they turn “the secret OS” from something you stumble into into something you can deliberately shape.
Takeaway: One concrete next step: map one value stream, draw your competency network, or propose one taskforce with a clear mandate. Pick one and start this week.
