Every design brief describes what the product does. Few describe what people feel before, during and after using it. That gap is why so many products come out functional and lifeless.
The job is never only functional
JTBD splits any job into three dimensions: the functional one (what the person wants to do), the social one (how they want to be seen) and the emotional one (how they want to feel). All three show up together whenever someone hires a product. Leaving the emotional one out doesn't simplify the job, it just measures it wrong.
The most common mistake is treating emotion as a brand topic, irrelevant to product. In practice, it's what decides whether the functional solution will be accepted, tolerated or experienced as embarrassment.
Earned wage access
On paper, earned wage access is simple: getting money the person has already earned a little earlier. Any bank transfer solves the functional part. What decided whether Xerpay's product worked was something else. For whoever asks, an advance carries the weight of admitting financial trouble in front of their employer.
The design challenge was never in the mechanics of the PIX transfer. It was in turning an experience lived as embarrassing into something human, without paternalism and without treating users like children.
Solving that takes understanding shame, exposure and self-image. Nice copy on top of a finished flow can't do it, the whole flow has to come from the emotion the job carries.
What generative AI makes obvious
AI-generated interfaces come out generic because the brief describes function and forgets emotion. The model isn't the problem. Repeating form for function's sake, with no brand thesis or visual semantics, looks like AI because the brief has zero depth.
Visual semantics and brand thesis are the formal translation of a specific emotion you want to trigger in a specific audience. Without that input, any generator, human or model, drifts to the average of what already exists: rounded cards, safe blue, soft shadows. The symptom shows in the visuals. The cause is in the brief.
Where emotion becomes a design decision
Emotion enters the process at concrete points, not as an adjective tossed at the end of the brief.
In JTBD, the emotional dimension gets mapped with the same rigor as the functional one: how the person wants to feel when they finish the task, and what they're afraid of feeling if they fail.
In the brand thesis, the target emotion becomes a formal criterion. Typography, color, motion and tone of voice are justified by it, not by trends.
In the flow, moments of exposure, vulnerability or social judgment get explicit design treatment instead of being left to the copy.
Pleasure or tolerance
Product design that ignores emotion doesn't become more objective, it becomes incomplete and calls itself pragmatic. At Xerpay, the transfer worked from day one. The design work was everything else.
For you, designer: mapping the emotional dimension of the job deserves the same rigor as the functional one. How the person wants to feel at the end of the task is a brief question, not a copy detail.
For you, founder: the functional layer solves what the person needs to do, and the emotional one decides whether they come back. Flat retention often hides an emotional job that hasn't been mapped yet.
For you, tech: the same goes for generative AI prompts. A brief without the emotional layer of the job returns the statistical generic, and the reason is rarely the model, it's the depth of whoever wrote the prompt.
