The Full Picture
How does it all fit on one grid?

Page 1 The Full Picture

Read the explanation
This deck answers: how does it all fit together? It puts families and levels on one grid, the single picture most people mean when they say job architecture, and shows that every job has one defined place while a cell can hold several jobs. From the grid it shows the three kinds of career moves, a simple formula for consistent titles, how a messy list of titles becomes a short list of clean jobs, when to keep jobs separate, and what information every job carries. It ends with a path-plotting activity, three quick questions, and a recap.
Page 2 Before You Start

Read the explanation
This deck covers the full picture. It is written for someone with no background in HR, compensation, or organization design, and it follows adult learning principles: why before what, one realistic example throughout, practice with answers, a short quiz, and a one-page recap. The example is Brightside Bakery, a made-up company of about 350 people with a bakery plant, twenty shops, a delivery team, and a head office. It grew fast without a plan for its jobs, so it has far more titles than real jobs and no shared way to compare them. The words on this page are defined again where they first appear.
Page 3 The Grid
Illustrative numbers, fictional company
Read the explanation
This grid is what most people picture when they hear job architecture. Families run across the top: Baking, Stores, Logistics, Accounting, and Marketing are five of Brightside's families. Levels run up the side. Each row holds jobs of about the same size, which is why a row can mix tracks: the P3 and M1 row holds Senior Accountant and Assistant Shop Manager. The small label shows the grade Brightside attaches to each row, which is Brightside's pay design choice. Every job has exactly one defined place, so anyone can see its family, its level, and the jobs around it. On this small slice each cell shows one job, but a cell can hold several jobs of the same size. Empty cells are normal. Not every family needs a job at every level, and Brightside has no Logistics job at grade 7 because its logistics team is small. The grid shows only part of Brightside's structure. A full grid would add the other families, such as Quality, Customer Service, IT Support, and People. The jobs and levels are illustrative.
Page 4 One Place per Job, Not One Job per Cell

Read the explanation
It is easy to read a grid and assume each cell holds exactly one job. That is not the rule. The rule is that every standardized job has one defined place in the architecture. A cell is a combination of family or subfamily, career track, and level, and several jobs can appropriately sit in the same cell. Take a larger marketing team than Brightside's. The cell Marketing, Digital Marketing, Professional, P3 could hold an SEO Specialist, a Paid Media Specialist, and a Marketing Automation Specialist. They are different jobs, each with its own code, description, and market match, because the work differs. They share a cell because all three meet P3 scope in the same discipline. The matrix classifies jobs. It does not require every job to occupy a unique cell, and nobody should invent an extra level just to give a job a cell of its own.
Page 5 Career Paths on the Grid

Read the explanation
Once jobs sit on the grid, career paths become visible. A promotion moves up within a family to a bigger job, such as Accountant to Senior Accountant. A lateral move stays on the same row but changes family, such as Lead Dispatcher in Logistics to Shift Lead in Stores. The job is about the same size, but the person builds new skills, and lateral moves often set up the next promotion. A growth move goes up and across at once, such as Shop Associate to Associate Marketing Specialist, usually after the person has built the new know-how. Many companies call this a career lattice rather than a ladder, because people can move in more than one direction. Publishing the grid and the level descriptions lets employees plan these moves themselves.
Page 6 A Title Formula

Read the explanation
A simple formula makes titles consistent: a level word plus the job name. On the Professional track in this example, level 1 uses Associate, level 2 uses no word, level 3 uses Senior, level 4 uses Lead, and level 5 uses Principal. So the Accountant job becomes Associate Accountant, Accountant, Senior Accountant, Lead Accountant, and Principal Accountant as it grows. The Support track reuses Senior and Lead at its levels 3 and 4. Management titles follow their own words: Supervisor or Assistant Manager, Manager, Senior Manager, and Director. The exact words vary by company. What matters is that each word means the same level everywhere, so a Senior in Accounting is the same size as a Senior in Marketing. Keep well-known names where everyone understands them, such as Controller or Head Baker, write the rules down, and apply them to every new job.
Page 7 From Messy to Clear
Illustrative numbers, fictional company
Read the explanation
Title cleanup is one of the most visible results of a job architecture. Brightside's marketing team of about twenty people used 13 different titles, some invented to reward people, some copied from other companies, and some created for one hire. When each role was compared on the work it does and its size, the 13 titles turned out to describe only 5 real jobs: Associate Marketing Specialist at P1, Marketing Specialist at P2, Senior Marketing Specialist at P3, Marketing Manager at M2, and Senior Marketing Manager at M3. Each old title maps to the job whose work it matches, shown here by color. The people and their work do not change, and neither does anyone's pay just because a title changes. When a new title looks like a step down, such as Director of Marketing becoming Senior Marketing Manager, explain it one to one before anything is announced, and show that the job's size and pay range did not shrink. The numbers are illustrative.
Page 8 Standardize Without Erasing Real Differences

Read the explanation
Standardizing does not mean forcing every local title into identical language. It means one job for work that is meaningfully the same. Brightside combined Delivery Driver, Driver, and Route Driver because the work, accountability, and requirements are the same. But some differences are real, and erasing them would make the architecture less accurate. Keep a separate job when accountability differs, as with a Shift Lead who leads a shift hands-on and an Assistant Shop Manager who is accountable for the team. Keep it separate when the labor market differs, as with a Food Scientist and a Quality Specialist, who are hired from different talent pools and priced against different survey jobs. Keep it separate when the regulatory context differs, as with a Food Safety Inspector who holds a certification with legal duties attached. Keep it separate when specialization is real, as with a Recipe Developer compared with a Baker. And keep it separate when the organizational purpose differs, as with a Customer Service Representative in the contact center compared with a Shop Associate, even though both serve customers.
Page 9 What Every Job Carries

Read the explanation
Behind every cell on the grid is a job record, the single source of truth for that job. A complete record carries the title and code, the number of positions mapped to it, the function, family, and subfamily, the career track and level, the grade and its pay range, the overtime status, the job description, the skills the job needs, the career paths into and out of it, and the salary survey jobs it is matched to. Different people use different parts. The HR system and payroll use the code, grade, and overtime status. Recruiters use the title, description, and pay range for job ads. Managers use the level description and career paths in development conversations. The pay team uses the grade and survey matches to keep ranges current. Leaders and analysts use the family and level to report headcount, costs, and pay equity. If the record is incomplete or out of date, every one of those uses inherits the error.
Page 10 Plot the Path

Read the explanation
This activity practices reading career paths on the grid. Maria starts as a Shop Associate at S2 in Stores. Her goal is Marketing Specialist at P2 in Marketing. Trace two different routes on the grid and name each move as a promotion, a lateral move, or a growth move. The model answers are on the next page.
Page 11 Plot the Path: Model Answers

Read the explanation
Model answers. Route one: a promotion to Senior Shop Associate at S3, then a lateral move to Associate Marketing Specialist at P1, which sits on the same row, once she has built some marketing know-how, then a promotion to Marketing Specialist. Route two: a growth move straight from Shop Associate to Associate Marketing Specialist, up one row and across, then a promotion to Marketing Specialist. Route one builds more experience before the switch. Route two is faster but asks her to build marketing skills first. Both are valid, and a good conversation with her manager would help Maria choose.
Page 12 Quick Check

Read the explanation
Three questions on the full picture. Question 1 checks that a cell can hold several jobs as long as each meets its scope. Question 2 checks the name for a same-size move into another family. Question 3 checks the title formula.
Page 13 Remember

Read the explanation
The recap keeps three ideas. The grid puts families across and levels up, and every job has one defined place, while a cell can hold several jobs. Career paths are promotions, lateral moves, and growth moves, all visible on the grid. And titles follow one formula, a level word plus a job name, used the same way everywhere, while real differences keep their own jobs. Quiz answers: 1 is B, several jobs can share a cell when each meets its scope. 2 is B, a lateral move. 3 is B, Senior Accountant.
Page 14 Copyright and Notices
Illustrative numbers, fictional company
Read the explanation
Job Architecture 101: The Full Picture. Copyright 2026 HRDigitalPlayground | Job Architecture. Published September 2026. Brightside Bakery is a fictional company and all examples are illustrative. The material is general education, not legal, tax, or financial advice.