diff --git a/src/modules/wds/data/agent-guides/saga/trigger-mapping.md b/src/modules/wds/data/agent-guides/saga/trigger-mapping.md index 015232760..2d8101014 100644 --- a/src/modules/wds/data/agent-guides/saga/trigger-mapping.md +++ b/src/modules/wds/data/agent-guides/saga/trigger-mapping.md @@ -28,18 +28,38 @@ Discover not just WHO your users are, but WHY they act and WHAT triggers their d ## The Trigger Map Structure +**Visual Flow (Left to Right):** + ``` -Business Goals (SMART + Vision) - ↓ -Target Groups (connected to specific goals) - ↓ -Detailed Personas (psychological depth) - ↓ -Usage Goals / Driving Forces - ├── Positive (wishes, desires, aspirations) - └── Negative (fears, frustrations, anxieties) +Business Goals → Product/Solution → Target Groups → Usage Goals +(Vision + (What you're (Who uses it) (Positive Drivers) + SMART building) (Negative Drivers) + Objectives) ``` +**Four-Layer Architecture:** + +1. **Business Goals** (Left) + - Vision statement(s) - inspirational direction + - SMART objectives - measurable targets + - Multiple goals can feed into the product + +2. **Product/Solution** (Center) + - Product name and description + - What the product does + - Central hub connecting goals to users + +3. **Target Groups** (Middle-Right) + - Prioritized personas (Primary 👥, Secondary 👤, etc.) + - Connected to the product + - Detailed psychological profiles + +4. **Usage Goals** (Right) + - **Positive Drivers** (✅ green) - What they want to achieve + - **Negative Drivers** (❌ red) - What they want to avoid + - Separated into distinct groups per target group + - Both types are equally important for design decisions + --- ## Business Goals Layer diff --git a/src/modules/wds/docs/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md b/src/modules/wds/docs/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md index 1fa98b71c..5c585feb9 100644 --- a/src/modules/wds/docs/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md +++ b/src/modules/wds/docs/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md @@ -310,7 +310,7 @@ The WDS Presentation page serves as the primary entry point for designers discov -Module 00: Getting Started with WDS +Module 00: Getting Started with WDS @@ -391,9 +391,60 @@ The WDS Presentation page serves as the primary entry point for designers discov + + + + + + + + +
+ +Module 04: Product Brief + + +

Module 04: Product Brief

+

Create your strategic foundation through AI-guided conversation. Learn how the Product Brief becomes the most powerful prompt you'll ever create - stopping AI hallucinations before they start and making your idea better through 30 structured questions. Everything happens in one environment with zero copy-paste chaos.

+ +
+ + + + + + + + +
+ +Module 05: Trigger Mapping + + +

Module 05: Trigger Mapping

+

Connect business goals to user psychology through 5 structured workshops. Learn the proven Effect Management methodology (20+ years heritage), map both positive and negative psychological drivers, and create a visual one-page strategy map. Includes systematic feature scoring for data-driven prioritization.

+ +
``` -**Rationale:** Four-module structure with video thumbnails (YouTube auto-generates), descriptions, and links to actual lessons. Uses clickable thumbnails linking to YouTube (more reliable than iframes). Provides clear learning path for Stina's hand-holding needs. +**Rationale:** Six-module structure with video thumbnails (YouTube auto-generates), descriptions, and links to actual lessons. Uses clickable thumbnails linking to YouTube (more reliable than iframes). Provides clear learning path for Stina's hand-holding needs. --- diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-00-youtube-show-notes.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-00-youtube-show-notes.md index 8e0badcac..e80026ed3 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/Module-00-youtube-show-notes.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-00-youtube-show-notes.md @@ -38,19 +38,19 @@ Standing at a crossroads? This 15-minute video explores the most important choic 🌊 *WDS Presentation:* -🛠️ *Installation Guide:* + Installation Guide: -📖 *Quick Start:* + Quick Start: -💬 *Discord Community:* -[Discord invite link] + UX-Design channel in the BMad Discord Community: + -📖 *GitHub Discussions:* + GitHub Discussions: -▶️ *Next Module:* Module 01 - Why WDS Matters + Next Module: Module 01 - Why WDS Matters 📚 *Full Course:* diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-notebook-lm-prompt.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-notebook-lm-prompt.md index 552be1eb5..063828331 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-notebook-lm-prompt.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-notebook-lm-prompt.md @@ -24,147 +24,137 @@ Create an engaging 25-30 minute podcast conversation between two hosts discussin **Conversation structure:** -### 1. Opening (2 min) - What Is This? +### 1. Opening (3 min) - The Real Question -The Curious Designer: "I'm starting a new project and I keep hearing about this Product Brief. What exactly is it?" +The Curious Designer: "I already know what app I want to build. Why should I waste time on a document?" -The Practical Guide: "It's a 2-3 page document that answers 5 critical questions: What are we building and why? Who is it for? How will we know it's successful? What else exists? What are our constraints? That's it. Simple, but it changes everything." +The Practical Guide: "That's exactly what everyone thinks. But here's what you're actually missing: You're about to spend weeks or months prompting AI, fighting hallucinations, correcting assumptions, copy-pasting between tools. The Product Brief isn't a document - it's the most powerful prompt you'll ever create. And it makes your idea better." -The Curious Designer: "Okay, but why do I need it?" +The Curious Designer: "Wait, a prompt? I thought it was planning documentation." -The Practical Guide: "Because every time you activate an agent in WDS - whether you're analyzing requirements, sketching interfaces, or writing content - that agent reads your Product Brief first. It's how they understand your project. It's your project's foundation, living right in your repo alongside your code." +The Practical Guide: "That's the paradigm shift. In WDS, the Product Brief IS your prompt - but it's a prompt that every agent reads automatically. You write it once through a guided conversation, and it stops AI hallucinations before they start. No more endless back-and-forth. No more 'but I already told you that.' The AI just knows your project." --- -### 2. How It's Actually Used (5 min) +### 2. One Environment, Zero Copy-Paste (4 min) -The Curious Designer: "So when do I actually use this document?" +The Curious Designer: "OK, but where does this actually happen? Am I jumping between ChatGPT and my code editor?" -The Practical Guide: "Every single time you work on the project. Let me show you: +The Practical Guide: "No! That's the breakthrough. Everything happens in your IDE - your code editor. You create the Product Brief there. You refine it there. Every agent reads it there. Your code lives there. Your documentation lives there. Everything in one place. -When you activate Saga to analyze user needs - she reads the Product Brief to understand your vision and target users. +No cutting and pasting between GPTs. No losing context. No 'wait, where did I save that?' It's all right there, version controlled, accessible to your entire team, ready for every phase of development." -When you activate Sketch to create wireframes - he reads the Product Brief to understand constraints and success criteria. +The Curious Designer: "So I'm not switching tools constantly?" -When you activate Lyra to write content - she reads the Product Brief to match your tone and positioning. - -Every agent starts by reading your Product Brief. It's how they stay aligned with your project's foundation." - -The Curious Designer: "Wait, so it's not just a planning document I create and forget about?" - -The Practical Guide: "Exactly! It's a living reference. And here's the key: it lives in your IDE, right in your project repo. Not on some server somewhere. Not in a Google Doc. Right there in `/docs/A-Product-Brief/product-brief.md` - one click away from your developers, your designers, your entire team." +The Practical Guide: "Never. You activate Saga in your IDE. She asks questions. You answer. The document builds right there in your editor. Then when you move to design, Sketch reads that same document - same place, same context. When you write content, Lyra reads it. When you code, developers read it. One environment, one source of truth, zero friction." --- -### 3. Creating It - The Actual Process (8 min) +### 3. Questions That Make Your Idea Better (6 min) -The Curious Designer: "Okay, I'm sold. How do I create this thing?" +The Curious Designer: "You said this makes my idea better. How?" -The Practical Guide: "After you create your repo in Module 02, you activate Saga the Analyst. She'll see the Product Brief is missing and just start the conversation. It's that simple." +The Practical Guide: "The process is around 30 questions where your answer leads to the next in a fun and engaging way. This challenges you to really think deeply about your product. Not surface-level stuff - deep strategic thinking. And I guarantee - you will feel MORE excited about your idea when you're done, not less. -The Curious Designer: "What does that conversation actually sound like?" +Saga asks things like: 'What problem are you actually solving?' You think you know, but when you have to articulate it clearly, you realize there's a deeper insight. -The Practical Guide: "Let me give you real examples. Saga asks questions like: +Then she digs deeper: 'Who is experiencing this problem?' Not just 'parents' but 'working parents juggling multiple kids' schedules while managing their own careers.' The specificity makes your solution sharper. -'What problem are you solving with this product?' +She asks: 'How will you measure success?' You can't say 'make it better' - you have to think: 'Reduce missed commitments by 50% in month one.' That clarity changes how you design. -You might say: 'Families struggle to coordinate schedules and responsibilities. Everyone's confused about who's doing what.' +She explores constraints: 'What's your budget? Timeline? Team size? Technical limitations?' Naming them isn't limiting - it's liberating. Now you know what you're working with. -Saga reflects back: 'So you're seeing families deal with coordination chaos - unclear responsibilities and missed commitments. Is that right?' +And she keeps going - about your competitive landscape, your differentiation, your stakeholders, your risks. Around 30 questions total that cover everything you need to think through before you start building." -You confirm, and she captures it in the vision section. +The Curious Designer: "So it's not just documentation, it's thinking?" -Then she asks: 'Who specifically is this for?' - -You say: 'Parents managing households - they're the ones coordinating everything.' - -Saga digs deeper: 'What about their situation makes this hard for them specifically?' - -You think out loud: 'They're juggling work, kids' activities, household tasks. Everything's in different apps or just in their heads.' - -Saga captures that, then asks: 'How will you know this is working for them?' - -You might start vague: 'They'll be less stressed.' - -Saga prompts: 'Let's make that measurable. What would less stress look like in numbers?' - -You refine: 'Reduce missed commitments by 50% in the first month. Achieve a satisfaction score of 8/10 or higher.' - -Saga writes it down as a SMART goal. - -See the pattern? She asks, you think out loud, she reflects back to confirm, then captures it. You're thinking together." - -The Curious Designer: "And this is all happening in my IDE?" - -The Practical Guide: "Yes! You're watching the document build in real-time in your code editor. Not in some separate tool. Right there in your project. When Saga asks about constraints, you mention you need to launch in 3 months with a small team. She captures that in the constraints section. When you talk about competitors, she structures it in the competitive landscape section. You're just having a conversation, and the document is writing itself." +The Practical Guide: "Exactly! You're refining your thinking in real-time. And here's the beautiful part - you're watching the document build as you talk. Every insight captured. Every refinement documented. And when your thinking evolves later - which it will - the document is right there at your fingertips. You update it immediately, and every agent sees the improved thinking instantly." --- -### 4. The 5 Questions (Quick Overview) (3 min) +### 4. Man and Machine Collaboration (5 min) -The Curious Designer: "You mentioned 5 questions. What are they?" +The Curious Designer: "Wait, so Saga is writing the document while I talk. Can I see what she's doing?" -The Practical Guide: "Here they are: +The Practical Guide: "Yes! And this is crucial. You review every single change the AI makes. You're not blindly accepting AI output. You're collaborating. -1. **What & Why** - Your vision and positioning. What problem are you solving and why does it matter? +Saga suggests a way to phrase your vision. You see it appear in the document. You think: 'Hmm, not quite right.' You say: 'Actually, let me refine that...' She updates it immediately. -2. **Who** - Your target users. Primary users, secondary users, stakeholders. Be specific. +This is powerful man-and-machine collaboration. You bring the strategic thinking. She brings the structure and ensures nothing gets missed. But you're always in control. You see every change. You approve every word. You refine together." -3. **How We'll Know** - Success criteria. Measurable outcomes. Not 'make it better' but 'reduce missed commitments by 50% in month one.' +The Curious Designer: "So I'm not just prompting and hoping?" -4. **Context** - Competitive landscape. What else exists? How are you different? - -5. **Boundaries** - Constraints. Technical, business, design. What are your limits? - -That's it. Saga walks you through each one. You just answer honestly, she helps you refine it, and captures it in the document." +The Practical Guide: "Never. You're working together in real-time. And because it's all in your IDE with version control, you can see the entire history. You can revert changes. You can branch and experiment. It's not black-box AI - it's transparent collaboration where you're always the decision maker." --- -### 5. The Human-in-the-Loop Approach (4 min) +### 5. Beyond the Brief - The Complete Foundation (4 min) -The Curious Designer: "This sounds different from other AI tools. What makes it different?" +The Curious Designer: "Is the Product Brief the only document I create?" -The Practical Guide: "It's the human-in-the-loop thinking partnership - inherited from the BMad methodology. Most AI tools either replace you or just take orders. WDS works differently. +The Practical Guide: "No! And this is where it gets even better. Saga will also set up additional documents in the same folder - right alongside your Product Brief. -You bring: Your vision, domain expertise, understanding of your users. -Saga brings: Structure, methodology, the right questions at the right time. +Need to define your main features? She creates a Core Features document. -You're not prompting an AI. You're not filling out a form. You're having a conversation with a thinking partner who helps you clarify what's in your head and ensures nothing important gets missed. +Need to specify supported languages? She creates a Language Selection document. -This is where you first experience what 'writing together' actually means. You stay in strategic thinking mode. Saga captures and structures your insights. You see the document building in real-time. You refine together. +Need to define your brand voice? She creates a Tone of Voice document. -The result is truly yours - just better articulated." +Need to capture your visual identity? She creates a Visual Design Brief. + +Whatever is crucial for YOUR project, she sets it up in the same place. Not scattered across tools. Not lost in chat history. Right there in `/docs/A-Product-Brief/` - organized, accessible, version controlled." + +The Curious Designer: "So it's not just one document, it's a complete strategic foundation?" + +The Practical Guide: "Exactly. And every document feeds into the next phase of your project. Your Product Brief leads to Trigger Mapping. Your Core Features lead to Scenarios. Your Tone of Voice leads to Content. Everything connects. Nothing is wasted." --- -### 6. How to Actually Do This (3 min) +### 6. Stopping Hallucinations Before They Start (4 min) -The Curious Designer: "Okay, I'm ready. What's the actual process?" +The Curious Designer: "You mentioned this stops AI hallucinations. How?" -The Practical Guide: "After you create your repo in Module 02: +The Practical Guide: "Because every document in WDS leads to the next. The Product Brief becomes the foundation for Trigger Mapping. Trigger Mapping becomes the foundation for Scenarios. Scenarios become the foundation for Design. -1. Open your IDE -2. Activate Saga: `@wds-saga project-brief` -3. She sees the Product Brief is missing -4. She starts the conversation -5. You answer her questions -6. She writes the document in real-time -7. You review and refine together -8. Done +Each agent reads the previous work before starting. They don't make assumptions. They don't hallucinate features you never asked for. They don't invent user needs that don't exist. -It's that simple. The document lives in `/docs/A-Product-Brief/product-brief.md` in your repo. Not on a server. Not in a separate tool. Right there with your code. +Without this foundation, you're constantly fighting: 'No, I didn't say that.' 'Why did you add this feature?' 'That's not my target user.' You're prompting forever just to get back to what you actually wanted. -And from that point forward, every agent you activate reads it first. When you work on user research, wireframes, content, technical architecture - they all start by understanding your Product Brief. It's your project's foundation." +With the Product Brief, the AI knows your project from the start. Every agent is aligned. Every decision is grounded in your documented strategy. The hallucinations just... stop." + +The Curious Designer: "So I'm not constantly correcting the AI?" + +The Practical Guide: "No. You're collaborating from a shared understanding. The AI isn't guessing - it's reading your Product Brief. It knows your constraints, your users, your goals. You spend your time refining and improving, not correcting and explaining." --- -### 7. Closing (2 min) +### 7. The Bottom Line (3 min) -The Curious Designer: "This makes so much sense. Why haven't I been doing this?" +The Curious Designer: "OK, I'm convinced. What's the actual time investment?" -The Practical Guide: "Because it used to be hard. Now it's just a conversation. Create your repo, activate Saga, talk it out. You'll have your strategic foundation, living in your IDE, referenced by every agent, guiding every decision. +The Practical Guide: "Maybe 2-3 hours for a thorough Product Brief. But here's what you're getting: -That's Module 04. Go create your Product Brief. Your future self will thank you." +You're creating the most powerful prompt possible - one that every agent reads automatically. + +You're stopping weeks of hallucination hell and endless prompting. + +You're setting up one environment where everything lives - no tool switching, no copy-paste. + +You're establishing transparent collaboration where you review every AI change. + +You're refining your thinking through questions that make your idea genuinely better. + +You're creating a living document that's always at your fingertips when your thinking evolves. + +You're building a complete strategic foundation with all supporting documents in one place. + +And you're supercharging your entire process - making the final product better than your original idea. + +That's not time wasted. That's time invested that pays back 10x, 50x, 100x throughout your project." + +The Curious Designer: "When you put it that way... why would I NOT do this?" + +The Practical Guide: "Exactly. Open your IDE. Activate Saga. Start the conversation. Your future self - the one who isn't fighting hallucinations at 2am - will thank you." --- diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-thumbnail-prompt.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-thumbnail-prompt.md index a3f0d6ab0..eb4230bb6 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-thumbnail-prompt.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-thumbnail-prompt.md @@ -5,9 +5,9 @@ Create a 1920x1080px YouTube thumbnail matching the reference image style. **What to Change from Reference:** **Headlines (Left side):** -- Line 1: "BUILD YOUR STRATEGIC" (Rubrik Light, 91pt, white) -- Line 2: "FOUNDATION IN" (Rubrik Bold, 91pt, white) -- Line 3: "30-45 MINUTES!" (Rubrik Bold, 91pt, white) +- Line 1: "INSTANT CLARITY" (Rubrik Light, 91pt, white) +- Line 2: "A PRODUCT BRIEF" (Rubrik Bold, 91pt, white) +- Line 3: "IN 30 QUESTIONS!" (Rubrik Bold, 91pt, white) - Line spacing: 79pt **Module Badge (Bottom-left):** @@ -15,9 +15,9 @@ Create a 1920x1080px YouTube thumbnail matching the reference image style. **Character Activity:** - Keep the woman's angle and position similar as in the first reference image. Keep the character neutral and stylized as it is -- Woman is working at her desk with a large strategic document/blueprint spread out in front of her +- Woman is working at her desk with a large product brief document/blueprint spread out in front of her - She's holding a pen/marker and has just finished writing, looking satisfied at the completed document -- On the desk: sticky notes, coffee cup, the strategic document with visible sections/structure +- On the desk: sticky notes, coffee cup, the product brief with visible sections/structure - Skip the tablet **Background Pattern:** @@ -26,7 +26,7 @@ Create a 1920x1080px YouTube thumbnail matching the reference image style. - Keep as in reference image **Workspace Props:** -- Add: stylized strategic document (visible structure/sections), sticky notes, pen/marker, coffee cup, notebook. No text should be visible or be presented with just scribble or gray markers +- Add: stylized product brief document (visible structure/sections), sticky notes, pen/marker, coffee cup, notebook. No text should be visible or be presented with just scribble or gray markers **Keep Everything Else from Reference:** - do not put light objects behind her face since we need to keep her silhouette clear diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-youtube-show-notes.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-youtube-show-notes.md index 713d1ca2a..f724dc684 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/Module-04-youtube-show-notes.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-04-youtube-show-notes.md @@ -1,6 +1,6 @@ Module 04 - Product Brief - Your Strategic Foundation Through Guided Conversation -[YouTube link to be added] + Teams waste weeks building the wrong thing beautifully. The Product Brief prevents this - a 2-3 page strategic document that answers the 5 questions every project needs before design starts. Create it through AI-guided conversation with Saga, your thinking partner. @@ -15,7 +15,12 @@ Teams waste weeks building the wrong thing beautifully. The Product Brief preven ⏱️ Timestamps -_To be added after video production_ +00:00 The AI Prompting Trap +01:00 The Paradigm Shift - Brief as Ultimate Prompt +02:00 The 30 Questions Process +03:00 One Environment Workflow +04:00 Ending AI Hallucinations +05:00 The Value Proposition 🎯 The 5 Strategic Questions @@ -51,8 +56,8 @@ Data & Privacy - Collection, storage, compliance 📖 *Project Brief Template:* -💬 *Discord Community:* -[Discord invite link] +💬 *UX-Design channel in the BMad Discord Community:* + 📖 *GitHub Discussions:* @@ -60,7 +65,8 @@ Data & Privacy - Collection, storage, compliance ◀️ *Previous Module:* Module 03 - Alignment & Signoff -▶️ *Next Module:* Module 05 - Trigger Mapping (Coming Soon) +▶️ *Next Module:* Module 05 - Trigger Mapping + 📚 *Full Course:* diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-05-notebook-lm-prompt.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-notebook-lm-prompt.md new file mode 100644 index 000000000..e13ca5641 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-notebook-lm-prompt.md @@ -0,0 +1,274 @@ +# Module 05: Trigger Mapping - NotebookLM Prompt + +## Instructions for NotebookLM + +Use this prompt to generate an engaging 6-7 minute audio conversation about Trigger Mapping in WDS. The conversation should feel natural, insightful, and practical - like two colleagues discussing a powerful methodology over coffee. + +--- + +## The Prompt + +Create a 6-7 minute conversational audio deep dive about Trigger Mapping in Whiteport Design Studio. + +**Opening Hook (0:00-0:30)** + +"We've all felt that excitement, right? You have a great idea. You're pumped. In your mind, you can already see how wonderful this is going to be. Next step? Let's jump into an AI dialog and make it happen. We can't wait! + +But what if we told you there's a way to elevate that idea? To focus your imagination even more? A way to refine and map out exactly how valuable your product is going to be - for yourself, for your organization, and for the end user. + +What we're talking about is a single slide that has the power to change how you work with digital products forever. We're talking about the Trigger Map. It's as powerful as it is for a hunter to aim properly before a shot. For a carpenter to measure twice before making a cut. Or for a doctor to diagnose before prescribing. + +With Whiteport Design Studio agents, making a Trigger map only this takes a few minutes, and it becomes the backbone of a solid digital strategy. But still, it is so compact that the end result can be easily fit it on a single presentation slide." + +**The Big Idea (0:30-1:00)** + +"Here's the missing link between strategy and design. Trigger Mapping connects three strategic layers in one visual map: + +First layer: Your business goals - what YOU need to achieve. Your vision, your measurable objectives. + +Second layer: Your target groups - WHO out there in the world will make sure, with their use of the product, that you achieve YOUR goals. Not just any users - the specific people whose behavior drives your success. + +Third layer: Their usage goals - what THEY are trying to achieve. Their psychological drivers - both what they want to accomplish and what they fear or want to avoid. This is THEIR why, not yours. + +The magic is in the connection: Your business goals are achieved THROUGH their usage. They use your product to achieve THEIR goals, and in doing so, they help you achieve YOURS. That's the strategic chain. That's why it's called a Trigger Map - you're mapping what triggers them to act in ways that serve your business. + +It's not just user research. It's strategic psychology mapped visually so everyone on your team understands this chain from business goal to user motivation to design decision. And it's based on 20+ years of proven methodology, not some new trend." + +**The Heritage (1:00-1:30)** + +Quick credibility moment: Trigger Mapping is based on Effect Management methodology from inUse in Sweden - created by Mijo Balic and Ingrid Domingues. This approach has been guiding strategic design for over 20 years. + +WDS modernized it in three key ways. First, simplified the map by removing features so it stays relevant as your product evolves. Second, added negative driving forces - because research shows people work harder to avoid pain than pursue gain. Third, integrated systematic feature scoring so you can prioritize based on real strategic impact, not opinions. + +**The Five Workshops (1:30-4:30)** + +This is the heart of the conversation. Walk through each workshop with energy and practical insight: + +**Workshop 1: Business Goals (30 seconds)** + +"First, you define what winning looks like on TWO levels. Vision - the visionary statement, the aspirational 'why' that motivates your team. Like 'Make remote work sustainable and healthy.' Then you ask the bridging question: 'When this vision is being realized, what will we observe in the world?' That leads to strategic objectives - measurable goals expressed using the SMART method. 'Achieve 5,000 active teams by Q4. Reach 70% retention rate.' Saga guides you through this in 15-20 minutes, connecting aspiration to accountability. This two-level clarity becomes your north star for everything that follows." + +**Workshop 2: Target Groups (45 seconds)** + +"Now the critical question: WHO out there in the world will make sure, with their use of the product, that you achieve your goals? This isn't about abstract segments - it's about real people whose lives your product will touch. Not demographics like 'parents aged 30-45' but behavioral profiles like 'busy working parents juggling multiple kids' schedules, desperately avoiding family conflict over forgotten responsibilities.' You identify 3-5 groups, create detailed personas, then prioritize ruthlessly. Which group's product usage has the highest impact on your business goals? Which is most feasible to reach? This ranking becomes critical because it determines where you focus your design efforts." + +**Workshop 3: Driving Forces (60 seconds)** + +"Here's where it gets psychological. For each persona, you map BOTH sides of motivation. Positive drivers - what do they want to achieve? What pulls them forward? And here's the WDS enhancement - negative drivers. What do they want to avoid? What fears push them to act? + +Think about it: A busy parent isn't just seeking 'better organization.' They're desperately avoiding the shame of missing their kid's soccer game. That negative driver - that fear - is often more powerful than any positive benefit. This is loss aversion in action. People work roughly twice as hard to avoid pain as they do to pursue equivalent gain. + +But here's the validation step: Once you've mapped these drivers, you ask the control questions. If this target group feels this way, would our offering be the best option for them? What alternatives do they have? Why should they care in the first place? These questions validate that your drivers actually connect to your product's value proposition. It's a reality check that prevents you from building for the wrong psychology." + +**Workshop 4: Prioritization (45 seconds)** + +"You can't design for everyone at once. So you prioritize ruthlessly. Which target groups matter most? Which psychological drivers are strongest? This isn't guessing - you're making strategic choices based on business impact and emotional intensity. The output is a ranked list. Your top group's top drivers become your design focus. Everything else is secondary." + +**Workshop 5: Feature Impact (60 seconds)** + +"Now comes the magic. You take your feature ideas and score them systematically against your prioritized drivers. Each feature gets rated on a 0-3 scale: How well does it address the top psychological drivers? You do this for each feature against each top driver, then sum the scores. + +The math is simple but the insight is profound. You end up with a scored feature list where every number traces back through psychological drivers, to target groups, to business goals. No more random feature requests. No more stakeholder opinion battles. Every design decision is backed by strategic data." + +**The Visual Map (4:30-5:00)** + +"The Trigger Map itself is beautifully simple. Business goals at the center. Target groups radiating out, ranked by priority. Their positive and negative drivers connected to each group. It's a one-page strategy document that everyone can understand - stakeholders, developers, designers. + +When someone asks 'why are we building this?' you point to the map. The answer is right there. This feature addresses this psychological driver, for this target group, which supports this business goal. Traceable reasoning. Strategic clarity." + +**The Workflow Integration (5:00-5:30)** + +"And here's what makes WDS different from traditional user research: you have flexibility in how you work. You can do this solo with Saga in your IDE through structured conversation - perfect for individual designers or remote teams. Or you can run it as a physical team workshop with a whiteboard, then upload a photo of your sketch to Saga who will digitize and structure it for you. + +Either way, it all happens in your IDE, right alongside your code and design files. Your answers become living documents that feed directly into the next phase. No separate research tools. No lost context. No copying and pasting between systems. Everything builds on everything. Your Product Brief informs your Trigger Map. Your Trigger Map guides your scenarios. Your scenarios drive your design. It's one continuous strategic thread." + +**The Value Proposition (5:30-6:30)** + +Bring it home with the core benefits: + +"So what do you get for 60-90 minutes of strategic work? First, you stop guessing. Every design decision is backed by mapped psychology and business strategy. Second, you get team alignment. Everyone sees the same strategic picture. No more endless debates about priorities. + +Third, you get systematic feature prioritization. That scored feature list becomes your roadmap, and it's defensible. When stakeholders ask why you're not building their pet feature, you can show them: here's our Trigger Map, here are our top drivers, here's how features score against them. Your feature scores lower. It's not personal - it's strategic. + +Fourth, you get traceable reasoning. Every feature connects to a psychological driver, every driver connects to a target group, every group connects to a business goal. No orphaned features. No random requests. Strategic clarity from top to bottom. + +And finally, you get a long-term reference document. The Trigger Map doesn't become outdated when features change. It stays relevant because it focuses on strategy, not implementation. Update it when your business goals shift or you learn new user psychology. But it's not something you're constantly maintaining." + +**Three Approaches for Different Situations (6:30-7:00)** + +"Now, WDS recognizes that you're not always starting from scratch. You might be in different situations, so we offer three approaches to Trigger Mapping. + +First, the full process we just covered - starting from scratch. Sixty to ninety minutes, five workshops, comprehensive strategic foundation. Perfect when you have no existing documentation and need to build everything from the ground up. + +Second, what if you already have documentation? Vision docs, user research, interview transcripts, project plans - maybe hundreds of pages gathering dust that nobody actually reads? That's where Documentation Synthesis comes in. Thirty to forty-five minutes. Saga analyzes your documentation, validates what's there, fills gaps through conversation, and transforms it all into a single-slide Trigger Map you can actually use. No more pasting 200 pages into AI chats. No more research reports nobody reads. One actionable strategic artifact. + +Third, what if you're in a real hurry? What if you need strategic guidance but don't have even 30 minutes? That's the Value Trigger Chain - or VTC. Fifteen to twenty minutes. You pick ONE strategic objective, identify ONE target group, map ONE key driver - typically negative, because that's often most powerful. One clear chain from business goal to user psychology to design decision. Quick strategic validation when time is tight. + +Think of it like this: Full Trigger Mapping is your comprehensive foundation for major products. Documentation Synthesis transforms existing research into actionable strategy. The Value Trigger Chain is your quick strategic check for focused features. All three are based on the same proven methodology. All three give you traceable reasoning. You just choose the approach that fits your situation." + +**The Closing (7:00-7:10)** + +"So whether you have 90 minutes to build from scratch, 30 minutes to synthesize existing documentation, or 15 minutes for quick validation, you have the tools to stop guessing and start knowing. This is 20 years of proven methodology, modernized and AI-guided for how we work today. + +Stop guessing. Start mapping." + +--- + +## Key Messaging Themes + +**Heritage & Credibility:** +- 20+ years of Effect Management methodology +- Created by pioneers at inUse, Sweden +- Battle-tested, not experimental +- WDS modernization makes it better + +**The Psychology Angle:** +- Both positive AND negative drivers +- Loss aversion principle (pain > gain) +- Emotional intensity matters +- Real human psychology, not surface wants + +**The Strategic Value:** +- Three-layer strategic chain (your goals → their usage → their psychology) +- Visual one-page reference showing all connections +- Systematic feature scoring +- Traceable reasoning for every decision + +**The WDS Advantage:** +- AI-guided through Saga +- Solo conversation or team whiteboard workshop +- Happens in your IDE +- Integrated workflow +- Living strategic document + +**The Practical Payoff:** +- 90 minutes saves months +- Stop guessing, start knowing +- Team alignment +- Defensible priorities + +--- + +## Visual Example: Simplified Trigger Map + +Here's a simplified Trigger Map structure to help explain the visual layout: + +```mermaid +graph LR + BG1["BUSINESS GOAL 1

Visionary Statement 1

Strategic Objectives:
• Strategic Objective 1
• Strategic Objective 2
• Strategic Objective 3"] + + BG2["BUSINESS GOAL 2

Visionary Statement 2

Strategic Objectives:
• Strategic Objective 1
• Strategic Objective 2
• Strategic Objective 3"] + + PRODUCT["Product/Solution Name"] + + TG1["👥 Primary Target Group"] + + TG2["👤 Secondary Target Group"] + + POS1["✅ POSITIVE DRIVERS:
• Positive Usage Goal 1
• Positive Usage Goal 2"] + + NEG1["❌ NEGATIVE DRIVERS:
• Negative Usage Goal 1
• Negative Usage Goal 2"] + + POS2["✅ POSITIVE DRIVERS:
• Positive Usage Goal 1
• Positive Usage Goal 2"] + + NEG2["❌ NEGATIVE DRIVERS:
• Negative Usage Goal 1
• Negative Usage Goal 2"] + + BG1 --> PRODUCT + BG2 --> PRODUCT + PRODUCT --> TG1 + PRODUCT --> TG2 + TG1 --> POS1 + TG1 --> NEG1 + TG2 --> POS2 + TG2 --> NEG2 + + style BG1 fill:#e3f2fd,stroke:#1976d2,stroke-width:3px + style BG2 fill:#e3f2fd,stroke:#1976d2,stroke-width:3px + style PRODUCT fill:#fff9c4,stroke:#f57f17,stroke-width:3px + style TG1 fill:#fff3e0,stroke:#f57c00,stroke-width:2px + style TG2 fill:#fff3e0,stroke:#f57c00,stroke-width:2px + style POS1 fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px + style NEG1 fill:#ffebee,stroke:#c62828,stroke-width:2px + style POS2 fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px + style NEG2 fill:#ffebee,stroke:#c62828,stroke-width:2px +``` + +**Key Visual Elements:** +- **Left (Blue):** Business Goals with vision statements and measurable SMART objectives +- **Center (Yellow):** The Product/Solution being built +- **Middle (Orange):** Target Groups radiating from the product, with priority indicators (👥 primary, 👤 secondary) +- **Right (Green/Red):** Usage Goals separated into positive drivers (✅ green - what they want) and negative drivers (❌ red - what they fear) +- **Arrows:** Show the strategic chain - business goals → product → target groups → their psychological drivers (both positive and negative) + +This one-page map makes the entire strategy visible and accessible to everyone on the team. + +--- + +## How Teams Use the Trigger Map + +**The Trigger Map isn't just created once - it's referenced throughout the entire product lifecycle:** + +### During Strategic Work +- **Workshop clarifies thinking** - Forces teams to articulate assumptions about users +- **Builds deep empathy** - Goes beyond demographics to understand psychological drivers +- **Creates shared understanding** - Everyone aligned on who matters and why +- **Establishes user starting point** - Where users are when they begin their journey + +### For Product Decisions +- **Feature prioritization** - Systematic scoring against top drivers (not opinions) +- **Scope negotiations** - Defend what's in/out with strategic rationale +- **Roadmap planning** - Sequence features by impact on priority drivers +- **MVP definition** - Build what addresses the most important drivers first + +### In Design & UX +- **Scenario creation** - Design realistic user journeys based on actual drivers +- **Content writing** - Messaging that speaks to positive desires and negative fears +- **Page-level features** - What functionality serves which drivers +- **Navigation design** - Paths that help users achieve their goals + +### For Marketing & Sales +- **Value proposition** - Messaging that addresses top psychological drivers +- **Landing page structure** - Sections targeting specific personas and their drivers +- **Ad copy** - Speak directly to what users want and what they fear +- **Sales enablement** - Equip teams with driver-based talking points + +### Ongoing Management +- **Bug prioritization** - Fix what hurts priority drivers most +- **Stakeholder communication** - One-page visual shows strategic rationale +- **Team alignment** - Resolve debates by referencing the map +- **Validation testing** - Test if your assumptions about drivers are accurate + +**The key insight:** This isn't a document you create and file away. It's a living strategic reference that guides every decision from features to marketing to support documentation. + +--- + +## Tone & Style + +- **Conversational but authoritative** - You know this works +- **Practical, not academic** - Focus on real benefits +- **Energetic about the psychology** - This is fascinating stuff +- **Confident about the value** - This prevents expensive mistakes +- **Respectful of the heritage** - Standing on giants' shoulders + +--- + +## What to Emphasize + +✅ The three-layer connection (YOUR goals → WHO achieves them → THEIR goals) +✅ The gap between Product Brief and design (the missing link) +✅ Both positive and negative drivers (the WDS enhancement) +✅ Systematic scoring (data over opinions) +✅ Visual one-page map (accessible to everyone) +✅ 20+ year heritage (proven, not trendy) +✅ 90 minutes prevents months of waste + +--- + +## What to Avoid + +❌ Getting too technical about the methodology +❌ Spending too long on any one workshop +❌ Making it sound complicated or academic +❌ Forgetting to mention the heritage +❌ Skipping the negative drivers emphasis +❌ Not connecting to real business value diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-05-thumbnail-prompt.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-thumbnail-prompt.md new file mode 100644 index 000000000..90d24a688 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-thumbnail-prompt.md @@ -0,0 +1,40 @@ +**IMPORTANT: Use the reference image as your exact style guide. Match all visual elements, colors, layout, and character design.** + +Create a 1920x1080px YouTube thumbnail matching the reference image style. + +**What to Change from Reference:** + +**Headlines (Left side):** +- Line 1: "TRIGGER MAPPING" (Rubrik Light, 91pt, white) +- Line 2: "YOUR ONE SLIDE STRATEGY" (Rubrik Bold, 91pt, white) +- Line 3: "FOR ANY DIGITAL PROJECT!" (Rubrik Bold, 91pt, white) +- Line spacing: 79pt + +**Module Badge (Bottom-left):** +- "05 Trigger Mapping" (Rubrik Regular, 108pt, white on red #ff1744) + +**Character Activity:** +- Keep the woman's angle and position similar as in the first reference image. Keep the character neutral and stylized as it is +- Woman is working with a large visual trigger map spread out in front of her +- She's connecting elements on the map with lines/arrows, showing strategic connections +- On the desk: sticky notes with "Business Goals", "Target Groups", "Drivers" visible as labels +- Expression: focused and strategic, making connections +- Skip the tablet + +**Background Pattern:** +- Clear the background from previous objects except the globe +- Add oversized and toned down strategic mapping elements (connected nodes, mind-map branches, arrows showing flow, target/bullseye icons) +- Keep as in reference image + +**Workspace Props:** +- Add: large trigger map diagram (visible strategic layers), sticky notes with labels, markers/pens, coffee cup, notebook +- The map should show visual hierarchy: center node with radiating connections +- No text should be visible or be presented with just scribble or gray markers + +**Keep Everything Else from Reference:** +- do not put light objects behind her face since we need to keep her silhouette clear +- Top-right branding text +- Character design and style +- Color scheme and layout + +. diff --git a/src/modules/wds/docs/learn-wds/course-explainers/Module-05-youtube-show-notes.md b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-youtube-show-notes.md new file mode 100644 index 000000000..3887e9294 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/course-explainers/Module-05-youtube-show-notes.md @@ -0,0 +1,65 @@ +Module 05 - Trigger Mapping - Connect Business Goals to User Psychology + + +Ever built something beautiful that nobody wanted? Trigger Mapping bridges business strategy to user psychology through 5 structured workshops, creating a visual one-page map that guides every design decision. Based on 20+ years of proven methodology. + +*Free & open-source* | 6 minutes | Core methodology module + +⏱️ Timestamps + +00:00 The Problem - Why Brilliant Ideas Fail +00:41 The Solution - What is a Trigger Map? +01:30 The Three Layers - Business Goals, Target Groups, Usage Goals +02:48 The Psychology - Positive vs Negative Drivers (Loss Aversion) +04:01 Building the Map - The Process & Visual +05:09 The Benefits - Stop Guessing, Start Mapping + +🎯 What You'll Create + +Visual one-page Trigger Map connecting: +• Business Goals → Target Groups → Usage Goals (positive + negative drivers) +• Data-driven feature prioritization +• Clear strategic rationale for every design decision + +📚 Course Resources + +🌊 *WDS Presentation:* + + +📖 *Module 05 Overview:* + + +📖 *Tutorial 05:* + + +📖 *Trigger Mapping Guide:* + + +💬 *UX-Design channel in the BMad Discord Community:* + + +📖 *GitHub Discussions:* + + +◀️ *Previous Module:* Module 04 - Product Brief + + +▶️ *Next Module:* Module 06 - Scenarios (Coming Soon) + +📚 *Full Course:* + + +⚡ Key Insight + +Negative drivers (fears/pains) are often more powerful than positive ones. Loss aversion: people work twice as hard to avoid pain as to pursue equivalent gain. + +📖 Heritage + +Based on Effect Management (Mijo Balic & Ingrid Domingues, inUse Sweden) and Impact Mapping (Gojko Adzic) + + +🎨 About WDS + +AI-augmented design methodology by Mårten Angner (Whiteport, Sweden). 90 minutes of strategic work saves months of building the wrong things. 🎯 + +#TriggerMapping #UserPsychology #FeaturePrioritization #WDS #StrategicDesign diff --git a/src/modules/wds/docs/learn-wds/course-explainers/module-01-YOUTUBE-SHOW-NOTES.md b/src/modules/wds/docs/learn-wds/course-explainers/module-01-YOUTUBE-SHOW-NOTES.md index 8eb0b412c..a24480be2 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/module-01-YOUTUBE-SHOW-NOTES.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/module-01-YOUTUBE-SHOW-NOTES.md @@ -40,8 +40,8 @@ This 30-minute deep dive explores why designers are irreplaceable in the AI era 📚 *Linchpin Book by Seth Godin:* -💬 *Discord Community:* -[Discord invite link] +💬 *UX-Design channel in the BMad Discord Community:* + 📖 *GitHub Discussions:* diff --git a/src/modules/wds/docs/learn-wds/course-explainers/module-02-YOUTUBE-SHOW-NOTES.md b/src/modules/wds/docs/learn-wds/course-explainers/module-02-YOUTUBE-SHOW-NOTES.md index cf9f1a561..6b7251abe 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/module-02-YOUTUBE-SHOW-NOTES.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/module-02-YOUTUBE-SHOW-NOTES.md @@ -44,14 +44,14 @@ Sound familiar? This 6-minute guided walkthrough takes you from complete beginne 🌊 *WDS Presentation:* [WDS Presentation](https://whiteport.com/whiteport-design-studio/) -💻 *Download Cursor:* [Download Cursor](https://cursor.sh) +💻 *Download Cursor:* -📥 *Download VS Code:* [Download VS Code](https://code.visualstudio.com) +📥 *Download VS Code:* -📥 *GitHub:* [GitHub](https://github.com) +📥 *GitHub:* -💬 *Discord Community:* -[Discord invite link] +💬 *UX-Design channel in the BMad Discord Community:* + 📖 *GitHub Discussions:* diff --git a/src/modules/wds/docs/learn-wds/course-explainers/module-03-YOUTUBE-SHOW-NOTES.md b/src/modules/wds/docs/learn-wds/course-explainers/module-03-YOUTUBE-SHOW-NOTES.md index ae5b50859..2a69dc70c 100644 --- a/src/modules/wds/docs/learn-wds/course-explainers/module-03-YOUTUBE-SHOW-NOTES.md +++ b/src/modules/wds/docs/learn-wds/course-explainers/module-03-YOUTUBE-SHOW-NOTES.md @@ -34,27 +34,28 @@ Struggling with the business side of design? Feel uncomfortable talking about mo 🌊 *WDS Presentation:* -📖 *Project Pitch Guide:* +Project Pitch Guide: -📖 *Service Agreement Templates:* +Service Agreement Templates: -� *Discord Community:* -[Discord invite link] +UX-Design channel in the BMad Discord Community: + -📖 *GitHub Discussions:* +GitHub Discussions: -◀️ *Previous Module:* Module 02 - Installation & Setup +Previous Module: Module 02 - Installation & Setup -▶️ *Next Module:* Module 04 - Product Brief (Coming Soon) +Next Module: Module 04 - Product Brief + -📚 *Full Course:* +Full Course: -🎯 *When to Use This Module:* +✅ *When to Use This Module:* ✅ Consultant pitching to client ✅ Employee seeking stakeholder approval ✅ You struggle with business conversations diff --git a/src/modules/wds/docs/learn-wds/course-explainers/trigger-map-example.jpg b/src/modules/wds/docs/learn-wds/course-explainers/trigger-map-example.jpg new file mode 100644 index 000000000..8b541238f Binary files /dev/null and b/src/modules/wds/docs/learn-wds/course-explainers/trigger-map-example.jpg differ diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-01-missing-link.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-01-missing-link.md new file mode 100644 index 000000000..e0e9cb962 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-01-missing-link.md @@ -0,0 +1,237 @@ +# Lesson 1: The Missing Link + +**Why Product Brief Alone Isn't Enough** + +--- + +## The Problem + +You've created a brilliant Product Brief. You know: + +- **WHAT** you're building (vision, positioning) +- **WHO** it's for (target users) +- **WHY** it matters (business goals) +- **HOW** you'll measure success (metrics) + +You're ready to start designing, right? + +**Wrong.** + +There's a critical gap between your Product Brief and your design decisions. A gap that causes even well-planned projects to build the wrong things beautifully. + +--- + +## The Gap: Strategy to Design + +Your Product Brief tells you the business strategy. But it doesn't tell you: + +- **What actually motivates your users?** +- **What psychological triggers drive their behavior?** +- **Which features will have the most impact?** +- **Why users would choose your solution over alternatives?** + +Without this connection, you're guessing. And guessing is expensive. + +--- + +## What Happens When You Skip This Step + +### Scenario 1: The Feature Factory + +**The team says:** "Let's build everything users might want!" + +**The result:** +- 50 features, none deeply solving real problems +- Users overwhelmed by complexity +- Development time wasted on low-impact features +- No clear prioritization strategy + +**The cost:** 6 months of development, mediocre product + +### Scenario 2: The Assumption Trap + +**The team says:** "We know what users need!" + +**The result:** +- Features based on team assumptions, not user psychology +- Beautiful designs that don't address real pain points +- Users don't adopt because it doesn't match their mental models +- Expensive redesigns after launch + +**The cost:** 3 months of design work thrown away + +### Scenario 3: The Stakeholder Whiplash + +**The team says:** "Let's ask stakeholders what to build!" + +**The result:** +- Every stakeholder has different opinions +- Features change based on who spoke last +- No strategic foundation for decisions +- Team loses confidence in the direction + +**The cost:** Endless meetings, demoralized team, delayed launch + +--- + +## The Real Cost + +**Time:** +- Weeks of designing the wrong features +- Months of building things nobody uses +- Endless debates about priorities + +**Money:** +- Wasted development resources +- Expensive post-launch pivots +- Lost market opportunity + +**Morale:** +- Team frustration from constant changes +- Designer confidence eroded +- Stakeholder trust damaged + +--- + +## What's Missing: The Strategic Bridge + +The Product Brief tells you **where you're going**. + +But you need to know **why users will come with you**. + +That's where Trigger Mapping comes in. + +--- + +## What Trigger Mapping Does + +Trigger Mapping creates the strategic bridge between business goals and user psychology: + +**It answers:** +- Which user groups can actually help you achieve your business goals? +- What positive outcomes are they seeking? +- What negative outcomes are they trying to avoid? +- Which psychological drivers are strongest? +- Which features will have the most strategic impact? + +**It provides:** +- A visual map connecting business goals → target groups → psychological drivers +- Prioritized list of user groups ranked by strategic value +- Scored feature list based on psychological impact +- Clear reasoning for every design decision +- Team alignment around strategic priorities + +--- + +## The Strategic Sequence + +Here's how it all connects: + +``` +Product Brief + ↓ +Trigger Map + ↓ +Design Decisions + ↓ +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 +**Features** = Implementations that deliver on both + +--- + +## A Generic Example + +**Product Brief says:** +- Vision: Help busy professionals stay healthy +- Target: Working professionals +- Goal: 10,000 active users in 6 months + +**But you still don't know:** +- Which professionals? (Executives? Freelancers? Remote workers?) +- What's their real pain? (Time? Motivation? Knowledge?) +- What are they trying to avoid? (Burnout? Weight gain? Medical issues?) +- Which features matter most? (Meal planning? Quick workouts? Sleep tracking?) + +**Trigger Mapping reveals:** +- **Top Group:** Remote workers (30-45, sedentary jobs) +- **Positive Driver:** Want to feel energized during work hours +- **Negative Driver:** Fear of burnout and health decline +- **Top Feature:** 5-minute desk exercises with energy tracking +- **Why:** Addresses both drivers, fits into work schedule, immediate benefit + +Now you know exactly what to design and why. + +--- + +## Your Insurance Policy + +Think of Trigger Mapping as insurance against: + +- ❌ Building features nobody uses +- ❌ Designing for the wrong user groups +- ❌ Guessing at priorities +- ❌ Stakeholder opinion battles +- ❌ Post-launch pivots + +It's 60-90 minutes of strategic work that saves months of wasted effort. + +--- + +## The Investment vs. Payoff + +**Investment:** +- 60-90 minutes with Saga running 5 workshops +- Structured questions that pull out strategic insights +- Visual map that everyone can understand + +**Payoff:** +- Clear feature prioritization (no more guessing) +- Team alignment around user psychology +- Confident design decisions backed by strategy +- Features that actually drive business goals +- Traceable reasoning for every choice + +**ROI:** 90 minutes saves 3-6 months of building the wrong things + +--- + +## What You'll Learn Next + +In the following lessons, you'll discover: + +- The 20+ year heritage of this methodology (proven, not trendy) +- How the 5 workshops actually work (step by step) +- The power of negative drivers (why fear is stronger than desire) +- How to create the visual Trigger Map (one-page strategy) +- How to score features systematically (data-driven decisions) + +--- + +## Key Takeaways + +✅ **Product Brief alone isn't enough** - It tells you business strategy, not user psychology +✅ **The gap is expensive** - Weeks of wasted design, months of wrong features +✅ **Trigger Mapping bridges the gap** - Connects business goals to psychological drivers +✅ **It's strategic insurance** - 90 minutes prevents months of rework +✅ **You get clarity** - Know exactly what to design and why + +--- + +## Reflection Questions + +Before moving to the next lesson, consider: + +1. Have you ever built features that users didn't adopt? What was missing? +2. How do you currently decide which features to prioritize? +3. What would change if you knew exactly which psychological drivers mattered most? + +--- + +[← Back to Module Overview](module-05-overview.md) | [Next: Lesson 2 - Heritage & Evolution →](lesson-02-heritage-evolution.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-02-heritage-evolution.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-02-heritage-evolution.md new file mode 100644 index 000000000..7676ff2a9 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-02-heritage-evolution.md @@ -0,0 +1,364 @@ +# Lesson 2: The Heritage & Evolution + +**From Effect Management to Trigger Mapping** + +--- + +## The Foundation: Effect Management + +Trigger Mapping isn't a new trend. It's built on 20+ years of proven methodology. + +The foundation is **Effect Management**, created by **Mijo Balic** and **Ingrid Domingues (Ottersten)** at **inUse** in Sweden. Their pioneering work on connecting business goals to user behavior through visual mapping - the **Effect Map** - revolutionized how we think about strategic software design. + +This methodology gained wider recognition through Gojko Adzic's book **"Impact Mapping: Making a Big Impact with Software Products and Projects"** (2012), which acknowledges Effect Mapping as a key influence. + +**Why this matters:** You're not learning an experimental approach. You're learning a battle-tested methodology that's guided strategic design for over two decades. + +--- + +## What is Effect Mapping? + +Effect Mapping is the original model that connects business goals to user behavior through a visual map. + +**The core structure:** +1. **Business Goals** - What the organization wants to achieve +2. **Actors** - Who can help achieve those goals (or prevent them) +3. **Impacts** - How actors' behavior changes +4. **Deliverables** - What features enable those behavior changes + +**The key insight:** Software creates value through changing user behavior. If you understand whose behavior needs to change and how, you can design the right features. + +**The visual format:** A mind-map style diagram radiating from business goals, showing the chain of reasoning from strategy to features. + +--- + +## Why WDS Modernized It: Trigger Mapping + +Effect Mapping is brilliant, but WDS adapted it for modern projects with three key improvements: + +### 1. Simplified for Longevity + +**Original Effect Mapping:** +- Includes features/deliverables on the map itself +- Map becomes outdated as features change +- Requires constant updating + +**WDS Trigger Mapping:** +- Removes features from the map +- Focuses only on strategic connections +- Map stays relevant even as features evolve +- Features are scored separately (Workshop 5) + +**Why this matters:** Your Trigger Map becomes a long-term strategic document, not a feature list that needs constant maintenance. + +### 2. Enhanced with Negative Psychology + +**Original Effect Mapping:** +- Focuses primarily on positive impacts (what users want to achieve) +- Less emphasis on what users want to avoid + +**WDS Trigger Mapping:** +- Explicitly maps **both** positive and negative driving forces +- Positive: What users want to achieve (goals, benefits, gains) +- Negative: What users want to avoid (fears, frustrations, pain) + +**Why this matters:** Research shows people work harder to avoid pain than pursue gain (loss aversion). Negative drivers are often more powerful motivators than positive ones. + +**Generic example:** +- **Positive driver:** "Want to stay organized" +- **Negative driver:** "Fear of missing important deadlines and looking unprofessional" +- **Which is stronger?** The fear of embarrassment drives more urgent action than the desire for organization. + +### 3. Integrated Systematic Scoring + +**Original Effect Mapping:** +- Prioritization happens through discussion +- Less formal scoring system + +**WDS Trigger Mapping:** +- Workshop 5: Feature Impact Analysis +- Systematic scoring of features against prioritized drivers +- Quantified impact scores for data-driven decisions +- Clear ranking of features by strategic value + +**Why this matters:** You get objective feature prioritization based on strategic impact, not opinions or politics. + +--- + +## The Three Strategic Layers + +Both Effect Mapping and Trigger Mapping use three core layers. Understanding these is essential: + +### Layer 1: Business Goals (Your WHY) + +**What it is:** +- Vision that motivates the team +- SMART objectives that measure success + +**Example:** +- Vision: "Make family dog care stress-free" +- Objective: "Achieve 10,000 active families by Q4" + +**Why it matters:** Everything traces back to these goals. Every feature must support them. + +### Layer 2: Target Groups (The WHO) + +**The core question:** +WHO out there in the world will make sure, with their use of the product, that you achieve your goals? + +**What it is:** +- Real people whose product usage drives your business success +- Specific user types from specific ICPs (Ideal Customer Profiles) +- Not demographics - behavioral and contextual profiles +- Not abstract segments - actual humans in real situations + +**Example:** +- Not: "Parents aged 30-45" +- Yes: "Busy working parents juggling multiple kids' schedules and family dog care" + +**Why it matters:** Different groups have different psychological drivers. You can't design for everyone. The product must give more value than the pain of using it for these specific people. + +### Layer 3: Usage Goals (Their WHY) + +**What it is:** +- Positive drivers: What users want to achieve +- Negative drivers: What users want to avoid + +**Example:** +- Positive: "Want to ensure dog is well cared for" +- Negative: "Fear of family conflict over forgotten responsibilities" + +**Why it matters:** This is the psychology that drives behavior. Design must address both sides. + +--- + +## The Core Insight: Flow of Value + +Here's the fundamental principle behind both methodologies: + +**Any software is about flow of value.** + +There's always a group of people (WHO) out there in the world who, through their use of the software in the intended way, make your success happen. + +**The critical chain:** +1. **WHO** - Specific people from specific ICPs +2. **Out there in the world** - Real people whose lives your product touches +3. **Will make sure** - Product must be used, and used in the intended way +4. **With their use of the product** - Product must give more value than pain of using it +5. **That you achieve your goals** - Their usage must connect to measurable business objectives + +These users have their own goals: +- **GAIN** - Benefits and positive outcomes they achieve +- **PAIN** - Resistance and friction they experience + +**The key equation:** Make GAIN > PAIN for users, so through their usage, they add value to your system. + +**Generic example:** +- **Your goal:** Increase subscription revenue +- **WHO:** Freelancers managing multiple clients (real people out there) +- **Their gain:** Organized project tracking, professional client communication +- **Their pain:** Learning curve, monthly cost, data migration +- **Your job:** Make gain significantly outweigh pain (value > usage pain) +- **Their usage:** They subscribe and use it for client management (intended way) +- **Result:** Through their usage, you hit revenue goals + +--- + +## How Prioritization Works + +When all three layers are prioritized, you have perfect guidance for design: + +**The prioritization cascade:** +1. Which business goal matters most right now? +2. Which target group can best help achieve that goal? +3. Which of their psychological drivers are strongest? +4. Which features best address those drivers? + +**Generic example:** +- **Top goal:** Increase user retention +- **Top group:** Power users (high engagement, at risk of churn) +- **Top driver (negative):** Fear of losing their data/work if they switch +- **Top feature:** Advanced export and backup capabilities +- **Why:** Addresses their fear, increases switching cost, improves retention + +--- + +## Why This Approach Works + +**It's traceable:** +- Every feature connects to a psychological driver +- Every driver connects to a target group +- Every group connects to a business goal +- No orphaned features, no guesswork + +**It's visual:** +- One-page map everyone can understand +- Stakeholders see the strategic connections +- Designers reference it for every decision +- Developers understand the "why" + +**It's flexible:** +- Business goals change? Update the map +- New user insights? Add to the map +- Features evolve? Map stays relevant +- Living strategic document + +**It's proven:** +- 20+ years of successful projects +- Used by organizations worldwide +- Adapted and refined over time +- Battle-tested methodology + +--- + +## Three Approaches: Choose Your Path + +WDS offers three ways to apply Trigger Mapping methodology, depending on your situation: + +### 1. Full Trigger Mapping (Starting from Scratch) + +**What it is:** +- Complete 5-workshop process +- Deep psychological mapping +- Systematic feature scoring +- Comprehensive strategic foundation + +**When to use:** +- Major product initiatives +- No existing documentation +- 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) + +--- + +### 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) + +--- + +### 3. Documentation Synthesis (Existing Research) + +**What it is:** +- Extract strategic elements from existing docs +- Organize research into actionable Trigger Map +- Identify gaps and validate assumptions +- Transform hundreds of pages into single-slide reference + +**When to use:** +- You have extensive vision/strategy documents +- User research or interview transcripts exist +- Project plans or roadmaps already created +- 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) + +**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. + +--- + +### Which Should You Use? + +**Use Full Trigger Mapping if:** +- Starting from scratch with no documentation +- Major product or feature initiative +- Multiple user groups to consider +- Need to prioritize among many features +- 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 +- Need to cut through extensive research +- 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. + +--- + +## The WDS Advantage + +By modernizing Effect Mapping into Trigger Mapping, WDS gives you: + +✅ **Proven methodology** - 20+ years of heritage, not experimental +✅ **Longer shelf life** - Map stays relevant as features evolve +✅ **Deeper psychology** - Both positive and negative drivers +✅ **Systematic scoring** - Data-driven feature prioritization +✅ **Three flexible approaches** - Full, lightweight, or synthesis from docs +✅ **AI-guided process** - Saga facilitates all workshops +✅ **Integrated workflow** - Lives in your IDE with your code + +--- + +## What You'll Learn Next + +Now that you understand the foundation and evolution, the next lesson walks through the 5 workshops step by step: + +1. Business Goals +2. Target Groups +3. Driving Forces +4. Prioritization +5. Feature Impact + +You'll see exactly how to create your Trigger Map. + +--- + +## Key Takeaways + +✅ **Effect Management is the foundation** - Created by Mijo Balic and Ingrid Domingues at inUse, Sweden +✅ **20+ years of proven results** - Not a trend, a battle-tested methodology +✅ **WDS modernized it** - Simplified map, added negative drivers, integrated scoring +✅ **Three strategic layers** - Business Goals → Target Groups → Usage Goals +✅ **Core insight** - Make user GAIN > PAIN, they drive your success +✅ **Traceable reasoning** - Every feature connects back to business goals + +--- + +## Further Reading + +**Books:** +- [Impact Mapping by Gojko Adzic](https://www.amazon.com/Impact-Mapping-Software-Products-Projects/dp/0955683645) - Building on Effect Mapping concepts + +**Online:** +- [impactmapping.org](https://www.impactmapping.org) - Resources and community + +--- + +[← Back to Lesson 1](lesson-01-missing-link.md) | [Next: Lesson 3 - The Five Workshops →](lesson-03-five-workshops.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-03-five-workshops-overview.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-03-five-workshops-overview.md new file mode 100644 index 000000000..c0142c6f7 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-03-five-workshops-overview.md @@ -0,0 +1,459 @@ +# Lesson 3: The Five Workshops Overview + +**Your Roadmap to Strategic Clarity** + +--- + +## What This Lesson Does + +Before you dive into each workshop, let's step back and see the complete picture. This lesson gives you a comfortable understanding of the entire Trigger Mapping process - what happens, why it happens, and how it all fits together. + +**You'll learn:** +- The flow of all 5 workshops +- How each workshop builds on the previous one +- What you'll create at each stage +- Why the process works +- What to expect when working with Saga + +**Time:** 10-12 minutes +**Goal:** Feel confident and prepared for the workshops ahead + +--- + +## The Big Picture + +Trigger Mapping happens through **5 structured workshops** facilitated by Saga the Analyst. Think of it as a guided conversation where Saga asks strategic questions and you provide the thinking. + +**Total time:** 60-90 minutes +**Format:** Conversational - like talking to a strategic consultant +**Output:** Complete Trigger Map + scored feature list +**Your role:** Provide strategic insight and make decisions +**Saga's role:** Ask the right questions, ensure nothing is missed, document everything + +--- + +## Why Five Workshops? + +Each workshop answers one critical strategic question: + +1. **Workshop 1: Business Goals** → "What does winning look like?" +2. **Workshop 2: Target Groups** → "WHO will make this happen through their product use?" +3. **Workshop 3: Driving Forces** → "What psychology drives their behavior?" +4. **Workshop 4: Prioritization** → "What matters most?" +5. **Workshop 5: Feature Impact** → "Which features have highest strategic impact?" + +**Together, they create a complete chain** from business goals to feature decisions. + +--- + +## The Flow: How Workshops Connect + +Each workshop builds on what came before: + +``` +Workshop 1: Business Goals + ↓ + "To achieve these goals, WHO do we need?" + ↓ +Workshop 2: Target Groups + ↓ + "What drives THESE people's behavior?" + ↓ +Workshop 3: Driving Forces + ↓ + "Which groups and drivers matter MOST?" + ↓ +Workshop 4: Prioritization + ↓ + "Which features address our TOP priorities?" + ↓ +Workshop 5: Feature Impact + ↓ +Strategic Roadmap +``` + +**The result:** Every feature traces back through drivers → groups → goals. No guesswork, no orphaned features. + +--- + +## What You'll Create in Each Workshop + +### Workshop 1: Business Goals (15-20 min) + +**You'll define:** +- Vision statement (visionary statement - aspirational) +- 3-5 strategic objectives (measurable, using SMART method) +- Connection between aspiration and measurement + +**Example output:** +- Vision: "Make remote work sustainable and healthy" +- Strategic Objectives: "5,000 active teams by Q4", "70% retention rate" + +**Why it matters:** Everything traces back to these goals. + +--- + +### Workshop 2: Target Groups (20-25 min) + +**You'll identify:** +- 3-5 user groups whose product usage drives your success +- Rich personas with context, goals, frustrations, fears +- Priority ranking by strategic value + +**Example output:** +- Group 1: Remote Team Leads (managing 5-10 people, fear team burnout) +- Group 2: Solo Remote Workers (isolation, need structure) +- Group 3: Remote Executives (organizational visibility) + +**Why it matters:** Different groups have different psychological drivers. You can't design for everyone. + +--- + +### Workshop 3: Driving Forces (20-30 min) + +**You'll map:** +- Positive drivers (what users want to achieve) +- Negative drivers (what users want to avoid) +- For each prioritized persona + +**Example output:** +- Positive: "Want to demonstrate effective leadership" +- Negative: "Fear team burnout without noticing" (often more powerful) + +**Why it matters:** This is the psychology that drives behavior. Design must address both sides. + +--- + +### Workshop 4: Prioritization (15-20 min) + +**You'll rank:** +- Target groups by strategic value +- Psychological drivers by emotional intensity +- Top 5-7 drivers become your scoring criteria + +**Example output:** +1. Remote Team Leads (highest impact) +2. Fear of team burnout (most urgent driver) +3. Want to demonstrate leadership (career driver) + +**Why it matters:** Creates focus. Not everything can be priority #1. + +--- + +### Workshop 5: Feature Impact (20-30 min) + +**You'll score:** +- 10-20 feature ideas against top drivers +- Each feature rated 0-3 on each driver +- Total scores create prioritized roadmap + +**Example output:** +- Daily team pulse check: 9 points (addresses top fears) +- Team chat: 3 points (lower strategic impact) + +**Why it matters:** Data-driven roadmap. Every feature justified by strategy. + +--- + +## What Makes This Process Comfortable + +### It's Conversational + +**Not this:** Fill out complex forms and templates +**This:** Answer Saga's questions in natural language + +**Example:** +- **Saga:** "What's the grand ambition behind this project?" +- **You:** "We want to make remote work sustainable and healthy for distributed teams." +- **Saga:** "Great. When that vision is being realized, what will we observe in the world?" + +### It's Guided + +**You're never stuck wondering:** +- "What should I think about next?" +- "Am I missing something important?" +- "Is this specific enough?" + +**Saga ensures:** +- Nothing is missed +- Vague answers get challenged +- Strategic focus is maintained +- Everything is documented + +### It's Iterative + +**You can:** +- Refine answers as you go +- Come back and adjust +- Challenge your own assumptions +- Update as you learn + +**Not set in stone:** The Trigger Map evolves with your understanding. + +### It's Practical + +**No theory for theory's sake:** +- Every question has a purpose +- Every answer informs design +- Every output is actionable +- Complete in 60-90 minutes + +--- + +## What to Expect: Your Experience + +### Before You Start + +**Preparation:** +- Have your Product Brief handy (reference for context) +- Set aside 60-90 minutes (can pause between workshops) +- Be ready to think strategically +- Don't worry about perfection - you can refine later + +### During the Workshops + +**The rhythm:** +1. Saga asks a question +2. You think and respond +3. Saga probes deeper or moves forward +4. Saga documents your answers +5. Repeat until workshop complete + +**Your mindset:** +- Be specific (avoid generic statements) +- Think about real people and real psychology +- Challenge your assumptions +- Stay honest about unknowns +- Connect everything back to business goals + +### After You Finish + +**You'll have:** +- Complete Trigger Map (one-page strategic document) +- Scored feature list (data-driven roadmap) +- Clear reasoning for every decision +- Alignment tool for your team +- Foundation for all design work + +--- + +## Common Questions + +### "What if I don't know the answer to something?" + +**That's valuable information.** Saga will help you identify: +- What you need to research +- What assumptions you're making +- Where you need user input + +**It's okay to say:** "I'm not sure - we'd need to validate that with users." + +### "Can I change my answers later?" + +**Absolutely.** The Trigger Map is a living document. As you: +- Learn from users +- Test assumptions +- Gather data +- Refine strategy + +You can update the map. The structure stays, the content evolves. + +### "What if I have more than 5 target groups?" + +**Start with 3-5 most strategic.** You can: +- Focus on highest-impact groups first +- Add more later if needed +- Combine similar groups + +**Remember:** Trying to serve everyone equally means serving no one well. + +### "How technical do I need to be?" + +**Not at all.** This is about: +- Strategic thinking +- User psychology +- Business goals +- Prioritization + +**Not about:** Code, architecture, technical implementation. + +--- + +## How Saga Helps You Succeed + +### Saga Asks the Right Questions + +**Structured inquiry:** +- Starts broad, gets specific +- Challenges vague answers +- Ensures completeness +- Maintains strategic focus + +### Saga Documents Everything + +**You don't need to:** +- Take notes +- Format outputs +- Track what you've covered +- Remember previous answers + +**Saga handles:** All documentation and organization. + +### Saga Keeps You on Track + +**Prevents:** +- Jumping ahead +- Missing critical steps +- Getting lost in details +- Losing strategic thread + +**Ensures:** Logical flow from goals to features. + +--- + +## What's Different from Traditional Approaches + +### Traditional: Feature Brainstorming + +**Problem:** +- "What features should we build?" +- No connection to strategy +- Loudest voice wins +- Orphaned features + +### Trigger Mapping: Strategic Foundation + +**Approach:** +- "What psychology drives our target users?" +- Every feature traces to strategy +- Data-driven decisions +- Complete traceability + +--- + +### Traditional: Demographic Personas + +**Problem:** +- "Males 25-40 with college degrees" +- Doesn't explain behavior +- Can't design from this + +### Trigger Mapping: Behavioral Profiles + +**Approach:** +- "Busy working parents juggling multiple kids' schedules, fearing family conflict" +- Explains psychology +- Actionable for design + +--- + +### Traditional: All Features Equal + +**Problem:** +- "Everything is important" +- No prioritization +- Diluted focus + +### Trigger Mapping: Scored Impact + +**Approach:** +- Feature A: 9 points (addresses top fears) +- Feature B: 3 points (nice-to-have) +- Clear priorities + +--- + +## The Value You Get + +### Strategic Clarity + +**Before:** "We should probably build X because competitors have it" +**After:** "Feature X scores 9 because it addresses our #1 persona's top fear, which drives our retention goal" + +### Team Alignment + +**Before:** Debates about what to build +**After:** Shared understanding of strategy, priorities, and reasoning + +### Defensible Decisions + +**Before:** "I think this is important" +**After:** "Here's the Trigger Map showing why this matters" + +### Design Confidence + +**Before:** Guessing what users need +**After:** Knowing what psychology drives behavior + +--- + +## Getting Ready for the Workshops + +### Mindset + +**Come with:** +- ✅ Openness to strategic thinking +- ✅ Willingness to prioritize ruthlessly +- ✅ Curiosity about user psychology +- ✅ Commitment to specificity + +**Leave behind:** +- ❌ Attachment to pet features +- ❌ "Everyone is our user" thinking +- ❌ Fear of making choices +- ❌ Generic "wants" statements + +### Preparation + +**Have ready:** +- Your Product Brief (for context) +- Understanding of business goals +- Initial thoughts on user groups +- List of feature ideas (for Workshop 5) + +**Don't need:** +- Perfect answers +- Complete certainty +- Technical details +- Finished designs + +--- + +## What's Next + +The next five lessons dive deep into each workshop: + +- **Lesson 4:** Workshop 1 - Business Goals (vision + SMART 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) +- **Lesson 8:** Workshop 5 - Feature Impact (scored roadmap) + +**Each lesson explains:** +- What the workshop does +- How it works +- What you'll create +- Common mistakes to avoid +- Tips for success + +**After the lessons:** Tutorial 05 walks you through all 5 workshops step-by-step with Saga. + +--- + +## Key Takeaways + +✅ **5 workshops, 60-90 minutes** - Structured, guided process +✅ **Each builds on previous** - Logical flow from goals to features +✅ **Conversational format** - Natural dialogue with Saga +✅ **Strategic foundation** - Every feature traces to psychology and goals +✅ **Practical outputs** - Trigger Map + scored feature list +✅ **Iterative and refinable** - Can update as you learn +✅ **No technical skills needed** - Strategic thinking only + +**You're ready.** The workshops are designed to guide you through strategic thinking you might not have done before. Trust the process, be specific, and let Saga help you create strategic clarity. + +--- + +[← 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* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-04-workshop-1-business-goals.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-04-workshop-1-business-goals.md new file mode 100644 index 000000000..41f4e06d4 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-04-workshop-1-business-goals.md @@ -0,0 +1,274 @@ +# 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* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-05-workshop-2-target-groups.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-05-workshop-2-target-groups.md new file mode 100644 index 000000000..fa2bebc53 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-05-workshop-2-target-groups.md @@ -0,0 +1,504 @@ +# Lesson 4: Workshop 2 - Target Groups + +**Who Is Ensuring Our Success?** + +--- + +## The Core Question + +**Identify WHO out there in the world will make sure, with their use of the product, that you achieve your goals.** + +This question contains the entire chain of value creation. Let's break it down: + +### Breaking Down the Question + +**"WHO"** +- Which representative from which ICP (Ideal Customer Profile)? +- Specific behavioral and contextual profiles +- Not demographics, but real people with real contexts + +**"Out there in the world"** +- These are real people whose lives your product needs to touch +- Not abstract user segments, but actual humans in specific situations +- Your product must reach and impact their reality + +**"Will make sure"** +- A product needs to be used, and used in the intended way +- Usage alone isn't enough - it must be the right usage +- Their behavior drives the outcome + +**"With their use of the product"** +- The product must give more value than the pain of using it +- If usage pain > value gained, they won't care +- They need motivation to engage and continue + +**"That you achieve your goals"** +- The use of the product must tie to measurable business goals +- Without this connection, success isn't possible +- This completes the chain: WHO → uses product → right way → creates value → achieves goals + +**This distinction is critical** and reflects throughout the entire Trigger Mapping methodology. + +--- + +## Overview + +Workshop 2 is where you identify the specific user groups whose behavior will drive your business success. You'll create detailed personas and prioritize them by strategic value. + +**Duration:** 20-25 minutes +**Format:** Conversational with Saga +**Output:** 3-5 prioritized personas with deep context + +--- + +## What You'll Do + +### 1. Identify Groups + +**Find the user types who can drive your success:** +- Not demographics ("parents aged 30-45") +- Behavioral and contextual profiles ("busy working parents juggling multiple schedules") +- Real people out there in the world whose lives your product will touch +- 3-5 distinct groups +- Focus on who can help achieve your business goals through their product use + +**Key question:** "WHO out there in the world will make sure, with their use of the product, that we achieve our goals?" + +### 2. Create Personas + +**For each group, develop a rich profile:** +- Name and context (their situation) +- Goals and motivations (what they want) +- Frustrations and fears (what they struggle with) +- Behavioral patterns (how they act) + +**Go beyond demographics** - understand their world, their challenges, their aspirations. + +### 3. Prioritize + +**Rank groups by strategic value:** +- Which groups have highest impact on business goals? +- Which are most feasible to reach and serve? +- Rank 1-N based on strategic importance + +**This ranking becomes critical** for the next workshops. + +--- + +## Key Questions Saga Asks + +### Identifying Groups + +- "Who are the people whose behavior will drive your business success?" +- "What different user types could help you achieve your goals?" +- "Looking at your objectives, who has the power to make them happen?" + +### Creating Personas + +- "Tell me about [group name]. What's their situation?" +- "What's their context? What are they trying to accomplish?" +- "What are their goals and motivations?" +- "What frustrates them in their current situation?" +- "What do they fear or want to avoid?" +- "What behavioral patterns do they exhibit?" + +### Prioritizing + +- "Which group has the most potential impact on your top business goal?" +- "Which group is most feasible to reach and serve effectively?" +- "How would you rank these groups by strategic value?" +- "Why does this group rank higher than the others?" + +--- + +## Generic Example + +### Target Group 1: Remote Team Leads + +**Context:** +- Managing 5-10 distributed team members across time zones +- Responsible for team performance and wellbeing +- Limited visibility into individual struggles + +**Goals:** +- Keep team productive and connected +- Recognize and support struggling members early +- Demonstrate effective leadership to management + +**Frustrations:** +- Can't tell who's struggling until it's too late +- Async communication creates gaps +- Hard to build team culture remotely +- Limited tools for monitoring team health + +**Fears:** +- Team burnout without noticing +- Missed deadlines due to unseen problems +- Poor performance reviews +- Losing top performers +- Team becoming disconnected + +**Behavioral Patterns:** +- Checks in with team daily +- Monitors project progress closely +- Seeks early warning signs +- Values data-driven insights + +**Priority:** #1 (High impact + reachable + urgent pain) + +--- + +### Target Group 2: Solo Remote Workers + +**Context:** +- Working alone from home without office structure +- No team to provide accountability or connection +- Struggling with boundaries and focus + +**Goals:** +- Stay focused and productive +- Maintain work-life boundaries +- Feel connected to professional community +- Advance career despite isolation + +**Frustrations:** +- Constant distractions at home +- Isolation and loneliness +- Overworking without clear boundaries +- Lack of professional development + +**Fears:** +- Career stagnation +- Burnout from overwork +- Losing touch with industry +- Being forgotten by management +- Professional isolation + +**Behavioral Patterns:** +- Seeks structure and routine +- Values community connection +- Struggles with self-discipline +- Craves professional growth + +**Priority:** #2 (Large market + moderate impact) + +--- + +### Target Group 3: Remote Executives + +**Context:** +- Overseeing multiple distributed teams +- Responsible for organizational performance +- Limited visibility into team dynamics + +**Goals:** +- Ensure organizational productivity +- Maintain company culture remotely +- Make data-driven decisions +- Retain top talent + +**Frustrations:** +- Can't gauge team morale +- Limited insights into team health +- Difficult to spot problems early +- Hard to maintain culture at scale + +**Fears:** +- Organizational dysfunction +- Mass turnover +- Productivity decline +- Cultural erosion +- Competitive disadvantage + +**Behavioral Patterns:** +- Relies on aggregated data +- Values high-level insights +- Needs quick decision-making tools +- Focuses on organizational metrics + +**Priority:** #3 (High value but harder to reach) + +--- + +## Another Generic Example: Public Transport App + +This example shows how the same "customers" (travelers) have completely different needs based on their context. + +### Target Group 1: Daily Commuters + +**Context:** +- Same route every workday (home ↔ work) +- Time-sensitive schedule (must arrive on time) +- Experienced with the system + +**Goals:** +- Get to work/home efficiently +- Minimize waiting time +- Avoid delays and disruptions + +**Frustrations:** +- Unexpected delays without warning +- Crowded vehicles during rush hour +- Unreliable schedules + +**Fears:** +- Being late to work (professional consequences) +- Missing important meetings +- Unpredictable commute times + +**Behavioral Patterns:** +- Checks app before leaving +- Knows alternative routes +- Values real-time updates +- Wants predictability + +**Priority:** #1 (Highest volume, daily usage, urgent needs) + +--- + +### Target Group 2: Tourists + +**Context:** +- Unfamiliar with the city and transit system +- Exploring multiple destinations +- No time pressure but limited trip duration + +**Goals:** +- Navigate unfamiliar system confidently +- Find best routes to attractions +- Understand ticketing and payment +- Maximize sightseeing time + +**Frustrations:** +- Confusing route options +- Unclear ticketing systems +- Language barriers +- Getting lost or taking wrong line + +**Fears:** +- Wasting vacation time being lost +- Looking foolish or incompetent +- Missing key attractions +- Overpaying for tickets + +**Behavioral Patterns:** +- Plans routes in advance +- Needs step-by-step guidance +- Values visual/map-based navigation +- Seeks reassurance at each step + +**Priority:** #2 (Growing market, different needs than commuters) + +--- + +### Target Group 3: Seniors + +**Context:** +- May have mobility limitations +- Less familiar with digital tools +- Often traveling during off-peak hours +- May need accessibility features + +**Goals:** +- Travel safely and comfortably +- Avoid physical strain (stairs, long walks) +- Feel confident using the system +- Maintain independence + +**Frustrations:** +- Complicated digital interfaces +- Lack of accessibility information +- Physical barriers (stairs, gaps) +- Small text and confusing layouts + +**Fears:** +- Falling or getting injured +- Being stranded or unable to get help +- Losing independence +- Embarrassment from not understanding technology + +**Behavioral Patterns:** +- Prefers simple, clear interfaces +- Values accessibility information +- Needs larger text and clear instructions +- May prefer human assistance options + +**Priority:** #3 (Important for accessibility, regulatory requirements) + +--- + +### Why This Example Works + +**Same product (public transport app), completely different needs:** + +**Commuters need:** +- Real-time delay alerts +- Quick route alternatives +- Predictability and reliability +- Speed and efficiency + +**Tourists need:** +- Step-by-step navigation +- Visual/map-based guidance +- Ticketing help +- Confidence and reassurance + +**Seniors need:** +- Accessibility information +- Simple, clear interfaces +- Larger text and buttons +- Safety and comfort features + +**The insight:** If you designed only for commuters (speed and efficiency), you'd fail tourists and seniors. If you designed only for tourists (detailed guidance), you'd frustrate commuters who want speed. Understanding these distinct groups allows you to prioritize features strategically. + +--- + +## Why Behavioral Profiles Matter + +### Not This (Demographics) + +"Parents aged 30-45 with household income $75K+" + +**Problem:** Doesn't tell you what drives behavior, what they need, or how to design for them. + +### This (Behavioral + Contextual) + +"Busy working parents juggling multiple kids' schedules, family dog care, and full-time jobs - constantly afraid of dropping the ball on family responsibilities" + +**Why it works:** You understand their world, their challenges, their fears. You can design for their actual needs. + +--- + +## Prioritization Criteria + +### Impact on Business Goals + +**Ask:** +- Which group's behavior most directly drives our objectives? +- Which group has the power to make our goals happen? +- Which group's success equals our success? + +**Example:** Remote Team Leads rank #1 because each one brings 5-10 users (their team), has budget authority, and urgent pain. + +### Feasibility to Reach + +**Ask:** +- Can we actually reach this group? +- Do we have channels to communicate with them? +- Can we serve them with our resources? +- Is the market size sufficient? + +**Example:** Executives rank lower because they're harder to reach despite high value. + +### Urgency of Pain + +**Ask:** +- How urgent is their problem? +- Are they actively seeking solutions? +- What's the cost of not solving this? + +**Example:** Team Leads have urgent pain (team burnout risk) vs Solo Workers have chronic pain (isolation). + +--- + +## What You Get from Workshop 2 + +✅ **3-5 prioritized personas** with rich context +✅ **Deep understanding** of each group's world +✅ **Clear ranking** by strategic value +✅ **Foundation** for psychological mapping +✅ **Focus** for design efforts + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Demographic Personas + +**Problem:** "Males 25-40 with college degrees" +**Why it fails:** Doesn't explain behavior or needs +**Fix:** Focus on context, goals, frustrations, fears + +### Mistake 2: Too Many Groups + +**Problem:** Identifying 10+ different user types +**Why it fails:** Dilutes focus, impossible to serve all +**Fix:** Limit to 3-5 most strategic groups + +### Mistake 3: No Prioritization + +**Problem:** "All groups are equally important" +**Why it fails:** Can't focus design efforts +**Fix:** Rank ruthlessly by strategic value + +### Mistake 4: Ignoring Feasibility + +**Problem:** Targeting groups you can't reach +**Why it fails:** Wastes resources on impossible goals +**Fix:** Balance impact with reachability + +### Mistake 5: Surface-Level Personas + +**Problem:** "They want to be productive" +**Why it fails:** Too generic to guide design +**Fix:** Dig deeper - what's their context? Their fears? + +--- + +## How This Feeds Into Next Workshops + +**Workshop 2 sets up the psychology mapping:** + +``` +Business Goals + ↓ +Target Groups (prioritized personas) + ↓ +Workshop 3: What drives each group's behavior? + ↓ +Workshop 4: Which drivers are most powerful? + ↓ +Workshop 5: Which features address top drivers? +``` + +The personas you create here become the foundation for understanding psychological drivers. + +--- + +## Tips for Success + +**DO:** +- ✅ Focus on behavioral and contextual profiles +- ✅ Dig deep into frustrations and fears +- ✅ Prioritize ruthlessly (not everyone is #1) +- ✅ Consider both impact and feasibility +- ✅ Create personas you can actually design for + +**DON'T:** +- ❌ Use demographic categories only +- ❌ Create too many personas +- ❌ Skip prioritization +- ❌ Accept surface-level descriptions +- ❌ Ignore feasibility constraints + +--- + +## What's Next + +Workshop 3 maps the psychological drivers for each persona - both what they want to achieve (positive drivers) and what they want to avoid (negative drivers). This is where you understand the psychology that drives behavior. + +--- + +## Key Takeaways + +✅ **Behavioral profiles, not demographics** - Context, goals, frustrations, fears +✅ **3-5 groups maximum** - Focus on strategic value +✅ **Prioritize ruthlessly** - Rank by impact + feasibility +✅ **Deep understanding** - Know their world, not just their age +✅ **Foundation for psychology** - These personas drive next workshops + +--- + +[← Back to Lesson 4](lesson-04-workshop-1-business-goals.md) | [Next: Lesson 6 - Workshop 3: Driving Forces →](lesson-06-workshop-3-driving-forces.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-06-workshop-3-driving-forces.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-06-workshop-3-driving-forces.md new file mode 100644 index 000000000..e08f3e2e8 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-06-workshop-3-driving-forces.md @@ -0,0 +1,458 @@ +# Lesson 5: Workshop 3 - Driving Forces + +**Map the Psychology That Drives Behavior** + +--- + +## Overview + +Workshop 3 is where you map the psychological drivers for each persona - both what they want to achieve and what they want to avoid. This is the core of understanding what actually drives user behavior. + +**Duration:** 20-30 minutes +**Format:** Conversational with Saga +**Output:** Complete psychological profile for each persona (positive + negative drivers) + +--- + +## What You'll Do + +For each persona from Workshop 2, you'll identify two types of drivers: + +### Positive Drivers (GAIN) + +**What users are moving TOWARD:** +- What do they want to achieve? +- What benefits are they seeking? +- What goals pull them forward? +- What positive outcomes motivate them? + +### Negative Drivers (PAIN) + +**What users are moving AWAY FROM:** +- What do they want to avoid? +- What frustrations do they experience? +- What fears push them to act? +- What problems are they trying to escape? + +**The key insight:** Both matter, but negative drivers often create more urgent action due to loss aversion. + +--- + +## Key Questions Saga Asks + +### For Positive Drivers + +- "What does this persona want to accomplish?" +- "What positive outcomes are they seeking?" +- "What would make their situation better?" +- "What goals are pulling them forward?" +- "What benefits would they value?" + +### For Negative Drivers + +- "What problems are they trying to avoid?" +- "What frustrates them about current solutions?" +- "What do they fear will happen if they don't solve this?" +- "What keeps them up at night?" +- "What would be embarrassing or costly?" + +### Digging Deeper + +- "Why does that matter to them emotionally?" +- "What's the deeper fear behind that frustration?" +- "How intense is this driver on a scale of 1-5?" +- "Is that specific enough, or is it too generic?" + +--- + +## Generic Example: Remote Team Lead + +### Positive Drivers (GAIN) + +**What they want to achieve:** + +1. **Want to build strong team culture despite distance** + - Emotional core: Pride in team cohesion + - Intensity: High (career identity) + +2. **Want to recognize and support struggling team members early** + - Emotional core: Caring for people they're responsible for + - Intensity: High (responsibility) + +3. **Want to demonstrate effective leadership to management** + - Emotional core: Career advancement and recognition + - Intensity: Very high (professional success) + +4. **Want team to feel connected and valued** + - Emotional core: Creating positive environment + - Intensity: Medium (aspirational) + +### Negative Drivers (PAIN) + +**What they want to avoid:** + +1. **Fear team members burning out without noticing** + - Emotional core: Guilt and responsibility + - Intensity: Very high (most urgent) + - Why powerful: Direct responsibility for people's wellbeing + +2. **Fear missing early warning signs of problems** + - Emotional core: Anxiety about blindness + - Intensity: High (constant worry) + - Why powerful: Feeling out of control + +3. **Fear being seen as ineffective manager** + - Emotional core: Professional embarrassment + - Intensity: Very high (career threat) + - Why powerful: Reputation and advancement at stake + +4. **Fear losing top performers to burnout** + - Emotional core: Failure and loss + - Intensity: High (business impact) + - Why powerful: Reflects on their leadership + +5. **Fear team becoming disconnected and disengaged** + - Emotional core: Loss of team cohesion + - Intensity: Medium (gradual problem) + - Why powerful: Undermines all other goals + +--- + +## Why Negative Drivers Are More Powerful + +### The Psychology: Loss Aversion + +Research shows people work roughly **twice as hard to avoid pain as to pursue equivalent gain**. + +**Generic examples:** + +**Scenario 1: Fitness** +- Positive: "Want to look good for summer" → Weak urgency +- Negative: "Fear health problems like parent had" → Strong urgency +- **Which drives action?** The fear + +**Scenario 2: Project Management** +- Positive: "Want to be organized" → Nice to have +- Negative: "Fear missing client deadline and losing contract" → Critical need +- **Which drives adoption?** The fear + +**Scenario 3: Email Management** +- Positive: "Want clean inbox" → Low urgency +- Negative: "Fear missing urgent client email" → High urgency +- **Which drives behavior change?** The fear + +### The Emotional Core + +Negative drivers often connect to powerful emotions: + +- **Shame:** "What will people think?" +- **Guilt:** "I'm letting people down" +- **Anxiety:** "What if this goes wrong?" +- **Embarrassment:** "This makes me look bad" +- **Fear:** "I could lose something important" + +**These emotions drive urgent action.** + +--- + +## Balancing Both Types + +The most powerful understanding comes from mapping BOTH: + +### How They Work Together + +**Positive drivers suggest:** +- The aspirational features +- Long-term value propositions +- What makes the experience delightful + +**Negative drivers suggest:** +- The urgent, must-have features +- What drives initial adoption +- What prevents churn + +**Example: Team Pulse Check Feature** + +**Addresses positive drivers:** +- Helps build team culture (shows you care) +- Demonstrates leadership (provides data) + +**Addresses negative drivers:** +- Prevents burnout blindness (early warning) +- Avoids looking ineffective (proactive management) + +**Why it works:** Solves urgent pain AND delivers aspirational benefit. + +--- + +## Common Patterns Across Contexts + +### Pattern 1: Professional Reputation + +**Positive:** Want to be seen as competent +**Negative:** Fear of looking incompetent + +**Design implication:** Features that help users look good and avoid embarrassment + +### Pattern 2: Time Management + +**Positive:** Want to be productive +**Negative:** Fear of wasting time or missing deadlines + +**Design implication:** Time-saving features + deadline protection + +### Pattern 3: Social Connection + +**Positive:** Want to build relationships +**Negative:** Fear of isolation or being left out + +**Design implication:** Connection features + FOMO prevention + +### Pattern 4: Control & Autonomy + +**Positive:** Want to feel in control +**Negative:** Fear of chaos and overwhelm + +**Design implication:** Organization tools + anxiety reduction + +--- + +## What You Get from Workshop 3 + +✅ **Complete psychological profile** for each persona +✅ **Both sides of motivation** (gain + pain) +✅ **Understanding of emotional intensity** +✅ **Foundation for feature decisions** +✅ **Insight into urgency** (what drives immediate action) + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Only Mapping Positive Drivers + +**Problem:** Missing the urgent pain that drives adoption +**Why it fails:** Don't understand what creates urgency +**Fix:** Always map both types + +### Mistake 2: Generic "Wants" Statements + +**Problem:** "Want to be productive" +**Why it fails:** Too vague to guide design +**Fix:** Be specific about context and outcomes + +### Mistake 3: Ignoring Emotional Intensity + +**Problem:** All drivers seem equal +**Why it fails:** Can't prioritize effectively +**Fix:** Identify which have strongest emotional pull + +### Mistake 4: Listing Features Instead of Psychology + +**Problem:** "Want a calendar feature" +**Why it fails:** That's a solution, not a driver +**Fix:** "Want to never miss family commitments due to work chaos" + +### Mistake 5: Avoiding Negative Drivers + +**Problem:** Focusing only on positive because negative feels uncomfortable +**Why it fails:** Miss the most powerful motivators +**Fix:** Embrace negative drivers - they're often more actionable + +--- + +## How This Feeds Into Next Workshops + +**Workshop 3 creates the psychological foundation:** + +``` +Business Goals + ↓ +Target Groups + ↓ +Driving Forces (positive + negative for each group) + ↓ +Workshop 4: Which drivers are most powerful? + ↓ +Workshop 5: Which features address top drivers? +``` + +The drivers you map here become the criteria for prioritization and feature scoring. + +--- + +## The Control Question: Validating Your Drivers + +Once you've identified the driving forces for each target group, validate them with these critical questions: + +### "If This Target Group Feels This Way, Would Our Offering Be the Best Option for Them?" + +**What this reveals:** +- Whether your product actually addresses their drivers +- If there's a real fit between their psychology and your solution +- Whether you're solving the right problem + +**Example validation:** + +**Target Group:** Remote Team Leads +**Top Driver:** Fear of team burnout without noticing + +**Control question:** "If they fear team burnout without noticing, would our daily pulse check be the best option?" + +**Validation:** +- ✅ Yes - provides early warning system they lack +- ✅ Addresses the specific fear directly +- ✅ Fits their daily workflow + +**If the answer is no or weak:** You may have identified the wrong drivers, or your product doesn't fit this group. + +--- + +### "What Alternatives Do They Have?" + +**What this reveals:** +- Competitive landscape from psychological perspective +- Whether your solution is truly differentiated +- What you're really competing against (often not what you think) + +**Example analysis:** + +**Target Group:** Remote Team Leads +**Driver:** Fear of team burnout without noticing + +**Alternatives they have:** +1. **Manual check-ins** - Time-consuming, inconsistent, relies on people speaking up +2. **Annual surveys** - Too infrequent, backward-looking, no early warning +3. **Gut feeling** - Unreliable, often too late, causes anxiety +4. **Nothing** - Hope for the best, react when crisis hits + +**Why our offering is better:** +- Daily automated pulse vs manual effort +- Real-time vs annual +- Data-driven vs gut feeling +- Proactive vs reactive + +**If you can't articulate why you're better:** Either the driver isn't strong enough, or your solution doesn't differentiate. + +--- + +### "Why Should They Care in the First Place?" + +**What this reveals:** +- Whether the driver has real urgency +- If the pain/gain is significant enough to motivate action +- Whether this is a "nice-to-have" or "must-have" + +**Example validation:** + +**Target Group:** Remote Team Leads +**Driver:** Fear of team burnout without noticing + +**Why should they care:** +- **Career impact:** Team burnout reflects poorly on their leadership +- **Business impact:** Losing top performers is costly and visible +- **Emotional impact:** Guilt and responsibility for people's wellbeing +- **Immediate consequence:** Can happen without warning, hard to recover from +- **Frequency:** Constant worry, not occasional concern + +**Urgency level:** Very high - active fear with career consequences + +**If they don't care enough:** The driver may be too weak to motivate product adoption. Look for stronger drivers or different target groups. + +--- + +## Using the Control Questions + +### When to Apply Them + +**After mapping drivers for each persona:** +1. List all drivers (positive and negative) +2. Apply control questions to top 3-5 drivers +3. Validate fit between drivers and your offering +4. Identify gaps or misalignments + +### What to Do with the Answers + +**If validation is strong:** +- ✅ Proceed with confidence +- ✅ Use these drivers for prioritization +- ✅ Design features that address them + +**If validation is weak:** +- ⚠️ Re-examine the drivers (are they accurate?) +- ⚠️ Consider different target groups +- ⚠️ Adjust your product strategy +- ⚠️ Look for stronger psychological drivers + +**If you can't beat alternatives:** +- 🚨 Major red flag - why would they choose you? +- 🚨 Need differentiation or different positioning +- 🚨 May need to pivot target group or offering + +### Generic Example: Fitness App + +**Target Group:** Busy professionals +**Driver:** Want to stay healthy despite hectic schedule + +**Control questions:** + +**1. Would our offering be best option?** +- Our app: 15-minute workouts, no equipment, fits any schedule +- ✅ Yes - specifically designed for time-constrained people + +**2. What alternatives do they have?** +- Gym membership (requires travel time, fixed hours) +- YouTube videos (overwhelming choice, no structure) +- Nothing (guilt, declining health) +- Our advantage: Minimal time, structured, no barriers + +**3. Why should they care?** +- Health declining, energy low +- Feeling guilty about neglecting fitness +- Want to set good example for kids +- Fear of health problems like parents had +- ✅ Strong urgency - both positive and negative drivers + +**Validation:** Strong fit. Proceed with this target group and driver. + +--- + +## Tips for Success + +**DO:** +- ✅ Map both positive AND negative drivers +- ✅ Be specific about context and emotions +- ✅ Identify emotional intensity +- ✅ Dig deeper than surface wants +- ✅ Focus on psychology, not features +- ✅ Apply control questions to validate drivers + +**DON'T:** +- ❌ Skip negative drivers +- ❌ Accept generic statements +- ❌ Ignore emotional core +- ❌ List features instead of drivers +- ❌ Treat all drivers as equal +- ❌ Skip validation - assume drivers are correct + +--- + +## What's Next + +Workshop 4 prioritizes these drivers - ranking which groups and which psychological drivers matter most. This creates the focus for all design decisions. + +--- + +## Key Takeaways + +✅ **Two types of drivers** - Positive (gain) and Negative (pain) +✅ **Negative is more powerful** - Loss aversion drives urgent action +✅ **Map both for each persona** - Complete psychological picture +✅ **Emotional intensity matters** - Not all drivers are equal +✅ **Be specific** - Avoid generic wants, find emotional core + +--- + +[← Back to Lesson 5](lesson-05-workshop-2-target-groups.md) | [Next: Lesson 7 - Workshop 4: Prioritization →](lesson-07-workshop-4-prioritization.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-07-workshop-4-prioritization.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-07-workshop-4-prioritization.md new file mode 100644 index 000000000..410be4515 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-07-workshop-4-prioritization.md @@ -0,0 +1,313 @@ +# Lesson 6: Workshop 4 - Prioritization + +**Rank What Matters Most** + +--- + +## Overview + +Workshop 4 is where you make strategic choices about what matters most. You'll rank your target groups and their psychological drivers to create clear priorities that guide all design decisions. + +**Duration:** 15-20 minutes +**Format:** Conversational with Saga +**Output:** Ranked target groups + ranked drivers for each group + +--- + +## What You'll Do + +### 1. Prioritize Target Groups + +**Rank your personas by strategic value:** +- Which groups have highest business impact? +- Which are most feasible to serve? +- Rank 1-N based on strategic importance + +**This ranking determines** which groups get design focus first. + +### 2. Prioritize Driving Forces + +**For each group, rank their psychological drivers:** +- Within each persona, which drivers are strongest? +- Which have most emotional intensity? +- Which would drive the most urgent action? +- Rank by power to drive behavior + +**This ranking determines** which drivers become your feature scoring criteria. + +--- + +## Key Questions Saga Asks + +### For Target Groups + +- "Which target group will have the biggest impact on your top business goal?" +- "Which group is most feasible to reach and serve effectively?" +- "How would you rank all groups from highest to lowest strategic value?" +- "Why does this group rank higher than the others?" +- "What makes this group more strategic?" + +### For Driving Forces + +- "For [top persona], which driving forces are most powerful?" +- "Which drivers have the most emotional intensity?" +- "Which pain points cause the most urgent need to act?" +- "Which positive drivers are strongest motivators?" +- "How would you rank these drivers by their power to drive behavior?" + +--- + +## Generic Example + +### Target Group Rankings + +**1. Remote Team Leads** (Priority #1) +- **Why #1:** High impact (each brings 5-10 users), reachable through professional channels, urgent pain (team burnout risk), budget authority +- **Business impact:** Directly drives user acquisition and retention goals +- **Feasibility:** Can reach through LinkedIn, management communities + +**2. Solo Remote Workers** (Priority #2) +- **Why #2:** Large market size, moderate impact per user, chronic pain (less urgent than team leads) +- **Business impact:** Volume play, good retention potential +- **Feasibility:** Reachable through remote work communities + +**3. Remote Executives** (Priority #3) +- **Why #3:** High value per user, but harder to reach, longer sales cycles +- **Business impact:** Strategic accounts, high revenue potential +- **Feasibility:** Difficult to reach, requires different approach + +--- + +### Driving Force Rankings: Remote Team Lead + +**Top 5 Prioritized Drivers:** + +**1. Fear of team burnout without noticing** (NEGATIVE) +- **Why #1:** Most urgent, highest emotional intensity, constant worry +- **Emotional core:** Guilt and responsibility for people's wellbeing +- **Urgency:** Very high (active problem) +- **Impact:** Directly threatens their success + +**2. Want to demonstrate effective leadership** (POSITIVE) +- **Why #2:** Career driver, strong motivation, measurable outcome +- **Emotional core:** Professional advancement and recognition +- **Urgency:** High (ongoing career goal) +- **Impact:** Affects long-term success + +**3. Fear of losing top performers** (NEGATIVE) +- **Why #3:** Business impact, reflects on leadership, costly outcome +- **Emotional core:** Failure and loss +- **Urgency:** High (retention risk) +- **Impact:** Damages team and reputation + +**4. Want to build strong team culture** (POSITIVE) +- **Why #4:** Aspirational, important but less urgent +- **Emotional core:** Pride in team cohesion +- **Urgency:** Medium (long-term goal) +- **Impact:** Enables other goals + +**5. Fear of missed deadlines** (NEGATIVE) +- **Why #5:** Important but less emotionally intense than top fears +- **Emotional core:** Professional embarrassment +- **Urgency:** Medium (project-dependent) +- **Impact:** Situational + +--- + +## Prioritization Criteria + +### For Target Groups + +**Business Impact:** +- Which group's behavior most directly drives objectives? +- Which group has power to make goals happen? +- What's the multiplier effect? (e.g., team leads bring teams) + +**Feasibility:** +- Can we actually reach this group? +- Do we have channels to communicate? +- Can we serve them with our resources? +- Is market size sufficient? + +**Urgency of Pain:** +- How urgent is their problem? +- Are they actively seeking solutions? +- What's the cost of not solving? + +**Strategic Fit:** +- Does this align with company strengths? +- Is this a sustainable advantage? +- Does this open future opportunities? + +### For Driving Forces + +**Emotional Intensity:** +- How strongly do they feel this? +- Does this keep them up at night? +- Is this a constant worry or occasional concern? + +**Urgency:** +- How immediate is the need? +- What triggers action on this? +- Is this active pain or chronic discomfort? + +**Impact on Behavior:** +- Would solving this drive adoption? +- Would this prevent churn? +- Does this create word-of-mouth? + +**Measurability:** +- Can we tell if we've addressed this? +- Can users articulate this need? +- Is there observable behavior change? + +--- + +## Why Prioritization Matters + +### Without Prioritization + +**Problems:** +- Try to serve everyone equally (serve no one well) +- Build features that address minor drivers +- Waste resources on low-impact groups +- No clear focus for design + +**Result:** Mediocre product that doesn't deeply solve anyone's problems. + +### With Prioritization + +**Benefits:** +- Focus design on highest-impact groups +- Address most powerful psychological drivers +- Allocate resources strategically +- Create deep value for top segments + +**Result:** Product that deeply solves urgent problems for strategic users. + +--- + +## The Prioritization Cascade + +Once you have rankings, design decisions become clear: + +``` +Top Business Goal + ↓ +Top Target Group (who can best achieve this?) + ↓ +Top Psychological Driver (what drives them most?) + ↓ +Features that address this driver +``` + +**Example:** +- **Goal:** Increase user retention to 70% +- **Top Group:** Remote Team Leads (high retention potential) +- **Top Driver:** Fear of team burnout without noticing +- **Top Feature:** Daily team pulse check with burnout indicators +- **Why:** Addresses their #1 fear, drives retention + +--- + +## What You Get from Workshop 4 + +✅ **Clear strategic priorities** - Know what matters most +✅ **Ranked target groups** - Focus design efforts +✅ **Ranked drivers** - Know which psychology to address +✅ **Decision framework** - Guide all feature discussions +✅ **Data for scoring** - Foundation for Workshop 5 + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Everything Is Priority #1 + +**Problem:** "All groups are equally important" +**Why it fails:** Dilutes focus, serves no one well +**Fix:** Make hard choices, rank ruthlessly + +### Mistake 2: Prioritizing by Ease + +**Problem:** "Let's focus on the easiest group first" +**Why it fails:** May not drive business goals +**Fix:** Balance impact with feasibility + +### Mistake 3: Ignoring Emotional Intensity + +**Problem:** Ranking drivers by logic, not emotion +**Why it fails:** Miss what actually drives behavior +**Fix:** Consider emotional intensity and urgency + +### Mistake 4: Too Many Top Priorities + +**Problem:** "Top 10 drivers are all critical" +**Why it fails:** Can't focus, spreads resources thin +**Fix:** Limit to top 5-7 drivers for scoring + +### Mistake 5: Forgetting Business Goals + +**Problem:** Prioritizing based on interesting psychology +**Why it fails:** Doesn't connect to business success +**Fix:** Always trace back to business objectives + +--- + +## How This Feeds Into Workshop 5 + +**Workshop 4 creates the scoring criteria:** + +``` +Business Goals + ↓ +Target Groups (ranked) + ↓ +Driving Forces (ranked for each group) + ↓ +Top 5-7 Drivers (scoring criteria) + ↓ +Workshop 5: Score features against these drivers +``` + +The top-ranked drivers become the columns in your feature scoring matrix. + +--- + +## Tips for Success + +**DO:** +- ✅ Make hard choices (not everything is #1) +- ✅ Consider both impact and feasibility +- ✅ Focus on emotional intensity +- ✅ Limit to top 5-7 drivers for scoring +- ✅ Trace priorities back to business goals + +**DON'T:** +- ❌ Avoid making choices +- ❌ Prioritize by ease alone +- ❌ Ignore emotional intensity +- ❌ Create too many "top" priorities +- ❌ Forget the business objectives + +--- + +## What's Next + +Workshop 5 uses these priorities to systematically score features. Each feature gets rated against your top-ranked drivers, creating a data-driven roadmap. + +--- + +## Key Takeaways + +✅ **Ruthless prioritization** - Not everything can be #1 +✅ **Two levels of ranking** - Groups first, then drivers +✅ **Strategic criteria** - Impact + feasibility + urgency +✅ **Top 5-7 drivers** - Become feature scoring criteria +✅ **Clear focus** - Guides all design decisions + +--- + +[← Back to Lesson 6](lesson-06-workshop-3-driving-forces.md) | [Next: Lesson 8 - Workshop 5: Feature Impact →](lesson-08-workshop-5-feature-impact.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-08-workshop-5-feature-impact.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-08-workshop-5-feature-impact.md new file mode 100644 index 000000000..8c698d5e6 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-08-workshop-5-feature-impact.md @@ -0,0 +1,474 @@ +# Lesson 7: Workshop 5 - Feature Impact + +**Score Features by Strategic Impact** + +--- + +## Overview + +Workshop 5 is where strategy becomes actionable roadmap. You'll systematically score your feature ideas against the prioritized psychological drivers from Workshop 4, creating a data-driven feature prioritization. + +**Duration:** 20-30 minutes +**Format:** Conversational with Saga +**Output:** Scored and ranked feature list + +--- + +## What You'll Do + +### 1. List Features + +**Brainstorm all potential features:** +- Ideas from Product Brief +- Stakeholder requests +- Competitive features +- User feedback +- Team suggestions + +**Aim for:** 10-20 features to evaluate + +### 2. Score Each Feature + +**Rate against top 5-7 prioritized drivers:** +- How well does this feature address each driver? +- Use 0-3 scale for each driver +- Be honest (don't inflate scores) + +**Scoring scale:** +- **3** = Directly addresses this driver (core solution) +- **2** = Significantly helps with this driver +- **1** = Somewhat related to this driver +- **0** = Doesn't address this driver + +### 3. Calculate Total Scores + +**Sum scores across all drivers:** +- Add up the scores for each feature +- Higher total = higher strategic impact +- This becomes your prioritization data + +### 4. Rank and Create Roadmap + +**Sort features by total score:** +- Highest scores = Phase 1 (highest impact) +- High scores = Phase 2 +- Medium scores = Phase 3 +- Low scores = Backlog or cut + +--- + +## Key Questions Saga Asks + +### Listing Features + +- "What features are you considering for this product?" +- "What ideas came up in your Product Brief?" +- "What have stakeholders requested?" +- "What do competitors offer that you're considering?" +- "Are there any features you're unsure about?" + +### Scoring Each Feature + +- "How well does [feature] address [top driver]?" +- "Does this feature create gain or reduce pain for this persona?" +- "On a scale of 0-3, how much impact does this have on [driver]?" +- "Why that score? What specifically does it address?" +- "Is this a 2 or a 3? What's the difference?" + +### Validation + +- "Are there features that would score higher that we haven't listed?" +- "Could we modify any features to increase their impact?" +- "Do these scores match your intuition? If not, why?" +- "Which features are you surprised scored high or low?" + +--- + +## Generic Example: Scoring Matrix + +### Context + +**Top 5 Prioritized Drivers (Remote Team Leads):** +1. Fear of team burnout without noticing (NEGATIVE) +2. Want to demonstrate effective leadership (POSITIVE) +3. Fear of losing top performers (NEGATIVE) +4. Want to build strong team culture (POSITIVE) +5. Fear of missed deadlines (NEGATIVE) + +### Features to Score + +| Feature | Burnout Fear | Leadership | Retention | Culture | Deadlines | **Total** | +|---------|-------------|------------|-----------|---------|-----------|-----------| +| Daily team pulse check | 3 | 2 | 2 | 1 | 1 | **9** | +| Team workload dashboard | 3 | 2 | 2 | 0 | 2 | **9** | +| Recognition system | 1 | 1 | 2 | 3 | 0 | **7** | +| 1-on-1 scheduling assistant | 2 | 2 | 1 | 1 | 0 | **6** | +| Meeting summaries | 0 | 1 | 0 | 1 | 2 | **4** | +| Async video updates | 1 | 1 | 0 | 2 | 0 | **4** | +| Team chat | 0 | 0 | 1 | 2 | 0 | **3** | + +### Detailed Scoring Example + +**Feature: Daily Team Pulse Check** + +**Against "Fear of team burnout without noticing" (Score: 3)** +- Directly addresses the fear +- Provides daily visibility into team health +- Early warning system for burnout indicators +- Core solution to the problem + +**Against "Want to demonstrate effective leadership" (Score: 2)** +- Provides data to show proactive management +- Enables evidence-based leadership decisions +- Significantly helps but not the primary purpose + +**Against "Fear of losing top performers" (Score: 2)** +- Early warning helps prevent burnout-driven turnover +- Identifies at-risk team members +- Significantly helps with retention + +**Against "Want to build strong team culture" (Score: 1)** +- Shows you care about team wellbeing +- Somewhat related but not primary benefit + +**Against "Fear of missed deadlines" (Score: 1)** +- Can identify capacity issues early +- Somewhat helps but not main purpose + +**Total: 9 points** (Highest strategic impact) + +--- + +**Feature: Team Chat** + +**Against "Fear of team burnout" (Score: 0)** +- Doesn't address burnout visibility +- No impact on this driver + +**Against "Want to demonstrate leadership" (Score: 0)** +- Doesn't provide leadership insights +- No impact on this driver + +**Against "Fear of losing performers" (Score: 1)** +- Helps with connection (minor retention factor) +- Somewhat related + +**Against "Want to build team culture" (Score: 2)** +- Enables team connection +- Significantly helps with culture + +**Against "Fear of missed deadlines" (Score: 0)** +- Doesn't address deadline management +- No impact on this driver + +**Total: 3 points** (Low strategic impact for this persona) + +--- + +## Prioritized Roadmap + +Based on scores, create phases: + +### Phase 1: Highest Impact (8-10 points) +- Daily team pulse check (9) +- Team workload dashboard (9) + +**Why first:** Directly address top fears, highest strategic value + +### Phase 2: High Impact (6-7 points) +- Recognition system (7) +- 1-on-1 scheduling assistant (6) + +**Why second:** Good strategic value, support top priorities + +### Phase 3: Medium Impact (4-5 points) +- Meeting summaries (4) +- Async video updates (4) + +**Why third:** Some value but lower priority + +### Backlog: Low Impact (0-3 points) +- Team chat (3) + +**Why backlog:** Doesn't address top strategic drivers for this persona + +--- + +## Why This Works + +### It's Strategic + +**Every score connects to:** +- A prioritized psychological driver +- A prioritized target group +- A business goal + +**Not arbitrary** - traceable to strategy + +### It's Objective + +**Traditional approach:** +"I think Feature A is more important" + +**Feature Impact approach:** +"Feature A scores 9, Feature B scores 4" + +**Data beats opinions** + +### It's Defensible + +**When stakeholders ask "Why aren't we building X?"** + +**You can show:** +1. Here's our Trigger Map +2. Here are our top prioritized drivers +3. Here's how features score against them +4. Feature X scores lower than our current roadmap + +**Strategic reasoning, not politics** + +### It's Flexible + +**When priorities change:** +- Update driver rankings +- Re-score features +- New roadmap emerges automatically + +**Strategy drives features, not the reverse** + +--- + +## Scoring Guidelines + +### Be Honest + +**Don't:** +- Inflate scores to justify pet features +- Score based on what you want to build +- Let politics influence scoring + +**Do:** +- Score based on actual impact +- Accept that some features score low +- Challenge your own assumptions + +### Be Specific + +**When scoring, ask:** +- "How SPECIFICALLY does this address the driver?" +- "What about this feature reduces that pain?" +- "What evidence supports this score?" + +### Use the Full Scale + +**0-3 scale exists for a reason:** +- **0** is okay - not everything addresses everything +- **3** should be rare - only direct solutions +- **1-2** is where most scores land + +### Consider Both Positive and Negative + +**Features can address:** +- Negative drivers (reduce pain, prevent fears) +- Positive drivers (enable goals, create gains) +- Both (most powerful features) + +--- + +## Common Patterns + +### Pattern 1: High Scores Across Multiple Drivers + +**What it means:** High-leverage feature addressing multiple needs + +**Example:** Daily pulse check scores high on burnout fear, leadership goals, retention fear + +**Action:** Prioritize - strategically valuable + +### Pattern 2: High Score on Top Driver Only + +**What it means:** Laser-focused solution for most important need + +**Example:** Workload balancing scores 3 on burnout fear, low on others + +**Action:** Still high priority if that driver is #1 + +### Pattern 3: Moderate Scores Across Many + +**What it means:** Nice-to-have that helps a bit with everything + +**Example:** Team chat scores 1-2 on multiple drivers + +**Action:** Lower priority - not solving urgent problems + +### Pattern 4: Low Scores Everywhere + +**What it means:** Feature doesn't connect to strategy + +**Example:** Fancy animations score 0-1 across all drivers + +**Action:** Cut it or deprioritize significantly + +--- + +## Beyond the Numbers + +### The Conversation Matters + +**Questions that emerge:** +- "Why doesn't this feature score higher?" +- "Could we modify it to address more drivers?" +- "Are we missing a feature that would score higher?" +- "Do these scores match our intuition?" + +**Insights from discussion:** +- Features can be refined to increase impact +- Missing features can be identified +- Assumptions can be challenged +- Strategy can be sharpened + +### Combining with Other Factors + +**Feature Impact = Strategic value** + +**Also consider:** +- **Feasibility:** How hard to build? +- **Dependencies:** What's required first? +- **Market timing:** Competitive urgency? +- **Resources:** Do we have capacity? + +**Combined formula:** +``` +Priority = (Strategic Impact × Feasibility) + Urgency Bonus +``` + +--- + +## What You Get from Workshop 5 + +✅ **Scored feature list** - Quantified strategic impact +✅ **Ranked roadmap** - Clear prioritization +✅ **Strategic justification** - Defensible decisions +✅ **Data-driven priorities** - Not opinions +✅ **Traceable reasoning** - Feature → Driver → Group → Goal + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Inflating Scores + +**Problem:** Scoring pet features higher than deserved +**Why it fails:** Undermines the whole system +**Fix:** Be brutally honest, challenge yourself + +### Mistake 2: Scoring Too Many Features + +**Problem:** Trying to score 50+ features +**Why it fails:** Takes too long, loses focus +**Fix:** Start with 10-20 most viable features + +### Mistake 3: Ignoring Low Scores + +**Problem:** "But we still need to build it" +**Why it fails:** Wastes resources on low-impact features +**Fix:** Accept that some features should be cut + +### Mistake 4: Not Re-Scoring + +**Problem:** Never updating scores as you learn +**Why it fails:** Roadmap becomes stale +**Fix:** Re-score quarterly or when strategy shifts + +### Mistake 5: Forgetting Feasibility + +**Problem:** Prioritizing impossible features +**Why it fails:** Can't actually execute +**Fix:** Combine strategic score with feasibility + +--- + +## Using the Scored Feature List + +### For Sprint Planning + +**Each sprint:** +- Reference the scored list +- Focus on highest-impact features +- Validate against Trigger Map +- Make trade-offs based on strategy + +### For Stakeholder Communication + +**When presenting:** +1. Show the Trigger Map +2. Show the scoring matrix +3. Show the prioritized list +4. Explain the strategic reasoning + +**Stakeholders appreciate:** +- Clear methodology +- Traceable decisions +- Strategic foundation +- Data-driven approach + +### For Design Decisions + +**During design:** +- Reference the scores +- Focus on high-impact features first +- Ensure design addresses the drivers +- Validate against scoring + +**Example:** +"We're designing the pulse check (score: 9). It needs to address burnout fear, so let's include early warning indicators and actionable suggestions." + +--- + +## The Complete Chain + +Now you have the full Trigger Mapping system: + +``` +Workshop 1: Business Goals (Vision + Objectives) + ↓ +Workshop 2: Target Groups (3-5 prioritized personas) + ↓ +Workshop 3: Driving Forces (positive + negative for each) + ↓ +Workshop 4: Prioritization (ranked groups and drivers) + ↓ +Workshop 5: Feature Impact (scored feature list) + ↓ +Strategic Roadmap (data-driven priorities) +``` + +**Every feature traces back to:** +- A psychological driver +- A target group +- A business goal + +**No orphaned features. No guesswork. Strategic clarity.** + +--- + +## What's Next + +You're ready to create your own Trigger Map. The tutorial walks through all 5 workshops step by step with Saga, and the next lessons cover how to create and use the visual Trigger Map. + +--- + +## Key Takeaways + +✅ **Systematic scoring** - Features rated 0-3 against prioritized drivers +✅ **Data-driven roadmap** - Total scores determine priorities +✅ **Strategically defensible** - Every decision traces to strategy +✅ **Flexible and updateable** - Re-score when strategy shifts +✅ **Beyond numbers** - The conversation reveals insights +✅ **Complete traceability** - Feature → Driver → Group → Goal + +--- + +[← Back to Lesson 7](lesson-07-workshop-4-prioritization.md) | [Next: Lesson 9 - Positive & Negative Drivers →](lesson-09-positive-negative-drivers.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-09-positive-negative-drivers.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-09-positive-negative-drivers.md new file mode 100644 index 000000000..13bf79202 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-09-positive-negative-drivers.md @@ -0,0 +1,348 @@ +# Lesson 4: Positive & Negative Drivers + +**The Psychology That Drives Behavior** + +--- + +## The Core Concept + +Every user has two types of motivations: + +**Positive Drivers (GAIN):** +- What they want to achieve +- Benefits they're seeking +- Goals that pull them forward + +**Negative Drivers (PAIN):** +- What they want to avoid +- Problems they're trying to escape +- Fears that push them to act + +**The key insight:** Both matter, but they work differently. Understanding both gives you the complete psychological picture. + +--- + +## Why Negative Drivers Are More Powerful + +Research in behavioral psychology consistently shows: **People work harder to avoid pain than to pursue gain.** + +This is called **loss aversion** - the psychological principle that losses feel roughly twice as painful as equivalent gains feel good. + +### Generic Examples + +**Scenario 1: Fitness App** + +**Positive driver:** "Want to look good for summer" +- Motivating? Yes +- Urgent? Not really +- Action trigger: Weak (can start "next week") + +**Negative driver:** "Fear of health problems like my parent had" +- Motivating? Extremely +- Urgent? Yes +- Action trigger: Strong (need to act now) + +**Which drives more sign-ups?** The fear. + +**Scenario 2: Project Management Tool** + +**Positive driver:** "Want to be more organized" +- Nice to have +- Can live without it +- Low urgency + +**Negative driver:** "Fear of missing client deadline and losing contract" +- Critical need +- Can't afford to fail +- High urgency + +**Which drives more conversions?** The fear. + +--- + +## How to Identify Positive Drivers + +Positive drivers are what users are moving TOWARD. + +### The Questions to Ask + +- What do they want to accomplish? +- What positive outcomes are they seeking? +- What would make their situation better? +- What goals are they trying to achieve? +- What benefits would they value? + +### Generic Examples Across Contexts + +**Professional Context:** +- Want to advance in career +- Want to be seen as competent leader +- Want to deliver high-quality work +- Want to build strong professional reputation +- Want to learn new skills + +**Personal Context:** +- Want to feel in control of their life +- Want to spend quality time with family +- Want to maintain healthy lifestyle +- Want to feel accomplished +- Want to reduce stress + +**Social Context:** +- Want to be respected by peers +- Want to contribute to community +- Want to build meaningful relationships +- Want to be seen as helpful +- Want to belong to a group + +### Avoiding Surface-Level Statements + +**❌ Too vague:** +- "Want to be productive" +- "Want to save time" +- "Want better results" + +**✅ Specific and meaningful:** +- "Want to complete projects without last-minute panic" +- "Want to leave work on time to have dinner with family" +- "Want to deliver work that impresses stakeholders" + +--- + +## How to Identify Negative Drivers + +Negative drivers are what users are moving AWAY FROM. + +### The Questions to Ask + +- What problems are they trying to avoid? +- What frustrates them about current situation? +- What do they fear will happen? +- What keeps them up at night? +- What would be embarrassing or costly? + +### Generic Examples Across Contexts + +**Professional Context:** +- Fear of missing important deadlines +- Fear of looking incompetent to boss/clients +- Fear of being passed over for promotion +- Fear of making costly mistakes +- Fear of falling behind in skills + +**Personal Context:** +- Fear of burnout and health decline +- Fear of missing important family moments +- Fear of losing control of their life +- Fear of financial instability +- Fear of disappointing loved ones + +**Social Context:** +- Fear of being judged by peers +- Fear of letting team down +- Fear of being excluded +- Fear of conflict and confrontation +- Fear of losing respect + +### The Emotional Core + +Negative drivers often have strong emotional components: + +- **Shame:** "What will people think?" +- **Guilt:** "I'm letting people down" +- **Anxiety:** "What if this goes wrong?" +- **Embarrassment:** "This makes me look bad" +- **Fear:** "I could lose something important" + +**These emotions drive urgent action.** + +--- + +## Balancing Both Types + +The most powerful understanding comes from mapping BOTH: + +### Generic Example: Email Management Tool + +**Positive Drivers:** +- Want to feel organized and in control +- Want to respond thoughtfully to important messages +- Want to maintain professional communication standards +- Want to reduce mental clutter + +**Negative Drivers:** +- Fear of missing urgent client emails +- Fear of looking unprofessional with late responses +- Fear of important messages getting buried +- Fear of constant email anxiety disrupting focus + +**The design insight:** +- Positive drivers suggest: Clean interface, thoughtful organization +- Negative drivers suggest: Urgent message alerts, priority inbox, "nothing missed" confidence + +**Both inform the solution, but negative drivers create urgency to adopt.** + +--- + +## Common Patterns + +### Pattern 1: Professional Reputation + +**Positive:** Want to be seen as competent +**Negative:** Fear of looking incompetent + +**Design implication:** Features that help users look good and avoid embarrassment + +### Pattern 2: Time Management + +**Positive:** Want to be productive +**Negative:** Fear of wasting time or missing deadlines + +**Design implication:** Time-saving features + deadline protection + +### Pattern 3: Social Connection + +**Positive:** Want to build relationships +**Negative:** Fear of isolation or being left out + +**Design implication:** Connection features + FOMO prevention + +### Pattern 4: Control & Autonomy + +**Positive:** Want to feel in control +**Negative:** Fear of chaos and overwhelm + +**Design implication:** Organization tools + anxiety reduction + +--- + +## How to Use This in Design + +### For Feature Prioritization + +Features that address negative drivers often rank higher because they solve urgent problems. + +**Generic example:** +- Feature A: "Nice dashboard for tracking progress" (positive driver) +- Feature B: "Alert system for missed critical tasks" (negative driver) +- **Which is more urgent?** Feature B (prevents pain) + +### For Messaging & Marketing + +**Positive-focused messaging:** +- "Achieve your goals" +- "Be more productive" +- "Build better habits" + +**Negative-focused messaging:** +- "Never miss another deadline" +- "Stop the chaos" +- "Avoid costly mistakes" + +**Which converts better?** Usually negative-focused (addresses urgent pain) + +### For User Onboarding + +**Show value by addressing both:** +1. Acknowledge the pain (negative driver) +2. Show how you solve it +3. Highlight the positive outcome + +**Generic example:** +"Tired of missing important emails? (negative) +Our priority inbox ensures nothing slips through. (solution) +Respond confidently and maintain your professional reputation. (positive)" + +--- + +## Workshop 3 in Practice + +When you're in Workshop 3 with Saga, you'll work through each persona systematically: + +**For each persona:** +1. List 3-5 positive drivers +2. List 3-5 negative drivers +3. Identify which are strongest +4. Note emotional intensity + +**Saga will challenge you:** +- "Is that specific enough?" +- "What's the emotional core of that fear?" +- "Why does that matter to them?" +- "What would happen if they don't solve this?" + +**Your job:** Dig deeper than surface-level wants. Find the real psychological drivers. + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Only Mapping Positive Drivers + +**Problem:** You miss the urgent pain that drives adoption +**Solution:** Always map both types + +### Mistake 2: Generic "Wants" Statements + +**Problem:** "Want to be productive" doesn't guide design +**Solution:** Be specific about context and outcomes + +### Mistake 3: Ignoring Emotional Intensity + +**Problem:** All drivers seem equal +**Solution:** Identify which have strongest emotional pull + +### Mistake 4: Assuming Positive = Good, Negative = Bad + +**Problem:** Negative drivers feel uncomfortable to discuss +**Solution:** Embrace them - they're often more powerful motivators + +### Mistake 5: Listing Features Instead of Psychology + +**Problem:** "Want a calendar feature" +**Solution:** "Want to never miss family commitments due to work chaos" + +--- + +## The Power of This Approach + +When you map both positive and negative drivers: + +✅ **Complete psychological picture** - Understand full motivation +✅ **Better feature prioritization** - Know what's urgent vs nice-to-have +✅ **Stronger messaging** - Address real pain points +✅ **Higher conversion** - Solve urgent problems +✅ **Better retention** - Deliver on both gain and pain reduction + +--- + +## What You'll Learn Next + +The next lesson shows you how to create the visual Trigger Map - the one-page strategic document that connects all these layers and becomes your team's reference for every design decision. + +--- + +## Key Takeaways + +✅ **Two types of drivers** - Positive (gain) and Negative (pain) +✅ **Negative is more powerful** - Loss aversion drives urgent action +✅ **Map both for each persona** - Complete psychological picture +✅ **Be specific** - Avoid generic wants, find emotional core +✅ **Use in design** - Negative drivers often indicate highest-priority features + +--- + +## Practice Exercise + +Think about a product you use regularly. Identify: + +1. What positive outcomes do you seek from it? +2. What negative outcomes are you trying to avoid? +3. Which driver is stronger for you? +4. How does the product address both? + +--- + +[← Back to Lesson 8](lesson-08-workshop-5-feature-impact.md) | [Next: Lesson 10 - Visual Trigger Map →](lesson-10-visual-trigger-map.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-10-visual-trigger-map.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-10-visual-trigger-map.md new file mode 100644 index 000000000..ccb5688e1 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-10-visual-trigger-map.md @@ -0,0 +1,411 @@ +# Lesson 5: The Visual Trigger Map + +**Your One-Page Strategic Document** + +--- + +## What Is the Trigger Map? + +The Trigger Map is a visual diagram that shows the strategic connections between: + +- **Business Goals** (center) - What you need to achieve +- **Target Groups** (radiating out) - Who can help you achieve it +- **Usage Goals** (connected to each group) - What drives their behavior + +**It's a one-page strategy document that everyone can understand.** + +--- + +## Why Visual Matters + +### The Problem with Text Documents + +Traditional strategy documents: +- 20+ pages of text +- Nobody reads them completely +- Hard to see connections +- Difficult to reference quickly +- Become outdated and ignored + +### The Power of Visual + +A Trigger Map: +- ✅ One page, scannable in 30 seconds +- ✅ Shows strategic connections visually +- ✅ Easy to reference during design +- ✅ Stakeholders understand immediately +- ✅ Stays relevant as features evolve + +**Visual = Accessible = Actually Used** + +--- + +## The Structure + +**The Trigger Map flows horizontally from left to right in four layers:** + +### Layer 1: Business Goals (Left) + +**What it shows:** +- Vision statement(s) - inspirational direction +- 3-5 SMART objectives - measurable targets +- Multiple goals can feed into the product + +**Visual cues:** +- Blue boxes on the left +- Clear hierarchy of goals +- All connect to the product/solution + +### Layer 2: Product/Solution (Center) + +**What it shows:** +- Product name +- Brief description of what it does +- Central hub of the map + +**Why it's central:** +- Connects business goals to users +- Shows what you're building +- Everything flows through here + +### Layer 3: Target Groups (Middle-Right) + +**What it shows:** +- 3-5 prioritized personas +- Priority indicators (👥 primary, 👤 secondary) +- Connected from the product + +**Visual cues:** +- Orange boxes +- Emoji indicators show priority +- Lines connect from product to each group + +### Layer 4: Usage Goals (Right) + +**What it shows:** +- **Positive drivers** (✅ green) - What they want to achieve +- **Negative drivers** (❌ red) - What they want to avoid +- Separated into distinct boxes per target group + +**Visual organization:** +- Green boxes for positive drivers +- Red boxes for negative drivers +- Each target group has both types +- Top drivers emphasized + +--- + +## Generic Example Structure + +``` +GOALS PRODUCT TARGET GROUPS DRIVERS +───────────────────── ─────────────────── ─────────────────── ──────────────────── +[BUSINESS GOAL 1] [PRODUCT/ [👥 PRIMARY [✅ POSITIVE] +Vision Statement 1 ──→ SOLUTION ──────→ TARGET GROUP] ───→ • Positive Goal 1 +Strategic Obj 1-3 Name & Brief profile • Positive Goal 2 + Description │ +[BUSINESS GOAL 2] │ [❌ NEGATIVE] +Vision Statement 2 ──→ └─────────────→ • Negative Goal 1 +Strategic Obj 1-3 • Negative Goal 2 + + + [👤 SECONDARY [✅ POSITIVE] + ────→ TARGET GROUP] ─────→ • Positive Goal 1 + Brief profile • Positive Goal 2 + │ + │ [❌ NEGATIVE] + └─────────────→ • Negative Goal 1 + • Negative Goal 2 +``` + +--- + +## How to Read the Map + +### Following the Strategic Chain + +**Start at center:** +"We want to achieve [business goal]" + +**Move to groups:** +"[Target group] can help us achieve this" + +**Look at drivers:** +"They're motivated by [positive drivers] and avoiding [negative drivers]" + +**Design implication:** +"So we should build features that address their top drivers" + +### Generic Example Walkthrough + +**Center:** "Achieve 10,000 active users by Q4" + +**Group 1:** "Remote team leads" (Priority #1) + +**Top positive driver:** "Want to demonstrate effective leadership" + +**Top negative driver:** "Fear team burnout without noticing" + +**Design insight:** "Build features that help leaders monitor team health and take action - this serves both their drivers AND our user growth goal" + +--- + +## What Makes a Good Trigger Map + +### Clarity + +**Good:** +- Clear hierarchy (what's most important) +- Specific drivers (not generic wants) +- Visual connections obvious +- Scannable in under a minute + +**Bad:** +- Everything seems equal priority +- Vague statements +- Cluttered with too much detail +- Requires explanation to understand + +### Actionability + +**Good:** +- Designers can reference it for decisions +- Clear which drivers to address first +- Obvious connections to features +- Guides prioritization + +**Bad:** +- Too abstract to guide design +- No clear priorities +- Doesn't connect to actual features +- Purely theoretical + +### Longevity + +**Good:** +- Focuses on strategy, not features +- Stays relevant as product evolves +- Updated only when strategy changes +- Long-term reference document + +**Bad:** +- Includes specific features (becomes outdated) +- Needs constant updating +- Tied to current implementation +- Becomes obsolete quickly + +--- + +## How Teams Use the Trigger Map + +### Designers + +**Use it to:** +- Guide every design decision +- Validate feature ideas +- Prioritize design work +- Explain design rationale + +**Example:** +"Should we add this feature? Let me check the Trigger Map... Yes, it addresses the top negative driver for our #1 target group." + +### Developers + +**Use it to:** +- Understand the "why" behind features +- Make implementation trade-offs +- Suggest technical alternatives +- Stay aligned with strategy + +**Example:** +"This technical approach would be faster but wouldn't address the key driver. Let's find a solution that serves the strategy." + +### Product Managers + +**Use it to:** +- Prioritize roadmap +- Evaluate feature requests +- Communicate strategy +- Make scope decisions + +**Example:** +"This stakeholder request doesn't connect to any of our top drivers. Let's deprioritize it." + +### Stakeholders + +**Use it to:** +- Understand strategic direction +- See how decisions connect to goals +- Provide informed feedback +- Trust the process + +**Example:** +"I can see how this feature addresses the fear of [negative driver] for our top group. That makes sense." + +--- + +## Creating Your Map + +### Tools + +**Simple options:** +- Pen and paper (sketch it first) +- Whiteboard (team workshops) +- Miro or FigJam (digital collaboration) +- Markdown with indentation (text-based) + +**What matters:** +- Visual hierarchy is clear +- Connections are obvious +- Easy to reference +- Team can access it + +### Process + +**During Workshop 2-4:** +- Saga helps you build it iteratively +- Start with goals +- Add groups +- Add drivers +- Refine and prioritize + +**After workshops:** +- Create clean visual version +- Share with team +- Post where everyone can see +- Reference in all design discussions + +--- + +## Keeping It Current + +### When to Update + +**Update when:** +- ✅ Business goals change significantly +- ✅ New user research reveals different drivers +- ✅ Strategic priorities shift +- ✅ New target group becomes important + +**Don't update when:** +- ❌ Features change (map is strategy, not features) +- ❌ Minor tweaks to objectives +- ❌ Tactical decisions +- ❌ Short-term experiments + +### Living Document Approach + +**The map should:** +- Be referenced weekly in design discussions +- Be updated quarterly (or when strategy shifts) +- Be visible to entire team +- Be the source of truth for strategic decisions + +**It should NOT:** +- Be created once and forgotten +- Be updated constantly +- Include implementation details +- Replace other documentation + +--- + +## The Power of One Page + +### Why One Page Matters + +**Cognitive load:** +- Humans can't hold complex strategy in working memory +- One page = graspable at a glance +- Visual connections = easier to remember + +**Accessibility:** +- Everyone can understand it +- No special training needed +- Quick reference during meetings +- Easy to share + +**Alignment:** +- Entire team sees same picture +- Reduces misunderstandings +- Creates shared language +- Builds strategic consensus + +--- + +## Common Mistakes + +### Mistake 1: Too Much Detail + +**Problem:** Map becomes cluttered and unusable +**Solution:** Keep it strategic - details go in supporting docs + +### Mistake 2: Including Features + +**Problem:** Map becomes outdated as features change +**Solution:** Features are scored separately (Workshop 5) + +### Mistake 3: No Visual Hierarchy + +**Problem:** Everything seems equally important +**Solution:** Use size, color, position to show priority + +### Mistake 4: Creating It Once and Forgetting + +**Problem:** Map doesn't guide actual decisions +**Solution:** Reference it constantly, update when strategy shifts + +### Mistake 5: Making It Too Pretty + +**Problem:** Spending hours on design instead of strategy +**Solution:** Clarity > beauty. Sketch is fine. + +--- + +## The Strategic Conversation + +The real value isn't the map itself - it's the strategic conversation that creates it. + +**The map is:** +- A record of strategic thinking +- A tool for alignment +- A guide for decisions +- A living reference + +**The conversation is:** +- Where insights emerge +- Where assumptions are challenged +- Where priorities become clear +- Where strategy is forged + +**Both matter. The map captures the conversation so you don't lose it.** + +--- + +## What You'll Learn Next + +The final lesson covers Feature Impact Scoring - how to systematically evaluate and rank features based on your Trigger Map. This is where strategy becomes actionable roadmap. + +--- + +## Key Takeaways + +✅ **One-page visual document** - Scannable, accessible, actually used +✅ **Shows strategic connections** - Goals → Groups → Drivers +✅ **Guides all design decisions** - Reference it constantly +✅ **Stays relevant** - Focuses on strategy, not features +✅ **Creates team alignment** - Everyone sees same strategic picture +✅ **Living document** - Update when strategy shifts, not when features change + +--- + +## Reflection Questions + +1. How would having a one-page strategy map change your design process? +2. What strategic decisions could you make faster with this reference? +3. How would this help align your team around priorities? + +--- + +[← Back to Lesson 9](lesson-09-positive-negative-drivers.md) | [Next: Lesson 11 - Feature Impact Scoring →](lesson-11-feature-impact-scoring.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-11-feature-impact-scoring.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-11-feature-impact-scoring.md new file mode 100644 index 000000000..526815d38 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/lesson-11-feature-impact-scoring.md @@ -0,0 +1,403 @@ +# Lesson 6: Feature Impact Scoring + +**Systematic Feature Prioritization** + +--- + +## The Problem with Traditional Prioritization + +How do most teams prioritize features? + +**Common approaches:** +- "The CEO wants it" (politics) +- "It seems important" (gut feeling) +- "Competitors have it" (copying) +- "Users asked for it" (squeaky wheel) +- "It's easy to build" (convenience) + +**The result:** Random feature lists with no strategic foundation. + +--- + +## The Feature Impact Approach + +Feature Impact Scoring connects features directly to your Trigger Map: + +**The logic:** +1. You've prioritized target groups (Workshop 4) +2. You've prioritized their driving forces (Workshop 4) +3. Now score each feature: How well does it address top drivers? +4. Features with highest scores = highest strategic impact + +**The result:** Data-driven prioritization based on user psychology and business goals. + +--- + +## How the Scoring Works + +### Step 1: List Your Features + +Brainstorm all potential features: +- Ideas from Product Brief +- Stakeholder requests +- Competitor features +- User feedback +- Team suggestions + +**Aim for:** 10-20 features to evaluate + +### Step 2: Set Up the Scoring Matrix + +Create a matrix with: +- **Rows:** Your features +- **Columns:** Top 5-7 prioritized driving forces +- **Cells:** Impact scores (0-3 scale) + +### Step 3: Score Each Feature + +For each feature, ask: "How well does this address [driving force]?" + +**Scoring scale:** +- **3** = Directly addresses this driver (core solution) +- **2** = Significantly helps with this driver +- **1** = Somewhat related to this driver +- **0** = Doesn't address this driver + +### Step 4: Calculate Total Scores + +Sum the scores across all drivers for each feature. + +**Higher total = Higher strategic impact** + +### Step 5: Rank and Prioritize + +Sort features by total score to create your prioritized roadmap. + +--- + +## Generic Example + +### Context + +**Top Target Group:** Remote Team Leads + +**Top Prioritized Drivers:** +1. Fear of team burnout without noticing (Negative - Priority 1) +2. Want to demonstrate effective leadership (Positive - Priority 2) +3. Fear of losing top performers (Negative - Priority 3) +4. Want to build strong team culture (Positive - Priority 4) +5. Fear of missed deadlines (Negative - Priority 5) + +### Features to Evaluate + +1. Daily team pulse check +2. Async video updates +3. Automated meeting summaries +4. Team workload dashboard +5. Recognition and kudos system + +### Scoring Matrix + +| Feature | Burnout Fear | Leadership | Losing Performers | Team Culture | Missed Deadlines | **Total** | +|---------|-------------|------------|-------------------|--------------|------------------|-----------| +| Daily pulse check | 3 | 2 | 2 | 1 | 1 | **9** | +| Team workload dashboard | 3 | 2 | 2 | 0 | 2 | **9** | +| Recognition system | 1 | 1 | 2 | 3 | 0 | **7** | +| Meeting summaries | 0 | 1 | 0 | 1 | 2 | **4** | +| Async video updates | 1 | 1 | 0 | 2 | 0 | **4** | + +### Prioritized Roadmap + +**Phase 1 (Highest Impact):** +1. Daily pulse check (Score: 9) +2. Team workload dashboard (Score: 9) + +**Phase 2 (High Impact):** +3. Recognition system (Score: 7) + +**Phase 3 (Lower Impact):** +4. Meeting summaries (Score: 4) +5. Async video updates (Score: 4) + +--- + +## Why This Works + +### It's Strategic + +Every score connects to: +- A prioritized driving force +- A prioritized target group +- A business goal + +**Not arbitrary - traceable to strategy** + +### It's Objective + +**Traditional:** "I think Feature A is more important" +**Feature Impact:** "Feature A scores 9, Feature B scores 4" + +**Data beats opinions** + +### It's Defensible + +When stakeholders ask "Why aren't we building X?" + +**You can show:** +- Here's our Trigger Map +- Here are our top drivers +- Here's how features score against them +- Feature X scores lower than our current roadmap + +**Strategic reasoning, not politics** + +### It's Flexible + +**When priorities change:** +- Update driver rankings +- Re-score features +- New roadmap emerges + +**Strategy drives features, not the reverse** + +--- + +## Scoring Guidelines + +### For Negative Drivers (Fears/Frustrations) + +**Ask:** "Does this feature help users avoid this pain?" + +**High score (3):** +- Directly prevents the feared outcome +- Provides early warning system +- Creates safety net + +**Example:** +- Driver: "Fear of team burnout without noticing" +- Feature: "Daily pulse check with burnout indicators" +- Score: 3 (directly addresses the fear) + +### For Positive Drivers (Goals/Benefits) + +**Ask:** "Does this feature help users achieve this goal?" + +**High score (3):** +- Directly enables the desired outcome +- Makes the goal achievable +- Provides clear progress toward goal + +**Example:** +- Driver: "Want to demonstrate effective leadership" +- Feature: "Team health dashboard with actionable insights" +- Score: 2 (provides data to demonstrate leadership) + +### When in Doubt + +**Be honest:** +- Don't inflate scores to justify pet features +- 0 is okay - not everything addresses everything +- Challenge yourself: "Does this REALLY address this driver?" + +**Saga will help:** +- "How specifically does this address the fear?" +- "What about this feature reduces that pain?" +- "Is this a 2 or a 3? What's the difference?" + +--- + +## Common Patterns + +### Pattern 1: High Scores Across Multiple Drivers + +**What it means:** This feature has high leverage - it addresses multiple psychological needs + +**Example:** +- Daily pulse check scores high on burnout fear, leadership goals, and retention fear +- **Action:** Prioritize this - it's strategically valuable + +### Pattern 2: High Score on Top Driver Only + +**What it means:** Laser-focused solution for most important need + +**Example:** +- Workload balancing tool scores 3 on burnout fear, low on others +- **Action:** Still high priority if that driver is #1 + +### Pattern 3: Moderate Scores Across Many Drivers + +**What it means:** Nice-to-have that helps a bit with everything + +**Example:** +- Team chat feature scores 1-2 on multiple drivers +- **Action:** Lower priority - not solving urgent problems + +### Pattern 4: Low Scores Everywhere + +**What it means:** Feature doesn't connect to strategy + +**Example:** +- Fancy animations score 0-1 across all drivers +- **Action:** Cut it or deprioritize significantly + +--- + +## Beyond the Numbers + +### The Conversation Matters + +The real value isn't just the scores - it's the strategic conversation: + +**Questions that emerge:** +- "Why doesn't this feature score higher?" +- "Could we modify it to address more drivers?" +- "Are we missing a feature that would score higher?" +- "Do these scores match our intuition? If not, why?" + +**Insights from discussion:** +- Features can be refined to increase impact +- Missing features can be identified +- Assumptions can be challenged +- Strategy can be sharpened + +### Combining with Other Factors + +Feature Impact is strategic value. You should also consider: + +**Feasibility:** +- How hard is this to build? +- Do we have the resources? +- What's the technical risk? + +**Dependencies:** +- Does this require other features first? +- Does this enable other features? + +**Market timing:** +- Is this urgent for competitive reasons? +- Is there a window of opportunity? + +**Combined prioritization:** +``` +Priority = (Strategic Impact × Feasibility) + Urgency Bonus +``` + +--- + +## Using the Scored Feature List + +### For Roadmap Planning + +**Phase 1:** Top-scoring features (typically 8-10 range) +**Phase 2:** High-scoring features (typically 6-7 range) +**Phase 3:** Medium-scoring features (typically 4-5 range) +**Backlog:** Low-scoring features (typically 0-3 range) + +### For Stakeholder Communication + +**When presenting roadmap:** +1. Show the Trigger Map +2. Show the scoring matrix +3. Show the prioritized list +4. Explain the strategic reasoning + +**Stakeholders appreciate:** +- Clear methodology +- Traceable decisions +- Strategic foundation +- Data-driven approach + +### For Design Decisions + +**During design:** +- Reference the scores +- Focus on high-impact features first +- Ensure design addresses the drivers +- Validate against the scoring + +**Example:** +"We're designing the pulse check (score: 9). It needs to address burnout fear, so let's include early warning indicators and actionable suggestions." + +--- + +## Updating Scores + +### When to Re-Score + +**Re-score when:** +- ✅ New user research changes driver priorities +- ✅ Business goals shift +- ✅ You learn features don't work as expected +- ✅ Quarterly strategy reviews + +**Don't re-score when:** +- ❌ Stakeholder has new pet feature +- ❌ Competitor launches something +- ❌ Minor tactical changes +- ❌ Every sprint planning meeting + +### The Living Roadmap + +**The scored feature list should:** +- Be updated quarterly (or when strategy shifts) +- Be referenced in every sprint planning +- Guide all feature discussions +- Evolve with your understanding + +--- + +## The Complete Picture + +Now you have the full Trigger Mapping system: + +``` +Workshop 1: Business Goals + ↓ +Workshop 2: Target Groups (prioritized) + ↓ +Workshop 3: Driving Forces (positive + negative) + ↓ +Workshop 4: Prioritization (top drivers identified) + ↓ +Workshop 5: Feature Impact (scored feature list) + ↓ +Strategic Roadmap (data-driven priorities) +``` + +**Every feature traces back to:** +- A psychological driver +- A target group +- A business goal + +**No orphaned features. No guesswork. Strategic clarity.** + +--- + +## What's Next + +You're ready to create your own Trigger Map. The tutorial will walk you through all 5 workshops step by step with Saga, creating your complete Trigger Map and scored feature list. + +--- + +## Key Takeaways + +✅ **Systematic scoring** - Features rated against prioritized drivers (0-3 scale) +✅ **Data-driven prioritization** - Total scores determine roadmap +✅ **Strategically defensible** - Every decision traces to strategy +✅ **Flexible and updateable** - Re-score when strategy shifts +✅ **Beyond numbers** - The conversation reveals insights +✅ **Complete traceability** - Feature → Driver → Group → Goal + +--- + +## Reflection Questions + +1. How would systematic scoring change your current prioritization process? +2. What features on your roadmap might score lower than you thought? +3. How would this help you defend design decisions to stakeholders? + +--- + +[← Back to Lesson 10](lesson-10-visual-trigger-map.md) | [Next: Tutorial - Create Your Trigger Map →](tutorial-05.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/module-05-overview.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/module-05-overview.md new file mode 100644 index 000000000..299b1b804 --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/module-05-overview.md @@ -0,0 +1,283 @@ +# Module 05: Trigger Mapping + +**Connect Business Goals to User Psychology** + +[Watch the Module Introduction Video](https://youtu.be/xs_cRk-NoJk) + +--- + +## Module Overview + +This module teaches you how to create a Trigger Map - the strategic bridge connecting what your business needs to what actually drives user behavior. Learn the proven methodology (20+ years of heritage), understand the 5 workshops, and discover how to map both positive and negative psychological drivers. + +**Time:** 95-125 minutes (11 lessons) +**Prerequisites:** Module 04 completed (Product Brief created) +**What you'll create:** Complete Trigger Map with prioritized features + +--- + +## What You'll Learn + +- Why jumping from brief to design fails (and what to do instead) +- The Effect Management heritage and WDS modernization +- The 3 strategic layers: Business Goals → Target Groups → Usage Goals +- How to run 5 workshops that map user psychology +- The power of negative driving forces (fears, frustrations) +- How to score features by strategic impact + +--- + +## Lessons + +### [Lesson 1: The Missing Link](lesson-01-missing-link.md) + +**Time:** 8-10 minutes + +Why Product Brief alone isn't enough: + +- The gap between strategy and design +- What happens when you skip user psychology +- How Trigger Mapping bridges business goals to user needs +- Real cost of designing without this foundation +- Your strategic insurance policy + +### [Lesson 2: The Heritage & Evolution](lesson-02-heritage-evolution.md) + +**Time:** 8-10 minutes + +From Effect Management to Trigger Mapping: + +- Effect Management methodology (inUse, Sweden) +- 20+ years of proven strategic design +- What WDS modernized (simplified map, negative drivers, feature scoring) +- The three strategic layers explained +- Why this approach works + +### [Lesson 3: The Five Workshops Overview](lesson-03-five-workshops-overview.md) + +**Time:** 10-12 minutes + +Your roadmap to strategic clarity: + +- The complete picture of all 5 workshops +- How each workshop builds on the previous one +- What you'll create at each stage +- What to expect when working with Saga +- Getting comfortable with the process + +### [Lesson 4: Workshop 1 - Business Goals](lesson-04-workshop-1-business-goals.md) + +**Time:** 8-10 minutes + +Define what winning looks like: + +- Understanding Vision (visionary statements) vs Strategic Objectives +- The bridging question: "What will we observe?" +- Creating strategic objectives using SMART method +- Workshop flow and key questions +- Foundation for all strategic decisions + +### [Lesson 5: Workshop 2 - Target Groups](lesson-05-workshop-2-target-groups.md) + +**Time:** 10-12 minutes + +Who is ensuring our success? + +- The core question: WHO will make sure, with their use of the product, that you achieve your goals +- Real people out there in the world (not abstract segments) +- Behavioral profiles vs demographics +- Creating rich personas with context +- Prioritizing by strategic value and product usage impact + +### [Lesson 6: Workshop 3 - Driving Forces](lesson-06-workshop-3-driving-forces.md) + +**Time:** 10-12 minutes + +Map the psychology that drives behavior: + +- Positive drivers (what users want to achieve) +- Negative drivers (what users want to avoid) +- Why negative drivers are more powerful (loss aversion) +- Emotional intensity and urgency +- Complete psychological profiles + +### [Lesson 7: Workshop 4 - Prioritization](lesson-07-workshop-4-prioritization.md) + +**Time:** 8-10 minutes + +Rank what matters most: + +- Prioritizing target groups by strategic value +- Prioritizing drivers by emotional intensity +- The prioritization cascade +- Creating focus for design efforts +- Foundation for feature scoring + +### [Lesson 8: Workshop 5 - Feature Impact](lesson-08-workshop-5-feature-impact.md) + +**Time:** 10-12 minutes + +Score features by strategic impact: + +- Systematic scoring (0-3 scale) +- Rating features against prioritized drivers +- Calculating total impact scores +- Creating data-driven roadmap +- Complete traceability from features to goals + +### [Lesson 9: Positive & Negative Drivers](lesson-09-positive-negative-drivers.md) + +**Time:** 10-12 minutes + +Deep dive into the psychology that drives behavior: + +- What are driving forces (positive and negative) +- Why negative drivers are more powerful (loss aversion) +- How to identify both types for each persona +- Generic examples across different contexts +- Avoiding surface-level "wants" statements + +### [Lesson 10: The Visual Trigger Map](lesson-10-visual-trigger-map.md) + +**Time:** 8-10 minutes + +**The Four-Layer Structure:** +- Business Goals → Product/Solution → Target Groups → Usage Goals (Positive + Negative separated) + +**What you'll learn:**ategic one-page document: + +- What the Trigger Map looks like +- How to read and use it +- Why it stays relevant as features evolve +- How teams use it for alignment +- When to update it (and when not to) + +### [Lesson 11: Feature Impact Scoring](lesson-11-feature-impact-scoring.md) + +**Time:** 9-11 minutes + +Deep dive into systematic feature prioritization: + +- How the scoring system works in detail +- Rating features against prioritized drivers +- Calculating total impact scores +- Creating your ranked feature list +- Making data-driven design decisions + +--- + +## Tutorials + +### [Tutorial 05: Create Your Trigger Map](tutorial-05.md) + +**Full Trigger Mapping Process (Starting from Scratch)** + +Step-by-step hands-on guide to creating your complete Trigger Map with Saga through all 5 workshops. + +**Time:** 60-90 minutes +**What you'll create:** Complete Trigger Map + scored feature list +**Best for:** Major products, multiple user groups, comprehensive strategy, no existing documentation + +--- + +### [Tutorial 05B: Create Your Value Trigger Chain](tutorial-05b-value-trigger-chain.md) + +**Lightweight Alternative (Quick Validation)** + +Quick strategic validation for focused user journeys - streamlined single-workshop approach. + +**Time:** 15-20 minutes +**What you'll create:** Single-chain map from goal to trigger +**Best for:** Smaller features, single journey, quick validation, time-constrained situations + +--- + +### [Tutorial 05C: Synthesize from Documentation](tutorial-05c-documentation-synthesis.md) + +**Documentation Synthesis (Existing Research)** + +Transform existing documentation into an actionable Trigger Map - validate and organize what you already have. + +**Time:** 30-45 minutes +**What you'll create:** Synthesized Trigger Map + gap analysis +**Best for:** Extensive vision docs, user research, plans, or interviews that need to be made actionable + +**Which tutorial should you use?** See [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md#three-approaches-choose-your-path) for guidance. + +--- + +## Key Concepts + +**Trigger Mapping:** +- Strategic bridge from business goals to user psychology +- Based on 20+ years of Effect Management methodology +- Visual one-page map showing strategic connections +- Created through 5 structured workshops with Saga +- Includes both positive and negative psychological drivers + +**The Three Strategic Layers:** +1. **Business Goals** - Your WHY (vision + SMART objectives) +2. **Target Groups** - The WHO (user types whose success drives yours) +3. **Usage Goals** - Their WHY (positive drivers + negative drivers) + +**The Five Workshops:** +1. **Business Goals** - Define vision and measurable objectives +2. **Target Groups** - Identify and create personas +3. **Driving Forces** - Map positive and negative psychology +4. **Prioritization** - Rank groups and drivers by impact +5. **Feature Impact** - Score features against drivers + +**WDS Modernization:** +- **Simplified:** Removed features from map (stays relevant longer) +- **Enhanced:** Added negative driving forces (fuller psychology) +- **Systematic:** Integrated feature scoring (data-driven decisions) + +**Positive vs Negative Drivers:** +- **Positive:** What users want to achieve (goals, benefits, gains) +- **Negative:** What users want to avoid (fears, frustrations, pain) +- **Key insight:** People work harder to avoid pain than pursue gain + +--- + +## Learning Outcomes + +By the end of this module, you will: + +- ✅ Understand why Trigger Mapping is essential before design +- ✅ Know the Effect Management heritage and WDS modernization +- ✅ Be able to facilitate all 5 Trigger Mapping workshops +- ✅ Understand how to identify positive and negative drivers +- ✅ Know how to create and use the visual Trigger Map +- ✅ Be able to score features by strategic impact +- ✅ Have confidence to create your own Trigger Map in 60-90 minutes + +--- + +## What You'll Create + +**Core Deliverables:** +- ✅ Business Goals (vision + 3-5 SMART objectives) +- ✅ Target Groups (3-5 prioritized personas) +- ✅ Driving Forces (positive + negative for each persona) +- ✅ Priority Rankings (groups and drivers ranked) +- ✅ Visual Trigger Map (one-page strategic document) +- ✅ Feature Impact Analysis (scored and ranked feature list) + +**Strategic Value:** +- Clear connection from business goals to user psychology +- Data-driven feature prioritization +- Team alignment around strategic priorities +- Foundation for all design decisions +- Traceable reasoning for every feature + +--- + +## Start Learning + +**[Begin with Lesson 1: The Missing Link →](lesson-01-missing-link.md)** + +--- + +[← Back to Module 04: Product Brief](../module-04-product-brief/module-04-overview.md) | [Next: Module 06: Scenarios →](../module-06-scenarios/module-06-overview.md) + +*Part of the WDS Course: From Designer to Linchpin* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05.md new file mode 100644 index 000000000..62b35b45c --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05.md @@ -0,0 +1,595 @@ +# Tutorial 05: Create Your Trigger Map + +**Hands-on guide to mapping business goals to user psychology** + +--- + +## Overview + +This tutorial walks you through creating a complete Trigger Map with Saga the Analyst. You'll complete all 5 workshops and create a scored feature list that guides your design decisions. + +**Time:** 60-90 minutes +**Prerequisites:** Module 04 completed (Product Brief created) +**What you'll create:** Complete Trigger Map + scored feature list + +--- + +## Before You Start + +### What You Need + +- ✅ Completed Product Brief (from Tutorial 04) +- ✅ WDS installed and Saga activated +- ✅ 60-90 minutes of focused time +- ✅ Open mind for strategic thinking + +### What to Expect + +**Saga will:** +- Guide you through 5 structured workshops +- Ask strategic questions +- Challenge vague answers +- Document everything +- Create your Trigger Map + +**You will:** +- Provide strategic thinking +- Make decisions +- Think deeply about user psychology +- Prioritize ruthlessly +- Connect strategy to features + +--- + +## Workshop 1: Business Goals (15-20 minutes) + +### Starting the Workshop + +**In your IDE, activate Saga:** + +``` +@saga I'm ready to start Trigger Mapping. Let's begin with Workshop 1: Business Goals. +``` + +### Understanding the Two Levels + +Business goals work on two levels: + +**Vision (Visionary Statements):** +- Aspirational and motivational +- Grand ambitions ("Be the best," "Top of mind") +- Easy to set, hard to measure +- Provides the "why" and emotional drive + +**Strategic Objectives:** +- Specific and measurable (expressed using SMART method) +- Observable evidence that vision is being realized +- Harder to set, easy to measure +- Provides the "what" and accountability + +### What Saga Will Ask + +**Step 1: 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?" + +**Step 2: Bridging Question** +- "When this vision is being realized, what will we observe in the world?" +- "What measurable evidence would prove you're succeeding?" + +**Step 3: 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 toward each goal?" + +### Your Task + +**1. Define your Vision:** +- Capture the grand ambition +- Focus on aspiration and motivation +- Don't worry about exact measurement + +**2. Bridge to observables:** +- Ask yourself: "What will we see when this is realized?" +- Transform vision into observable evidence + +**3. Create 3-5 SMART objectives:** +- Specific (not vague) +- Measurable (with numbers) +- Achievable (realistic) +- Relevant (to business) +- Time-bound (with deadline) + +See [SMART Method Reference](../../models/smart-goals-model.md) for detailed guidance on creating strategic objectives. + +### Example Interaction + +**Saga:** "What's the grand ambition behind this project?" + +**You:** "Make remote work sustainable and healthy for distributed teams." + +**Saga:** "Good vision. Now, when remote work is sustainable and healthy, what will we observe in the world? What measurable evidence would prove you're succeeding?" + +**You:** "We'd see teams using our tool daily, staying with us long-term, and growing their usage. We'd see revenue that proves the business model works." + +**Saga:** "Excellent. Let's turn those observations into SMART objectives. What specific numbers would prove daily usage?" + +**You:** "We need to achieve 5,000 active teams by Q4 2024, with at least 70% weekly retention and $50K monthly recurring revenue." + +**Saga:** "Perfect. Let's document your vision and all your strategic objectives..." + +### Workshop 1 Output + +You'll have: +- ✅ Clear vision statement (visionary statement) +- ✅ 3-5 strategic objectives (using SMART method) +- ✅ Connection between aspiration and measurement +- ✅ Documented success criteria +- ✅ Foundation for all strategic decisions + +--- + +## Workshop 2: Target Groups (20-25 minutes) + +### The Core Question + +**WHO out there in the world will make sure, with their use of the product, that you achieve your goals?** + +This workshop identifies real people whose product usage drives your business success. + +### Starting Workshop 2 + +**Continue with Saga:** + +``` +@saga Let's move to Workshop 2: Target Groups. +``` + +### What Saga Will Ask + +**The core question:** +- "WHO out there in the world will make sure, with their use of the product, that you achieve your goals?" +- "Which representatives from which ICP (Ideal Customer Profile) can drive your success?" +- "What real people's lives will your product touch?" + +**Identifying groups:** +- "What different user types could help you achieve your goals through their product use?" +- "What's the context for each group? What are they trying to accomplish?" +- "How will their use of the product connect to your business objectives?" + +**Creating personas:** +- "Tell me about [group name]. What's their situation?" +- "What are their goals and motivations?" +- "What frustrates them in their current situation?" +- "What do they fear or want to avoid?" +- "How will the product need to give more value than the pain of using it?" + +**Prioritizing:** +- "Which group's product usage has the most potential impact on your top business goal?" +- "Which group is most feasible to reach and serve effectively?" +- "How would you rank these groups by strategic value?" + +### Your Task + +**Identify 3-5 distinct groups:** +- Real people out there in the world (not abstract segments) +- Not demographics ("parents aged 30-45") +- Behavioral and contextual profiles ("busy working parents juggling multiple kids' schedules") +- Specific enough to design for +- Focus on who will use the product in ways that achieve your goals + +**Create persona for each:** +- Name and context (their real-world situation) +- Goals and motivations +- Frustrations and fears +- Behavioral patterns +- How their product use connects to your business goals + +**Rank by priority:** +- Which group's usage matters most for business goals? +- Which is most feasible to serve? +- Which will use the product in the intended way? + +### Example Interaction + +**Saga:** "WHO out there in the world will make sure, with their use of the product, that you achieve your goals?" + +**You:** "I see three main groups: remote team leads managing distributed teams, solo remote workers without office structure, and remote executives overseeing multiple teams. The team leads are critical because their daily use of team health monitoring directly drives our retention goal." + +**Saga:** "Good start. Let's dig into the first group - remote team leads. What's their context? What are they trying to accomplish? And how will their use of the product help you achieve your business objectives?" + +**You:** "They're managing 5-10 people across time zones. They want to keep the team productive and connected, but they can't see who's struggling. They fear team burnout and missed deadlines. If they use our pulse check feature daily, they'll prevent burnout, which drives our 70% retention goal." + +**Saga:** "Excellent. That's specific and connects their usage to your business goals. Let's create a full persona for this group..." + +### Workshop 2 Output + +You'll have: +- ✅ 3-5 prioritized target groups +- ✅ Detailed persona for each +- ✅ Clear ranking by strategic value +- ✅ Foundation for psychological mapping + +--- + +## Workshop 3: Driving Forces (20-30 minutes) + +### Starting Workshop 3 + +**Continue with Saga:** + +``` +@saga Let's move to Workshop 3: Driving Forces. +``` + +### What Saga Will Ask + +**For each persona, Saga will explore:** + +**Positive drivers:** +- "What does [persona] want to accomplish?" +- "What positive outcomes are they seeking?" +- "What would make their situation better?" +- "What goals are pulling them forward?" + +**Negative drivers:** +- "What problems are they trying to avoid?" +- "What frustrates them about current solutions?" +- "What do they fear will happen if they don't solve this?" +- "What keeps them up at night?" + +**Emotional core:** +- "Why does that matter to them emotionally?" +- "What's the deeper fear behind that frustration?" +- "How intense is this driver on a scale of 1-5?" + +### Your Task + +**For each persona:** +- List 3-5 positive drivers (what they want) +- List 3-5 negative drivers (what they fear) +- Identify which are strongest +- Note emotional intensity + +**Be specific:** +- Not: "Want to be productive" +- Yes: "Want to complete projects without last-minute panic and look competent to stakeholders" + +### Example Interaction + +**Saga:** "Let's explore the driving forces for Remote Team Leads. What do they want to accomplish?" + +**You:** "They want to demonstrate effective leadership to their management. They want to build a strong team culture despite the distance. They want to support team members before problems escalate." + +**Saga:** "Good. Now let's look at the other side - what do they fear or want to avoid?" + +**You:** "They fear team members burning out without them noticing. They fear being seen as an ineffective manager. They fear losing their top performers to burnout or better opportunities." + +**Saga:** "Excellent. Which of these drivers feels most urgent and emotionally intense?" + +**You:** "The fear of team burnout is the strongest. It's both urgent and has high emotional weight - they feel responsible for their team's wellbeing." + +### Workshop 3 Output + +You'll have: +- ✅ Complete psychological profile for each persona +- ✅ Both positive and negative drivers mapped +- ✅ Understanding of emotional intensity +- ✅ Foundation for feature decisions + +--- + +## Workshop 4: Prioritization (15-20 minutes) + +### Starting Workshop 4 + +**Continue with Saga:** + +``` +@saga Let's move to Workshop 4: Prioritization. +``` + +### What Saga Will Ask + +**Prioritizing groups:** +- "Which target group will have the biggest impact on your top business goal?" +- "Which group is most feasible to reach and serve effectively?" +- "How would you rank all groups from highest to lowest strategic value?" + +**Prioritizing drivers:** +- "For [top persona], which driving forces are most powerful?" +- "Which drivers have the most emotional intensity?" +- "Which would drive the most urgent action?" +- "How would you rank these drivers?" + +### Your Task + +**Create rankings:** +- Rank target groups 1-N +- For each group, rank their drivers +- Identify top 5-7 drivers overall +- These become your scoring criteria + +**Consider:** +- Business impact (which drives goals?) +- Emotional intensity (which drives action?) +- Urgency (what needs solving now?) +- Feasibility (what can you address?) + +### Example Interaction + +**Saga:** "Looking at your three target groups, which will have the biggest impact on your goal of reaching 10,000 active users?" + +**You:** "Remote Team Leads are #1. They have teams of 5-10 people, so each lead we convert brings multiple users. They also have budget authority and urgent pain." + +**Saga:** "Good reasoning. And for Remote Team Leads, which of their driving forces are most powerful?" + +**You:** "The fear of team burnout without noticing is #1 - it's urgent and emotionally intense. Second is wanting to demonstrate effective leadership - that's their career driver." + +**Saga:** "Perfect. Let's document these rankings..." + +### Workshop 4 Output + +You'll have: +- ✅ Ranked list of target groups +- ✅ Ranked drivers for each group +- ✅ Top 5-7 drivers identified overall +- ✅ Clear strategic priorities + +--- + +## Workshop 5: Feature Impact (20-30 minutes) + +### Starting Workshop 5 + +**Continue with Saga:** + +``` +@saga Let's move to Workshop 5: Feature Impact Analysis. +``` + +### What Saga Will Ask + +**Feature brainstorming:** +- "What features are you considering for this product?" +- "What ideas came up in your Product Brief?" +- "What have stakeholders requested?" +- "What do competitors offer?" + +**Scoring each feature:** +- "How well does [feature] address [top driver]?" +- "Does this create gain or reduce pain for this persona?" +- "On a scale of 0-3, how much impact does this have?" +- "Why that score? What specifically does it address?" + +**Validation:** +- "Are there features that would score higher?" +- "Could we modify any features to increase impact?" +- "Do the scores match your intuition?" + +### Your Task + +**List 10-20 features:** +- Ideas from Product Brief +- Stakeholder requests +- Competitive features +- Your own ideas + +**Score each feature:** +- Against top 5-7 prioritized drivers +- Use 0-3 scale (0=no impact, 3=directly addresses) +- Be honest (don't inflate scores) +- Calculate total for each feature + +**Create prioritized roadmap:** +- Sort by total score +- Group into phases +- Identify quick wins + +### Example Interaction + +**Saga:** "Let's score your first feature: Daily Team Pulse Check. How well does this address the fear of team burnout without noticing?" + +**You:** "That's a 3 - it directly addresses that fear by giving daily visibility into team health." + +**Saga:** "Good. And how about the desire to demonstrate effective leadership?" + +**You:** "That's a 2. It gives them data to show they're monitoring and responding to team needs." + +**Saga:** "Excellent. Let's continue scoring this feature against the other drivers..." + +### Scoring Matrix Example + +| Feature | Burnout Fear | Leadership | Retention | Culture | Deadlines | **Total** | +|---------|-------------|------------|-----------|---------|-----------|-----------| +| Daily pulse check | 3 | 2 | 2 | 1 | 1 | **9** | +| Workload dashboard | 3 | 2 | 2 | 0 | 2 | **9** | +| Recognition system | 1 | 1 | 2 | 3 | 0 | **7** | +| Meeting summaries | 0 | 1 | 0 | 1 | 2 | **4** | + +### Workshop 5 Output + +You'll have: +- ✅ Complete feature list (10-20 features) +- ✅ Scored against top drivers +- ✅ Total impact score for each +- ✅ Prioritized roadmap +- ✅ Strategic justification for priorities + +--- + +## Creating the Visual Trigger Map + +### Understanding the Structure + +**The Trigger Map flows horizontally (left to right) in four layers:** + +``` +Business Goals → Product/Solution → Target Groups → Usage Goals + (Positive + Negative) +``` + +1. **Business Goals** (Left, Blue) - Your vision and SMART objectives +2. **Product/Solution** (Center, Yellow) - What you're building +3. **Target Groups** (Middle-Right, Orange) - Prioritized personas (👥 primary, 👤 secondary) +4. **Usage Goals** (Right, Green/Red) - Positive drivers (✅) and negative drivers (❌) separated + +### After All Workshops + +**Ask Saga to create the visual map:** + +``` +@saga Please create the visual Trigger Map document that shows the strategic connections. +``` + +### What You'll Get + +**A document showing:** +- Business goals at center +- Target groups radiating out (prioritized) +- Positive drivers for each group +- Negative drivers for each group +- Visual hierarchy showing priorities + +### Using the Map + +**Reference it for:** +- Every design decision +- Feature discussions +- Stakeholder presentations +- Team alignment +- Strategic reviews + +**Keep it:** +- Visible to entire team +- Updated when strategy shifts +- As single source of strategic truth + +--- + +## What You've Accomplished + +✅ **Business Goals** - Clear vision and SMART objectives +✅ **Target Groups** - 3-5 prioritized personas with deep context +✅ **Driving Forces** - Positive and negative psychology mapped +✅ **Prioritization** - Ranked groups and drivers by strategic value +✅ **Feature Impact** - Scored and prioritized feature roadmap +✅ **Visual Trigger Map** - One-page strategic reference document + +--- + +## Using Your Trigger Map + +### For Design Decisions + +**Before designing any feature:** +1. Check the Trigger Map +2. Identify which drivers it addresses +3. Verify it serves a top-priority group +4. Ensure it connects to business goals +5. Design with that strategic context + +### For Stakeholder Communication + +**When presenting roadmap:** +1. Show the Trigger Map first +2. Explain the strategic layers +3. Show the scoring matrix +4. Present prioritized features +5. Trace each feature back to strategy + +### For Team Alignment + +**In sprint planning:** +1. Reference the Trigger Map +2. Discuss how features address drivers +3. Validate priorities against scores +4. Make trade-offs based on strategy +5. Keep strategic focus + +--- + +## Keeping It Current + +### Quarterly Review + +**Every quarter:** +- Review business goals (still accurate?) +- Review target groups (priorities changed?) +- Review drivers (new insights from users?) +- Re-score features if needed +- Update the visual map + +### When to Do Full Update + +**Re-run workshops when:** +- Business strategy shifts significantly +- New user research reveals different psychology +- Market conditions change dramatically +- Product pivots to new direction + +**Don't re-run for:** +- Minor feature changes +- Tactical adjustments +- Short-term experiments +- Individual stakeholder requests + +--- + +## Common Questions + +**Q: What if I don't know the answers to Saga's questions?** +A: That's okay! Mark it as an assumption to validate. The map helps you identify what you need to learn. + +**Q: How many features should I score?** +A: Start with 10-15. You can always add more later. Focus on the features you're seriously considering. + +**Q: What if two features have the same score?** +A: Consider feasibility, dependencies, and market timing as tie-breakers. + +**Q: Can I update scores as I learn more?** +A: Yes! The scoring should evolve with your understanding. Update quarterly or when you have new insights. + +**Q: What if stakeholders disagree with the priorities?** +A: Show them the Trigger Map and scoring matrix. Walk through the strategic reasoning. If they still disagree, explore whether the strategy itself needs updating. + +--- + +## Next Steps + +**Immediate:** +- Share Trigger Map with your team +- Post it where everyone can see it +- Reference it in your next design discussion +- Use scores to guide sprint planning + +**Next Module:** +- [Module 06: Scenarios](../module-06-scenarios/module-06-overview.md) +- Transform your Trigger Map into detailed user scenarios + +--- + +## Tips for Success + +**DO ✅** +- Be specific about drivers (avoid generic wants) +- Think about emotional intensity +- Prioritize ruthlessly (not everything is #1) +- Score honestly (don't inflate to justify pet features) +- Reference the map constantly + +**DON'T ❌** +- Rush through workshops (take time to think) +- Accept vague answers (push for specificity) +- Skip negative drivers (they're often more powerful) +- Create the map once and forget it +- Let politics override strategic scores + +--- + +**Your Trigger Map is the strategic foundation that guides every design decision. Use it well!** + +[← Back to Lesson 6](lesson-06-feature-impact-scoring.md) | [Back to Module Overview](module-05-overview.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05b-value-trigger-chain.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05b-value-trigger-chain.md new file mode 100644 index 000000000..49523203f --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05b-value-trigger-chain.md @@ -0,0 +1,393 @@ +# Tutorial 05B: Create Your Value Trigger Chain + +**Quick strategic validation for focused user journeys** + +--- + +## Overview + +This tutorial walks you through creating a Value Trigger Chain - a lightweight, streamlined version of Trigger Mapping. Perfect for when you need quick strategic validation or are working with a single, focused user journey. + +**Time:** 15-20 minutes +**Prerequisites:** Module 04 completed (Product Brief created) +**What you'll create:** Single-chain map from business goal to user trigger + +--- + +## When to Use This Approach + +**Value Trigger Chain is ideal for:** +- ✅ Smaller features or iterations +- ✅ Single user journey focus +- ✅ Quick strategic validation +- ✅ Early-stage exploration +- ✅ Time-constrained situations + +**Use Full Trigger Mapping instead if:** +- ❌ Multiple user groups to consider +- ❌ Complex feature prioritization needed +- ❌ Long-term strategic planning +- ❌ Need defensible stakeholder justification + +**Not sure which to use?** See [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md#two-approaches-choose-your-depth) + +--- + +## Before You Start + +### What You Need + +- ✅ Completed Product Brief (from Tutorial 04) +- ✅ WDS installed and Saga activated +- ✅ 15-20 minutes of focused time +- ✅ One clear user journey in mind + +### What to Expect + +**Saga will:** +- Guide you through one streamlined workshop +- Ask focused questions +- Help you create a single value chain +- Document the essential connections + +**You will:** +- Define one strategic objective +- Identify one primary user +- Map their key driver +- Connect to specific trigger moment + +--- + +## The Value Trigger Chain Workshop + +### Starting the Workshop + +**In your IDE, activate Saga:** + +``` +@saga I want to create a Value Trigger Chain for [brief description of feature/journey]. Let's do the lightweight version. +``` + +--- + +## Step 1: Define Your Strategic Objective (3 minutes) + +### What Saga Will Ask + +**Focus on one measurable goal:** +- "What's the one strategic objective this feature/journey needs to achieve?" +- "How will you measure success?" +- "By when do you need to achieve this?" + +### Your Task + +**Pick ONE objective from your Product Brief:** +- Must be specific and measurable (using SMART method) +- Should be achievable through this single journey +- Clear timeframe + +**Example:** +"Increase trial-to-paid conversion to 25% by Q3 2024" + +**Not:** +"Improve user experience and increase revenue and build brand awareness" +(Too many objectives - use Full Trigger Mapping for this) + +--- + +## Step 2: Identify Your Primary User (3 minutes) + +### What Saga Will Ask + +**WHO will make this happen through their product use:** +- "Who is the ONE user type whose behavior drives this objective?" +- "What's their context and situation?" +- "What are they trying to accomplish?" + +### Your Task + +**Define one primary user:** +- Behavioral profile, not demographics +- Specific context +- Clear connection to your objective + +**Example:** +"Startup founders evaluating project management tools during their first team expansion (3-10 people). They're overwhelmed by options and need to make a decision quickly before their team grows chaotic." + +**Why this works:** +- Specific behavioral context +- Clear situation +- Connects to trial-to-paid conversion (they need to decide) + +--- + +## Step 3: Map the Key Driver (4 minutes) + +### What Saga Will Ask + +**What's the ONE psychological driver:** +- "What's the strongest driver for this user in this journey?" +- "Is it positive (what they want) or negative (what they fear)?" +- "Why does this matter emotionally to them?" + +### Your Task + +**Identify the dominant driver:** +- Usually negative drivers are stronger (loss aversion) +- Must be specific to this journey +- Should have emotional intensity + +**Example:** +**Negative Driver:** "Fear of making the wrong tool choice and wasting team's time learning a system they'll have to abandon" + +**Why this works:** +- Specific fear (not generic "want good tool") +- Emotional (embarrassment, wasted time, team frustration) +- Directly relevant to trial-to-paid decision + +--- + +## Step 4: Define the Trigger Moment (4 minutes) + +### What Saga Will Ask + +**When does this driver activate:** +- "What specific moment triggers this driver?" +- "What's happening in their world when they feel this most strongly?" +- "What prompts them to take action?" + +### Your Task + +**Identify the trigger moment:** +- Specific situation or event +- When the driver becomes urgent +- What makes them act NOW + +**Example:** +**Trigger Moment:** "When their team asks 'Which tool are we using?' for the third time in a week, and they realize they're losing credibility by not having made a decision" + +**Why this works:** +- Specific moment (third time asked) +- Emotional trigger (losing credibility) +- Creates urgency (need to decide now) + +--- + +## Step 5: Connect to Your Solution (3 minutes) + +### What Saga Will Ask + +**How does your feature address this:** +- "What does your feature do at this trigger moment?" +- "How does it reduce the pain or enable the gain?" +- "Why is this better than alternatives?" + +### Your Task + +**Define the value connection:** +- What your feature does +- How it addresses the driver +- Why it works at this trigger moment + +**Example:** +**Solution:** "Guided comparison tool that shows them exactly how our features map to their team size and use case, with a 'Decision Confidence Score' that validates their choice" + +**Why this works:** +- Addresses the fear (reduces wrong-choice risk) +- Provides validation (confidence score) +- Specific to the trigger moment (helps them decide NOW) + +--- + +## Your Value Trigger Chain + +### The Complete Chain + +``` +Strategic Objective + ↓ +"Increase trial-to-paid conversion to 25% by Q3 2024" + ↓ +Primary User + ↓ +"Startup founders evaluating tools during first team expansion" + ↓ +Key Driver (Negative) + ↓ +"Fear of making wrong choice and wasting team's time" + ↓ +Trigger Moment + ↓ +"When team asks 'which tool?' for 3rd time - losing credibility" + ↓ +Solution + ↓ +"Guided comparison tool with Decision Confidence Score" + ↓ +Result: User converts because fear is reduced, decision validated +``` + +--- + +## Validating Your Chain + +### The Control Questions + +Ask yourself: + +**1. Is the connection clear?** +- Can you trace from objective → user → driver → trigger → solution? +- Does each step logically lead to the next? + +**2. Is this the strongest path?** +- Is this the PRIMARY user for this objective? +- Is this their STRONGEST driver? +- Is this the most URGENT trigger moment? + +**3. Does your solution actually work?** +- Does it address the driver at the trigger moment? +- Is it better than alternatives? +- Why should they care? + +**If any answer is weak:** Revisit that step and strengthen the connection. + +--- + +## Generic Example: Fitness App + +### The Chain + +**Objective:** "Achieve 1,000 daily active users by Q4 2024" + +**Primary User:** "Busy professionals who want to exercise but struggle with consistency" + +**Key Driver (Negative):** "Fear of losing fitness progress when work gets hectic" + +**Trigger Moment:** "When they miss their third workout in a row and feel guilty" + +**Solution:** "3-minute 'Streak Saver' workout that counts toward their weekly goal" + +**Why it works:** +- Addresses the fear (prevents losing progress) +- Works at trigger moment (when they've missed workouts) +- Low barrier (only 3 minutes) +- Maintains streak (reduces guilt) + +--- + +## What You Get + +✅ **Clear strategic connection** - Objective to solution in one chain +✅ **Focused validation** - One user, one driver, one trigger +✅ **Quick decision-making** - Is this feature worth building? +✅ **Defensible reasoning** - Traceable logic +✅ **15-20 minute investment** - Fast strategic check + +--- + +## When to Expand to Full Trigger Mapping + +**Consider the full process if you discover:** +- Multiple user types are equally important +- Several drivers compete for priority +- You need to score many features +- Stakeholders need comprehensive justification +- The project is more complex than initially thought + +**The Value Trigger Chain is a starting point.** If it reveals complexity, upgrade to Full Trigger Mapping. + +--- + +## Common Mistakes to Avoid + +### Mistake 1: Too Many Objectives + +**Problem:** Trying to achieve 5 different goals in one chain +**Why it fails:** Dilutes focus, unclear success criteria +**Fix:** Pick ONE objective, use Full Trigger Mapping for multiple goals + +### Mistake 2: Generic User + +**Problem:** "All users" or "people who want X" +**Why it fails:** Can't identify specific drivers or triggers +**Fix:** Get specific about context and situation + +### Mistake 3: Vague Driver + +**Problem:** "Want better experience" +**Why it fails:** Not actionable, no emotional core +**Fix:** Find the specific fear or desire with emotional intensity + +### Mistake 4: Missing the Trigger + +**Problem:** No specific moment when driver activates +**Why it fails:** Don't know when to intervene +**Fix:** Identify the exact situation that creates urgency + +### Mistake 5: Solution Doesn't Connect + +**Problem:** Feature doesn't actually address the driver +**Why it fails:** Won't drive the objective +**Fix:** Ensure solution reduces pain or enables gain at trigger moment + +--- + +## Tips for Success + +**DO:** +- ✅ Focus on ONE clear path +- ✅ Be specific at every step +- ✅ Find the emotional core +- ✅ Validate the connections +- ✅ Keep it simple + +**DON'T:** +- ❌ Try to map everything (use Full Trigger Mapping for that) +- ❌ Accept vague or generic statements +- ❌ Skip the trigger moment +- ❌ Forget to validate the chain +- ❌ Overcomplicate it + +--- + +## What's Next + +### If This Validated Your Feature + +**Move to scenario design:** +- Use this chain to inform your scenario +- Design for the trigger moment +- Address the driver directly +- Measure against the objective + +### If This Revealed Complexity + +**Upgrade to Full Trigger Mapping:** +- [Tutorial 05: Create Your Trigger Map](tutorial-05.md) +- Map multiple users and drivers +- Score features systematically +- Build comprehensive strategy + +### If This Showed a Problem + +**Revisit your Product Brief:** +- Is the objective right? +- Is this the right user? +- Should you pivot the feature? +- Do you need more research? + +--- + +## Key Takeaways + +✅ **Lightweight but strategic** - Quick validation with clear reasoning +✅ **One clear path** - Objective → User → Driver → Trigger → Solution +✅ **15-20 minutes** - Fast strategic check +✅ **Know when to expand** - Upgrade to Full Trigger Mapping when needed +✅ **Traceable logic** - Every step connects to the next + +--- + +[← Back to Lesson 2](lesson-02-heritage-evolution.md) | [Full Trigger Mapping Tutorial →](tutorial-05.md) + +*Part of Module 05: Trigger Mapping* diff --git a/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05c-documentation-synthesis.md b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05c-documentation-synthesis.md new file mode 100644 index 000000000..70a21915d --- /dev/null +++ b/src/modules/wds/docs/learn-wds/module-05-trigger-mapping/tutorial-05c-documentation-synthesis.md @@ -0,0 +1,475 @@ +# Tutorial 05C: Synthesize from Documentation + +**Transform existing research into an actionable Trigger Map** + +--- + +## Overview + +This tutorial walks you through synthesizing your existing documentation into a complete Trigger Map with Saga the Analyst. Instead of starting from scratch, you'll validate and organize what you already have, filling gaps through focused conversation. + +**Time:** 30-45 minutes +**Prerequisites:** Existing documentation (vision docs, user research, plans, or interviews) +**What you'll create:** Synthesized Trigger Map + gap analysis + +--- + +## When to Use This Approach + +**Documentation Synthesis is ideal for:** +- ✅ You have extensive vision/strategy documents +- ✅ User research or interview transcripts exist +- ✅ Project plans or roadmaps already created +- ✅ Need to make existing documentation actionable +- ✅ Documentation is too long for anyone to read + +**Use Full Trigger Mapping instead if:** +- ❌ Starting from scratch with no documentation +- ❌ Documentation is minimal or non-existent + +**Use Value Trigger Chain instead if:** +- ❌ Need quick validation (under 20 minutes) +- ❌ Single user journey focus + +**Not sure which to use?** See [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md#three-approaches-choose-your-path) + +--- + +## The Problem This Solves + +**Common scenario:** +- Organization spends thousands on research +- 200-page reports nobody reads +- Interview transcripts gathering dust +- Vision documents lost in shared drives +- Designers paste 100+ pages into AI chats (hitting token limits) + +**The solution:** +Transform that investment into a **single-slide strategic artifact** you can actually use in daily design work and AI conversations. + +--- + +## Before You Start + +### What You Need + +**Documentation (any combination of):** +- Vision or strategy documents +- User research reports +- Interview transcripts +- Target group analysis +- Project plans or roadmaps +- Feature specifications +- Market research + +**Also need:** +- ✅ WDS installed and Saga activated +- ✅ 30-45 minutes of focused time +- ✅ Ability to share documentation (paste, upload, or describe) + +### What to Expect + +**Saga will:** +- Analyze your documentation +- Frame questions based on what your material suggests +- Validate findings with you +- Fill gaps through conversation +- Identify documentation strengths and weaknesses +- Create your Trigger Map + +**You will:** +- Share your documentation +- Validate what Saga extracts +- Fill gaps where documentation is incomplete +- Make prioritization decisions +- Confirm strategic alignment + +**Important:** Documentation may only answer **part** of the Trigger Map questions. That's normal. Saga will frame questions as "Your material suggests X, is this correct?" and fill gaps collaboratively. + +--- + +## Workshop Flow + +### Starting the Workshop + +**In your IDE, activate Saga:** + +``` +@saga I have existing documentation I want to synthesize into a Trigger Map. I have [describe what you have: vision docs, user research, plans, etc.]. +``` + +**Then share your documentation:** +- Paste content directly into chat +- Upload files +- Provide links to documents +- Describe what's available + +--- + +## Workshop 1: Business Goals (5-10 minutes) + +### What Saga Will Do + +**Analyze your documentation for:** +- Vision statements (explicit or implied) +- Strategic objectives (SMART or vague) +- Business goals and success criteria + +### Three Scenarios + +**Scenario 1: Clear vision and objectives found** +``` +Saga: "Your documentation suggests this vision: +'Be the most trusted platform for dog owners in Sweden' + +Is this accurate?" +``` + +**Scenario 2: Vague or implied vision** +``` +Saga: "I found aspirational language in your docs. +It seems like your vision is: [interpreted vision] +But this isn't explicitly stated. Is this accurate?" +``` + +**Scenario 3: No vision found (reverse engineering)** +``` +Saga: "I don't see an explicit vision statement. +However, based on your objectives and plans, +the implied vision seems to be: [inferred vision] + +This is reverse-engineered from what you're trying to achieve. +Does this capture your aspirational goal?" +``` + +### Your Task + +**Validate or refine:** +- Does the extracted vision capture your aspirational goal? +- Are the objectives truly SMART (Specific, Measurable, Achievable, Relevant, Time-bound)? +- Do objectives connect to the vision? + +**Fill gaps:** +- If vision is missing, define it +- If objectives are vague, sharpen them using SMART method + +--- + +## Workshop 2: Target Groups (5-10 minutes) + +### What Saga Will Do + +**Analyze your documentation for:** +- User segments or personas +- Behavioral descriptions +- User contexts and situations +- Demographics (but will push for psychology) +- User quotes or interview insights + +### Three Scenarios + +**Scenario 1: Target groups found** +``` +Saga: "Your documentation identifies these user groups: +1. Dog Trainers - Professional trainers with 1000+ followers +2. Dog Owners - First-time owners seeking guidance +3. Veterinarians - Professionals recommending resources + +I found 3 groups total. Should we focus on the top 3-4 most critical for your objectives?" +``` + +**Scenario 2: Demographics only (needs behavioral depth)** +``` +Saga: "Your documentation mentions: +- Women aged 25-40 +- Urban professionals +- Pet owners + +However, these are demographic descriptions. +For Trigger Mapping, we need behavioral profiles. + +For each group, what's their context and situation when using your product?" +``` + +**Scenario 3: No clear target groups** +``` +Saga: "I don't see clear target group definitions. +Based on the context, these groups might be relevant: +- [Inferred group 1]: [reasoning] +- [Inferred group 2]: [reasoning] + +Who are the 3-4 key user groups whose product usage will drive your objectives?" +``` + +### Your Task + +**Validate or refine:** +- Are these the right target groups? +- Do descriptions capture behavioral context (not just demographics)? +- Is there psychological depth (goals, frustrations, context)? + +**Fill gaps:** +- Transform demographics into behavioral profiles +- Add context and situation +- Include user quotes from research if available + +--- + +## Workshop 3: Driving Forces (5-10 minutes) + +### What Saga Will Do + +**For each persona, analyze documentation for:** +- Positive drivers (wants, desires, aspirations) +- Negative drivers (fears, frustrations, anxieties) +- Pain points and desired outcomes + +### Common Pattern: Missing Negative Drivers + +**Most documentation focuses on positive wants:** +``` +Saga: "Your documentation suggests Dog Trainers want to: +- Build their professional reputation +- Share training techniques +- Connect with potential clients + +But I don't see explicit fears or frustrations. + +Let's think about the flip side: What do they fear or want to avoid? +- Fear of looking unprofessional? +- Fear of wasting time on ineffective platforms? +- Frustration with current solutions?" +``` + +### Your Task + +**Validate or refine:** +- Do positive drivers capture what users want to achieve? +- Are negative drivers identified? (Often missing in docs) +- Are drivers specific to usage context (not general life goals)? + +**Fill gaps:** +- Transform pain points into psychological drivers +- Identify fears and frustrations (loss aversion is powerful!) +- Make drivers specific to product usage context + +**Remember:** Negative drivers are often MORE powerful than positive ones. + +--- + +## Workshop 4: Prioritization (5-10 minutes) + +### What Saga Will Do + +**Check documentation for priority signals:** +- Explicit priority statements +- Resource allocation (budget, team focus) +- Timeline emphasis (what's first) +- Frequency of mention +- Depth of research on certain groups + +**Then prioritize through conversation:** +``` +Saga: "For each group, let's assess: + +Impact on objectives: If this group succeeds with your product, +how much does it drive your objectives? (High/Medium/Low) + +Feasibility: How easy is it to reach and serve this group? +(High/Medium/Low) + +Let's start with Dog Trainers: +- Impact on objectives? +- Feasibility?" +``` + +### Your Task + +**Assess each group:** +- Impact on objectives (High/Medium/Low) +- Feasibility to reach and serve (High/Medium/Low) + +**Validate prioritization:** +- Does the ranking align with your strategic thinking? +- Are top drivers the most critical to address? +- Does the focus statement capture where design efforts should go? + +--- + +## Gap Analysis & Validation (5-10 minutes) + +### What Saga Will Do + +**Identify documentation strengths:** +``` +✅ Clear vision statement +✅ Deep user research with interview quotes +✅ Behavioral personas with psychological depth +``` + +**Identify gaps:** +``` +⚠️ Objectives are vague (not fully SMART) + - Impact: Hard to measure success + - What we did: Sharpened through conversation + +⚠️ Negative drivers not explicitly mentioned + - Impact: Missing powerful motivators + - What we did: Inferred from pain points and validated +``` + +**Validate strategic alignment:** +``` +Saga: "Your documentation says you want: +'Be the most trusted platform for dog owners' + +Your plan/features suggest: +'Focus on professional trainers and monetization' + +⚠️ Potential misalignment detected: +- Documentation emphasizes trust and all dog owners +- Plan focuses on professional segment and revenue +- Recommendation: Clarify if vision should be narrowed or plan broadened +``` + +### Your Task + +**Review gaps:** +- Accept gaps and note for future research? +- Fill critical gaps now through focused conversation? + +**Validate alignment:** +- Does your plan support your vision? +- Are there contradictions between docs and plans? +- Should anything be adjusted? + +--- + +## What You'll Receive + +### Trigger Map Documentation + +**Same comprehensive output as full Trigger Mapping:** +- Vision statement +- Strategic objectives (SMART) +- Prioritized target groups with personas +- Driving forces (positive and negative) +- Mermaid diagram visualization +- Strategic focus statement + +**Plus additional synthesis artifacts:** +- Gap analysis (what's strong vs. weak in documentation) +- Alignment check (does plan match vision?) +- Recommendations for future research + +### How to Use Your Trigger Map + +**Daily design work:** +- Reference it when making design decisions +- Validate features against prioritized drivers +- Keep team aligned on strategic priorities + +**AI conversations:** +- Share single-slide Trigger Map instead of 200-page reports +- Provide strategic context without hitting token limits +- Much more useful than pasting extensive documentation + +**Team alignment:** +- Single source of truth for strategy +- Clear priorities everyone understands +- Defensible design decisions + +**Future research:** +- Gap analysis guides what to research next +- Identifies assumptions to validate +- Prevents redundant research + +--- + +## Tips for Success + +### Prepare Your Documentation + +**Before starting:** +- Gather all relevant documents +- Know what you have (vision, research, plans, etc.) +- Be ready to share (paste, upload, or describe) + +**Don't worry if:** +- Documentation is incomplete (normal!) +- Some sections are vague (we'll sharpen them) +- Negative drivers aren't mentioned (we'll add them) +- Prioritization isn't explicit (we'll determine it) + +### During the Workshop + +**Be honest about gaps:** +- "I don't know" is a valid answer +- Gaps help identify future research needs +- Better to acknowledge than guess + +**Validate actively:** +- Don't just accept what Saga extracts +- Correct misinterpretations +- Refine vague statements + +**Think psychologically:** +- Move beyond demographics to behavior +- Consider both positive and negative drivers +- Focus on usage context, not general life goals + +### After the Workshop + +**Use your Trigger Map:** +- Reference it in design decisions +- Share it in AI chats for context +- Keep it updated as strategy evolves + +**Address gaps:** +- Plan research to fill critical gaps +- Validate assumptions with users +- Update Trigger Map as you learn + +--- + +## Common Questions + +**Q: What if my documentation is really extensive (100+ pages)?** +A: Perfect use case! Saga will extract the strategic elements and create a single-slide reference. Much more useful than reading hundreds of pages. + +**Q: What if documentation contradicts itself?** +A: Saga will identify contradictions during alignment check. You'll discuss and resolve them. + +**Q: What if I only have partial documentation (e.g., just user research, no vision)?** +A: No problem. Saga will extract what's there and fill gaps through conversation. You'll end up with a complete Trigger Map. + +**Q: Can I update the Trigger Map later if documentation changes?** +A: Yes! You can re-run synthesis or update specific sections as your strategy evolves. + +**Q: How is this different from just reading my documentation?** +A: Trigger Map organizes research into actionable structure, identifies gaps, validates alignment, and creates a single-slide reference you can actually use daily. + +--- + +## Next Steps + +**After completing this tutorial:** + +1. **Review your Trigger Map** - Does it accurately represent your strategy? +2. **Address critical gaps** - Plan research to fill important missing pieces +3. **Share with team** - Get alignment on strategic priorities +4. **Use in design work** - Reference it when making design decisions +5. **Proceed to Module 06** - UX Design (where Trigger Map guides your work) + +--- + +## Related Resources + +- [Lesson 2: Heritage & Evolution](lesson-02-heritage-evolution.md) - Understanding the three approaches +- [Tutorial 05: Full Trigger Mapping](tutorial-05.md) - Starting from scratch +- [Tutorial 05B: Value Trigger Chain](tutorial-05b-value-trigger-chain.md) - Quick validation +- [Module 05 Overview](module-05-overview.md) - Complete module guide + +--- + +**Ready to transform your documentation into an actionable Trigger Map?** Activate Saga and begin! 🎯 diff --git a/src/modules/wds/docs/method/phase-2-trigger-mapping-guide.md b/src/modules/wds/docs/method/phase-2-trigger-mapping-guide.md index 63505d35a..d7b95b8df 100644 --- a/src/modules/wds/docs/method/phase-2-trigger-mapping-guide.md +++ b/src/modules/wds/docs/method/phase-2-trigger-mapping-guide.md @@ -76,15 +76,42 @@ These users have their own goals: **The key:** Make GAIN > PAIN for users, so through their usage, they add value to your system. -### The Three Layers +### The Four-Layer Structure -The Trigger Map combines three critical layers in one picture: +The Trigger Map flows horizontally (left to right) in four layers: -1. **Business Goals** - Your WHY (Vision that motivates, and SMART objectives that measure success) -2. **Target Groups** - The WHO (User types whose success drives your success) -3. **Usage Goals** - Their WHY (Driving forces both positive - what they wish to achieve, and negative - what they wish to avoid) +**Visual Flow:** +``` +Business Goals → Product/Solution → Target Groups → Usage Goals + (Positive + Negative) +``` -When all levels are then prioritized, you have perfect guidance for design: +**The Layers:** + +1. **Business Goals** (Left) - YOUR WHY + - Vision statement(s) - inspirational direction + - SMART objectives - measurable targets + - Multiple goals can feed into the product + +2. **Product/Solution** (Center) - WHAT YOU'RE BUILDING + - Product name and description + - Central hub connecting goals to users + - What the product does + +3. **Target Groups** (Middle-Right) - THE WHO + - Prioritized personas (Primary 👥, Secondary 👤) + - User types whose success drives your success + - Detailed psychological profiles + +4. **Usage Goals** (Right) - THEIR WHY + - **Positive Drivers** (✅ green) - What they want to achieve + - **Negative Drivers** (❌ red) - What they want to avoid + - Separated into distinct groups per target group + - Both types equally important for design + +**Strategic Guidance:** + +When all levels are prioritized, you have perfect guidance for design: - Present features that add value to your most prioritized goal first - To the highest prioritized target group diff --git a/src/modules/wds/docs/models/models-guide.md b/src/modules/wds/docs/models/models-guide.md index c1f1e76dc..c7f925620 100644 --- a/src/modules/wds/docs/models/models-guide.md +++ b/src/modules/wds/docs/models/models-guide.md @@ -62,6 +62,20 @@ Each model includes: --- +### [SMART Method](./smart-goals-model.md) + +**By:** George T. Doran (1981) +**Core Idea:** A framework for expressing measurable, achievable objectives using five criteria: Specific, Measurable, Achievable, Relevant, and Time-bound. + +**Applied in WDS:** +Used in Trigger Mapping Workshop 1 to transform vision (visionary statements) into strategic objectives. Ensures business objectives are measurable and trackable. + +**When to use it:** When defining strategic objectives that need to be measurable and actionable. + +**Reference:** [SMART Method Reference](smart-goals-model.md) + +--- + ### [Action Mapping](./action-mapping.md) **By:** Cathy Moore (2008+) @@ -213,6 +227,7 @@ These models represent decades of insight from brilliant thinkers who've shaped - **Mijo Balic & Ingrid Domingues** - Connecting goals to user behavior - **Gojko Adzic** - Making strategic planning accessible - **Simon Sinek** - Teaching us to start with WHY +- **George T. Doran** - Creating measurable, achievable objectives - **Cathy Moore** - Focusing on action over information - **Kathy Sierra** - Championing user capability diff --git a/src/modules/wds/docs/models/smart-goals-model.md b/src/modules/wds/docs/models/smart-goals-model.md new file mode 100644 index 000000000..e39dbc155 --- /dev/null +++ b/src/modules/wds/docs/models/smart-goals-model.md @@ -0,0 +1,294 @@ +# SMART Method Reference + +**A framework for expressing measurable, achievable objectives** + +--- + +## Overview + +The SMART method is a widely-used framework for transforming vague ambitions into concrete, actionable objectives. Originally attributed to George T. Doran's 1981 paper "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives," this approach has become a standard in business planning, project management, and strategic design. + +In WDS, strategic objectives are expressed using the SMART method, providing measurable evidence that your vision (visionary statements) is being realized. + +--- + +## The SMART Criteria + +Each objective should meet all five criteria: + +### S - Specific + +**What it means:** +- Clear and unambiguous +- Answers who, what, where, when, why +- No room for interpretation + +**Bad example:** "Increase user engagement" +**Good example:** "Increase daily active users in the mobile app" + +**Why it matters:** Specific goals give clear direction and prevent confusion about what success looks like. + +### M - Measurable + +**What it means:** +- Quantifiable with numbers or clear milestones +- Progress can be tracked objectively +- You can answer "how much?" or "how many?" + +**Bad example:** "Improve customer satisfaction" +**Good example:** "Achieve an NPS score of 50 or higher" + +**Why it matters:** If you can't measure it, you can't manage it or prove you've achieved it. + +### A - Achievable + +**What it means:** +- Realistic given your resources and constraints +- Challenging but not impossible +- Within your team's capability + +**Bad example:** "Become the #1 app in the world in 30 days" (with a team of 2) +**Good example:** "Reach top 10 in our category in the App Store within 6 months" + +**Why it matters:** Unachievable goals demoralize teams. Achievable goals motivate action. + +### R - Relevant + +**What it means:** +- Aligned with broader business objectives +- Matters to your organization's success +- Worth the investment of time and resources + +**Bad example:** "Get 1 million Twitter followers" (when your customers aren't on Twitter) +**Good example:** "Build an email list of 10,000 qualified leads in our target market" + +**Why it matters:** Irrelevant goals waste resources on metrics that don't drive business success. + +### T - Time-bound + +**What it means:** +- Has a clear deadline or timeframe +- Creates urgency and accountability +- Enables progress tracking + +**Bad example:** "Increase revenue eventually" +**Good example:** "Increase monthly recurring revenue to $50K by Q4 2024" + +**Why it matters:** Without deadlines, goals become wishes. Timeframes create commitment and enable planning. + +--- + +## SMART in WDS Workflow + +### Vision to Objectives Flow + +In WDS Trigger Mapping (Workshop 1: Business Goals), you work through this progression: + +**1. Start with Vision (Soft Goals)** +- Aspirational and motivational +- Example: "Make remote work sustainable and healthy" + +**2. Ask "What Will We Observe?"** +- Bridge from vision to measurable reality +- "When this vision is realized, what will we see in the world?" + +**3. Define SMART Objectives (Hard Goals)** +- Transform observations into SMART format +- Example: "Achieve 5,000 active teams by Q4 2024" + +### Why Both Levels Matter + +**Vision (Soft Goals):** +- Provides motivation and direction +- Easy to set, hard to measure +- Inspires the team + +**SMART Objectives (Hard Goals):** +- Provides accountability and tracking +- Harder to set, easy to measure +- Proves progress + +**Together:** You get both inspiration and accountability. + +--- + +## Generic Examples + +### Example 1: SaaS Product + +**Vision:** "Be the top-of-mind solution for team collaboration" + +**Bridging Question:** "When we're top-of-mind, what will we observe?" + +**SMART Objectives:** +- **S**pecific: Increase paid team subscriptions +- **M**easurable: Reach 10,000 paid teams +- **A**chievable: Based on current growth rate and market size +- **R**elevant: Directly supports revenue and market position goals +- **T**ime-bound: By Q4 2024 + +**Result:** "Reach 10,000 paid team subscriptions by Q4 2024" + +### Example 2: Mobile App + +**Vision:** "Fastest growing health app in our category" + +**Bridging Question:** "What would prove we're the fastest growing?" + +**SMART Objectives:** +- **S**pecific: Daily active users in the health & fitness category +- **M**easurable: 100,000 daily active users +- **A**chievable: Based on current trajectory and marketing budget +- **R**elevant: Growth directly supports market leadership goal +- **T**ime-bound: Within 6 months of launch + +**Result:** "Achieve 100,000 daily active users within 6 months of launch" + +### Example 3: E-commerce Platform + +**Vision:** "Most trusted marketplace for sustainable products" + +**Bridging Question:** "How would we measure trust?" + +**SMART Objectives:** +- **S**pecific: Customer retention and repeat purchase rate +- **M**easurable: 70% of customers make repeat purchase within 90 days +- **A**chievable: Industry average is 40%, we're targeting above average +- **R**elevant: Repeat purchases indicate trust and satisfaction +- **T**ime-bound: Achieve by end of fiscal year + +**Result:** "Achieve 70% repeat purchase rate within 90 days by end of fiscal year" + +--- + +## Common Mistakes + +### Mistake 1: Vague Objectives + +**Problem:** "Improve user experience" +**Why it fails:** Not specific or measurable +**Fix:** "Increase average session time from 5 to 8 minutes by Q3" + +### Mistake 2: No Numbers + +**Problem:** "Get more customers" +**Why it fails:** Not measurable +**Fix:** "Acquire 1,000 new paying customers by end of quarter" + +### Mistake 3: Unrealistic Targets + +**Problem:** "Become profitable in 2 weeks" (for a startup) +**Why it fails:** Not achievable +**Fix:** "Reach break-even point within 18 months" + +### Mistake 4: Irrelevant Metrics + +**Problem:** "Get 100,000 Instagram followers" (for B2B enterprise software) +**Why it fails:** Not relevant to business goals +**Fix:** "Generate 500 qualified enterprise leads through LinkedIn" + +### Mistake 5: No Deadline + +**Problem:** "Increase revenue someday" +**Why it fails:** Not time-bound +**Fix:** "Increase MRR from $20K to $50K by December 31, 2024" + +--- + +## Testing Your SMART Objectives + +Ask these questions for each objective: + +**Specific:** +- Can everyone on the team explain what this means? +- Is there any ambiguity about what we're trying to achieve? + +**Measurable:** +- Can we track progress with a number or clear milestone? +- Will we know definitively when we've achieved this? + +**Achievable:** +- Given our resources, is this realistic? +- Have similar organizations achieved similar goals? + +**Relevant:** +- Does this directly support our vision and business goals? +- Is this worth the investment of time and resources? + +**Time-bound:** +- Is there a specific deadline? +- Can we create a timeline for progress milestones? + +--- + +## SMART Objectives in Trigger Mapping + +Once you have SMART objectives from Workshop 1, they become the foundation for: + +**Workshop 2: Target Groups** +- Which user groups can help you achieve these objectives? + +**Workshop 3: Driving Forces** +- What psychological drivers would motivate those groups to act? + +**Workshop 4: Prioritization** +- Which groups and drivers have highest impact on objectives? + +**Workshop 5: Feature Impact** +- Which features best support achieving these objectives? + +**The chain:** SMART objectives → Target groups → Psychological drivers → Prioritized features + +--- + +## Historical Context + +### Origins + +**George T. Doran** first published the SMART criteria in the November 1981 issue of *Management Review* in his article "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives." + +### Evolution + +Over time, various interpretations have emerged: +- **A** has been interpreted as Attainable, Assignable, or Action-oriented +- **R** has been interpreted as Realistic, Results-oriented, or Resourced +- **T** has been interpreted as Timely, Time-based, or Trackable + +The core principle remains: goals should be clear, measurable, and actionable. + +### Modern Application + +SMART goals are now standard practice in: +- Business strategy and planning +- Project management (Agile, Scrum) +- Personal development +- Marketing and sales +- Product development +- Strategic design (like WDS) + +--- + +## Further Reading + +**Original Source:** +- Doran, G. T. (1981). "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives." *Management Review*, Vol. 70, Issue 11, pp. 35-36. + +**Related WDS Resources:** +- [Phase 2: Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) +- [Module 05: Trigger Mapping](../learn-wds/module-05-trigger-mapping/module-05-overview.md) +- [Lesson 3: The Five Workshops](../learn-wds/module-05-trigger-mapping/lesson-03-five-workshops.md) + +--- + +## Key Takeaways + +✅ **SMART = Specific, Measurable, Achievable, Relevant, Time-bound** +✅ **Transforms vague ambitions into concrete objectives** +✅ **In WDS: Vision (soft goals) + SMART Objectives (hard goals)** +✅ **Bridge question: "What will we observe when vision is realized?"** +✅ **Foundation for all strategic decisions in Trigger Mapping** +✅ **Created by George T. Doran in 1981, now industry standard** + +--- + +*Part of the WDS Models & Frameworks collection* diff --git a/src/modules/wds/workflows/2-trigger-mapping/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/instructions.md index da490696a..e642e8358 100644 --- a/src/modules/wds/workflows/2-trigger-mapping/instructions.md +++ b/src/modules/wds/workflows/2-trigger-mapping/instructions.md @@ -5,7 +5,7 @@ - + Hi {user_name}! I'm Saga, and I'll facilitate your **Trigger Mapping** session. Trigger Mapping connects your business goals to user psychology. It answers: @@ -15,42 +15,101 @@ Trigger Mapping connects your business goals to user psychology. It answers: - **What** do they want to avoid (negative drivers)? - **Which** features matter most? -We'll work through 4 core workshops, plus 1 optional workshop: +WDS offers **three approaches** depending on your situation: -1. **Business Goals** - Vision → SMART objectives +**Which path fits your situation?** + +1. **Starting from scratch** - Build your Trigger Map through guided workshops (60-90 min) + - No existing documentation + - We'll discover everything together + - Full strategic foundation + +2. **Quick validation** - Create a focused Value Trigger Chain (15-20 min) + - Single user journey + - No measurable goals + - Fast strategic check + - Lightweight version + +3. **Existing documentation** - Synthesize your research into a Trigger Map (30-45 min) + - You have vision docs, user research, plans, or interviews + - I'll extract and organize the strategic elements + - Create actionable artifact from extensive documentation + +Which approach would you like? + + + Great! We'll build your complete Trigger Map through 4 core workshops, plus 1 optional: + +1. **Business Goals** - Vision → Strategic objectives 2. **Target Groups** - Who are your key users? 3. **Driving Forces** - What motivates and concerns them? 4. **Prioritization** - What matters most? 5. **Feature Impact** (Optional) - Which features serve priorities best? -After workshops, I'll create comprehensive documentation with a visual trigger map. - -Each workshop builds on the previous. You can run them all together (60-90 min) or spread across sessions. - -Ready to begin? 🎯 - -Would you like to: - -1. **Full session** - All 4 core workshops now (Feature Impact optional at end) -2. **Workshop by workshop** - Start with Business Goals, continue later -3. **Jump to specific workshop** - If you've done some already - - - Proceed through all workshops sequentially +Each workshop builds on the previous. You can run them all together (60-90 min) or spread across sessions. + + Would you like to: + + a. **Full session** - All 4 core workshops now (Feature Impact optional at end) + b. **Workshop by workshop** - Start with Business Goals, continue later + c. **Jump to specific workshop** - If you've done some already + + + Proceed through all workshops sequentially + + + + Run Workshop 1, then offer to save and continue later + + + + Which workshop? + 1. Business Goals + 2. Target Groups + 3. Driving Forces + 4. Prioritization + 5. Feature Impact + Jump to selected workshop + - Run Workshop 1, then offer to save and continue later + Perfect! We'll create a **Value Trigger Chain** - a focused, lightweight version. + +This takes 15-20 minutes and creates one clear path: +- ONE strategic objective +- ONE primary user +- ONE key driver (usually negative, as it's often most powerful) +- Clear connection from goal to psychology + +This is ideal for quick validation or focused features. + + Load and execute VTC workflow: ../../shared/vtc-workshop/instructions.md + Skip to handover after VTC complete - Which workshop? - 1. Business Goals - 2. Target Groups - 3. Driving Forces - 4. Prioritization - 5. Feature Impact - Jump to selected workshop + Excellent! Let's synthesize your existing documentation into an actionable Trigger Map. + +This approach: +- Extracts strategic elements from your docs +- Organizes into clear Trigger Map structure +- Identifies gaps and validates assumptions +- Creates single-slide reference from hundreds of pages + +Much more useful for daily design work than reading through extensive documentation! + + **What documentation do you have?** You can share: + +- Vision or strategy documents +- User research or target group analysis +- Interview transcripts or research reports +- Project plans or roadmaps +- Any combination of the above + +Please share what you have (paste content, upload files, or describe what's available). + + Load and execute documentation synthesis workflow: workshops/0-documentation-synthesis/instructions.md diff --git a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md index 715cb0fe6..c595d838a 100644 --- a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md +++ b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md @@ -7,11 +7,19 @@ **Generate Professional Mermaid Diagram** -This workflow creates a visual trigger map with: +This workflow creates a visual trigger map with four-layer horizontal structure: + +**Structure (Left to Right):** +1. **Business Goals** (Left) - Vision + SMART objectives +2. **Product/Solution** (Center) - What you're building +3. **Target Groups** (Middle-Right) - Prioritized personas +4. **Usage Goals** (Right) - Positive (✅ green) and Negative (❌ red) drivers separated + +**Visual Features:** - Light gray professional styling - Gold-highlighted primary goal - Emoji-decorated nodes -- Clear connections between goals, platform, personas, and driving forces +- Clear left-to-right flow showing strategic connections Load and execute: steps/step-01-initialize-structure.md diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/instructions.md new file mode 100644 index 000000000..33d028a37 --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/instructions.md @@ -0,0 +1,140 @@ +# Workshop 0: Documentation Synthesis + +You are Saga the Analyst - facilitating strategic clarity from existing documentation +Documentation may only answer PART of the Trigger Map questions +Frame questions as: "Your material suggests X, is this correct?" not as pure extraction + + + + +**Documentation Synthesis Workshop** 📚 + +I'll help you transform your existing documentation into an actionable Trigger Map. + +Here's how this works: +- I'll analyze your documentation +- We'll go through the same workshops as building from scratch +- But I'll frame questions based on what your material suggests +- Where documentation is incomplete, we'll fill gaps through conversation + +This creates a single-slide strategic reference from your extensive documentation. + +Let's begin! + + + +Let me review your documentation... + +Read through all provided documentation carefully +Create mental map of what's covered: +- Vision/strategy statements (present/absent/vague?) +- Business goals or objectives (SMART/vague/missing?) +- User research findings (deep/shallow/none?) +- Target group descriptions (behavioral/demographic/missing?) +- User pain points, needs, desires (explicit/implied/absent?) +- Project plans or feature lists (detailed/high-level/none?) +- Psychological insights about users (present/absent?) + + +**Documentation analyzed.** + +I can see you have: +{{what_is_present}} + +{{#if gaps_identified}} +I notice some areas are less covered: +{{what_is_missing_or_vague}} +{{/if}} + +We'll work through the same workshops as building a Trigger Map from scratch, but I'll use your documentation to inform the questions. Where your docs are clear, I'll validate. Where they're incomplete, we'll fill gaps together. + +Ready to start with Business Goals? + + + +**Workshop 1: Business Goals** 🎯 + +Let's validate and refine your business goals from the documentation. + +Load and execute: step-01-business-goals.md +Store outputs: vision_statement, objectives + + + +**Workshop 2: Target Groups** 👥 + +Now let's identify and deepen your target group definitions. + +Load and execute: step-02-target-groups.md +Store outputs: target_groups, personas + + + +**Workshop 3: Driving Forces** 🧠 + +Time to map the psychological drivers for each persona. + +Load and execute: step-03-driving-forces.md +Store outputs: driving_forces_positive, driving_forces_negative for each persona + + + +**Workshop 4: Prioritization** 🎯 + +Let's determine what matters most strategically. + +Load and execute: step-04-prioritization.md +Store outputs: prioritized_groups, prioritized_drivers, focus_statement + + + +**Gap Analysis & Validation** ✅ + +Let me analyze the quality and completeness of what we've built. + +Load and execute: step-05-gap-analysis.md +Store outputs: gap_analysis, alignment_check + + + + + Your documentation includes a feature list. Would you like to run the **Feature Impact workshop** to score features against your prioritized drivers? + +This creates a data-driven priority list for development. + + + Load and execute: ../5-feature-impact/instructions.md + Store feature_impact_analysis + + + + No problem! Proceeding to handover... + + + + + Your documentation doesn't include a feature list, so we'll skip Feature Impact for now. You can run it later when you have features to evaluate. + + + + +**Documentation Synthesis Complete!** 🎉 + +I've transformed your extensive documentation into an actionable Trigger Map. + +**What you started with:** +{{original_doc_summary}} + +**What you now have:** +- ✅ Single-slide Trigger Map +- ✅ Clear strategic priorities +- ✅ Actionable psychological insights +- ✅ Gap analysis for future research +- ✅ Validated strategic alignment + +Now let me prepare the handover to Phase 4: UX Design... + +Load and execute: ../../handover/instructions.md + + + diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-01-business-goals.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-01-business-goals.md new file mode 100644 index 000000000..12ad3f1df --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-01-business-goals.md @@ -0,0 +1,124 @@ +# Documentation Synthesis - Step 1: Business Goals + +Frame as validation: "Your material suggests X, is this correct?" +Fill gaps through conversation if documentation incomplete + + + +Analyze documentation for vision and objectives + + + **Vision Statement** + +Your documentation suggests this vision: + +> {{extracted_vision}} + +Is this the aspirational goal you're working toward? + + Does this capture your vision, or should we refine it? + + Refine based on feedback + vision_statement + + + + **Vision Statement** + +I found some aspirational language in your documentation. It seems like your vision is: + +> {{interpreted_vision}} + +But this isn't explicitly stated. Is this accurate? + + Should we use this, or define a clearer vision statement? + + Refine or create vision statement + vision_statement + + + + **Vision Statement** + +I don't see an explicit vision statement in your documentation. However, based on your objectives and plans, the **implied vision** seems to be: + +> {{inferred_vision}} + +This is reverse-engineered from what you're trying to achieve. + + Does this capture your aspirational goal? Or should we define it differently? + + Create vision statement through conversation + vision_statement + + +--- + +**Strategic Objectives** + + + Your documentation includes these measurable objectives: + +{{#each extracted_objectives}} +**Objective {{@index + 1}}:** {{this.statement}} +- Metric: {{this.metric}} +- Target: {{this.target}} +- Timeline: {{this.timeline}} +{{/each}} + +These look SMART (Specific, Measurable, Achievable, Relevant, Time-bound). + + Are these the right strategic objectives? Any adjustments? + + objectives + + + + Your documentation mentions these goals: + +{{#each extracted_goals}} +- "{{this.original}}" +{{/each}} + +These aren't fully SMART yet. Let me help sharpen them: + +{{#each extracted_goals}} +**From documentation:** "{{this.original}}" +**Suggested SMART version:** {{this.smart_version}} +{{/each}} + + Do these SMART versions capture what you need to measure? + + Refine objectives based on feedback + objectives + + + + I don't see measurable objectives in your documentation. + +Based on your vision and plans, what would indicate you're succeeding? + + What metrics would prove you're achieving your vision? + +Think about: +- User metrics (adoption, engagement, retention) +- Business metrics (revenue, growth, market share) +- Quality metrics (satisfaction, referrals, reviews) + + Create objectives through conversation using SMART method + objectives + + +**Workshop 1 Complete!** ✅ + +**Vision:** +{{vision_statement}} + +**Strategic Objectives:** +{{#each objectives}} +{{@index + 1}}. {{this.statement}} +{{/each}} + +Next, we'll identify who can help you achieve these goals. + + diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-02-target-groups.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-02-target-groups.md new file mode 100644 index 000000000..f7209b426 --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-02-target-groups.md @@ -0,0 +1,143 @@ +# Documentation Synthesis - Step 2: Target Groups + +Frame as validation: "Your material suggests X, is this correct?" +Documentation may have demographics but need behavioral depth + + + +Analyze documentation for target groups and user research + + + **Target Groups** + +Your documentation identifies these user groups: + +{{#each extracted_groups}} +**{{@index + 1}}. {{this.name}}** +{{this.description}} + +Key characteristics from your docs: +{{#each this.characteristics}} +- {{this}} +{{/each}} +{{/each}} + +I found {{group_count}} groups total. + + Are these the right groups? Should we focus on the top 3-4 most critical for your objectives? + + Help prioritize to 3-4 groups maximum + target_groups + + + + **Target Groups** + +Your documentation mentions these users: + +{{#each extracted_groups}} +- {{this.name}}: {{this.demographic_description}} +{{/each}} + +However, these are mostly demographic descriptions. For Trigger Mapping, we need **behavioral** profiles. + + For each group, what's their **context and situation** when using your product? What are they trying to accomplish? + + Transform demographic descriptions into behavioral profiles through conversation + target_groups + + + + **Target Groups** + +I don't see clear target group definitions in your documentation. + +Based on the context and objectives, these groups might be relevant: +{{#each inferred_groups}} +- **{{this.name}}**: {{this.reasoning}} +{{/each}} + + Who are the 3-4 key user groups whose product usage will drive your objectives? + +Remember the core question: WHO out there in the world will make sure, with their use of the product, that you achieve your goals? + + Define target groups through conversation + target_groups + + +--- + +**Creating Detailed Personas** + +Now let's add psychological depth to each group... + +For each target group, check documentation for: +- Context and situation +- Goals and aspirations +- Frustrations and fears +- Behavioral patterns +- User quotes or interview insights + + + + Your research provides good psychological depth. Here are the personas: + +{{#each personas}} +**{{this.name}}** + +{{this.description}} + +**Context:** {{this.context}} +**Goals:** {{this.goals}} +**Frustrations:** {{this.frustrations}} +{{#if this.quote}}**Quote from research:** "{{this.quote}}"{{/if}} +{{/each}} + + Do these capture the psychological depth we need? Any refinements? + + personas + + + + Your documentation has basic user descriptions, but we need more psychological depth. + +{{#each personas}} +**{{this.name}}** + +From your docs: {{this.basic_description}} + +To make this actionable, we need to understand: +{{/each}} + + For each persona: +- What's their **context** when using your product? +- What are they trying to **accomplish** (usage goals)? +- What **frustrates** them in this context? +- What do they **fear** or want to avoid? + + Build psychological depth through conversation + personas + + + + I found some great quotes from your user interviews: + +{{#each quotes}} +"{{this.quote}}" - {{this.source}} +{{/each}} + +These reveal real psychology. Let me incorporate these into the personas... + + Use quotes to enrich persona descriptions + + +**Workshop 2 Complete!** ✅ + +**Target Groups (Prioritized):** +{{#each prioritized_groups}} +{{@index + 1}}. {{this.name}} +{{/each}} + +Next, we'll map what drives each group psychologically. + + diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-03-driving-forces.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-03-driving-forces.md new file mode 100644 index 000000000..756b6351c --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-03-driving-forces.md @@ -0,0 +1,133 @@ +# Documentation Synthesis - Step 3: Driving Forces + +Frame as validation: "Your material suggests X, is this correct?" +Documentation often focuses on positive wants - probe for negative drivers + + + +For each persona, analyze documentation for psychological drivers + +**Mapping Psychological Drivers** + +For each persona, we need to understand BOTH sides of motivation: +- **Positive drivers** (what they want to achieve) +- **Negative drivers** (what they fear or want to avoid) + +Remember: Negative drivers are often more powerful (loss aversion principle). + +{{#each personas}} + +--- + +**{{this.name}}** + + + **Positive Drivers (What they want)** + +Your documentation suggests {{this.name}} wants to: + +{{#each this.extracted_positive}} +- {{this}} +{{/each}} + + Do these capture what {{this.name}} is trying to achieve? Anything missing? + + Refine positive drivers based on feedback + + + + **Positive Drivers (What they want)** + +Your documentation mentions general needs like: +{{#each this.vague_wants}} +- "{{this}}" +{{/each}} + +These are too vague. Let's make them specific to the **usage context**. + + When {{this.name}} uses your product, what specific outcomes do they want? + +Not general life goals, but what they want to accomplish **in this usage context**. + + Create specific usage-context positive drivers + + + + **Positive Drivers (What they want)** + +Your documentation doesn't explicitly state what {{this.name}} wants to achieve. + + When {{this.name}} uses your product, what are they trying to accomplish? What positive outcomes do they seek? + + Define positive drivers through conversation + + + + **Negative Drivers (What they fear/avoid)** + +Your research identifies these fears and frustrations: + +{{#each this.extracted_negative}} +- {{this}} +{{/each}} + + Do these capture what {{this.name}} wants to avoid? Any other fears or frustrations? + + Refine negative drivers based on feedback + + + + **Negative Drivers (What they fear/avoid)** + +Your documentation mentions pain points: +{{#each this.pain_points}} +- {{this}} +{{/each}} + +Let's frame these as **psychological drivers** - what they fear or want to avoid. + + Based on these pain points, what does {{this.name}} fear? What are they trying to avoid? + +Think about: +- Fear of embarrassment or looking unprofessional +- Fear of wasting time or money +- Fear of making wrong decisions +- Frustration with current solutions +- Anxiety about outcomes + + Transform pain points into negative drivers + + + + **Negative Drivers (What they fear/avoid)** + +Your documentation focuses on what users want, but doesn't mention fears or frustrations. + +This is common - but negative drivers are often MORE powerful than positive ones! + + What does {{this.name}} fear or want to avoid in this context? + +Think about the flip side of their positive wants: +- If they want to look professional, they fear looking unprofessional +- If they want to save time, they fear wasting time +- If they want to make good decisions, they fear making wrong ones + +What are {{this.name}}'s fears and frustrations? + + Define negative drivers through conversation + + +{{this.name}}_driving_forces + +{{/each}} + +**Workshop 3 Complete!** ✅ + +**Driving Forces Mapped:** +{{#each personas}} +- **{{this.name}}**: {{this.positive_count}} positive drivers, {{this.negative_count}} negative drivers +{{/each}} + +Next, we'll prioritize which groups and drivers matter most. + + diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-04-prioritization.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-04-prioritization.md new file mode 100644 index 000000000..e1c5047ec --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-04-prioritization.md @@ -0,0 +1,130 @@ +# Documentation Synthesis - Step 4: Prioritization + +Documentation rarely includes explicit prioritization +Use conversation to determine what matters most + + + +**Prioritizing Strategic Elements** + +Your documentation gives us the pieces. Now we need to prioritize: +- Which target groups have highest impact on your objectives? +- Which groups are most feasible to reach? +- Which driving forces are most frequent and intense? + +Check if documentation includes any prioritization signals: +- Explicit priority statements +- Resource allocation (budget, team focus) +- Timeline emphasis (what's first) +- Frequency of mention +- Depth of research on certain groups + + + + Based on your documentation, I see these priority signals: + +{{#each priority_signals}} +- {{this.signal}}: suggests {{this.implication}} +{{/each}} + +This suggests the following prioritization: + + + + Your documentation doesn't explicitly prioritize between groups or drivers. + +Let's determine priorities together: + + +**Target Group Prioritization** + +{{#each target_groups}} +**{{@index + 1}}. {{this.name}}** +{{/each}} + +For each group, let's assess: + +**Impact on objectives:** If this group succeeds with your product, how much does it drive your objectives? (High/Medium/Low) + +**Feasibility:** How easy is it to reach and serve this group? (High/Medium/Low) + +Let's start with {{first_group.name}}: +- Impact on objectives? +- Feasibility? + +For each group, gather impact and feasibility ratings +Calculate priority score (Impact × Feasibility) +Rank groups by priority + +**Priority Ranking:** + +{{#each prioritized_groups}} +{{@index + 1}}. **{{this.name}}** ({{this.priority_level}}) + - Impact on objectives: {{this.impact}} + - Feasibility: {{this.feasibility}} + - Reasoning: {{this.reasoning}} +{{/each}} + +Does this prioritization align with your strategic thinking? + +prioritized_groups + +--- + +**Driving Forces Prioritization** + +Now let's identify the top drivers across all groups: + +Analyze driving forces for: +- Frequency (how many groups share this driver?) +- Intensity (how strongly do they feel this?) +- Alignment with top-priority groups + + +**Top Driving Forces:** + +{{#each top_drivers}} +{{@index + 1}}. **{{this.driver}}** ({{this.type}}) + - Affects: {{this.groups_affected}} + - Intensity: {{this.intensity}} + - Priority: {{this.priority_level}} +{{/each}} + +Do these feel like the most critical drivers to address? + +prioritized_drivers + +--- + +**Design Focus Statement** + +Based on this prioritization: + +Generate focus statement combining: +- Top priority group +- Top 3-5 drivers +- Connection to objectives + + +{{focus_statement}} + +Does this capture where design efforts should focus? + +focus_statement + +**Workshop 4 Complete!** ✅ + +**Strategic Priorities Set:** +- Top group: {{top_group.name}} +- Top drivers: {{top_driver_count}} identified +- Focus statement: Defined + +{{#if feature_list_in_docs}} +Your documentation includes a feature list. Would you like to run the optional **Feature Impact workshop** to score features against these priorities? +{{/if}} + +{{#if no_feature_list}} +Next, I'll create your comprehensive Trigger Map documentation and handover. +{{/if}} + + diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-05-gap-analysis.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-05-gap-analysis.md new file mode 100644 index 000000000..37bb9c92f --- /dev/null +++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-05-gap-analysis.md @@ -0,0 +1,141 @@ +# Documentation Synthesis - Step 5: Gap Analysis & Validation + +Identify what's strong vs. weak in documentation +Validate strategic alignment between docs and plans + + + +**Gap Analysis & Validation** + +Let me analyze what we've built from your documentation... + +Compare original documentation to synthesized Trigger Map: +- What was clear and strong? +- What was vague or missing? +- What did we fill through conversation? +- Are there contradictions or misalignments? + + +**Documentation Strengths:** + +{{#each strengths}} +✅ {{this.area}}: {{this.description}} +{{/each}} + + + **Gaps Identified:** + +{{#each gaps}} +⚠️ **{{this.area}}**: {{this.gap}} + - Impact: {{this.impact}} + - What we did: {{this.how_filled}} +{{/each}} + + + + **Critical Gaps:** + +{{#each critical_gaps}} +❌ **{{this.area}}**: {{this.gap}} + - **Impact:** {{this.impact}} + - **Recommendation:** {{this.recommendation}} +{{/each}} + + These gaps could affect your strategy. Would you like to: + +a. **Address now** - Fill these gaps through focused conversation +b. **Note for later** - Document as areas for future research +c. **Accept as-is** - Work with what we have + +Which approach? + + + Run targeted mini-workshops for critical gaps + + + + Document gaps in handover notes + + + +--- + +**Strategic Alignment Check** + +Reverse engineer: Does the plan match the vision? +- Compare stated vision to implied vision from plans +- Check if objectives align with vision +- Verify target groups serve objectives +- Validate features address drivers + + +**Consistency Check:** + +Your documentation says you want: +> {{vision_statement}} + +Your plan/features suggest: +> {{plan_implications}} + + + ✅ **Strong alignment** - Your plans effectively support your vision. + +The Trigger Map reveals a coherent strategy where: +- Objectives measure progress toward vision +- Target groups drive objectives through their usage +- Driving forces are addressed by planned approach + + + + ⚠️ **Potential misalignment detected:** + +{{#each misalignments}} +**Issue {{@index + 1}}:** {{this.issue}} +- **Documentation says:** {{this.doc_says}} +- **Plan implies:** {{this.plan_implies}} +- **Recommendation:** {{this.recommendation}} +{{/each}} + + These misalignments could indicate: +- Vision and plan aren't fully aligned +- Documentation is outdated +- Hidden assumptions need surfacing + +Should we address these before finalizing the Trigger Map? + + Discuss and resolve misalignments + + +--- + +**What You've Accomplished** + +From your documentation, we've created: + +✅ **Clear Vision**: {{vision_statement}} +✅ **{{objective_count}} Strategic Objectives**: Measurable and SMART +✅ **{{group_count}} Prioritized Target Groups**: Behavioral profiles with psychological depth +✅ **{{driver_count}} Driving Forces**: Both positive and negative +✅ **Strategic Focus**: {{focus_statement}} +✅ **Gap Analysis**: {{gap_count}} areas identified for future research + +**What you now have:** +- Single-slide strategic reference (instead of {{page_count}} pages) +- Clear priorities for design decisions +- Psychological insights organized and actionable +- Gaps identified for future research +- Validated strategic alignment + +**What you can do with this:** +- Reference it in daily design work +- Share it in AI chats for context (much better than pasting extensive docs) +- Use it for team alignment +- Guide feature prioritization +- Validate design decisions + +Ready to proceed to documentation generation and handover? + +gap_analysis +alignment_check + +