Something went wrong!
Hang in there while we get back on track
Transform Customer Interview Quote
Converts a raw customer quote about daily workflow struggles into a properly structured JTBD statement with analysis explaining construction choices, mistakes avoided, and validation tips.
Input
What you provide to the skill
I spend 30 minutes every morning figuring out what my team is working on before I can start planning.
Output
What the skill generates for you
═══════════════════════════════════════════════════════════════════
JOBS-TO-BE-DONE STATEMENT
═══════════════════════════════════════════════════════════════════
When: A manager starts their workday and needs to understand team activity before planning their own work
I want to: Quickly assess what each team member is currently working on
So I can: Begin strategic planning and decision-making without wasting time on information gathering
═══════════════════════════════════════════════════════════════════
ANALYSIS OF STATEMENT CONSTRUCTION
═══════════════════════════════════════════════════════════════════
✅ SITUATION IDENTIFIED: “starts their workday and needs to understand team activity before planning”
- Captured the recurring daily trigger: beginning of workday
- Identified the dependency: planning requires team visibility first
- Made specific but applicable to any similar situation
✅ MOTIVATION EXTRACTED: “Quickly assess what each team member is currently working on”
- Used strong verb: “assess” implies evaluation and comprehension
- Made specific: “each team member” and “currently working on”
- Removed timeframe (“30 minutes”) from motivation - that’s a pain point, not the job
- Avoided solution language (no mention of specific tools or systems)
✅ DESIRED OUTCOME DEFINED: “Begin strategic planning and decision-making without wasting time on information gathering”
- Real outcome isn’t just “knowing” - it’s being able to start planning work
- Quantified the pain: “30 minutes” becomes “without wasting time”
- Clear “done” state: Can begin planning activities
- Distinct from motivation: assessing status ≠ making planning decisions
═══════════════════════════════════════════════════════════════════
COMMON MISTAKES AVOIDED
═══════════════════════════════════════════════════════════════════
❌ SOLUTION LANGUAGE
Pain point involves: “check Jira, then Slack, then ask people”
Problem: These are current solutions/workarounds. The job exists regardless.
Fix: Focused on underlying need - quick team activity assessment
❌ TIME-SPECIFIC TRIGGER
Could have written: “When 30 minutes have passed every morning”
Problem: The “30 minutes” is the pain, not the job trigger
Fix: Trigger is “starts workday needing team visibility”
❌ WEAK OUTCOME
Could have written: “so I can know what’s happening”
Problem: “Knowing” isn’t a measurable outcome. What do you do with that knowledge?
Fix: Real outcome is being able to start planning without delay
═══════════════════════════════════════════════════════════════════
VALIDATION TIPS
═══════════════════════════════════════════════════════════════════
Test this statement by asking:
-
Does this job exist even if current tools didn’t exist?
✅ Yes - managers have always needed team visibility before planning -
Is the outcome measurable?
✅ Yes - can measure time spent gathering information vs. time to start planning -
Could this statement inspire multiple different solutions?
✅ Yes - unified dashboard, automated status summaries, AI digests,
standardized update formats, async video updates, visual team boards, etc.
═══════════════════════════════════════════════════════════════════
ALTERNATIVE PHRASINGS
═══════════════════════════════════════════════════════════════════
MORE SPECIFIC VERSION (narrower scope):
“When a manager begins daily planning with multiple direct reports working on interdependent tasks, I want to identify potential blockers or conflicts in their work, so I can proactively address coordination issues before they cause delays”
MORE GENERAL VERSION (broader scope):
“When a leader needs to allocate their attention across multiple responsibilities, I want to understand current team status without manual investigation, so I can focus my time on high-value activities rather than information gathering”
CONFIDENCE LEVEL: High (85%)
About This Skill
Transform customer interviews, pain points, and vague needs into properly structured Jobs-to-be-Done statements with quality validation and educational explanations.
View Skill DetailsMore Examples
Analyze and Fix Flawed JTBD Statement
Analyzes an existing poorly-formed JTBD statement, identifies all critical issues (circular logic, solution language, vague outcome), provides a corrected version, and explains why features built from the original likely failed.
Transform Vague Workshop Outputs
Takes multiple vague workshop outputs from operations managers and transforms each into structured JTBD statements, identifying which are solution-focused vs job-focused, with confidence levels and next steps.