Job Architecture 101
What it is, what it is made of, and why organisations break without one.
Ask anything about job architecture
Drawing from 12 Job Architecture guides · 184 pages.
The Architect
Job Architecture
Intelligence
Briefing 01 · Diagnosis
What I’d do
Start with 9 enterprise levels, then flex only where the work genuinely requires it.
Why
Too many levels create false promotion paths, title inflation, and inconsistent pay decisions.
6 sources · High confidence · 3 relevant guides
Nine guides, numbered in reading order. Each one assumes only what the guides before it have covered. Every published guide is a bookmarked PDF you can keep.
What it is, what it is made of, and why organisations break without one.
Every track that exists, and how to choose the four to six you need.
The granularity decision, made with real descriptor language.
The universal criteria model, and how to write descriptors that hold.
The end-to-end process, and the rule that keeps it honest.
Title grammar, inflation control, and governance that holds.
Keeping the architecture alive after the project ends.
How to land it without everyone assuming it is about pay.
What the architecture unlocks once it is actually live.
Starter taxonomies, recommended track sets and the failure modes specific to each kind of organisation. Read the Foundations Series first — the playbooks assume it.
Coverage structures, three lines of defence, and licensed roles.
The dual ladder done properly, and where Product actually lives.
Clinical ladders, credentialing, and the provider split.
Plant hierarchy, skilled trades, and the hourly boundary.
The leverage pyramid and partner-track architecture.
Deal teams, platform operations, and the advisory track.
Minimum viable architecture, and what to defer.
Field and corporate as two different shapes.