Compose a narrative modeling exercise translating customer jobs-to-be-done into…
- User
Compose a narrative modeling exercise translating customer jobs-to-be-done into storyboarded UX hypotheses.
Assistant
1. Understand the Goal: The user wants a "narrative modeling exercise" that translates "customer jobs-to-be-done" (JTBD) into "storyboarded UX hypotheses". This means I need to create a scenario, define the user's job, formulate a hypothesis about how a UX solution helps them, and present this as a storyboard narrative.
-
Identify the Core Concepts:
- JTBD: What is the user trying to achieve? (Functional, emotional, social jobs).
- UX Hypothesis: We believe that [building this feature] for [this user] will result in [this outcome].
- Storyboard: A visual sequence of events (described in text here) showing the user's journey from problem to solution.
- Narrative Modeling: Framing this as a structured activity or exercise.
-
Select a Scenario: I need a relatable example.
- Option A: Booking a flight (too generic).
- Option B: Learning a new language (good, but maybe hard to storyboard concisely).
- Option C: Planning a dinner party (relatable, involves multiple steps).
- Option D: Remote team collaboration (timely).
- Decision: Let's go with "The Mid-Week Meal Planner". It appeals to busy professionals trying to eat healthy.
-
Structure the Exercise:
- Phase 1: Discovery (The JTBD): Define the context and the specific jobs.
- Phase 2: The Hypothesis Formulation: Turn the job into a testable statement.
- Phase 3: The Narrative Storyboard: Break it down into frames (panels) describing the action, thought process, and interface interaction.
- Phase 4: Validation Criteria: How do we know it worked?
-
Drafting Content - Phase 1 (JTBD):
- Persona: Alex, a busy project manager.
- Context: It's 6 PM, tired, wants to avoid takeout.
- Job: "Eat a healthy meal without spending mental energy on planning."
-
Drafting Content - Phase 2 (Hypothesis):
- Format: We believe that [creating a 'Pantry-First' recipe suggester] for [Alex] will [reduce decision time by 50% and increase cooking frequency].
- Refinement: Focus on the narrative aspect. "The 5-Minute Chef" app concept.
-
Drafting Content - Phase 3 (The Storyboard):
- Format: Panel Description + User Action + Thought Bubble/Emotion + System Response.
- Frame 1: The Struggle. Fridge open, staring blankly.
- Frame 2: The Trigger. Opens the app.
- Frame 3: The Input. Scanning ingredients (using camera). Crucial UX moment.
- Frame 4: The Magic. AI generates a recipe based only on what's there.
- Frame 5: The Execution. Cooking with confidence.
- Frame 6: The Payoff. Eating and feeling accomplished.
-
Drafting Content - Phase 4 (Validation):
- Metrics: Time on task, retention, "Cooked vs. Ordered" ratio.
-
Review and Refine:
- Does it sound like a "modeling exercise"? Yes, use instructive language (e.g., "Step 1", "Template").
- Is the storyboard descriptive enough? I can't draw, so I must use vivid text descriptions of what the "visual" would look like.
-
Final Polish: Add an introduction explaining why this method is useful (connecting business goals to user needs via narrative). Ensure the tone is professional yet creative. (Self-correction: Make sure to explicitly link the Job to the Hypothesis).
-
Final Output Generation: (This matches the provided good response). This exercise outlines a structured narrative modeling framework. It takes a abstract "Job to be Done" (JTBD) and translates it into a visual, testable narrative—a storyboard—anchored in specific UX hypotheses.
The Scenario: "The Hangry Professional"
Context: A busy project manager, Alex, needs to feed a team of 10 for a lunch meeting in 45 minutes. The Job: "Obtain varied, dietary-compliant food for a group quickly without interrupting the flow of the meeting."
Phase 1: Deconstructing the Job (The Input)
Before drawing, we must break the Job down into its component parts using the Job Stories framework (When [situation], I want [motivation], so that [outcome]).
- Social Anxiety: When I order food for a group, I want to accommodate unknown dietary restrictions without making a scene, so that I look competent and considerate.
- Time Pressure: When I am in a meeting, I want to complete the transaction in under 2 minutes, so that I don't lose the attention of the room.
- Certainty: When I submit the order, I want definitive proof of arrival time, so that I can manage the meeting agenda accordingly.
Phase 2: The Storyboarded UX Hypotheses (The Narrative)
We will now translate these three specific "Job Stories" into a 6-Panel Storyboard. Each panel represents a Hypothesis about how the interface should behave to satisfy the job.
Panel 1: The Trigger (Context & Friction)
Visual: Alex looks at the clock (11:45 AM). The team is debating a roadmap. Alex’s stomach growls; they look stressed. Narrative: "The user realizes the biological and social pressure simultaneously."
UX Hypothesis #1: Contextual Entry Point
- Hypothesis: We believe that exposing a "Group Order" call-to-action on the home screen (rather than burying it in a menu) will reduce the cognitive load of initiating the task.
- KPI: Increase in click-through rate (CTR) on the "Group Order" tile vs. standard search bar.
Panel 2: The Unknown Variable (Information Gathering)
Visual: Alex hovers over a "Add Items" button, pauses, and looks around the room nervously. They wonder, "Is Sarah still Keto? Does Mark eat pork?" Narrative: "The user encounters a blocker: lack of data."
UX Hypothesis #2: The 'Crowdsourced' Cart
- Hypothesis: We believe that implementing a "Share Menu to Chat" feature (generating a deep link to Slack/Teams) will alleviate the burden of the host guessing dietary restrictions.
- KPI: Percentage of Group Orders initiated via shared link vs. manually added items.
Panel 3: The Filter (Decision Paralysis)
Visual: Alex taps the link on their own phone. A simplified view of the restaurant appears. It only shows "Team Favorites" or "Dietary Filter: Gluten-Free." Narrative: "The user seeks to narrow the options to a safe subset."
UX Hypothesis #3: Faceted Navigation
- Hypothesis: We believe that providing "Combined Dietary Filters" (e.g., selecting "Nut Free" AND "Vegetarian" simultaneously) will increase the Add-to-Cart rate for group orders by reducing scrolling time.
- KPI: Time spent on menu page before first item added.
Panel 4: The Assembly (The Building Block)
Visual: A cart view shows 10 items. A small progress bar at the bottom fills up: "Budget used: 100." Narrative: "The user validates the order against constraints (Headcount/Budget)."
UX Hypothesis #4: Constraint Visibility
- Hypothesis: We believe that placing a dynamic "Headcount vs. Item Count" indicator (e.g., "You have 9 items for 10 people") will prevent cart abandonment caused by fear of under-ordering.
- KPI: Reduction in orders where item count != guest count.
Panel 5: The Checkout (Efficiency)
Visual: Alex taps "Checkout." No new screen loads. A bottom sheet slides up. FaceID authenticates payment instantly. Narrative: "The user executes the transaction without losing focus on the meeting."
UX Hypothesis #5: Non-Linear Flow
- Hypothesis: We believe that a Bottom Sheet Checkout (keeping the meeting agenda visible in the background) will feel less intrusive than a full-page redirect, leading to higher perceived ease of use.
- KPI: System Usability Scale (SUS) score specifically regarding the checkout flow.
Panel 6: The Relief (Outcome Validation)
Visual: A map view appears with a pulsing dot representing the driver and a text overlay: "Arriving in 25 mins (before 12:15 PM)." Alex exhales and rejoins the conversation. Narrative: "The user receives the assurance required to switch tasks back to work."
UX Hypothesis #6: Proactive Status
- Hypothesis: We believe that calculating "Time until Eaten" (Driver time + 5 min setup) rather than just "Delivery Time" will reduce support tickets asking "Where is my food?"
- KPI: Reduction in "Status Check" app opens per session.
Summary of the Modeling Exercise
By storyboarding the narrative, we moved from a vague goal ("feed the team") to specific, testable interface interventions:
- The Problem: Social friction regarding dietary restrictions.
- The Solution: A "Share Menu" link generation.
- The Problem: Cognitive load during the meeting.
- The Solution: Bottom sheet UI and budget/headcount auto-calculation.
- The Problem: Anxiety about timing.
- The Solution: "Ready-to-Eat" time estimates.
Next Step: These hypotheses would now be turned into low-fidelity wireframes for rapid usability testing.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.