← Back to Concept Contrast

Concept Contrast Fable

Jobs to be done and user personas: one asks what to do, the other asks who does it

Conclusion first:When doing product planning, jobs to be done and user personas are often put on the same slide and discussed together. The core of JTBD is what task the user wants to complete and in what situation; the core of a persona is what characteristics, preferences and constraints the person doing this has. Mixing the two types of information can make the product right for a type of person but wrong for the task.

When doing product planning, jobs to be done and user personas are often put on the same slide and discussed together. The core of JTBD is what task the user wants to complete and in what situation; the core of a persona is what characteristics, preferences and constraints the person doing this has. Mixing the two types of information can make the product right for a type of person but wrong for the task.

Fable

The bridge crew’s two notebooks

Villages on both sides of the river hired a bridge crew to build a bridge. Before starting, the crew did two surveys. The first recorded the real reasons people crossed the river: going to market, taking children to school, hauling grain to the mill, going to the clinic on the opposite bank during rainstorms. Each reason noted the time, frequency, and how people currently made do. The second recorded the age, income, means of transport, and literacy rate of the people crossing.

When the team lead handed the two sets of notes to the design group, he casually said, "They're all user needs, look at them together." So the design group drew a scenic bridge with an elevator, because the second set of notes said there were many young people, they liked taking photos, and they were willing to pay for aesthetics. The bridge was built beautifully and became a popular spot that needed improvement.

A month after the bridge opened, the village filed a joint complaint. The landscape bridge's steps were too steep—elderly people carrying grain simply couldn't get up them. An elevator was installed, but it only ran during peak tourist season and was locked in the off-season to save power. The flatbed carts for hauling grain were wider than the gap between the steps, so every crossing required splitting the grain into small bundles and making three trips back and forth. The scene written in the first note—'taking children to school on a stormy day'—had never been considered on the landscape bridge.

The work crew went back through their notes and only then discovered the problem. In the first set of notes, the task "transporting grain" had five sub-conditions: load-bearing, uphill, different surfaces in sunny and rainy weather, a fixed time window, and the need for two people to coordinate. In the second set of notes, "young people like taking photos" was a description of part of the people, but it was almost irrelevant to the task of "transporting grain"—young people did not transport grain, and the people transporting grain did not care about taking photos.

When they rebuilt the bridge the second time, the crew set new rules: first list tasks according to JTBD, writing clearly for each task the scenario, constraints, and success criteria; then treat user personas as additional conditions for each task, such as "the primary executor of this task is a woman over fifty, carrying an average load of forty jin." Tasks select the architecture; personas adjust the parameters.

The new bridge used a gentle slope design, with anti-slip paving and a rest platform in the middle. It was less pretty, but grain carriers could push their carts across in fifteen minutes. Fewer young people came to take photos, but the flow of market-goers across the river increased sixfold. The work crew later wrote this rule into their quotes: charge by the number of tasks, and let the portrait affect only the coefficient on the unit price.

Later, someone asked why they did not add a freight passage to the first bridge. The crew's answer was direct: once the main structure of a bridge is set, adding more is just applying a patch. If the task and the profile are mixed up at the blueprint stage, what gets built is a bridge that looks good on the surface but never solved the river-crossing problem.

Tasks to be completed

The task a user wants to complete or the progress they want to make in a certain situation; the focus is on "what to do," and it is the root of functional requirements.

User profile

A generalized description of the target user group's characteristics, behaviors, preferences, and constraints, focused on "who does it," used to tune details rather than determine the main storyline.

Story Mapping

  • The first note recorded the reason for crossing the river and the scenario: JTBD, focused on task, time, and constraints
  • The second note records age, income, and preferences: user profile, focusing on the executor's characteristics
  • A landscape bridge built to the persona but unable to carry grain: a classic failure of persona-driven design that ignores the task
  • Structure by task, tune parameters by profile: JTBD determines the main architecture, profiles fine-tune it

Applying it to an Agent project

When planning Agent features for Andy Ren Xu, first use JTBD to clarify in which scenarios users want the Agent to accomplish what, and what success and failure look like for that task. Then bring in user personas and ask: how do the people completing this task differ in technical familiarity, time budget and collaboration style? These differences only affect interaction details, not the core task logic.

京ICP备2026014272号