From George A. Miller (The Magical Number Seven, Plus or Minus Two, 1956), extended by William G. Chase and Herbert A. Simon (1973) and Nelson Cowan (2001).
Groups many details into a few labeled units, nested where needed, so whatever a reader or learner must hold at once fits in working memory.
Nine loose onboarding facts, regrouped into four units a new hire can hold
A new dispatcher's welcome email listed every fact in one run. Place each fact in the unit it belongs to, grouped by two things she already knows: when she needs it, and whether it is about tools or people. Nine items to hold become four names, each opening onto two or three. The first fact is placed as an example. Illustrative.
Items (select one, then a box)
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
Not placedPlacedDay-one setupWho you meet firstSystems to learnHow the team works
What it is about
Tools, systemsPeople, routines
Day-one setup
Systems to learn
Who you meet first
How the team works
First weekFirst month
When she needs it
Laptop at reception. Collect the laptop from reception before 9 on day one.Not placed yet.Laptop at reception. Collect the laptop from reception before 9 on day one.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Something to pick up on the first morning: setup.Laptop at reception. Collect the laptop from reception before 9 on day one.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.Laptop at reception. Collect the laptop from reception before 9 on day one.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Laptop at reception. Collect the laptop from reception before 9 on day one.How the team works: One unit: the meetings and approvals that run every week once she is on her own.Badge photo by 10. Security takes badge photos until 10 on Mondays.Not placed yet.Badge photo by 10. Security takes badge photos until 10 on Mondays.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.First-morning setup, with a deadline attached.Badge photo by 10. Security takes badge photos until 10 on Mondays.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.Badge photo by 10. Security takes badge photos until 10 on Mondays.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Badge photo by 10. Security takes badge photos until 10 on Mondays.How the team works: One unit: the meetings and approvals that run every week once she is on her own.Two-step sign-in. Install the sign-in app on her phone before logging in.Not placed yet.Two-step sign-in. Install the sign-in app on her phone before logging in.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Nothing else works until it is done: setup.Two-step sign-in. Install the sign-in app on her phone before logging in.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.Two-step sign-in. Install the sign-in app on her phone before logging in.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Two-step sign-in. Install the sign-in app on her phone before logging in.How the team works: One unit: the meetings and approvals that run every week once she is on her own.Lunch with her buddy. Tuesday lunch with the dispatcher assigned as her buddy.Not placed yet.Lunch with her buddy. Tuesday lunch with the dispatcher assigned as her buddy.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Lunch with her buddy. Tuesday lunch with the dispatcher assigned as her buddy.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.A person on the first week's calendar.Lunch with her buddy. Tuesday lunch with the dispatcher assigned as her buddy.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Lunch with her buddy. Tuesday lunch with the dispatcher assigned as her buddy.How the team works: One unit: the meetings and approvals that run every week once she is on her own.Shadow night shift. Thursday evening alongside the night dispatcher.Not placed yet.Shadow night shift. Thursday evening alongside the night dispatcher.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Shadow night shift. Thursday evening alongside the night dispatcher.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.A person to meet in week one, and a routine she sees once before she runs it.Shadow night shift. Thursday evening alongside the night dispatcher.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Shadow night shift. Thursday evening alongside the night dispatcher.How the team works: One unit: the meetings and approvals that run every week once she is on her own.The routing software. Three online lessons on the routing screen, due by the end of the month.Not placed yet.The routing software. Three online lessons on the routing screen, due by the end of the month.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.The routing software. Three online lessons on the routing screen, due by the end of the month.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.The routing software. Three online lessons on the routing screen, due by the end of the month.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.A system she grows into: the lessons run across the month.The routing software. Three online lessons on the routing screen, due by the end of the month.How the team works: One unit: the meetings and approvals that run every week once she is on her own.Escalation runbook. The guide to which faults go to which on-call engineer.Not placed yet.Escalation runbook. The guide to which faults go to which on-call engineer.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Escalation runbook. The guide to which faults go to which on-call engineer.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.Escalation runbook. The guide to which faults go to which on-call engineer.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Reference she learns by using, over the month.Escalation runbook. The guide to which faults go to which on-call engineer.How the team works: One unit: the meetings and approvals that run every week once she is on her own.The Monday huddle. Fifteen minutes at 8 every Monday to set the week's priorities.Not placed yet.The Monday huddle. Fifteen minutes at 8 every Monday to set the week's priorities.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.The Monday huddle. Fifteen minutes at 8 every Monday to set the week's priorities.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.The Monday huddle. Fifteen minutes at 8 every Monday to set the week's priorities.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.The Monday huddle. Fifteen minutes at 8 every Monday to set the week's priorities.How the team works: One unit: the meetings and approvals that run every week once she is on her own.A standing routine once she is on her own.Who approves overtime. The shift lead approves overtime; the manager only above ten hours.Not placed yet.Who approves overtime. The shift lead approves overtime; the manager only above ten hours.Day-one setup: One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.Who approves overtime. The shift lead approves overtime; the manager only above ten hours.Who you meet first: One unit: the people on her calendar in week one, in the order she meets them.Who approves overtime. The shift lead approves overtime; the manager only above ten hours.Systems to learn: One unit: the software and the runbook she grows into over the month, not on day one.Who approves overtime. The shift lead approves overtime; the manager only above ten hours.How the team works: One unit: the meetings and approvals that run every week once she is on her own.How the team works week to week, not a first-day fact.
Your sort matched 0 of 9.Your sort matched 1 of 9.Your sort matched 2 of 9.Your sort matched 3 of 9.Your sort matched 4 of 9.Your sort matched 5 of 9.Your sort matched 6 of 9.Your sort matched 7 of 9.Your sort matched 8 of 9.Your sort matched 9 of 9.
Day-one setup
One unit: the things to collect and switch on before the first shift. Remember the name, and the three come with it.
Who you meet first
One unit: the people on her calendar in week one, in the order she meets them.
Systems to learn
One unit: the software and the runbook she grows into over the month, not on day one.
How the team works
One unit: the meetings and approvals that run every week once she is on her own.
The sort
Laptop at reception: Day-one setup. Something to pick up on the first morning: setup.
Badge photo by 10: Day-one setup. First-morning setup, with a deadline attached.
Two-step sign-in: Day-one setup. Nothing else works until it is done: setup.
Lunch with her buddy: Who you meet first. A person on the first week's calendar.
Shadow night shift: Who you meet first. A person to meet in week one, and a routine she sees once before she runs it.
The routing software: Systems to learn. A system she grows into: the lessons run across the month.
Escalation runbook: Systems to learn. Reference she learns by using, over the month.
The Monday huddle: How the team works. A standing routine once she is on her own.
Who approves overtime: How the team works. How the team works week to week, not a first-day fact.
An example
A utility's dispatch center sent every new hire a welcome email with twenty separate items: where to collect the laptop, when badge photos stop, who to have lunch with, which lessons to finish, who approves overtime. Each line was clear. New dispatchers still arrived without a badge and asked the same questions for weeks, and the training lead counted nineteen repeat questions from the last three hires.
She rebuilt the email around four headings: day-one setup, who you meet first, systems to learn, and how the team works. Each held four to six items, and each heading answered a question a new person already asks: what do I need this morning, and who will I see? Inside the setup unit, the items ran in the order she would do them. The next two hires asked six repeat questions between them, and both had badges by ten.
Why it works
Working memory is small. People hold only a handful of separate things at once, and the limit counts units, not facts: a familiar group of items costs about as much to hold as one item. That is why a phone number is remembered in three parts and a chess master can recall a whole board.
Chunking uses that rule on purpose. Grouping details into a few named units, each built on something the audience already knows, lets them hold the names and open each one when needed. A list of twenty asks for twenty slots; four named groups of five ask for four, and the label brings back the rest. The material does not shrink. What the audience must carry at one moment does.
The thinking behind it
George A. Miller George A. Miller, a founder of cognitive psychology, observed in his 1956 paper on the magical number seven, in Psychological Review, that people hold about seven items in immediate memory, and that the limit is counted in chunks, meaningful units, not in raw bits of information. Recoding information into larger chunks therefore extends what can be held. Miller treated seven as a rough figure, and later work put it lower.
William G. Chase William G. Chase and Herbert A. Simon, in Perception in Chess (1973), found that chess masters recalled real game positions far better than novices but lost the advantage on positions set at random. Their explanation was that expertise rests on a large store of familiar patterns, each recalled as one chunk, which is why groups built on what an audience already knows work best.
Nelson Cowan Nelson Cowan, a working memory researcher at the University of Missouri, argued in The Magical Number 4 in Short-Term Memory (2001) that once rehearsal and chunking are controlled for, people hold about four chunks at once, well below Miller's seven. The difference matters in practice. For anyone designing a deck, a course, or a handover, four is the safer number of top-level groups, with more detail inside each.
How to run it
Count what must be held at once. List every separate item the audience needs at the same moment, not everything in the material.
Find what they already know. Look for categories, sequences, or questions in the audience's head that the items can hang on.
Group the items. Aim for four to seven items a group, and move an item that fits two groups to the one where it will be used.
Name each group plainly. Use a label that predicts its contents, so the name alone brings back what sits under it.
Order inside each group. Put items in the order they will be done or met, which adds a second cue to the label.
Nest until the top fits. If there are more than about four top-level groups, group the groups.
Test on a newcomer. Ask someone new to recall the structure the next day; the groups they forget need a better name or a different home.
Where it goes wrong
The groups follow the author's logic. A handover organized by department or by system makes sense to the person who built it and to no one arriving. Group by questions the audience already asks.
The labels are vague. Headings such as general information or other items hold anything, so they cue nothing. If a reader cannot guess what sits under a heading, rename it.
Everything gets chunked, including what needs no holding. Reference material that people look up when needed only gets heavier with layers. Chunk what must be held in mind at one moment, and leave the rest searchable.
When to use something else
Pyramid Principle. When the material is an argument, and the groups must each support one point at the top.
Mind Mapping. When the structure is still being found, and the job is getting everything out before grouping it.
Affinity Diagram. When a team has a pile of notes and the groups have to emerge from the notes themselves.
Where it sits in SOLVE eX
Any step: Tools that serve every step: habits of thought and checks on the thinking itself.
Go to the source
The Magical Number Seven, Plus or Minus Two, Psychological Review, 1956
Perception in Chess, Cognitive Psychology, 1973
The Magical Number 4 in Short-Term Memory, Behavioral and Brain Sciences, 2001