Personas exist to decide, not to decorate

What it is

A laminated poster in the hallway that no one opens to kill a proposal in the sprint review has already become décor. Personas for decision not display means the artifact earns its keep by taking a side on a live option: which path to keep, which stretch of flow to cut, whose failure to serve first. A persona that cannot change any pending item is a souvenir of research having happened.

Why it happens

Display personas are optimized for circulation: a face, a pull-quote, color blocks that make people feel users have been seen. Decision personas are optimized for action: given two mutually exclusive schemes, they point to which one injures a consequential constraint of that role. Organizations reward the former, because posters can be accepted and shown upstairs; the latter creates conflict, because it demands dropping a line of work. Unless the persona is bound to a pending list, the team screens a slide at the start and continues as planned. Traces of use say more about whether it is still an analytic output than production quality does.

Studying it

Trace citations of the persona in the decision chain: requirements reviews, option trade-offs, scope cuts, launch priority—and whether a citation actually changed an option. Compare “poster, no citation” with “no poster, every trade-off names which role is being served” on whether scope changes can be walked back to a user constraint. Outcomes: count of consequential citations in decision records, number of schemes dropped because of a persona, and whether members can, without the poster, say what that role would veto.

Where it stops holding

Personas in fundraising or recruiting decks are display by design; do not hold them to a research standard of trade-off, and do not re-import them into product decisions. Teaching and workshops may use simplified characters if they are marked as unsafe for scheduling. One persona asked to serve too many opposed decisions becomes agreeable and therefore unable to veto anything; split the role or switch to scenarios. Where regulation or contract has already locked the option space, a persona has no side to take and need not be forced in.

Applying it

• Bind each persona to two or three near-term mutually exclusive choices, and write which side it supports and which it kills.
• Add a review column: “which constraint of which role does this satisfy?” If it cannot be filled, do not wrap the requirement in persona language.
• Posters may exist, but the same role’s veto list must be one click away on the board or in the doc; a picture without a list is unused.
• Archive or rebuild any persona that has not been used to choose or kill a scheme in a quarter; do not keep displaying it as “we know our users.”

Related

• Same group: Q4.03.1 Personas must be built from data, not invented · Q4.03.2 Demographics do not constitute a behavioral difference
• Adjacent: Q4.17 Communicating findings and acting on them · Q4.09 Opportunity ranking
• Search terms: personas for decision not display · persona in critique · decorative persona