whiteport-design-studio 0.1.0

package/docs/learn-wds/module-04-product-brief/module-04-overview.md

@@ -0,0 +1,194 @@
+# Module 04: Product Brief
+
+**Your Strategic Foundation in 30-45 Minutes**
+
+---
+
+## Module Overview
+
+This module teaches you how to create a Product Brief - the strategic foundation that prevents chaos and saves weeks of rework. Learn what the document is, why it matters, and how WDS makes creating it fast through AI-guided conversation.
+
+**Time:** 46-58 minutes (6 lessons)  
+**Prerequisites:** Module 02 completed (WDS installed)  
+**What you'll create:** Product Brief (2-3 pages) + optional strategic documents as needed
+
+---
+
+## What You'll Learn
+
+- Why projects fail without strategic foundation (and how to prevent it)
+- The 5 strategic questions every Product Brief must answer
+- What the document looks like and how it's structured
+- How WDS makes this fast (30-45 min vs days of meetings)
+- How teams use the Product Brief throughout the project
+- Additional strategic documents you can create as needed
+
+---
+
+## Lessons
+
+### [Lesson 1: The Chaos Problem](lesson-01-chaos-problem.md)
+
+**Time:** 6-8 minutes
+
+Why projects fail before they start:
+
+- The cost of no foundation (wasted design, misalignment, scope creep)
+- What the Product Brief does (single source of truth)
+- Time investment vs payoff (30-45 min saves weeks)
+- Your insurance policy against chaos
+
+### [Lesson 2: The 5 Strategic Questions](lesson-02-five-questions.md)
+
+**Time:** 10-12 minutes
+
+What every Product Brief must answer:
+
+- **What & Why** - Vision and positioning
+- **Who** - Target users and stakeholders
+- **How We'll Know** - Success criteria (measurable outcomes)
+- **Context** - Competitive landscape (alternatives, differentiation)
+- **Boundaries** - Constraints (technical, business, design)
+
+### [Lesson 3: The Document Structure](lesson-03-document-structure.md)
+
+**Time:** 8-10 minutes
+
+What a Product Brief actually looks like:
+
+- Template structure walkthrough
+- Key sections and what goes in each
+- How to keep it concise (2-3 pages max)
+- Making it scannable and useful
+- Living document approach
+
+### [Lesson 4: How WDS Makes This Great](lesson-04-wds-advantage.md)
+
+**Time:** 8-10 minutes
+
+The unique features that ensure excellence:
+
+- Human-in-the-loop thinking partnership (BMad methodology)
+- AI-guided discovery (no blank page paralysis)
+- Conversational approach (talk it out, Saga writes it down)
+- Structured output (proper formatting automatically)
+- Built-in best practices (SMART goals, constraint checklists)
+- Two levels: Simplified vs Complete (based on project needs)
+
+### [Lesson 5: Using Your Product Brief](lesson-05-using-brief.md)
+
+**Time:** 6-8 minutes
+
+How this document powers your entire project:
+
+- How designers use it (reference for every decision)
+- How developers use it (understand the "why")
+- How stakeholders use it (track progress, prevent scope creep)
+- How product managers use it (roadmaps, user stories)
+- When to update it (and when not to)
+
+### [Lesson 6: Additional Strategic Documents](lesson-06-additional-documents.md)
+
+**Time:** 8-10 minutes
+
+Expanding your strategic foundation:
+
+- Core Features Document (feature prioritization)
+- Tone of Voice Guide (brand personality, communication)
+- Visual Design Brief (visual direction, inspiration)
+- Technical Architecture Brief (platform, integrations)
+- Content Strategy (content types, publishing)
+- Localization Strategy (multi-language planning)
+- Accessibility Requirements (compliance, user needs)
+- Data & Privacy Strategy (collection, storage, compliance)
+
+---
+
+## Tutorial
+
+**[Tutorial: Create Your Product Brief →](tutorial-04.md)**
+
+Step-by-step hands-on guide to creating your Product Brief with Saga.
+
+**Time:** 30-45 minutes  
+**What you'll create:** Complete Product Brief document
+
+---
+
+## Key Concepts
+
+**Product Brief:**
+- 2-3 page strategic document
+- Answers 5 critical questions (What/Why, Who, How We'll Know, Context, Boundaries)
+- Single source of truth for entire team
+- Created in 30-45 minutes through AI-guided conversation
+- Living document that evolves with the project
+
+**The 5 Strategic Questions:**
+1. **What & Why** - Vision and positioning (what you're building, why it matters, who it's for)
+2. **Who** - Target users and stakeholders (who uses it, who decides, who builds)
+3. **How We'll Know** - Success criteria (user, business, technical, design metrics)
+4. **Context** - Competitive landscape (alternatives, differentiation, positioning)
+5. **Boundaries** - Constraints (technical, business, design limitations)
+
+**WDS Advantage:**
+- **Speed:** 30-45 min vs days of meetings
+- **AI-Guided:** Saga asks the right questions, no blank page
+- **Conversational:** Natural dialogue, not form-filling
+- **Professional:** Built-in best practices (SMART goals, checklists)
+- **Flexible:** Two levels (simplified vs complete)
+- **Living:** Easy to update as you learn
+
+**Additional Documents:**
+- Optional strategic documents created as needed
+- All live in Project Brief folder
+- Same conversational approach with Saga
+- Expand foundation based on project complexity
+
+---
+
+## Learning Outcomes
+
+By the end of this module, you will:
+
+- ✅ Understand why the Product Brief prevents chaos and saves weeks
+- ✅ Know the 5 strategic questions that guide every design decision
+- ✅ Be able to structure a clear, concise Product Brief
+- ✅ Understand how WDS makes this fast through AI guidance
+- ✅ Know how teams use the Product Brief throughout the project
+- ✅ Be able to create additional strategic documents as needed
+- ✅ Have confidence to create your own Product Brief in 30-45 minutes
+
+---
+
+## What You'll Create
+
+**Core:**
+- ✅ Product Brief (2-3 pages)
+  - Vision & positioning
+  - Target users & stakeholders
+  - Success criteria (measurable)
+  - Competitive landscape
+  - Constraints (technical, business, design)
+
+**Optional (as needed):**
+- ✅ Core Features Document
+- ✅ Tone of Voice Guide
+- ✅ Visual Design Brief
+- ✅ Technical Architecture Brief
+- ✅ Content Strategy
+- ✅ Localization Strategy
+- ✅ Accessibility Requirements
+- ✅ Data & Privacy Strategy
+
+---
+
+## Start Learning
+
+**[Begin with Lesson 1: The Chaos Problem →](lesson-01-chaos-problem.md)**
+
+---
+
+[← Back to Course Overview](../00-course-overview.md) | [Next: Module 05: Trigger Mapping →](../module-05-trigger-mapping/module-05-overview.md)
+
+*Part of the WDS Course: From Designer to Linchpin*

package/docs/learn-wds/module-04-product-brief/tutorial-04.md

@@ -0,0 +1,400 @@
+# Tutorial 04: Create Your Project Brief
+
+**Hands-on guide to defining your project vision, goals, and constraints**
+
+---
+
+## Overview
+
+This tutorial walks you through creating a complete project brief that serves as the foundation for all design decisions.
+
+**Time:** 30-45 minutes  
+**Prerequisites:** Module 01 completed  
+**What you'll create:** A complete project brief document
+
+---
+
+## What You'll Learn
+
+- How to articulate project vision clearly
+- Defining measurable business goals
+- Identifying stakeholders and their needs
+- Documenting technical and business constraints
+- Setting success criteria
+
+---
+
+## Before You Start
+
+**You'll need:**
+
+- A project idea (existing or new)
+- 30-45 minutes of focused time
+- Access to stakeholder information (if available)
+
+**AI Support:**
+
+- AI agent will guide you through each section
+- Ask clarifying questions
+- Help structure your thinking
+- Suggest improvements
+
+---
+
+## Step 1: Define Project Vision (10 min)
+
+### What is it?
+
+The project vision is a clear, compelling statement of what you're building and why it matters.
+
+### How to do it:
+
+**Ask yourself:**
+
+- What problem does this solve?
+- Who benefits from this solution?
+- What makes this unique or valuable?
+- What's the desired end state?
+
+**Example (Dog Week):**
+
+```
+Vision: A family coordination platform that helps parents manage
+their dog's care schedule, ensuring every family member knows their
+responsibilities and the dog's needs are consistently met.
+```
+
+**Your turn:**
+
+```
+Write your project vision:
+[Your vision here]
+```
+
+**AI Support:**
+
+```
+Agent: "Let me help you refine your vision. Tell me:
+- What problem are you solving?
+- Who is this for?
+- What makes it valuable?"
+```
+
+---
+
+## Step 2: Set Business Goals (10 min)
+
+### What are they?
+
+Specific, measurable objectives that define project success from a business perspective.
+
+### How to do it:
+
+**Framework: SMART Goals**
+
+- **S**pecific - Clear and unambiguous
+- **M**easurable - Can track progress
+- **A**chievable - Realistic given resources
+- **R**elevant - Aligned with business strategy
+- **T**ime-bound - Has a deadline
+
+**Example (Dog Week):**
+
+```
+Business Goals:
+1. Acquire 1,000 active families within 6 months of launch
+2. Achieve 70% weekly active user rate
+3. Reduce family coordination time by 50%
+4. Generate $50K MRR within 12 months
+```
+
+**Your turn:**
+
+```
+List 3-5 business goals:
+1. [Goal 1]
+2. [Goal 2]
+3. [Goal 3]
+```
+
+**AI Support:**
+
+```
+Agent: "Let's make these goals SMART. For each goal, I'll help you:
+- Make it specific and measurable
+- Set realistic targets
+- Define timeframes"
+```
+
+---
+
+## Step 3: Identify Stakeholders (5 min)
+
+### Who are they?
+
+People who have a stake in the project's success or will be affected by it.
+
+### How to do it:
+
+**Categories:**
+
+- **Primary Users** - Direct users of the product
+- **Secondary Users** - Indirect beneficiaries
+- **Business Stakeholders** - Decision makers, investors
+- **Technical Stakeholders** - Developers, IT, infrastructure
+- **External Stakeholders** - Partners, regulators, community
+
+**Example (Dog Week):**
+
+```
+Stakeholders:
+- Primary: Parents managing family dog care
+- Secondary: Children participating in care, the dog
+- Business: Founders, investors
+- Technical: Development team, hosting provider
+- External: Veterinarians (future integration)
+```
+
+**Your turn:**
+
+```
+List your stakeholders by category:
+[Your stakeholders]
+```
+
+---
+
+## Step 4: Document Constraints (10 min)
+
+### What are they?
+
+Limitations and requirements that shape your design decisions.
+
+### How to do it:
+
+**Categories:**
+
+**Technical Constraints:**
+
+- Platform requirements (web, mobile, desktop)
+- Browser/device support
+- Performance requirements
+- Integration requirements
+- Security/compliance needs
+
+**Business Constraints:**
+
+- Budget limitations
+- Timeline requirements
+- Resource availability
+- Market positioning
+- Competitive landscape
+
+**Design Constraints:**
+
+- Brand guidelines
+- Accessibility requirements
+- Localization needs
+- Existing design systems
+
+**Example (Dog Week):**
+
+```
+Constraints:
+Technical:
+- Must work on mobile (iOS/Android) and web
+- Swedish language primary, English secondary
+- GDPR compliance required
+- Offline capability for core features
+
+Business:
+- 6-month timeline to MVP
+- Bootstrap budget (no external funding yet)
+- Small team (2 developers, 1 designer)
+
+Design:
+- Family-friendly visual language
+- WCAG 2.1 AA accessibility
+- Swedish cultural considerations
+```
+
+**Your turn:**
+
+```
+Document your constraints:
+[Your constraints]
+```
+
+**AI Support:**
+
+```
+Agent: "Let's identify constraints you might have missed:
+- Have you considered accessibility?
+- What about localization?
+- Any regulatory requirements?
+- Performance expectations?"
+```
+
+---
+
+## Step 5: Define Success Criteria (5 min)
+
+### What is it?
+
+Specific metrics that indicate whether the project achieved its goals.
+
+### How to do it:
+
+**Framework:**
+
+- **User Success** - How users benefit
+- **Business Success** - Revenue, growth, efficiency
+- **Technical Success** - Performance, reliability, scalability
+- **Design Success** - Usability, satisfaction, engagement
+
+**Example (Dog Week):**
+
+```
+Success Criteria:
+
+User Success:
+- 80% of users report reduced coordination stress
+- Average task completion time < 2 minutes
+- 90% task completion rate
+
+Business Success:
+- 1,000 active families by month 6
+- 70% weekly active users
+- $50K MRR by month 12
+
+Technical Success:
+- 99.9% uptime
+- Page load < 2 seconds
+- Zero critical security issues
+
+Design Success:
+- SUS score > 75
+- NPS score > 40
+- 80% feature discoverability
+```
+
+**Your turn:**
+
+```
+Define your success criteria:
+[Your criteria]
+```
+
+---
+
+## Step 6: Review and Refine (5 min)
+
+### Checklist:
+
+**Completeness:**
+
+- ✓ Vision is clear and compelling
+- ✓ Goals are SMART
+- ✓ All stakeholder groups identified
+- ✓ Constraints documented
+- ✓ Success criteria defined
+
+**Quality:**
+
+- ✓ Vision is inspiring and actionable
+- ✓ Goals are measurable and realistic
+- ✓ Constraints are specific and justified
+- ✓ Success criteria are trackable
+
+**AI Support:**
+
+```
+Agent: "Let me review your project brief:
+- Is the vision clear?
+- Are goals measurable?
+- Have we missed any constraints?
+- Can we track these success criteria?"
+```
+
+---
+
+## Step 7: Save Your Project Brief
+
+**Create file:** `A-Project-Brief/project-brief.md`
+
+**Use template from:** `workflows/1-project-brief/project-brief/complete/project-brief.template.md`
+
+**Populate with your content:**
+
+- Vision
+- Business goals
+- Stakeholders
+- Constraints
+- Success criteria
+
+---
+
+## What You've Accomplished
+
+✅ **Clear project vision** - Everyone knows what you're building and why  
+✅ **Measurable goals** - You can track progress and success  
+✅ **Stakeholder map** - You know who to consider in decisions  
+✅ **Documented constraints** - Design decisions have clear boundaries  
+✅ **Success criteria** - You'll know when you've succeeded
+
+---
+
+## Next Steps
+
+**Immediate:**
+
+- Share project brief with stakeholders for feedback
+- Get alignment on vision and goals
+- Confirm constraints are accurate
+
+**Next Module:**
+
+- [Module 03: Identify Target Groups](../module-03-identify-target-groups/module-03-overview.md)
+- Start mapping WHO your users are
+
+---
+
+## Common Questions
+
+**Q: What if I don't have all the information yet?**  
+A: Start with what you know. Mark sections as "TBD" and refine as you learn more. The brief is a living document.
+
+**Q: How detailed should constraints be?**  
+A: Detailed enough to guide decisions. If a constraint will affect design choices, document it specifically.
+
+**Q: Can I change the brief later?**  
+A: Absolutely! The brief evolves as you learn. Update it when new information emerges or priorities shift.
+
+**Q: What if stakeholders disagree on goals?**  
+A: Use the brief to facilitate alignment discussions. Document disagreements and work toward consensus before proceeding.
+
+---
+
+## Tips for Success
+
+**DO ✅**
+
+- Be specific and concrete
+- Make goals measurable
+- Document the "why" behind constraints
+- Get stakeholder input early
+- Keep it concise (2-3 pages max)
+
+**DON'T ❌**
+
+- Write vague, aspirational statements
+- Set unrealistic goals
+- Skip constraint documentation
+- Work in isolation
+- Over-engineer the brief
+
+---
+
+**Your project brief is the foundation for everything that follows. Take the time to get it right!**
+
+[← Back to Module 02](module-02-overview.md) | [Next: Module 03 →](../module-03-identify-target-groups/module-03-overview.md)