Personas, Journey Maps, and Jobs-to-be-Done

"Walk me through how you'd build a persona" or "tell me about a journey map you've used" are not vocabulary checks. Every candidate who has read one design blog can define both terms. What the interviewer is actually probing is whether you understand these as synthesis tools — instruments that turn a messy pile of interview transcripts, analytics, and support tickets into something a team can act on — and whether you know how each one fails when used carelessly. A candidate who describes a persona as a poster with a stock photo and a made-up name has described the failure mode, not the tool.

The four tools in this subject — personas, journey maps, Jobs-to-be-Done, and service blueprints — get used interchangeably by candidates who haven't actually shipped with them, but they answer genuinely different questions. A persona answers "who." A journey map answers "where in the flow does the problem live." JTBD answers "what progress is this person actually trying to make, independent of who they are." A service blueprint answers "is this even a screen problem, or is it something happening behind the screen." Reaching for the wrong one — proposing a persona workshop when the real ask is "find where users drop off" — is itself a mismatch signal interviewers notice, because it suggests you reach for a familiar tool rather than the one the problem actually calls for.

This is subject three of the UI/UX Design Interview track. It builds directly on user-research-methods — these are the tools you use to synthesize the interviews and behavioral data that subject covers into something decision-ready — and feeds forward into information-architecture-and-navigation (a journey map's identified pain point often turns out to be an IA problem) and design-metrics-and-product-thinking (a JTBD hypothesis is exactly the kind of thing you'd validate against a metric). Wherever a distinction below changes which tool you'd actually reach for on a real project, this subject says so.