Before your category review rejects an idea as too small, count every person who shares the need behind it.
In May 2013, August de los Reyes was six months into his job as head of design for Xbox when he hurt his back and needed emergency surgery. The spinal injury left him disabled. Back at work and in daily life, he kept running into products and places that didn’t fit him, and he came to see disability as a design problem: a mismatch between a person and the world built around them.
He started pushing Microsoft to design for people like him, and Kat Holmes, a principal design director, took up the idea. Her team studied groups that products usually overlook, such as deaf people and people with dyslexia, and ran design sprints where people with disabilities worked alongside product teams as designers. What the teams learned became Microsoft’s Inclusive Design Toolkit.
The approach also had to answer a business objection: designing for people with a disability can look like designing for a small market. In the US, about 26,000 people a year lose an arm or hand for good. On a category review slide, an idea built for that group looks small, and small ideas often get stopped early.
So the toolkit counts everyone else who shares the same need. About 13 million people can use only one arm for a while, after an injury like a broken wrist. Another 8 million can use only one arm in certain moments, like a parent holding a baby. Together, that comes to more than 21 million people.
The toolkit turns that count into a method any team can use. The method starts with the customer who struggles most, then counts everyone who shares the same need. Innovation teams can use it to choose who tests an idea and to bring the full market size to the keep-or-kill call.
1. Start with the customer who struggles most
In 1980, the World Health Organization described disability as a limit a person has because of a health condition. In 2001, the WHO updated its definition to describe what happens when a person’s body meets the world around them. Microsoft’s toolkit follows the newer definition, so it treats disability as a mismatch between a person and a product, place or situation.
The newer definition changes where a design team looks for problems. Every mismatch becomes something the team can design for, and many of them are temporary or tied to a moment. So the toolkit lists people wearing a cast, ordering dinner in a foreign country, trying to hear in a loud crowd and doing tasks with one hand while holding a baby.
Microsoft’s method starts with the people who face the strongest mismatch every day: people with a permanent disability. Design teams often call this customer the extreme user. When a product serves extreme users poorly, they adapt, sometimes in ways the designers never planned for, and teams find their best insights in those adaptations. Because extreme users live with the problem every day, they can show a team early whether an idea solves it.
2. Map the same need across three groups
Testing with extreme users alone still points to a small market. Microsoft’s Persona Spectrum widens the view: a simple grid that shows one need in three forms, permanent, temporary and situational. The toolkit shows the grid with sample people for four abilities:
Ability | Permanent | Temporary | Situational |
Touch | One arm | Arm injury | New parent holding a baby |
See | Blind | Cataract | Distracted driver |
Hear | Deaf | Ear infection | Bartender |
Speak | Non-verbal | Laryngitis | Heavy accent |
Innovation leaders can run the grid as a short working session with the concept team, before any customer test is done:
The team names the need behind the concept in plain words, such as “can use only one hand,” and puts the extreme user in the permanent column.
The team fills in the temporary and situational columns with people who share the same need for a short time or in certain moments.
The team checks the concept against each column. Because the three groups share one need, a product built for the permanent group should work for the other two. A product designed for someone with one arm, for instance, also works for someone with a wrist injury or a parent holding a baby.
The finished grid also tells the team who to invite into the concept test. A team can imagine how someone in each column would use a product, but the toolkit points out that only the people themselves know what frustrates them or gives them joy. Microsoft’s teams learn this by spending time with the people who have the need. A test group drawn from all three columns, with the extreme user first, gives the keep-or-kill call evidence from everyone the product could serve.
3. Put a number on each group before the review
The grid from step 2 shows who shares a need. A category review also judges an idea on market size, so each column needs a number before the concept goes in front of the business. For upper-limb needs in the US, Microsoft built its count from public sources: the US Census Bureau, the CDC, patient groups such as the Amputee Coalition and the Limbs for Life Foundation, and a university disability statistics center. Innovation teams can size their own columns the same way:
Permanent (26,000 a year): census data, public health data and patient groups give the size of the extreme user group.
Temporary (13 million): injury and illness data give the number of people who have the need for weeks or months each year.
Situational (8 million): this column takes the most judgment, because it counts moments instead of conditions, such as how many people become new parents each year.
At review, the business may doubt a large situational number. Products that already grew from a small group to a mass market help answer that doubt, and the toolkit names two. Closed captions started for people who are hard of hearing and now help travelers in loud airports and parents teaching children to read. High-contrast screens started for people with low vision and now help anyone using a phone in bright sunlight.
Take the numbers and the extreme users’ feedback into the review. Together they answer the two questions the business will ask: how big the market is, and whether the idea works for the people who need it most.
Exercise: the three-column sizing sheet.
Fill in these five lines after the step 2 session, before the concept goes to review. Your business case then shows the full market and where each number comes from.
Need, in plain words: ______
Permanent: who ______ / how many ______ / source ______
Temporary: who ______ / how many ______ / source ______
Situational: who ______ / how many ______ / source ______
A past product that made the same jump: ______

