238 lines
6.5 KiB
Markdown
238 lines
6.5 KiB
Markdown
# 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*
|