Thinking Tools3.3 Mapping the System Around the ProblemAlso known as 9-Windows, Multi-Screen Operator
Developed by Genrich Altshuller as part of TRIZ (Creativity as an Exact Science, 1979).
A three-by-three grid that places a problem in its past, present, and future at three scales (part, system, and surroundings), exposing constraints and resources usually missed.
A hospital's morning queue at the intake desk, seen through nine windows
The center window is the problem as first stated. Place each other fact in its window, by when it belongs and at what scale; the panel says what that window adds. The corner windows are the ones people skip, and they hold most of the answer here. The first fact is placed as an example. Illustrative.
Items (select one, then a box)
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Not placedPlacedSetting beforeSetting nowSetting to comeThe system beforeThe system nowThe system to comeParts beforeParts nowParts to come
Scale
SurroundingsThe systemParts
Setting before
Setting now
Setting to come
The system before
The system now
The system to come
Parts before
Parts now
Parts to come
PastPresentFuture
Time
25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Not placed yet.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.The system before: How the same job was done before. A past version can hold a solution that was dropped.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.The system now: The problem as first stated. Every other window is read against this one.The problem as stated, and the window most fixes stop at: hire a fifth clerk.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.The system to come: The planned or likely next version of the system.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Parts now: The components of today's system: forms, devices, steps, roles.25-minute queue. Four clerks at the intake desk; a 25-minute wait between 7:45 and 8:30.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Not placed yet.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.The system before: How the same job was done before. A past version can hold a solution that was dropped.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.The system now: The problem as first stated. Every other window is read against this one.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.The system to come: The planned or likely next version of the system.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Parts now: The components of today's system: forms, devices, steps, roles.A part of today's system that doubles the work at the desk.Four-page paper form. Each patient fills in a consent and history form by hand, which a clerk then retypes.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Not placed yet.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.The surroundings set the peak. Opening the garage at 6:45 spreads arrivals.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.The system before: How the same job was done before. A past version can hold a solution that was dropped.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.The system now: The problem as first stated. Every other window is read against this one.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.The system to come: The planned or likely next version of the system.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Parts now: The components of today's system: forms, devices, steps, roles.Garage opens 7:30. The parking garage opens at 7:30, so most patients reach the desk within the same quarter hour.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Not placed yet.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Two wing desks. Before the wings merged, two smaller desks each served half the patients.The system before: How the same job was done before. A past version can hold a solution that was dropped.The old system split the queue. A second check-in point at the far entrance is a cheap option.Two wing desks. Before the wings merged, two smaller desks each served half the patients.The system now: The problem as first stated. Every other window is read against this one.Two wing desks. Before the wings merged, two smaller desks each served half the patients.The system to come: The planned or likely next version of the system.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Parts now: The components of today's system: forms, devices, steps, roles.Two wing desks. Before the wings merged, two smaller desks each served half the patients.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Not placed yet.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.The system before: How the same job was done before. A past version can hold a solution that was dropped.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.The system now: The problem as first stated. Every other window is read against this one.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.The system to come: The planned or likely next version of the system.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Usually skipped, and a resource: the old part moved the form-filling out of the queue. Bring it back as an emailed form.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Parts now: The components of today's system: forms, devices, steps, roles.Forms sent by mail. Until two years ago, forms went out with appointment letters and came back filled in.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Phone booking. The booking office used to space morning appointments ten minutes apart.Not placed yet.Phone booking. The booking office used to space morning appointments ten minutes apart.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Usually skipped, and the cause: since online booking, almost everyone picks 8:00.Phone booking. The booking office used to space morning appointments ten minutes apart.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Phone booking. The booking office used to space morning appointments ten minutes apart.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Phone booking. The booking office used to space morning appointments ten minutes apart.The system before: How the same job was done before. A past version can hold a solution that was dropped.Phone booking. The booking office used to space morning appointments ten minutes apart.The system now: The problem as first stated. Every other window is read against this one.Phone booking. The booking office used to space morning appointments ten minutes apart.The system to come: The planned or likely next version of the system.Phone booking. The booking office used to space morning appointments ten minutes apart.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Phone booking. The booking office used to space morning appointments ten minutes apart.Parts now: The components of today's system: forms, devices, steps, roles.Phone booking. The booking office used to space morning appointments ten minutes apart.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Check-in kiosks. Self-service kiosks are budgeted for next year.Not placed yet.Check-in kiosks. Self-service kiosks are budgeted for next year.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Check-in kiosks. Self-service kiosks are budgeted for next year.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Check-in kiosks. Self-service kiosks are budgeted for next year.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Check-in kiosks. Self-service kiosks are budgeted for next year.The system before: How the same job was done before. A past version can hold a solution that was dropped.Check-in kiosks. Self-service kiosks are budgeted for next year.The system now: The problem as first stated. Every other window is read against this one.Check-in kiosks. Self-service kiosks are budgeted for next year.The system to come: The planned or likely next version of the system.The planned system. On its own it moves the queue from the clerks to the kiosks.Check-in kiosks. Self-service kiosks are budgeted for next year.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Check-in kiosks. Self-service kiosks are budgeted for next year.Parts now: The components of today's system: forms, devices, steps, roles.Check-in kiosks. Self-service kiosks are budgeted for next year.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Not placed yet.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.The system before: How the same job was done before. A past version can hold a solution that was dropped.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.The system now: The problem as first stated. Every other window is read against this one.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.The system to come: The planned or likely next version of the system.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Parts now: The components of today's system: forms, devices, steps, roles.Kiosk ID scan. The kiosks need a readable photo ID, and about one patient in five brings none.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.Usually skipped: a new part brings a new constraint that will fill the clerk line again.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Not placed yet.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Setting before: What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Setting now: What surrounds the system today: buildings, schedules, rules, and other systems it depends on.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Setting to come: What will surround it later. Often skipped: a fix that works today may fail against the coming load.Usually skipped: a fifth clerk is outgrown before the wing opens.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.The system before: How the same job was done before. A past version can hold a solution that was dropped.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.The system now: The problem as first stated. Every other window is read against this one.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.The system to come: The planned or likely next version of the system.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Parts before: The components the old system used. Often skipped: an old part can be a resource to bring back.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Parts now: The components of today's system: forms, devices, steps, roles.New clinic wing. A new wing opens in eighteen months, adding about 30 percent more morning patients.Parts to come: The components the next system will need. Often skipped: a new part can bring a new constraint.
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.
Setting before
What surrounded the system before. Often skipped: a change out here can explain the problem better than anything at the desk.
Setting now
What surrounds the system today: buildings, schedules, rules, and other systems it depends on.
Setting to come
What will surround it later. Often skipped: a fix that works today may fail against the coming load.
The system before
How the same job was done before. A past version can hold a solution that was dropped.
The system now
The problem as first stated. Every other window is read against this one.
The system to come
The planned or likely next version of the system.
Parts before
The components the old system used. Often skipped: an old part can be a resource to bring back.
Parts now
The components of today's system: forms, devices, steps, roles.
Parts to come
The components the next system will need. Often skipped: a new part can bring a new constraint.
The sort
25-minute queue: The system now. The problem as stated, and the window most fixes stop at: hire a fifth clerk.
Four-page paper form: Parts now. A part of today's system that doubles the work at the desk.
Garage opens 7:30: Setting now. The surroundings set the peak. Opening the garage at 6:45 spreads arrivals.
Two wing desks: The system before. The old system split the queue. A second check-in point at the far entrance is a cheap option.
Forms sent by mail: Parts before. Usually skipped, and a resource: the old part moved the form-filling out of the queue. Bring it back as an emailed form.
Phone booking: Setting before. Usually skipped, and the cause: since online booking, almost everyone picks 8:00.
Check-in kiosks: The system to come. The planned system. On its own it moves the queue from the clerks to the kiosks.
Kiosk ID scan: Parts to come. Usually skipped: a new part brings a new constraint that will fill the clerk line again.
New clinic wing: Setting to come. Usually skipped: a fifth clerk is outgrown before the wing opens.
An example
A hospital's patient-intake desk had a 25-minute queue every morning between 7:45 and 8:30, and the request in front of the operations director was a fifth clerk.
She drew nine boxes and put the queue in the middle. Below it went the parts: the four-page paper form patients filled in and a clerk retyped. Above it went the surroundings: the parking garage opened at 7:30, so nearly everyone arrived in the same fifteen minutes. The past column held what had been forgotten. The wings used to have two smaller desks, forms used to go out by mail with the appointment letter, and the booking office had spaced morning slots ten minutes apart until online booking let everyone pick 8:00. The future column held the planned kiosks, which needed a photo ID that one patient in five never brought, and a new wing that would add 30 percent more morning patients.
The fifth clerk came off the list. The plan became staggered online slots, emailed forms, an earlier garage opening, and kiosks with a staffed fallback.
Why it works
Problems arrive framed at one scale and one moment: this desk, this morning. The fixes found there are fixes to this desk, this morning, such as another clerk. The nine windows force two shifts at once. Moving up and down in scale shows the parts the problem is made of and the larger system that shapes it; moving across in time shows how the problem came to be and what it will meet next.
The corner windows matter most because nobody looks there by habit. The past surroundings often hold the cause, a change outside the system that nobody connected to it, and the past parts often hold a resource that was dropped. The future windows show which fixes will be outgrown before they pay off.
The thinking behind it
Genrich Altshuller Genrich Altshuller, an engineer and inventor, built TRIZ, the theory of inventive problem solving, from the study of thousands of patents, and set out the system operator, the nine-screen grid, in Creativity as an Exact Science (1979; English translation 1984). TRIZ holds that technical systems evolve along knowable patterns, so looking at a system's past and future, and at its parts and its surroundings, shows where the next invention is likely to come from and what resources lie unused around the problem.
How to run it
Draw the grid. Three columns for past, present, and future; three rows for parts, the system, and its surroundings.
State the problem in the center. Describe the system today in one line, with the number that makes it a problem.
Fill the parts below it. List the components of the system now: forms, devices, steps, roles.
Fill the surroundings above it. List what the system depends on or sits inside: buildings, schedules, other teams, rules.
Fill the past column. For each row, ask how it was done or what surrounded it before the problem appeared.
Fill the future column. For each row, write what is planned or likely, including the load the system will face.
Read the corners for constraints and resources. Mark each corner window's facts as a cause, a resource to reuse, or a constraint on any fix.
Where it goes wrong
The grid is filled but not read. Nine boxes of notes feel like analysis, and the team goes back to the fix it started with. Finish by writing, for each corner, what it changes about the fix.
The rows are the wrong scale. If the system is drawn too large, the parts row holds whole departments and the surroundings row holds the economy. Pick the system someone can change, and keep each row one step from it.
The past column becomes nostalgia. Old ways are listed as better without asking why they were dropped. Note what each past version cost, so a resource brought back does not bring its old problem with it.
When to use something else
TRIZ. When the problem is a contradiction inside the system, two needs that pull against each other, and a known principle may resolve it.
Iceberg Model. When the problem repeats, and the question is which structure keeps producing it.
Futures Wheel. When the job is tracing the consequences of one coming change outward, ring by ring.