whiteport-design-studio 0.2.2 → 0.3.0

package/docs/learn/module-05-platform-requirements/tutorial-05.md

@@ -0,0 +1,377 @@
+# Tutorial 05: Create Your Platform Requirements
+
+**Hands-on guide to documenting technical boundaries with Saga**
+
+---
+
+## Overview
+
+This tutorial walks you through creating a platform requirements document that captures the technical reality your design must work within.
+
+**Time:** 15-20 minutes
+**Prerequisites:** Module 04 (Product Brief) completed
+**Agent:** Saga
+**What you'll create:** `A-Product-Brief/platform-requirements.md`
+
+---
+
+## Before You Start
+
+**You'll need:**
+
+- Your completed Product Brief
+- Basic understanding of the project's technical context
+- Access to technical stakeholders (helpful but not required)
+
+**Saga will help you:**
+
+- Ask the right questions
+- Identify gaps you might miss
+- Document clearly and consistently
+- Prepare handoff to development
+
+---
+
+## Step 1: Start the Conversation with Saga (2 min)
+
+### Open your AI IDE and start a conversation:
+
+**You say:**
+> "I need to create platform requirements for my project. I've completed my Product Brief. Can you help me document the technical boundaries?"
+
+**Saga responds with initial questions about your project context.**
+
+### Provide context:
+
+Share your Product Brief or summarize:
+- What you're building
+- Who it's for
+- Key goals
+
+This gives Saga the context to ask relevant questions.
+
+---
+
+## Step 2: Define Platforms (3 min)
+
+### Saga will ask about platforms:
+
+> "What platforms are you targeting? Web, mobile native, desktop, or a combination?"
+
+### Think through:
+
+- Where will users primarily access this?
+- Do you need offline capability?
+- Are there device-specific requirements?
+- What browsers or OS versions must you support?
+
+### Example response:
+
+> "We're building a PWA that works on mobile and desktop browsers. Users will primarily use it on their phones. We need basic offline capability for core features. Must support modern browsers — Chrome, Safari, Firefox, Edge."
+
+### Saga documents and probes deeper:
+
+> "What about offline capability — which features must work offline, and which can require connection?"
+
+---
+
+## Step 3: Identify Integrations (3 min)
+
+### Saga asks about integrations:
+
+> "What systems does this need to integrate with? Think about authentication, payments, data sources, and third-party services."
+
+### Categories to consider:
+
+**Authentication:**
+- How will users log in?
+- Is there an existing identity system?
+- Do you need social login?
+
+**Data:**
+- Where does data live?
+- What existing databases connect?
+- What external data do you need?
+
+**Services:**
+- Payment processing?
+- Email/SMS notifications?
+- Maps or location?
+- Analytics?
+
+### Example response:
+
+> "Authentication through Supabase, with optional Google login. All data in Supabase PostgreSQL. We'll need push notifications eventually. No payment processing for MVP."
+
+### Saga probes:
+
+> "Are there any legacy systems or existing tools users currently use that this should connect with?"
+
+---
+
+## Step 4: Document Constraints (3 min)
+
+### Saga asks about limitations:
+
+> "What constraints are you working within? Think about technical limitations, budget, team skills, timeline, and regulations."
+
+### Areas to cover:
+
+**Technical:**
+- Hosting limitations?
+- Performance requirements?
+- Platform restrictions?
+
+**Budget:**
+- What can't you afford?
+- What's the spending limit?
+
+**Team:**
+- What skills are missing?
+- What's the team size?
+
+**Timeline:**
+- When must this launch?
+- Are there phases?
+
+**Regulatory:**
+- Privacy requirements?
+- Accessibility mandates?
+- Industry regulations?
+
+### Example response:
+
+> "Bootstrap budget — using Supabase free tier. Solo developer, no mobile expertise. MVP needed in 8 weeks. GDPR compliance required for Swedish users. No budget for native app development."
+
+### Saga clarifies:
+
+> "For GDPR, does your app handle any child data? That might require additional considerations."
+
+---
+
+## Step 5: Assess Complexity (2 min)
+
+### Saga asks about challenges:
+
+> "Where do you see technical complexity or challenges? Which integrations feel risky or uncertain?"
+
+### Rate each major component:
+
+- **Low** — Well-understood, team has experience
+- **Medium** — Achievable but requires research
+- **High** — Significant unknowns, may need spikes
+- **Unknown** — Needs investigation
+
+### Example response:
+
+> "Push notifications on iOS PWA feel medium complexity — I've read there are limitations. Offline sync is probably medium too. Basic auth and CRUD operations are low — Supabase handles that well."
+
+### Saga summarizes:
+
+> "So we have medium complexity on push notifications and offline sync, with lower complexity on core features. I'll flag the iOS push notification limitations as something that needs research."
+
+---
+
+## Step 6: Identify Knowledge Gaps (2 min)
+
+### Saga asks what's unknown:
+
+> "What don't you know yet? What assumptions haven't been validated? What needs research or a proof-of-concept?"
+
+### Categories:
+
+- **Needs Research** — Documentation review, competitor analysis
+- **Needs Spike** — Technical proof-of-concept
+- **Needs Decision** — Team or stakeholder choice required
+
+### Example response:
+
+> "I don't know how iOS 17 handles PWA push notifications. Not sure about Supabase performance with complex row-level security. We haven't decided if we'll eventually go React Native."
+
+### Saga documents:
+
+> "I'll create three knowledge gap items:
+> 1. Research: iOS 17+ PWA push notification behavior
+> 2. Research: Supabase RLS performance characteristics
+> 3. Decision needed: React Native vs PWA long-term"
+
+---
+
+## Step 7: Review and Finalize (3 min)
+
+### Saga presents the complete document:
+
+> "Here's your platform requirements document. Let me read it back so you can confirm everything is accurate."
+
+### Review checklist:
+
+- ✓ All target platforms listed
+- ✓ Key integrations captured
+- ✓ Constraints are specific and accurate
+- ✓ Complexity levels feel right
+- ✓ Knowledge gaps are clear and actionable
+
+### Make corrections:
+
+If anything is missing or wrong, tell Saga:
+
+> "Add that we need to support Swedish and English languages. And the timeline is actually 10 weeks, not 8."
+
+### Saga updates the document.
+
+---
+
+## Step 8: Save the Document (1 min)
+
+### Saga will save to:
+
+`A-Product-Brief/platform-requirements.md`
+
+### Confirm the save:
+
+> "Save this as platform-requirements.md in the A-Product-Brief folder."
+
+### Saga confirms:
+
+> "Platform requirements saved. This document is now part of your strategic foundation alongside your Product Brief."
+
+---
+
+## Step 9: Handoff to Development (Optional)
+
+### If you want parallel development:
+
+> "Please prepare a handoff for development with the knowledge gaps that need investigation."
+
+### Saga creates handoff:
+
+> "Handoff prepared for development:
+>
+> **Research Tasks:**
+> - iOS 17+ PWA push notification behavior
+> - Supabase RLS performance characteristics
+>
+> **Spike Tasks:**
+> - Offline sync conflict resolution patterns
+>
+> **Pending Decisions:**
+> - React Native vs PWA long-term strategy
+>
+> Development can start while you continue to UX design with Freya."
+
+---
+
+## What You've Created
+
+### Your platform-requirements.md includes:
+
+```markdown
+# Platform Requirements
+
+## Platforms
+- Primary: Progressive Web App (PWA)
+- Mobile: iOS and Android via PWA
+- Desktop: Web browser (Chrome, Safari, Firefox, Edge)
+- Offline: Core features must work offline
+
+## Integrations
+- Authentication: Supabase Auth, Google OAuth optional
+- Database: Supabase PostgreSQL
+- Storage: Supabase Storage
+- Future: Push notifications
+
+## Constraints
+- Technical: PWA approach, Supabase free tier initially
+- Budget: Bootstrap phase
+- Team: Solo developer
+- Regulatory: GDPR compliance
+- Timeline: MVP in 10 weeks
+
+## Complexity & Challenges
+- Medium: Push notifications (iOS limitations), offline sync
+- Low: Authentication, basic CRUD
+
+## Knowledge Gaps
+- Research: iOS 17+ PWA push notifications
+- Research: Supabase RLS performance
+- Spike: Offline sync patterns
+- Decision: React Native vs PWA long-term
+```
+
+---
+
+## What Happens Next
+
+### Immediate:
+
+- Platform requirements inform all design decisions
+- Knowledge gaps become development research tasks
+- You have a clear picture of what's possible
+
+### Next Phase:
+
+- **Module 07: The Design Phase** — Meet Freya and begin UX design
+- Design within these boundaries
+- Reference platform requirements when making decisions
+
+---
+
+## Tips for Success
+
+**DO:**
+
+- Be honest about constraints
+- Document what you don't know
+- Ask technical stakeholders if unsure
+- Update as you learn more
+
+**DON'T:**
+
+- Guess at technical details
+- Skip knowledge gaps
+- Assume constraints are permanent
+- Over-engineer the document
+
+---
+
+## Common Questions
+
+**Q: What if I don't know the technical details?**
+A: That's what knowledge gaps are for. Document what you don't know and let the development agent investigate.
+
+**Q: Should I talk to developers before creating this?**
+A: Helpful but not required. Saga will ask questions that surface what you know. Mark unknowns as knowledge gaps.
+
+**Q: Can this document change?**
+A: Absolutely. It's a living document. Update it as you learn more or as the project evolves.
+
+**Q: What if I realize a constraint later?**
+A: Add it to the document. Better to discover and document late than never.
+
+---
+
+## You've Completed Module 05!
+
+**Platform Requirements Complete**
+
+You now have:
+- ✅ Product Brief (Module 04)
+- ✅ Platform Requirements (Module 05)
+
+**Next up: Trigger Mapping to connect business goals to user psychology.**
+
+**Your strategic foundation is solid.**
+
+---
+
+## Next Module
+
+**[Module 06: Trigger Mapping →](../module-06-trigger-mapping/module-06-overview.md)**
+
+Connect business goals to user psychology with Saga.
+
+---
+
+[← Back to Lesson 2](lesson-02-defining-platform-requirements.md) | [Back to Module Overview](module-05-platform-requirements-overview.md)
+
+*Part of Module 05: Platform Requirements*

package/docs/{learn-wds/module-05-trigger-mapping → learn/module-06-trigger-mapping}/lesson-01-missing-link.md

@@ -1,4 +1,6 @@
-# Lesson 1: The Missing Link
+# Module 06: Trigger Mapping
+
+## Lesson 1: The Missing Link
 
 **Why Product Brief Alone Isn't Enough**
 
@@ -25,6 +27,7 @@ There's a critical gap between your Product Brief and your design decisions. A g
 
 Your Product Brief tells you the business strategy. But it doesn't tell you:
 
+- **What actually drives the business?**
 - **What actually motivates your users?**
 - **What psychological triggers drive their behavior?**
 - **Which features will have the most impact?**
@@ -139,7 +142,7 @@ Features That Work
 
 **Product Brief** = Business strategy (what, why, who at high level)  
 **Trigger Map** = User psychology (who specifically, why they act, what drives them)  
-**Design** = Solutions that connect strategy to psychology  
+**UX Design** = Solutions that connect strategy to psychology  
 **Features** = Implementations that deliver on both
 
 ---
@@ -232,6 +235,6 @@ Before moving to the next lesson, consider:
 
 ---
 
-[← Back to Module Overview](module-05-overview.md) | [Next: Lesson 2 - Heritage & Evolution →](lesson-02-heritage-evolution.md)
+[← Back to Module Overview](module-06-overview.md) | [Next: Lesson 2 - Heritage & Evolution →](lesson-02-heritage-evolution.md)
 
-*Part of Module 05: Trigger Mapping*
+*Part of Module 06: Trigger Mapping*

package/docs/{learn-wds/module-05-trigger-mapping → learn/module-06-trigger-mapping}/lesson-02-heritage-evolution.md

@@ -1,4 +1,6 @@
-# Lesson 2: The Heritage & Evolution
+# Module 06: Trigger Mapping
+
+## Lesson 2: The Heritage & Evolution
 
 **From Effect Management to Trigger Mapping**
 
@@ -93,7 +95,7 @@ Both Effect Mapping and Trigger Mapping use three core layers. Understanding the
 
 **What it is:**
 - Vision that motivates the team
-- SMART objectives that measure success
+- Strategic objectives (using SMART model) that measure success
 
 **Example:**
 - Vision: "Make family dog care stress-free"
@@ -211,9 +213,9 @@ When all three layers are prioritized, you have perfect guidance for design:
 
 ---
 
-## Three Approaches: Choose Your Path
+## Two Approaches: Choose Your Path
 
-WDS offers three ways to apply Trigger Mapping methodology, depending on your situation:
+WDS offers two ways to create your Trigger Map, depending on whether you're starting from scratch or have existing documentation:
 
 ### 1. Full Trigger Mapping (Starting from Scratch)
 
@@ -224,41 +226,24 @@ WDS offers three ways to apply Trigger Mapping methodology, depending on your si
 - Comprehensive strategic foundation
 
 **When to use:**
-- Major product initiatives
 - No existing documentation
+- Major product initiatives
 - Complex user psychology
 - Multiple target groups
 - Long-term strategic planning
 - When you need defensible prioritization
 
-**Time investment:** 60-90 minutes  
-**Output:** Complete Trigger Map + scored feature list  
-**Tutorial:** [Tutorial 05: Create Your Trigger Map](tutorial-05.md)
+**Three engagement modes** let you choose your speed:
+- **Workshop** — Saga facilitates, you provide insights (45-60 min)
+- **Suggest** — Saga suggests, you review each step (20-35 min)
+- **Dream** — Saga creates autonomously, you review final result (15-25 min)
 
----
-
-### 2. Value Trigger Chain (Quick Validation)
-
-**What it is:**
-- Streamlined single-workshop approach
-- Focus on one primary user journey
-- Quick strategic validation
-- Essential connections only
-
-**When to use:**
-- Smaller features or iterations
-- Single user journey focus
-- Quick strategic check
-- Early-stage validation
-- Time-constrained situations
-
-**Time investment:** 15-20 minutes  
-**Output:** Single-chain map from goal to trigger  
-**Tutorial:** [Tutorial 05B: Create Your Value Trigger Chain](tutorial-05b-value-trigger-chain.md)
+**Output:** Complete Trigger Map + scored feature list
+**Tutorial:** [Tutorial 06: Create Your Trigger Map](tutorial-06.md)
 
 ---
 
-### 3. Documentation Synthesis (Existing Research)
+### 2. Documentation Synthesis (Existing Research)
 
 **What it is:**
 - Extract strategic elements from existing docs
@@ -273,9 +258,9 @@ WDS offers three ways to apply Trigger Mapping methodology, depending on your si
 - Need to make existing documentation actionable
 - Documentation is too long for anyone to read
 
-**Time investment:** 30-45 minutes  
-**Output:** Synthesized Trigger Map + gap analysis  
-**Tutorial:** [Tutorial 05C: Synthesize from Documentation](tutorial-05c-documentation-synthesis.md)
+**Time investment:** 30-45 minutes
+**Output:** Synthesized Trigger Map + gap analysis
+**Tutorial:** [Tutorial 06C: Synthesize from Documentation](tutorial-06c-documentation-synthesis.md)
 
 **The problem this solves:**
 Organizations spend thousands on research that sits unused. 200-page reports nobody reads. Interview transcripts gathering dust. This approach transforms that investment into a single-slide strategic artifact you can actually use in daily design work and AI chats.
@@ -292,13 +277,6 @@ Organizations spend thousands on research that sits unused. 200-page reports nob
 - Stakeholders need strategic justification
 - Building long-term product strategy
 
-**Use Value Trigger Chain if:**
-- Iterating on existing features
-- One clear user journey to validate
-- Need quick strategic check
-- Early exploration phase
-- Time is very limited (under 20 minutes)
-
 **Use Documentation Synthesis if:**
 - You have vision docs, user research, or plans
 - Documentation exists but isn't being used
@@ -306,7 +284,7 @@ Organizations spend thousands on research that sits unused. 200-page reports nob
 - Want to validate strategic alignment
 - Need actionable artifact from existing investment
 
-**Pro tip:** Learn Full Trigger Mapping first (this module). Once you understand the complete process, you'll know when to use the lightweight version or documentation synthesis.
+**Note:** When you need strategic context for a scenario or content piece later, you don't create a separate map — you pick the relevant business goal, persona, and driving forces from the Trigger Map you already have.
 
 ---
 
@@ -359,6 +337,6 @@ You'll see exactly how to create your Trigger Map.
 
 ---
 
-[← Back to Lesson 1](lesson-01-missing-link.md) | [Next: Lesson 3 - The Five Workshops →](lesson-03-five-workshops.md)
+[← Back to Module Overview](module-06-overview.md) | [← Back to Lesson 1](lesson-01-missing-link.md) | [Next: Lesson 3 - The Five Workshops →](lesson-03-five-workshops-overview.md)
 
-*Part of Module 05: Trigger Mapping*
+*Part of Module 06: Trigger Mapping*

package/docs/{learn-wds/module-05-trigger-mapping → learn/module-06-trigger-mapping}/lesson-03-five-workshops-overview.md

@@ -1,4 +1,6 @@
-# Lesson 3: The Five Workshops Overview
+# Module 06: Trigger Mapping
+
+## Lesson 3: The Five Workshops Overview
 
 **Your Roadmap to Strategic Clarity**
 
@@ -423,7 +425,7 @@ You can update the map. The structure stays, the content evolves.
 
 The next five lessons dive deep into each workshop:
 
-- **Lesson 4:** Workshop 1 - Business Goals (vision + SMART objectives)
+- **Lesson 4:** Workshop 1 - Business Goals (vision + strategic objectives)
 - **Lesson 5:** Workshop 2 - Target Groups (WHO ensures success)
 - **Lesson 6:** Workshop 3 - Driving Forces (psychology that drives behavior)
 - **Lesson 7:** Workshop 4 - Prioritization (what matters most)
@@ -436,7 +438,7 @@ The next five lessons dive deep into each workshop:
 - Common mistakes to avoid
 - Tips for success
 
-**After the lessons:** Tutorial 05 walks you through all 5 workshops step-by-step with Saga.
+**After the lessons:** Tutorial 06 walks you through all 5 workshops step-by-step with Saga.
 
 ---
 
@@ -454,6 +456,6 @@ The next five lessons dive deep into each workshop:
 
 ---
 
-[← Back to Lesson 2](lesson-02-heritage-evolution.md) | [Next: Lesson 4 - Workshop 1: Business Goals →](lesson-04-workshop-1-business-goals.md)
+[← Back to Module Overview](module-06-overview.md) | [← Back to Lesson 2](lesson-02-heritage-evolution.md) | [Next: Lesson 4 - Workshop 1: Business Goals →](lesson-04-workshop-1-business-goals.md)
 
-*Part of Module 05: Trigger Mapping*
+*Part of Module 06: Trigger Mapping*