508 lines
17 KiB
Markdown
508 lines
17 KiB
Markdown
# Module 06: Trigger Mapping
|
|
|
|
## Lesson 9: 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.
|
|
|
|
---
|
|
|
|
## The Critical Distinction: Psychological Framing
|
|
|
|
**Even when drivers seem "technically the same," the psychological framing is different.**
|
|
|
|
### Proactive vs Reactive Modes
|
|
|
|
Consider these two statements:
|
|
- **"Everything is possible"** (POSITIVE framing)
|
|
- **"Nothing is impossible"** (NEGATIVE framing)
|
|
|
|
Logically, they express the same concept. Psychologically, they reveal completely different mental states:
|
|
|
|
**"Everything is possible" - Proactive Mode:**
|
|
- **Mental state:** Aspirational, forward-looking, seeking opportunity
|
|
- **Emotional tone:** Optimistic, energized, exploratory
|
|
- **Triggers action by:** Opening possibilities, creating excitement
|
|
- **Design implications:** Inspire, enable discovery, celebrate potential
|
|
- **Example:** "Achieve your dreams," "Build something amazing"
|
|
|
|
**"Nothing is impossible" - Reactive Mode:**
|
|
- **Mental state:** Overcoming barriers, fighting against limits, defensive
|
|
- **Emotional tone:** Determined, defiant, problem-solving
|
|
- **Triggers action by:** Removing obstacles, proving doubters wrong
|
|
- **Design implications:** Remove friction, show path through barriers, validate capability
|
|
- **Example:** "Overcome any obstacle," "Break through limits"
|
|
|
|
### Why This Matters for Design
|
|
|
|
**The same feature can be framed for proactive or reactive users:**
|
|
|
|
**Feature:** Goal-setting tool
|
|
|
|
**Proactive framing (positive driver):**
|
|
- **Persona in proactive mode:** "Want to achieve big goals"
|
|
- **UI language:** "Dream big," "Set your vision," "What do you want to create?"
|
|
- **Visual tone:** Bright, aspirational, open-ended
|
|
- **Onboarding:** "What excites you? Let's build toward it."
|
|
|
|
**Reactive framing (negative driver):**
|
|
- **Persona in reactive mode:** "Fear of goals slipping away"
|
|
- **UI language:** "Never lose track," "Stay on target," "Don't let this slip"
|
|
- **Visual tone:** Focused, protective, structured
|
|
- **Onboarding:** "What's at risk if you don't stay focused? Let's prevent that."
|
|
|
|
**Both address goal-setting. The psychological approach is completely different.**
|
|
|
|
### Identifying the Mode During Workshop 3
|
|
|
|
**When Saga explores drivers, she helps you identify the mode:**
|
|
|
|
> **Saga:** "When they think about advancing their career, are they moving toward something exciting or away from something they fear?"
|
|
> **You:** "They're worried about being stuck in their current role forever..."
|
|
> **Saga:** "So it's reactive - fear of stagnation. That's different from proactive ambition. Note that."
|
|
|
|
**This distinction affects:**
|
|
1. **Feature design** - How features are structured and presented
|
|
2. **UI language** - The words and tone used in the interface
|
|
3. **Visual hierarchy** - What gets emphasized and how
|
|
4. **Onboarding flow** - How you introduce value to users
|
|
5. **Success metrics** - What users celebrate vs what they avoid
|
|
|
|
### Example: Remote Team Lead
|
|
|
|
**Same underlying need, different psychological modes:**
|
|
|
|
**Proactive framing:**
|
|
- **Driver:** "Want to build strong, connected team culture"
|
|
- **Mode:** Seeking positive outcome
|
|
- **Feature approach:** Team-building activities, connection tools, culture dashboards
|
|
- **UI tone:** "Let's strengthen your team," "Build something great together"
|
|
|
|
**Reactive framing:**
|
|
- **Driver:** "Fear of team becoming disconnected and disengaged"
|
|
- **Mode:** Preventing negative outcome
|
|
- **Feature approach:** Engagement alerts, disconnect warnings, intervention prompts
|
|
- **UI tone:** "Catch problems early," "Don't let disconnection grow"
|
|
|
|
**Both serve team connection. The design psychology is fundamentally different.**
|
|
|
|
---
|
|
|
|
## 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 (Proactive):** Want to be seen as competent leader
|
|
- **Mode:** Seeking recognition and advancement
|
|
- **Design approach:** Showcase achievements, highlight strengths, enable excellence
|
|
- **UI tone:** "Shine," "Excel," "Lead with confidence"
|
|
|
|
**Negative (Reactive):** Fear of looking incompetent
|
|
- **Mode:** Avoiding embarrassment and judgment
|
|
- **Design approach:** Prevent mistakes, provide safety nets, avoid exposure
|
|
- **UI tone:** "Avoid errors," "Stay protected," "Don't get caught off guard"
|
|
|
|
**Design implication:** Features that help users look good (proactive) AND avoid embarrassment (reactive)
|
|
|
|
### Pattern 2: Time Management
|
|
|
|
**Positive (Proactive):** Want to accomplish more and be productive
|
|
- **Mode:** Maximizing potential and achievement
|
|
- **Design approach:** Enable efficiency, celebrate completion, unlock capacity
|
|
- **UI tone:** "Achieve more," "Maximize your day," "Unlock potential"
|
|
|
|
**Negative (Reactive):** Fear of wasting time or missing deadlines
|
|
- **Mode:** Protecting against failure and loss
|
|
- **Design approach:** Prevent time waste, deadline alerts, crisis avoidance
|
|
- **UI tone:** "Never miss a deadline," "Stop the time drain," "Stay on track"
|
|
|
|
**Design implication:** Time-saving features (proactive) + deadline protection (reactive)
|
|
|
|
### Pattern 3: Social Connection
|
|
|
|
**Positive (Proactive):** Want to build strong, meaningful relationships
|
|
- **Mode:** Growing connections and belonging
|
|
- **Design approach:** Facilitate bonding, enable sharing, celebrate togetherness
|
|
- **UI tone:** "Connect deeper," "Build community," "Grow together"
|
|
|
|
**Negative (Reactive):** Fear of isolation or being left out
|
|
- **Mode:** Preventing disconnection and exclusion
|
|
- **Design approach:** Alert to missed interactions, FOMO prevention, inclusion signals
|
|
- **UI tone:** "Don't miss out," "Stay included," "Avoid isolation"
|
|
|
|
**Design implication:** Connection features (proactive) + FOMO prevention (reactive)
|
|
|
|
### Pattern 4: Control & Autonomy
|
|
|
|
**Positive (Proactive):** Want to feel empowered and in command
|
|
- **Mode:** Seeking mastery and capability
|
|
- **Design approach:** Enable control, provide powerful tools, celebrate autonomy
|
|
- **UI tone:** "Take control," "Master your domain," "Own your outcomes"
|
|
|
|
**Negative (Reactive):** Fear of chaos and overwhelm
|
|
- **Mode:** Preventing collapse and loss of control
|
|
- **Design approach:** Reduce complexity, provide structure, prevent overwhelm
|
|
- **UI tone:** "Stop the chaos," "Regain control," "Prevent overwhelm"
|
|
|
|
**Design implication:** Organization tools that empower (proactive) + anxiety reduction (reactive)
|
|
|
|
---
|
|
|
|
## How to Use This in Design
|
|
|
|
### Critical: Know the Persona's Mode
|
|
|
|
**Before designing features, identify whether the persona is in:**
|
|
- **Proactive mode** - Seeking gain, exploring possibilities, building toward
|
|
- **Reactive mode** - Avoiding pain, solving problems, protecting against
|
|
|
|
**This affects EVERYTHING about the design:**
|
|
|
|
| Design Element | Proactive Mode | Reactive Mode |
|
|
|----------------|----------------|---------------|
|
|
| **Language** | Aspirational, enabling | Protective, preventing |
|
|
| **Visual tone** | Bright, open, inspiring | Focused, structured, safe |
|
|
| **Feature presentation** | "Unlock potential" | "Prevent problems" |
|
|
| **Urgency level** | Lower (can start tomorrow) | Higher (need it now) |
|
|
| **Success metrics** | Achievement celebrated | Disasters avoided |
|
|
|
|
**Example: Same notification feature, different modes:**
|
|
- **Proactive:** "You're on track to hit your goal! Keep it up!"
|
|
- **Reactive:** "Warning: You're falling behind. Act now to stay on track."
|
|
|
|
### For Feature Prioritization
|
|
|
|
Features that address negative drivers (reactive mode) often rank higher because they solve urgent problems.
|
|
|
|
**Generic example:**
|
|
- Feature A: "Dashboard for tracking progress toward goals" (proactive, positive driver)
|
|
- Feature B: "Alert system for missed critical tasks" (reactive, negative driver)
|
|
- **Which is more urgent?** Feature B (prevents pain happening NOW)
|
|
|
|
**But framing matters:**
|
|
- Same dashboard, proactive framing: "See how far you've come!"
|
|
- Same dashboard, reactive framing: "Don't let tasks slip through!"
|
|
|
|
### For Messaging & Marketing
|
|
|
|
**Proactive-focused messaging (positive drivers):**
|
|
- "Achieve your goals"
|
|
- "Build something great"
|
|
- "Unlock your potential"
|
|
- Appeals to: Aspirational users seeking growth
|
|
|
|
**Reactive-focused messaging (negative drivers):**
|
|
- "Never miss another deadline"
|
|
- "Stop the chaos before it starts"
|
|
- "Prevent costly mistakes"
|
|
- Appeals to: Users with urgent pain points
|
|
|
|
**Which converts better?** Usually reactive-focused (addresses urgent pain)
|
|
|
|
**But best approach:** Lead with reactive (hook the pain), deliver proactive (show the gain)
|
|
|
|
### For User Onboarding
|
|
|
|
**Match the persona's mode:**
|
|
|
|
**If persona is in reactive mode:**
|
|
1. Acknowledge the specific pain immediately
|
|
2. Show how you prevent that pain
|
|
3. Then highlight positive outcomes as bonus
|
|
|
|
**If persona is in proactive mode:**
|
|
1. Validate their ambition
|
|
2. Show how you enable their goals
|
|
3. Address preventable obstacles as supporting points
|
|
|
|
**Example: Onboarding for Remote Team Lead**
|
|
|
|
**Reactive mode (fear of burnout):**
|
|
> "Worried about team burnout creeping up unnoticed? Get daily pulse checks that catch problems early, so you can intervene before it's too late."
|
|
|
|
**Proactive mode (want to build culture):**
|
|
> "Ready to build a thriving remote team culture? Use daily pulse checks to understand your team's needs and celebrate what's working."
|
|
|
|
**Same feature. Completely different psychological approach.**
|
|
|
|
**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-seeking) and Negative (pain-avoidance)
|
|
✅ **Negative is more powerful** - Loss aversion drives urgent action (roughly 2x stronger)
|
|
✅ **Psychological framing matters** - "Everything is possible" ≠ "Nothing is impossible" (proactive vs reactive)
|
|
✅ **Identify the persona's mode** - Proactive (seeking) or Reactive (avoiding) affects ALL design decisions
|
|
✅ **Map both for each persona** - Complete psychological picture with mode identification
|
|
✅ **Be specific** - Avoid generic wants, find emotional core AND mental state
|
|
✅ **Design implications are different** - Language, tone, visuals, urgency all change based on mode
|
|
✅ **Use in design phase** - Freya needs to know if persona is proactive or reactive to design appropriately
|
|
|
|
---
|
|
|
|
## 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 Module Overview](module-06-overview.md) | [← 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 06: Trigger Mapping*
|