Glossary

The Working Vocabulary

This is not a dictionary. These are claims. The vocabulary is load-bearing, and every term is a wedge, not a description. If a definition here reads like Wikipedia, it failed.

The Force

The Compression: Building software is collapsing in cost. Coordination is not. Whatever existed to make work legible upward now stands exposed as the dominant expense. It is happening now.
Forcing Function: Reality arriving whether you scheduled it or not. Organizations respond to forcing functions or get restructured by the ones that did. AI is the current one on engineering org design.
Malinvestment: The hierarchical instinct to grow scope and headcount without moving revenue, valuation, or user outcomes. In the old org it was invisible. In the compressed org, the exhaust makes it loud.

The Structure

Fire Team: Two people. One pair. The smallest unit that can ship something real without asking permission. An Expert Scaler and a Slop Cannon, deployed across streams, recomposed when the problem changes.
Expert Scaler: Holds the architecture in their head and knows what not to build. Not a manager. Not a reviewer. Pattern recognition earned by breaking systems. Widened by a Slop Cannon who proposes things the Expert Scaler alone would never ask for.
Slop Cannon: Ships rough, fast, in public. A creative waterfall, often from outside engineering or an early-career engineer with subject-matter expertise, unburdened by what the stack supposedly cannot do. The lack of deep technical knowledge is part of what makes them valuable. Paired with an Expert Scaler who keeps the ideas from dying on first contact with production.
10x Engineer: A preview of the fire team. One person who held both halves, taste and velocity, and delivered what the old org could not process. The industry called them anomalies. They were early.
The Compressed Organization: The structural response to a post-AI cost function. Fewer layers. Smaller units. Experts who build. Leaders who curate problems and taste instead of translating status. Not a layoff. A resizing.

The Diseases

Career Ladder: Not a development tool. An organizational self-portrait. It persists because the org needs to see itself, not because it builds people.
Legibility vs Value: Most orgs optimize for being understood by leadership. The compressed org optimizes for being useful to users. These goals compete more often than anyone admits.
Process Theater: Ceremony that produces the appearance of rigor and no change in outcome. Sprint planning nobody follows. Reviews that rubber-stamp decisions already made. The test: if you removed it, would the product be worse?
Calibration Theater: Careers negotiated by people who have never read the engineer's code. A closed room ratifying narratives assembled by managers about work they could not operate.
Inherited Complexity: Process that made sense once, and exists now because removing it would require someone to admit it outlived its purpose. Approval chains from a decade-old incident. Review boards whose members have not deployed in years.
Translation Layer: Anyone whose job is to explain the work to someone who will never do it. Every layer adds latency and loses fidelity. Minimize.
Coordination Overhead: The cost of everyone agreeing on what everyone else is doing. Meetings. Updates. Handoffs. The traditional org calls it the price of doing business. The compressed org calls it the business.

The Mechanics

Minimum Valuable Project (MVaP): The smallest shape of work that delivers real user value. Not the smallest thing that can ship. The smallest thing worth shipping. An Expert Scaler and a Slop Cannon orient every pairing around finding it and delivering it before the calendar runs out.
Structured Exhaust: What a fire team leaves behind when it ships. Measurable signals of value created, captured in fields the business can evaluate. Replaces the middle manager's subjective interpretation of who contributed what.
Domain Expert as Builder: The compliance analyst writes the compliance tool. The trader builds the trading interface. The translation layer between 'knows the problem' and 'ships the solution' collapses when the model generates code the domain expert could always describe.