whiteport-design-studio 0.2.2 → 0.3.0

package/docs/learn-wds/module-05-map-triggers-outcomes/tutorial-04.md

@@ -1,460 +0,0 @@
-# Tutorial 04: Map Triggers & Outcomes
-
-**Hands-on guide to understanding WHAT triggers user needs and WHY your business exists**
-
----
-
-## Overview
-
-This tutorial teaches you how to map the psychological triggers that drive user behavior and connect them to business outcomes.
-
-**Time:** 45-60 minutes  
-**Prerequisites:** Module 03 completed (Target Groups identified)  
-**What you'll create:** A complete trigger map for your top target group
-
----
-
-## What You'll Learn
-
-- How to identify user trigger moments
-- Mapping from trigger → need → solution → outcome
-- Connecting user psychology to business value
-- Prioritizing features by trigger impact
-- Creating a traceable chain of reasoning
-
----
-
-## Step 1: Select Your Top Target Group (5 min)
-
-From Module 03, choose your highest-priority target group.
-
-**Example (Dog Week):**
-
-```
-Target Group: Busy Parents with Family Dog
-Priority: #1 (highest impact + feasibility)
-```
-
-**Your turn:**
-
-```
-Selected Target Group: [Your top group]
-Why this group: [Reasoning]
-```
-
----
-
-## Step 2: Identify Trigger Moments (15 min)
-
-### What is a trigger?
-
-A specific moment when a user realizes they have a need your product can solve.
-
-### Framework: The Trigger Moment
-
-**Ask:**
-
-- WHEN does the user feel pain/frustration?
-- WHAT specific situation causes this?
-- WHY does this matter to them emotionally?
-
-**Example (Dog Week - Busy Parents):**
-
-**Trigger 1: Morning Chaos**
-
-```
-WHEN: Monday morning, everyone rushing
-WHAT: Nobody knows who's walking the dog
-WHY: Stress, guilt, family conflict, dog's needs unmet
-```
-
-**Trigger 2: Forgotten Feeding**
-
-```
-WHEN: Evening, parent realizes dog wasn't fed
-WHAT: Uncertainty about who was responsible
-WHY: Guilt, worry about dog's health, family tension
-```
-
-**Trigger 3: Vet Appointment Missed**
-
-```
-WHEN: Vet calls about missed appointment
-WHAT: Nobody remembered or knew about it
-WHY: Embarrassment, concern for dog, wasted money
-```
-
-**Your turn:**
-
-```
-Identify 3-5 trigger moments for your target group:
-
-Trigger 1: [Name]
-WHEN: [Specific moment]
-WHAT: [Specific situation]
-WHY: [Emotional impact]
-
-Trigger 2: [Name]
-WHEN:
-WHAT:
-WHY:
-
-[Continue for 3-5 triggers]
-```
-
-**AI Support:**
-
-```
-Agent: "Let's dig deeper into each trigger:
-- What happens right before this moment?
-- What emotions does the user feel?
-- How often does this happen?
-- What do they try now (that doesn't work)?"
-```
-
----
-
-## Step 3: Map User Needs (10 min)
-
-### What is the need?
-
-The underlying requirement the user has when triggered.
-
-### Framework: From Trigger to Need
-
-**For each trigger, ask:**
-
-- What does the user need in this moment?
-- What would make this situation better?
-- What's the core problem to solve?
-
-**Example (Dog Week):**
-
-**Trigger: Morning Chaos**
-
-```
-Need: Know immediately who's responsible for dog care today
-Need: See the full week's schedule at a glance
-Need: Get reminded before tasks are due
-```
-
-**Trigger: Forgotten Feeding**
-
-```
-Need: Track whether tasks were completed
-Need: Get notifications when tasks are overdue
-Need: See task history to avoid confusion
-```
-
-**Your turn:**
-
-```
-For each trigger, identify 2-3 core needs:
-
-Trigger 1: [Name]
-Needs:
-- [Need 1]
-- [Need 2]
-- [Need 3]
-
-[Continue for all triggers]
-```
-
----
-
-## Step 4: Define Solutions (10 min)
-
-### What is the solution?
-
-The specific feature or capability that addresses the need.
-
-### Framework: Need to Solution
-
-**For each need, ask:**
-
-- What feature would solve this?
-- How would it work?
-- What's the simplest version?
-
-**Example (Dog Week):**
-
-**Need: Know who's responsible today**
-
-```
-Solution: Daily schedule view with assigned responsibilities
-- Shows today's tasks
-- Highlights current user's tasks
-- Shows who's assigned to each task
-```
-
-**Need: Get reminded before tasks are due**
-
-```
-Solution: Smart notifications
-- Reminder 1 hour before task
-- Escalation if task not completed
-- Family-wide visibility of overdue tasks
-```
-
-**Your turn:**
-
-```
-For each need, define a solution:
-
-Need: [Need description]
-Solution: [Feature name]
-- [How it works]
-- [Key capabilities]
-- [User benefit]
-
-[Continue for all needs]
-```
-
-**AI Support:**
-
-```
-Agent: "Let's validate each solution:
-- Does this truly solve the need?
-- Is it the simplest solution?
-- Are there edge cases to consider?
-- How does this connect to business goals?"
-```
-
----
-
-## Step 5: Map Business Outcomes (10 min)
-
-### What is the outcome?
-
-The business value created when users get their needs met.
-
-### Framework: Solution to Outcome
-
-**For each solution, ask:**
-
-- How does this create business value?
-- What metrics improve?
-- How does this support business goals?
-
-**Example (Dog Week):**
-
-**Solution: Daily schedule view**
-
-```
-User Outcome: Reduced stress, better dog care
-Business Outcome:
-- Increased daily active users (checking schedule)
-- Higher retention (solving real pain)
-- Word-of-mouth growth (visible family benefit)
-Metrics: DAU, retention rate, NPS
-```
-
-**Solution: Smart notifications**
-
-```
-User Outcome: Never miss dog care tasks
-Business Outcome:
-- Increased engagement (notification opens)
-- Higher task completion (core value delivered)
-- Premium feature potential (advanced notifications)
-Metrics: Notification open rate, task completion rate, conversion
-```
-
-**Your turn:**
-
-```
-For each solution, map to business outcomes:
-
-Solution: [Feature name]
-User Outcome: [How user benefits]
-Business Outcome: [How business benefits]
-Metrics: [What you'll measure]
-
-[Continue for all solutions]
-```
-
----
-
-## Step 6: Create Trigger Map Visualization (10 min)
-
-### Format:
-
-```
-TARGET GROUP: [Group name]
-
-TRIGGER → NEED → SOLUTION → OUTCOME
-
-1. [Trigger name]
-   WHEN: [Moment]
-   ↓
-   NEED: [Core need]
-   ↓
-   SOLUTION: [Feature]
-   ↓
-   OUTCOME: [Business value]
-   METRICS: [Measurements]
-
-2. [Next trigger...]
-```
-
-**Example (Dog Week - Simplified):**
-
-```
-TARGET GROUP: Busy Parents with Family Dog
-
-TRIGGER → NEED → SOLUTION → OUTCOME
-
-1. Morning Chaos
-   WHEN: Monday morning, nobody knows dog responsibilities
-   ↓
-   NEED: Know who's responsible for dog care today
-   ↓
-   SOLUTION: Daily schedule view with assigned tasks
-   ↓
-   OUTCOME: Increased DAU, higher retention
-   METRICS: Daily active users, 7-day retention
-
-2. Forgotten Feeding
-   WHEN: Evening, uncertainty about feeding
-   ↓
-   NEED: Track task completion in real-time
-   ↓
-   SOLUTION: Task completion tracking + notifications
-   ↓
-   OUTCOME: Higher engagement, core value delivered
-   METRICS: Task completion rate, notification opens
-```
-
-**Your turn:**
-
-```
-Create your trigger map:
-[Your complete map]
-```
-
----
-
-## Step 7: Prioritize by Impact (5 min)
-
-### Framework: Impact Score
-
-**For each trigger-to-outcome chain, rate:**
-
-- **User Impact** (1-5): How much does this help the user?
-- **Business Impact** (1-5): How much business value does this create?
-- **Feasibility** (1-5): How easy is this to build?
-
-**Calculate:** `Priority Score = (User Impact + Business Impact) × Feasibility`
-
-**Example (Dog Week):**
-
-```
-1. Morning Chaos → Daily Schedule
-   User: 5, Business: 5, Feasibility: 4
-   Score: (5+5) × 4 = 40 ⭐ HIGHEST PRIORITY
-
-2. Forgotten Feeding → Task Tracking
-   User: 5, Business: 4, Feasibility: 4
-   Score: (5+4) × 4 = 36 ⭐ HIGH PRIORITY
-
-3. Vet Appointment → Calendar Integration
-   User: 4, Business: 3, Feasibility: 2
-   Score: (4+3) × 2 = 14 → LOWER PRIORITY
-```
-
-**Your turn:**
-
-```
-Score and rank your triggers:
-[Your prioritized list]
-```
-
----
-
-## Step 8: Save Your Trigger Map
-
-**Create file:** `B-Trigger-Map/trigger-map-[target-group].md`
-
-**Use template from:** `workflows/2-trigger-mapping/templates/trigger-map.template.md`
-
----
-
-## What You've Accomplished
-
-✅ **Identified trigger moments** - You know WHEN users need your product  
-✅ **Mapped user needs** - You understand WHAT users need  
-✅ **Defined solutions** - You know WHAT to build  
-✅ **Connected to business** - You know WHY each feature matters  
-✅ **Prioritized features** - You know WHAT to build first
-
----
-
-## The Power of Trigger Mapping
-
-**This is strategic gold:**
-
-- Every feature traces back to a real user trigger
-- Every decision is backed by user psychology
-- Every feature connects to business value
-- No more guessing what to build
-- No more building things nobody uses
-
-**When product managers ask "what should we build next?"**  
-→ You have the answer, backed by data and reasoning
-
----
-
-## Next Steps
-
-**Immediate:**
-
-- Repeat for your top 2-3 target groups
-- Compare trigger maps across groups
-- Identify overlapping needs (efficiency opportunity)
-
-**Next Module:**
-
-- [Module 05: Prioritize Features](../module-05-prioritize-features/module-05-overview.md)
-- Create your feature roadmap based on trigger impact
-
----
-
-## Common Questions
-
-**Q: How many triggers should I identify per target group?**  
-A: Start with 3-5 major triggers. You can always add more later.
-
-**Q: What if multiple triggers lead to the same solution?**  
-A: Perfect! This means the solution has high leverage. Document all triggers it solves.
-
-**Q: Should I map triggers for all target groups?**  
-A: Start with your top 1-2 groups. Add more as needed.
-
-**Q: How do I validate these triggers are real?**  
-A: User research, interviews, observation. The trigger map is a hypothesis to test.
-
----
-
-## Tips for Success
-
-**DO ✅**
-
-- Be specific about trigger moments
-- Focus on emotional impact (the "why")
-- Connect everything to business outcomes
-- Prioritize ruthlessly
-- Test assumptions with users
-
-**DON'T ❌**
-
-- List generic "user wants X" statements
-- Skip the emotional "why"
-- Create solutions without clear triggers
-- Try to solve everything at once
-- Forget to measure outcomes
-
----
-
-**Your trigger map is the strategic foundation that guides every design decision!**
-
-[← Back to Module 04](module-04-overview.md) | [Next: Module 05 →](../module-05-prioritize-features/module-05-overview.md)

package/docs/learn-wds/module-05-trigger-mapping/lesson-04-workshop-1-business-goals.md

@@ -1,274 +0,0 @@
-# Lesson 3: Workshop 1 - Business Goals
-
-**Define What Winning Looks Like**
-
----
-
-## Overview
-
-Workshop 1 is where you establish the strategic foundation for your entire Trigger Map. You'll define both your aspirational vision and concrete measurable objectives that prove you're succeeding.
-
-**Duration:** 15-20 minutes  
-**Format:** Conversational with Saga  
-**Output:** Vision statement + 3-5 strategic objectives
-
----
-
-## Understanding the Two Levels
-
-Business goals work on two distinct levels:
-
-### 1. Vision (Visionary Statements)
-
-**What it is:**
-- Aspirational and motivational
-- Grand ambitions that reflect focus and direction
-- Not exact or measurable
-- Examples: "Be the best," "Fastest in market," "Top of mind"
-
-**Characteristics:**
-- Easy to set, hard to measure
-- Provides the "why" and emotional drive
-- Inspires and motivates the team
-- Gives direction without rigid constraints
-
-### 2. Strategic Objectives
-
-**What it is:**
-- Specific and measurable (expressed using SMART method)
-- Observable evidence that vision is being realized
-- Concrete milestones you can track
-- Examples: "10,000 users by Q4," "70% retention rate"
-
-**Characteristics:**
-- Harder to set, easy to measure
-- Provides the "what" and accountability
-- Enables progress tracking
-- Creates clear success criteria
-
-**Why both matter:** Visionary statements provide motivation and direction. Objectives provide accountability and proof of progress. Together they create both inspiration and measurement.
-
----
-
-## The Workshop Flow
-
-### Step 1: Start with Vision
-
-**Capture the grand ambition:**
-- What's the aspirational future state?
-- What motivates the team?
-- What's the "why" behind this project?
-- Don't worry about exact measurement yet
-
-**Example:**
-"Make remote work sustainable and healthy for distributed teams"
-
-### Step 2: Ask "What Will We Observe?"
-
-**Bridge from soft to hard goals:**
-- When this vision is being realized, what will we see in the world?
-- What measurable evidence proves we're succeeding?
-- What observable changes indicate progress?
-
-**This is the critical bridging question** that transforms aspiration into measurable reality.
-
-**Example:**
-"When remote work is sustainable and healthy, we'll observe teams using tools daily, staying engaged long-term, and growing their usage. We'll see business metrics that prove the model works."
-
-### Step 3: Define Strategic Objectives
-
-**Transform observations into specific goals:**
-- 3-5 concrete objectives
-- Each expressed using SMART method (Specific, Measurable, Achievable, Relevant, Time-bound)
-- Focus on what's truly measurable
-- Set realistic timeframes
-
-See [SMART Method Reference](../../models/smart-goals-model.md) for detailed guidance on creating strategic objectives.
-
-**Example:**
-1. Achieve 5,000 active teams by Q4 2024
-2. Increase average session time to 15 minutes daily
-3. Reach 70% weekly retention rate
-4. Generate $50K MRR by end of year
-
----
-
-## Key Questions Saga Asks
-
-### For Vision (Visionary Statements)
-
-- "What's the grand ambition behind this project?"
-- "What does 'winning' look like at the highest level?"
-- "What vision motivates your team?"
-- "Why does this project matter?"
-
-### Bridging to Objectives
-
-- "When this vision is being realized, what will we observe in the world?"
-- "What measurable evidence would prove you're succeeding?"
-- "What would we see that indicates progress toward this vision?"
-
-### For Strategic Objectives (using SMART method)
-
-- "What specific, measurable outcomes would prove success?"
-- "By when do you need to achieve these objectives?"
-- "How will you measure progress?"
-- "What counts as 'active' or 'successful' in your context?"
-
----
-
-## Generic Example Walkthrough
-
-### Vision (Soft Goal)
-
-"Make remote work sustainable and healthy for distributed teams"
-
-**Why this works:**
-- Aspirational and motivating
-- Clear direction without rigid constraints
-- Easy to communicate and remember
-- Inspires the team
-
-### Bridging Question
-
-"When remote work is sustainable and healthy, what will we observe?"
-
-**Observations:**
-- Teams using our solution daily
-- High retention rates (people stay)
-- Growing usage patterns
-- Sustainable business model (revenue)
-
-### Strategic Objectives (using SMART method)
-
-1. **Achieve 5,000 active teams by Q4 2024**
-   - Specific: Active teams (defined metric)
-   - Measurable: 5,000 teams
-   - Achievable: Based on market size and growth rate
-   - Relevant: Proves market adoption
-   - Time-bound: Q4 2024
-
-2. **Increase average session time to 15 minutes daily**
-   - Specific: Session time metric
-   - Measurable: 15 minutes
-   - Achievable: Industry benchmarks
-   - Relevant: Indicates engagement
-   - Time-bound: Daily measurement
-
-3. **Reach 70% weekly retention rate**
-   - Specific: Weekly retention
-   - Measurable: 70% rate
-   - Achievable: Above industry average
-   - Relevant: Proves value delivery
-   - Time-bound: Weekly tracking
-
-4. **Generate $50K MRR by end of year**
-   - Specific: Monthly recurring revenue
-   - Measurable: $50K
-   - Achievable: Based on pricing and targets
-   - Relevant: Business sustainability
-   - Time-bound: End of year
-
----
-
-## What You Get from Workshop 1
-
-✅ **Inspiring vision** that motivates the team  
-✅ **Measurable objectives** that prove progress  
-✅ **Clear connection** between ambition and accountability  
-✅ **Foundation** for all strategic decisions  
-✅ **Alignment** on both "why" and "what"
-
----
-
-## Common Mistakes to Avoid
-
-### Mistake 1: Skipping the Vision
-
-**Problem:** Jumping straight to metrics without capturing the aspiration  
-**Why it fails:** Team loses motivation, no emotional connection  
-**Fix:** Start with the grand ambition, then bridge to metrics
-
-### Mistake 2: Vague Objectives
-
-**Problem:** "Improve user experience" or "Get more customers"  
-**Why it fails:** Can't measure progress, no accountability  
-**Fix:** Make every objective SMART with specific numbers
-
-### Mistake 3: Too Many Objectives
-
-**Problem:** Listing 15 different metrics to track  
-**Why it fails:** Dilutes focus, creates confusion  
-**Fix:** Limit to 3-5 most critical objectives
-
-### Mistake 4: Unrealistic Targets
-
-**Problem:** "Become #1 in the world in 30 days"  
-**Why it fails:** Demoralizes team, loses credibility  
-**Fix:** Set challenging but achievable goals based on resources
-
-### Mistake 5: Missing the Bridge
-
-**Problem:** Vision and objectives feel disconnected  
-**Why it fails:** Team doesn't see how metrics prove vision  
-**Fix:** Use the bridging question to connect them explicitly
-
----
-
-## How This Feeds Into Next Workshops
-
-**Workshop 1 creates the foundation:**
-
-```
-Business Goals (Vision + Objectives)
-    ↓
-Workshop 2: Which user groups can help achieve these?
-    ↓
-Workshop 3: What drives those groups' behavior?
-    ↓
-Workshop 4: Which groups and drivers matter most?
-    ↓
-Workshop 5: Which features address top priorities?
-```
-
-Everything traces back to the goals you define here.
-
----
-
-## Tips for Success
-
-**DO:**
-- ✅ Start with aspiration before metrics
-- ✅ Use the bridging question explicitly
-- ✅ Make objectives truly SMART
-- ✅ Limit to 3-5 key objectives
-- ✅ Reference your Product Brief
-
-**DON'T:**
-- ❌ Skip the vision (just list metrics)
-- ❌ Accept vague objectives
-- ❌ Set unrealistic targets
-- ❌ Create too many objectives
-- ❌ Forget to connect vision to objectives
-
----
-
-## What's Next
-
-Workshop 2 identifies WHO can help you achieve these goals - your target groups. You'll create prioritized personas that become the foundation for understanding user psychology.
-
----
-
-## Key Takeaways
-
-✅ **Two levels of goals** - Vision (visionary/aspirational) + Strategic Objectives (measurable using SMART method)  
-✅ **Bridging question is critical** - "What will we observe when vision is realized?"  
-✅ **Strategic objectives using SMART method** - Specific, Measurable, Achievable, Relevant, Time-bound  
-✅ **3-5 objectives maximum** - Focus on what truly matters  
-✅ **Foundation for everything** - All workshops build from here
-
----
-
-[← Back to Lesson 3](lesson-03-five-workshops-overview.md) | [Next: Lesson 5 - Workshop 2: Target Groups →](lesson-05-workshop-2-target-groups.md)
-
-*Part of Module 05: Trigger Mapping*