Systems thinking is the whole job now
Netflix's CPTO says it's the top skill she hires for. We'd go further: most companies can't think in systems because they can't see their own.
Elizabeth Stone, Netflix's Chief Product and Technology Officer, was asked what skill matters most now. Her answer wasn't a technology. It was systems thinking — the ability to hold the whole interconnected thing in your head rather than being excellent at one isolated piece. She also frames excellence as an operating system: something structural a company runs on, not a personal virtue a few people happen to have.
We'd push that one step further, from the perspective of people who install this machinery inside businesses for a living.
Systems thinking isn't primarily a skill shortage. It's a visibility shortage. You can hire the most capable systems thinker available and drop them into a company where the system is unobservable, and they will do what everyone else does: form a partial mental model from whatever they can see, and optimise their corner of it.
Your org chart is not your system
The org chart is a map of reporting lines. It says almost nothing about how work actually moves.
The real system is the path a refund takes from request to money leaving the account. It's who gets consulted before a pricing exception is granted, and on what basis. It's how an incident escalates at 2am, including the step where someone messages a colleague directly because the official route is too slow.
None of that is in the org chart. Very little of it is in any document. It's distributed across people's heads, and every individual holds a genuine but partial view. The company as a whole knows how it works. No single person does — and no system does either.
That was survivable when execution was human. People are superb at routing around missing documentation: they ask, they infer, they escalate, they learn by getting it wrong once. Institutional knowledge could stay tacit because the executors were the same people who held it.
AI removes the tolerance
Software that can act — rather than just record — has to be told how the company works. It doesn't absorb ambiguity by watching. It can't read the room, ask the person two desks over, or sense that this customer is a special case for reasons nobody wrote down.
This is why so many capable AI deployments underdeliver. The model isn't the limitation. The limitation is that it's operating on a company that has never made itself legible — to software, or frankly to itself.
So the demand for systems thinking is real, but the sequence usually gets inverted. You don't get systems thinking by hiring for it. You get it by making the system visible, at which point a lot of ordinarily capable people start thinking in systems — because they finally can.
Excellence as an operating system
Stone's framing is the useful one. Treat excellence as infrastructure rather than as a set of talented individuals, and it survives people leaving. Treat it as individual virtue and you're re-teaching it to every new joiner, forever, with drift each time.
The practical form of that: a living map of how the company operates — how decisions get made, what the exceptions are, which rule wins when two conflict — maintained as a working artefact rather than a document written once and abandoned. Once that exists, two things become possible that weren't before. People can see the whole. And software can act on it.
Those are the same problem. That's the part we think most companies still haven't clocked: the work of becoming legible to AI is identical to the work of becoming comprehensible to your own team. You were going to have to do it anyway. AI just made it urgent, and put a number on the cost of not having done it.
← All posts