Transform Vague Workshop Outputs

═══════════════════════════════════════════════════════════════════
JTBD STATEMENT TRANSFORMATION
═══════════════════════════════════════════════════════════════════
Context: B2B tool, Operations Managers

───────────────────────────────────────────────────────────────────

1. “Want faster reports” → SOLUTION-FOCUSED, NEEDS CLARIFICATION
   ───────────────────────────────────────────────────────────────────

⚠️ PROBLEM: “Faster reports” is a solution characteristic, not a job.

QUESTIONS TO CLARIFY THE JOB:

• Why do they need reports faster?
• What decision are they trying to make?
• What happens when reports are slow?

POSSIBLE JTBD STATEMENT (pending validation):
“When an operations manager needs to present performance data to leadership,
I want to generate accurate status summaries quickly, so I can meet reporting
deadlines without last-minute scrambling”

CONFIDENCE LEVEL: Medium (60%)

───────────────────────────────────────────────────────────────────
2. “Need better collaboration” → TOO VAGUE, MULTIPLE JOBS LIKELY
───────────────────────────────────────────────────────────────────

⚠️ PROBLEM: “Collaboration” is extremely broad.

POSSIBLE UNDERLYING JOBS:

JOB A - Information sharing:
“When a team member needs to communicate operational changes, I want to share
updates with all affected parties simultaneously, so I can ensure everyone has
consistent information without repeated explanations”

JOB B - Decision coordination:
“When multiple stakeholders need to weigh in on an operational decision, I want
to gather input efficiently, so I can move forward without delays or missed
perspectives”

CONFIDENCE LEVEL: Low (30%)
RECOMMENDATION: Interview operations managers to identify which specific job matters most.

───────────────────────────────────────────────────────────────────
3. “Should integrate Slack” → PURE SOLUTION, NOT A JOB
───────────────────────────────────────────────────────────────────

❌ PROBLEM: Integration with Slack is a solution, not a job.

UNDERLYING JOB (likely):
“When operational status changes in a way that affects my team’s work, I want
to be notified immediately in my primary communication channel, so I can respond
quickly without constantly checking multiple tools”

WHY THIS WORKS:
✅ Removes solution language (“Slack” is one possible channel)
✅ Identifies trigger: “status changes that affect my team’s work”
✅ Clear outcome: “respond quickly without constant checking”
✅ Solution-agnostic: Could be Slack, email, Teams, SMS, in-app, etc.

CONFIDENCE LEVEL: High (85%)

───────────────────────────────────────────────────────────────────
4. “Save time on data entry” → CLOSER, NEEDS SPECIFICITY
───────────────────────────────────────────────────────────────────

JTBD STATEMENT:
“When an operations manager receives new operational information, I want to
capture it in our system with minimal manual input, so I can maintain accurate
records without interrupting my workflow”

IMPROVEMENTS MADE:
✅ Added situation: “receives new operational information”
✅ Clarified motivation: “capture with minimal manual input”
✅ Specific outcome: “accurate records without workflow interruption”
✅ Avoided solution: Didn’t specify how (automation, imports, voice, templates)

CONFIDENCE LEVEL: High (80%)

═══════════════════════════════════════════════════════════════════
SUMMARY & RECOMMENDATIONS
═══════════════════════════════════════════════════════════════════

✅ READY TO USE (high confidence):
#3 - Slack integration → notification job (85%)
#4 - Data entry → capturing information job (80%)

⏸️ NEEDS CUSTOMER VALIDATION (medium confidence):
#1 - Faster reports (60%)

🔍 REQUIRES MORE DISCOVERY (low confidence):
#2 - Collaboration (30%) - too broad, likely 3+ different jobs

NEXT STEPS:

1. Use ready-to-use statements (#3, #4) immediately
2. Conduct 3-5 customer interviews for reporting use cases
3. Run separate discovery on collaboration pain points