The three shapes. Inside Departmental Design, Module I — Design — this lesson names a specific move the operating principal makes when the situation calls for it. The register is institutional: a working understanding of Functional vs. product vs. matrix, sized to be reached for in a real conversation, not recited from a slide.
- 01State Functional vs. product vs. matrix in the disciplined sense used throughout Departmental Design, without softening or slogan.
- 02Recognize the situation in which Functional vs. product vs. matrix is the right move — and the adjacent situation in which it is the wrong one.
- 03Execute Functional vs. product vs. matrix in a live case drawn from your own work or a documented case study, and defend the reasoning in one paragraph.
- 04Connect Functional vs. product vs. matrix to adding people, geographies, and lines of business without hollowing the institution so it strengthens the practice rather than replacing it.
The move, stated plainly
The three shapes. 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 operating principal hires functional vs. product vs. matrix, this is what the move actually is — no more, no less.
Where it lives in the growth curve
Module I exists because . Functional vs. product vs. matrix is one of the scaling 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 executes it
In practice, the operating principal does not consult Functional vs. product vs. matrix the way a novice consults a checklist. The move is trained in until it becomes an available response — something to delegates without ceremony when the moment arrives. The mark of understanding is not that you can recite Functional vs. product vs. matrix; it is that you catch yourself using it, unprompted, and can explain afterward why you did.
The empire-builder's misreading, corrected
The most common misreading is to treat Functional vs. product vs. matrix as a maneuver you deploy on the other party. It is not. The institution scales without diluting the standards that made it worth scaling — and the professional application of Functional vs. product vs. matrix 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.
- Functional vs. product vs. matrix is a working move, not a slogan.
- It belongs to Module I — Design — 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, Functional vs. product vs. matrix compounds; used cynically, it does not.
- Sull, D. — Simple Rules for a Complex World. — The disciplined study of scaling decision rules.
- Ghemawat, P. — Redefining Global Strategy. — The canonical treatment of cross-border expansion.
- Bloomberg, M., Winkler, M. — Bloomberg by Bloomberg. — A working founder's account of scaling an institution.
- 1003 — Departmental Design, Module I: Design. The Anabasis Academy. — The parent module. Re-read the module framing after finishing the lesson.