JOBS TO BE DONE: SWITCHING STORY WORKSHEET Original ShowMeYourSaaS teaching resource | 2026-10-27 Riley and StatusLedger are fictional. No real interview findings are claimed. COMPLETED STORY Situation: Riley prepares a Friday client project review for a small studio. Existing approach: chase colleagues for notes, copy changes into a shared document, and send the update. It is familiar and flexible. Trigger: a client hears about an important risk only after a deadline slips. Desired progress: gather and check unresolved issues before the client call. Alternatives: improve a document template; add a recurring meeting; reuse the current project tool; try StatusLedger. Trial: one internal project with an inspectable output before client-facing use. FORCES MAP Pressure: the late disclosure makes the current preparation process feel risky. Attraction: a process that exposes unresolved questions before the call. Anxiety: colleagues may not maintain another tool; client material needs care. Habit: the document is familiar and easy to edit. These interpretations must be checked in actual research. JOB STATEMENT DRAFT When I prepare a client project review, I want unresolved issues gathered and checked before the call, so I can explain the current state confidently and agree on the next action. The statement leaves room for software, a document, a meeting, or another approach. DIMENSIONS TO CHECK Functional: a checked issue list. Emotional: less uncertainty before the call. Social: being seen as dependable. Do not assign these motives to a real person without evidence. EVIDENCE TABLE Story action: Riley tries an internal project before client use. Interpretation: concern about client-facing quality shapes the trial. Open question: could a clearer document template serve the job? Next test: observe a permitted synthetic review with two proposed approaches. The fictional record does not estimate market size or willingness to pay. BLANK INTERVIEW AND ANALYSIS RECORD Permission and source reference: Recent actual decision to investigate: First awareness of the problem: Trigger that made action worthwhile: Search and alternatives: What the old method did well: New approach considered and why: Anxieties / cost / habits: Decision and first use: What changed after use: Observed actions and permitted quotations: Interpretations, labeled separately: Counterexamples or contradictory evidence: Job statement draft: Functional / emotional / social dimensions to verify: Segment boundary or contextual constraint: Next evidence needed: Decision / owner / review date: NEUTRAL PROMPTS What happened the last time? What did you do next? What alternatives did you consider? What made that option difficult? Why did this become worth addressing then? What nearly stopped you? Avoid introducing your preferred product as the expected answer.