Job architecture / title rationalization
Job Family Mapping
Job family mapping organizes every role in the company into families and sub-families of similar work, each with a level structure — turning years of title inflation into one coherent architecture.
It is the skeleton that levelling, pay ranges, career paths and curricula all hang from.
- Problem
- Job architecture / title rationalization
- Altitude
- Enterprise
- Effort to run
- Heavy
- Evidence base
- Established
Theory & origin
Job architecture practice was codified by the big rewards consultancies (Mercer, Korn Ferry, Willis Towers Watson) as organizations discovered that uncontrolled titles make everything downstream impossible: you cannot benchmark pay, design career paths or plan workforce supply when 700 titles describe 180 actual roles. A family groups work of a similar nature (engineering, finance, sales); sub-families sharpen it (software engineering vs. data engineering); levels within each family describe increasing scope and mastery on one consistent scale. The design tension is granularity: too few families and levelling gets crude, too many and the architecture recreates the title chaos it replaced. The output is deliberately role-based — it becomes the input to job profiling, which describes each role the architecture names.
Explore the model
How a consultant runs it
- 01 Inventory the real titles first — the 700-title spreadsheet is the burning-platform slide that funds the work.
- 02 Define families by nature of work, not by department: a data engineer in marketing belongs to engineering, not marketing.
- 03 Keep the family count single-digit and sub-families under ~50; granularity is the enemy of maintenance.
- 04 Level on one consistent scale across families (scope, autonomy, mastery) so cross-family moves and pay comparisons work.
- 05 Map every incumbent to a family/sub-family/level, publish the mapping rules, and stand up governance before the first exception request arrives.
When to use
- 01 Title chaos: benchmarking, levelling or pay equity work is blocked because titles do not describe roles
- 02 Before job evaluation, career pathing or academy design — they all consume the architecture as input
- 03 Post-merger, to reconcile two incompatible title and level systems into one
When not to use
- 01 Companies small enough to know every role by name — architecture overhead beats its value below roughly 150 people
- 02 As a covert re-levelling or pay-cut exercise; the architecture will be blamed for the decisions hidden inside it
- 03 Without governance capacity: an unguarded architecture re-inflates within two promotion cycles
Worked example
A 3,200-person insurer cannot run pay equity analysis: 700 live titles, no levels, "Senior" meaning three different things by department. The mapping lands on 9 families, 42 sub-families and 7 levels; every incumbent is mapped in manager-validated workshops. The inventory finds 61 titles describing 14 actual roles and 40 people levelled above their work. Benchmarking becomes possible for the first time — the pay-equity fix is priced at €1.8m — and the new-title gate cuts title creation by 90%. Job profiling picks up the 180 named roles as its worklist.
Common pitfalls
- 01 Letting departments define their own families, recreating the silo logic the architecture should cut across
- 02 Too many sub-families — granularity feels precise and guarantees the structure is stale in a year
- 03 Mapping people generously instead of roles honestly, baking today’s inflation into the new architecture
- 04 Launching without a title gatekeeper, so the 700-title problem regrows on top of the new skeleton
Sample deliverable
One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.
Input — raw data
- Engineering titles210
- Operations titles180
- Commercial titles140
- Corporate titles95
Process — mapped
Titles are inventoried per area and collapsed into families, sub-families and levelled roles
Architecture build — 700 titles, multifinance group
- 700 titles → 9 families · 42 sub-families
- Duplicates61 titles for 14 roles
- Handoff180 role profiles to write