Anyone can do anything now.
AI has made execution fast and accessible. A single builder can design, build, market and analyse in a single day. And because of that, something unexpected happens: teams produce more, but lose track of what the output is actually for.
For a long time, skill was the constraint. Execution depended on specialists, coordination, and time. That is no longer true.
Once execution becomes abundant, what limits progress doesn’t disappear, it shifts. What limits progress is no longer whether something can be built, but whether the system knows what it’s trying to achieve.
A different way to see it
Take a restaurant.
The Head Chef designs the menu, the kitchen prepares the food, front of house serves it, and management reviews performance at the end of the week. Each part focuses on its role, and together they produce a consistent experience. The system works because it’s built for coordination. When execution is difficult, dividing work across specialists is what makes delivery possible, so the structure itself becomes the solution.
Now imagine the restaurant wants to improve something simple: more guests returning.
That outcome touches everything — food quality, speed of service, attentiveness, atmosphere — but it isn’t defined in a way that makes the outcome visible day to day. So when something slips, no one in the restaurant can locate it clearly, even though everyone is doing their job.
A guest hesitates before ordering dessert because their main meal took too long to arrive. Front of house notices the hesitation, but the kitchen doesn’t see it, and management only recognises the pattern at the end of the week, when it shows up in reviews and a drop in dessert orders. The signal exists, but it’s fragmented across the restaurant, so no one can act on it with confidence.
The restaurant still works, but it slows and stutters because no one can see clearly where things are going wrong. The signals are spread across the floor, the kitchen, and the end-of-week reports, so nothing looks obviously broken, and nothing changes.
Clarity
Clarity starts by making the outcome visible.
In the restaurant, that means one thing: meals arrive within 15 minutes, and satisfaction is tracked daily. Everyone can see it as it happens, so they can respond immediately instead of waiting to stay aligned.
For that to work, two things have to exist at the same time: 1. the outcome must be defined as a contract 2. the restaurant must be able to adjust towards it continuously.
If either is missing, the restaurant can still deliver, but it won’t improve, because there’s nothing concrete to act on.
Seams
In the restaurant, the Head Chef defines the outcome properly: • guests receive their meals within 15 minutes of ordering, • guests are asked about their experience before they leave
This isn’t a goal or an aspiration, it’s a contract, which means it can be measured and, because it can be measured, it can be improved.
The shift isn’t in the wording, it’s in what becomes impossible to ignore once the contract exists. Not as opinions but as signals, hesitation becomes visible, delays become visible, trade-offs become visible.
The kitchen misses the 15-minute mark, so the delay is visible immediately. Front of house sees the consequence: a guest hesitates before ordering dessert and mentions the wait. Management can see both during service instead of piecing it together later.
Roles, in practice
Once the outcome is defined, roles stop being descriptions and start becoming contributions to a shared result. The Head Chef turns belief into something testable. The kitchen adjusts until the outcome holds. Front of house sees where it breaks first, which means the loop begins with them, not management.
A guest mentions the wait felt long, that signal moves back to the kitchen, prep changes, timing tightens, and the next table moves faster. No meeting is required because the system itself carries the signal, and no escalation is needed because the adjustment happens where the problem appears.
What looked like separate roles becomes a continuous loop of observation and response, held together by the visibility of the outcome rather than coordination between people.
How work moves
Once the outcome is clear, the focus shifts from who missed the table to what caused the delay. Orders are taken quickly, which exposes where delays actually occur, and once those delays are visible, the kitchen stops asking who missed the table and starts asking where the delay is coming from.
Prep is reorganised, table flow is adjusted, and each change reveals the next constraint, so improvement becomes continuous rather than something deferred to reviews or retrospectives.
Work no longer moves step by step between people, it moves against the outcome, and because the outcome is visible, progress can be seen and adjusted in real time.
Where AI fits
The restaurant analogy only goes so far, but the same pattern holds: if the outcome isn’t clear, making the system faster doesn’t fix it, it just scales the lack of visibility.
AI only behaves differently when the outcome is defined, because now AI isn’t executing steps, it’s operating against a result. When success is explicit, the system can test, adjust, and improve, not because it’s been instructed to, but because it can see what it’s moving towards.
Nothing about the capability changed. Only the target did. And that’s what makes improvement possible.
The shift
For a long time, companies were designed around execution, so that’s what they learned to manage. Execution is no longer the constraint, but the systems built to manage it haven’t changed so they’re no longer fit for purpose.
What matters now is whether the system can see what it’s trying to achieve.