PostEngineering leadership

Most AI reorganizations are not about speed. They are confessions.

When a company redraws the org chart around AI, it is usually admitting the previous decision model can no longer carry the coordination load. The org chart changes after the operating model has already started failing.

Lukman Nuriakhmetov

1 min read · May 22, 2026

When a company redraws the org chart around AI, it is usually admitting that the previous decision model can no longer carry the coordination load.

I have been through enough restructurings to stop reading them as pure strategy theater. Reorgs happen when the old structure starts leaking too much friction: too many handoffs, too much management drag, too little end-to-end ownership, too many decisions waiting for a meeting. AI just makes that visible faster.

The new tool gets the press release, but the deeper story is almost always organizational. The company is trying to move decision-making closer to the work because the previous shape became too slow, too abstract, or too managerial for the new demands. The org chart changes after the operating model has already started failing.

The interesting question is never "why the reorg?" It is "what stopped working badly enough that they had to admit it?"

Tags: engineering-leadership · org-design · ai-strategy · organizational-change

Explore this topic

Engineering leadership →

Related thinking

NoteAugust 24, 2026

The Model Stopped Being the Interesting Variable

Week of August 17, 2026. Mistral tripled accuracy on financial filings — 26.7% to 86% — by changing how the model searches, not which model searches. Two different models from two different labs got the same roughly threefold lift from the same harness. That pattern ran through the week: authorisation splitting into four separate questions, a token optimisation that cut tokens and raised total cost by half, throughput outgrowing the review capacity around it, and execution moving into shared team channels. The leverage kept turning out to sit outside the model. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

14 min

NoteAugust 17, 2026

The Consequence Detached From the Cause

Week of August 10, 2026. A compromise from March turned out this month to have touched roughly 2,500 organisations — the blast radius took five months to become visible. That gap ran through the whole week: authority outliving the context that granted it, one upstream assumption fanning out across a graph of agents, a fast step producing no faster system, a metric drifting from the thing it measures. The link between an action and its consequence stopped being local. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

14 min

NoteAugust 10, 2026

Capability Outran Confirmation

Week of August 3, 2026. Frontier models generated 6,080 security patches and roughly a quarter of them worked — while a plausible-but-wrong hint in the prompt cut the success rate to one in six, and the agents followed the hint over their own evidence. The same gap opened everywhere: peak capability diverging from production reliability, agents that cannot verify themselves, operational data capping what any model can automate, and portable artifacts carrying no portable trust. Production got cheap. Confirming what was produced did not. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read

14 min