The Manifesto

Most engineering orgs are not optimized for building. They are optimized for legibility.

Legibility to leadership. Legibility to boards. Legibility to whoever needs a dashboard to know whether the company is shipping.

What does "optimized for legibility" mean in practice? It means the structure produces artifacts whose primary purpose is to make the work understandable to people who do not do it. The calibration deck exists so that people who do not read code can rank the people who write it. The values document lives in a Slack channel with nine hundred and eighty members, silent since October, because what mattered was that the document existed, not that anyone referenced it. A director's weekly ask becomes a chief-of-staff's Jira epic becomes a ticket an engineer is expected to pretend matters. The apparatus is not an accident.

The layers are the product.

This was an expensive but defensible structure for most of software's history. Building was genuinely hard. Large teams, long cycles, expensive mistakes. Coordinating that work across a hundred engineers required interpretation layers. Directors translated product strategy into engineering plans. Program managers tracked dependencies across teams. Engineering managers converted individual contributor output into leadership-legible narratives. The tax was real. So was the complexity it managed.

AI changed the cost function. Not eventually. Now. A single person with domain expertise and an AI assistant can ship in a day what a team of eight would have taken a month to produce. That is not a forecast. That is Tuesday.

The pattern shows up everywhere once you start looking. An accountant without coding experience writes the reconciliation tool her team had been asking engineering to schedule for over a year. Someone early in their career ships a long-carried task against a staging branch before the review is on anyone's calendar. No heroics. The tools met people where they were.

When building gets that cheap, coordination becomes the dominant cost. Not compute. Not salaries. The largest line item in your engineering budget is the org chart and the ceremonies that keep it upright.

AI did not create this problem. It made it impossible to ignore.

Legibility is not leadership.

The compressed org is not anti-structure. It is not anti-management. It is not a call for anarchy or solo-founder romanticism. It is a call to notice what the structure is actually doing. Which parts of the apparatus are load-bearing, meaning the parts that produce, move, or protect something a user cares about, and which parts exist because the apparatus produces apparatus. Kill the second kind. Keep the first, and keep it honest.

The structural claim: layers replaced with pairs. Two people at a time, one problem, a week of deep focus, then recomposed against the next. No standing committees. No round-tripped status. The work finds the pair, the pair closes it, the pair dissolves and reforms. Expert Scaler and Slop Cannon. Deep technical judgment and a creative waterfall in the same room, talking.

There is a cost. The compressed org asks something of its practitioners that most orgs currently do not ask, and do not train for.

You give up the script. No playbook tells you what you do at the staff level this year to make principal next year. No leveling rubric tells you how to spend your time. The evidence is what shipped and what it changed. That is a harder game for people who wanted the game to be legible in a different way.

You give up the buffer. Middle management absorbs chaos. It takes leadership's whims and filters them before they hit the engineer. It takes the engineer's frustration and smooths it before it hits leadership. The compressed org expects the practitioner and the funder to talk directly. That requires trust infrastructure the buffer used to generate on both sides' behalf.

You give up deniability. When your work is legible through the system, the system sees your output. It also sees your absence. Nobody gets credit for a story about what they shipped if the telemetry shows nothing ship-shaped arriving.

Leadership does not go away. It changes shape. The job is problem curation and taste. Not translating status. Not managing a Jira board. Knowing which hill matters this week, and matching it to the pair that can take it. A harder job than it sounds, and one that cannot be automated.

The middle was never load-bearing.

Most orgs carry three to five times the coordination the work actually asked for. The compressed org strips it and reinvests in people who ship. Domain experts become builders. Juniors become dangerous. The people who used to sit in status meetings sit in front of a terminal paired with AI, shipping real work. Not because anyone forced them to. Because the tools finally met them where they were.

Not downsizing. Resizing.

The org chart is not the work. It never was.