The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
product, ux & customer framework
Map trigger, first thought, passive looking, active looking, decision and consumption.
quick answer
JTBD Timeline is a journey map swimlane for Customer journey. It turns the decision into named fields, evidence, and a visible jtbd timeline worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Map trigger, first thought, passive looking, active looking, decision and consumption.
Use Customer Journey Map when its output is closer to the conversation you need: Map customer stages, actions, thoughts, emotions, pain points and opportunities.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
A filled example so you can see the shape before applying JTBD Timeline to your own context.
A filled example so you can see the shape before applying JTBD Timeline to your own context.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the journey map swimlane, and explain what decision the output should change.
Apply JTBD Timeline to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the JTBD Timeline structure: - Persona: - stages: - touchpoints/actions: - thoughts/emotions: - pain points: - opportunities: Ask only for missing inputs that would change the output. Then render the journey map swimlane and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the jtbd timeline worksheet / visual makes clearer.
Write the concrete customer journey choice, tradeoff, or conversation the framework should change.
Fill the important slots: Persona, stages, touchpoints/actions, thoughts/emotions.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the jtbd timeline worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use JTBD Timeline as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Map customer stages, actions, thoughts, emotions, pain points and opportunities.
Map user activities, tasks and release slices.
Connect mission, strategy, goals, roadmap and tasks.
faq
Map trigger, first thought, passive looking, active looking, decision and consumption.
Business context; objectives; available evidence; stakeholder judgment
JTBD Timeline worksheet / visual
Use JTBD Timeline when the decision matches this job: Map trigger, first thought, passive looking, active looking, decision and consumption.
Avoid it when you need Customer Journey Map's output instead: Map customer stages, actions, thoughts, emotions, pain points and opportunities.
It is both: a structure for thinking and a visible journey map swimlane that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the jtbd timeline worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use Customer Journey Map when the real output you need is closer to: Map customer stages, actions, thoughts, emotions, pain points and opportunities.
Yes. Describe your context and Ask PL can ask for missing inputs, render the journey map swimlane, and explain what decision it should change.