Structure follows work. Inside Scaling Operations, Module II — Redesign — this lesson names a specific move the operator makes when the situation calls for it. The register is institutional: a working understanding of Org design for growth, sized to be reached for in a real conversation, not recited from a slide.
- 01State Org design for growth in the disciplined sense used throughout Scaling Operations, without softening or slogan.
- 02Recognize the situation in which Org design for growth is the right move — and the adjacent situation in which it is the wrong one.
- 03Execute Org design for growth in a live case drawn from your own work or a documented case study, and defend the reasoning in one paragraph.
- 04Connect Org design for growth to designing the system so the ordinary case runs without heroics so it strengthens the practice rather than replacing it.
The mechanism, stated plainly
Structure follows work. Read the sentence twice. It is not a slogan; it is the compressed form of the lesson. The rest of this module returns to it, so the sentence is worth learning by heart. When the operator designs org design for growth, this is what the move actually is — no more, no less.
Where it lives in the operating system
Module II exists because . Org design for growth is one of the operations moves that lives inside that situation. Notice which earlier lessons this one leans on and which later lessons will lean on it — the sequencing is deliberate, and the module reads differently once you place this piece.
How the operator actually runs it
In practice, the operator does not consult Org design for growth the way a novice consults a checklist. The move is trained in until it becomes an available response — something to improves without ceremony when the moment arrives. The mark of understanding is not that you can recite Org design for growth; it is that you catch yourself using it, unprompted, and can explain afterward why you did.
The bureaucrat's misreading, corrected
The most common misreading is to treat Org design for growth as a maneuver you deploy on the other party. It is not. The system runs cleanly when the founder is not in the room — and the professional application of Org design for growth sits inside that criterion, not outside it. When the move is used cynically, the results are short-lived and the reputation cost is high. When it is used cleanly, it compounds.
- Org design for growth is a working move, not a slogan.
- It belongs to Module II — Redesign — because that is the situation it addresses.
- Mastery is unprompted use in the right situation.
- The adjacent lessons in this module are its natural context.
- Used cleanly, Org design for growth compounds; used cynically, it does not.
- Deming, W. E. — Out of the Crisis. — The foundational text on system quality and management responsibility.
- Goldratt, E. — The Goal. — The theory of constraints, taught as a novel about a working plant.
- Womack, J., Jones, D. — Lean Thinking. — The disciplined study of value, flow, and waste.
- 613 — Scaling Operations, Module II: Redesign. The Anabasis Academy. — The parent module. Re-read the module framing after finishing the lesson.