whiteport-design-studio 0.1.0

package/docs/learn-wds/course-explainers/Module-04-notebook-lm-prompt.md

@@ -0,0 +1,163 @@
+# NotebookLM Prompt: Module 04 - Product Brief
+
+**Use this prompt to generate audio/video content for Module 04: Product Brief**
+
+---
+
+## Instructions for NotebookLM
+
+**This is a single, self-contained prompt file.**
+
+Simply upload THIS FILE to NotebookLM and use the prompt below to generate engaging audio/video content. No other files needed.
+
+---
+
+## Prompt
+
+Create an engaging 25-30 minute podcast conversation between two hosts discussing Module 04 of the Whiteport Design Studio (WDS) course: Product Brief.
+
+**IMPORTANT: WDS stands for Whiteport Design Studio - always refer to it by its full name "Whiteport Design Studio" or "WDS" throughout the conversation.**
+
+**Host 1 (The Curious Designer):** A designer ready to start a project and wants to understand the practical process.
+
+**Host 2 (The Practical Guide):** A designer who uses the Product Brief as a living reference throughout every project phase.
+
+**Conversation structure:**
+
+### 1. Opening (3 min) - The Real Question
+
+The Curious Designer: "I already know what app I want to build. Why should I waste time on a document?"
+
+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: "Wait, a prompt? I thought it was planning documentation."
+
+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. One Environment, Zero Copy-Paste (4 min)
+
+The Curious Designer: "OK, but where does this actually happen? Am I jumping between ChatGPT and my code editor?"
+
+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.
+
+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."
+
+The Curious Designer: "So I'm not switching tools constantly?"
+
+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. Questions That Make Your Idea Better (6 min)
+
+The Curious Designer: "You said this makes my idea better. How?"
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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."
+
+The Curious Designer: "So it's not just documentation, it's thinking?"
+
+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. Man and Machine Collaboration (5 min)
+
+The Curious Designer: "Wait, so Saga is writing the document while I talk. Can I see what she's doing?"
+
+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.
+
+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.
+
+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."
+
+The Curious Designer: "So I'm not just prompting and hoping?"
+
+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. Beyond the Brief - The Complete Foundation (4 min)
+
+The Curious Designer: "Is the Product Brief the only document I create?"
+
+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.
+
+Need to define your main features? She creates a Core Features document.
+
+Need to specify supported languages? She creates a Language Selection document.
+
+Need to define your brand voice? She creates a Tone of Voice document.
+
+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. Stopping Hallucinations Before They Start (4 min)
+
+The Curious Designer: "You mentioned this stops AI hallucinations. How?"
+
+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.
+
+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.
+
+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.
+
+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. The Bottom Line (3 min)
+
+The Curious Designer: "OK, I'm convinced. What's the actual time investment?"
+
+The Practical Guide: "Maybe 2-3 hours for a thorough Product Brief. But here's what you're getting:
+
+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."
+
+---
+
+## End of Prompt
+
+Generate the podcast conversation following this structure, maintaining natural dialogue flow while covering all key concepts. Make it engaging, practical, and action-oriented.

package/docs/learn-wds/course-explainers/Module-04-thumbnail-prompt.md

@@ -0,0 +1,36 @@
+**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: "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):**
+- "04 Product Brief" (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 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 product brief with visible sections/structure
+- Skip the tablet
+
+**Background Pattern:**
+- Clear the background from previous objects except the globe
+- Add oversized and toned down strategic elements (checkmarks, document icons, organizational charts, flowchart nodes)
+- Keep as in reference image
+
+**Workspace Props:**
+- 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
+- Top-right branding text
+- Character design and style
+- Color scheme and layout
+

package/docs/learn-wds/course-explainers/Module-04-youtube-show-notes.md

@@ -0,0 +1,95 @@
+Module 04 - Product Brief - Your Strategic Foundation Through Guided Conversation
+
+<https://youtu.be/yhKxkuLq1kQ>
+
+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.
+
+*You'll learn:*
+✅ Why projects fail without strategic foundation (and how to prevent it)
+✅ The 5 strategic questions every Product Brief must answer
+✅ What the document looks like and how teams use it
+✅ How WDS ensures excellence through thinking partnership
+✅ Additional strategic documents you can create as needed
+
+*Free & open-source* | 46-58 minutes | Foundation module
+
+⏱️ Timestamps
+
+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
+
+*What & Why* - Vision and positioning (what you're building, why it matters)
+*Who* - Target users and stakeholders (who uses it, who decides)
+*How We'll Know* - Success criteria (measurable outcomes)
+*Context* - Competitive landscape (alternatives, differentiation)
+*Boundaries* - Constraints (technical, business, design limitations)
+
+📋 What You'll Create
+
+*Core Document:*
+Product Brief (2-3 pages) - Single source of truth for entire team
+
+*Optional Documents (as needed):*
+Core Features - Feature prioritization (must/should/could/won't have)
+Tone of Voice - Brand personality and communication guidelines
+Visual Design Brief - Visual direction and inspiration
+Technical Brief - Architecture and integration requirements
+Content Strategy - Content types, goals, publishing
+Localization Strategy - Multi-language/region planning
+Accessibility Requirements - Compliance and user needs
+Data & Privacy - Collection, storage, compliance
+
+📚 Course Resources
+
+🌊 *WDS Presentation:*
+<https://whiteport.com/whiteport-design-studio/>
+
+📖 *Tutorial 04:*
+<https://github.com/whiteport-collective/whiteport-design-studio/blob/main/docs/learn-wds/module-04-product-brief/tutorial-04.md>
+
+📖 *Project Brief Template:*
+<https://github.com/whiteport-collective/whiteport-design-studio/blob/main/src/modules/wds/workflows/1-project-brief/project-brief/complete/project-brief.template.md>
+
+💬 *UX-Design channel in the BMad Discord Community:*
+<https://discord.gg/Pn63gAuX>
+
+📖 *GitHub Discussions:*
+<https://github.com/whiteport-collective/whiteport-design-studio/discussions>
+
+◀️ *Previous Module:* Module 03 - Alignment & Signoff
+<https://www.youtube.com/watch?v=TKjOLlU8UCE>
+
+▶️ *Next Module:* Module 05 - Trigger Mapping
+<https://youtu.be/xs_cRk-NoJk>
+
+📚 *Full Course:*
+<https://github.com/whiteport-collective/whiteport-design-studio/blob/main/docs/learn-wds/00-course-overview.md>
+
+⚡ *The WDS Advantage*
+
+*Thinking Partnership:* Human-in-the-loop collaboration from BMad methodology
+*AI-Guided:* No blank page, no missed elements
+*Conversational:* Talk it out, Saga writes it down
+*Professional:* Built-in best practices (SMART goals, constraint checklists)
+*Flexible:* Two levels (simplified or complete based on needs)
+*Living:* Easy to update as you learn
+
+✅ *Next Steps:*
+1. Watch this module to understand the Product Brief approach
+2. Complete Tutorial 04 to create your Product Brief with Saga
+3. Add optional documents as your project needs them
+4. Share with team for alignment
+5. Start Module 05: Trigger Mapping
+
+🎨 *About WDS*
+AI-augmented design methodology by Mårten Angner (Whiteport, Sweden). The Product Brief is your project's constitution - everything else is legislation.
+
+#ProductBrief #DesignStrategy #ProjectPlanning #WDS #StrategicFoundation #AIGuided
+
+*This one document is the difference between confident execution and constant confusion. 🎯*

package/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["<b>BUSINESS GOAL 1</b><br/><br/>Visionary Statement 1<br/><br/><b>Strategic Objectives:</b><br/>• Strategic Objective 1<br/>• Strategic Objective 2<br/>• Strategic Objective 3"]
+    
+    BG2["<b>BUSINESS GOAL 2</b><br/><br/>Visionary Statement 2<br/><br/><b>Strategic Objectives:</b><br/>• Strategic Objective 1<br/>• Strategic Objective 2<br/>• Strategic Objective 3"]
+    
+    PRODUCT["<b>Product/Solution Name</b>"]
+    
+    TG1["👥 <b>Primary Target Group</b>"]
+    
+    TG2["👤 <b>Secondary Target Group</b>"]
+    
+    POS1["<b>✅ POSITIVE DRIVERS:</b><br/>• Positive Usage Goal 1<br/>• Positive Usage Goal 2"]
+    
+    NEG1["<b>❌ NEGATIVE DRIVERS:</b><br/>• Negative Usage Goal 1<br/>• Negative Usage Goal 2"]
+    
+    POS2["<b>✅ POSITIVE DRIVERS:</b><br/>• Positive Usage Goal 1<br/>• Positive Usage Goal 2"]
+    
+    NEG2["<b>❌ NEGATIVE DRIVERS:</b><br/>• Negative Usage Goal 1<br/>• 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

package/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
+
+.