Day 321 of the Daily · Product Management

The Persona Spectrum

5 min read · 4 principles · apply it by lunch

Exclusion isn’t a fact about a person. It’s a fact about the thing somebody built.

The question

Take the last hundred people who started with your product and gave up inside a week: you’ve filed most of them under not interested, but how many were holding a baby, standing in a loud room, squinting at a screen in bright sun or working one-handed on a train — and could anyone on your team tell those two groups apart from the data you keep?

The idea

Kat Holmes was Microsoft’s principal director of inclusive design from 2014 to 2017, and her book Mismatch: How Inclusion Shapes Design, published by MIT Press in 2018, moves the whole subject off the ground most product teams have it on. Exclusion isn’t a property of a person, in her account; it’s a mismatch — a bad fit between a human body and something somebody designed — and the designer is the one who made it. That reframing turns accessibility from a compliance line into a product decision, and it arrives with an instrument attached. The persona spectrum, from the inclusive design toolkit Microsoft published while she was there, takes any ability you’ve quietly assumed and reads it across three populations. Permanent: a person with one arm. Temporary: a person six weeks into a cast. Situational: a parent with a baby on one hip. One mismatch, one fix, three groups — and the first group is much the smallest of the three. The toolkit’s own principle is solve for one, extend to many. Sam Farber watched his wife struggle with a kitchen peeler because of her arthritis, took the problem to the New York design firm Smart Design, and launched OXO Good Grips in 1990. The fat rubber handle was built for arthritic hands and bought by everybody.

In the Daily · 4 principles and a template

The Persona Spectrum is Day 321 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 331 · Product Management

Privacy by Design

Open your signup form and your database side by side, and for every field you ask a new customer to hand over, name the decision your business would make differently if that box came back empty — then, once you’ve been through the lot, how many are left that you’d defend to the person who typed them in? Somebody chose every one of those fields. Very few of them were chosen on purpose.

See the framework →
Day 340 · Product Management

Feature Fatigue

Of the last three things you shipped because a prospect asked for them on a sales call, how many of the customers you already had have opened any of them since? You don’t have to guess — the number is sitting in your analytics this morning, and it’s almost always a good deal lower than the person who asked for it would believe.

See the framework →
Day 349 · Product Management

Technical Debt

Can you name the last release that slipped for no reason anyone could point at, and then name the shortcut — taken months earlier, probably by someone who wrote a ticket about it at the time — that actually made it slip? If the two won’t connect, that doesn’t mean you’re paying no interest. It means you’re paying it without an invoice.

See the framework →
Day 358 · Product Management

The Product Operating Review

If someone stopped you on the way in and asked what your product learnt last month, what you shipped because of it, what that shipping actually moved, and what the whole thing now costs to keep alive — how many of the four could you answer with a number rather than a story?

See the framework →