convoke-agents 2.0.0

package/_bmad/bme/_vortex/workflows/empathy-map/empathy-map.template.md

@@ -0,0 +1,143 @@
+---
+title: "Empathy Map: {user-name}"
+date: {date}
+created-by: {user-name} with Isla (discovery-empathy-expert)
+research-sources: {research-sources}
+status: DRAFT
+---
+
+# Empathy Map: {user-name}
+
+## Executive Summary
+
+**Key Insights:**
+{key-insights}
+
+**Primary Pain Points:**
+{top-3-pain-points}
+
+**Top Desired Gains:**
+{top-3-gains}
+
+---
+
+## Target User Profile
+
+**Who:** {user-demographics}
+
+**Job-to-be-done:** {job-to-be-done}
+
+**Context:** {user-context}
+
+**Research Sources:**
+{research-sources-list}
+
+---
+
+## Says & Thinks
+
+### What They SAY (Direct Quotes)
+
+{says-list}
+
+### What They THINK (Inferred Thoughts)
+
+{thinks-list}
+
+---
+
+## Does & Feels
+
+### What They DO (Observable Actions)
+
+{does-list}
+
+### What They FEEL (Emotional States)
+
+{feels-list}
+
+---
+
+## Pain Points
+
+**Priority:** High = Critical | Medium = Important | Low = Nice-to-fix
+
+{pain-points-detailed}
+
+**Summary:**
+- **High Priority:** {count-high}
+- **Medium Priority:** {count-medium}
+- **Low Priority:** {count-low}
+
+---
+
+## Desired Gains
+
+**Priority:** High = Must-have | Medium = Important | Low = Nice-to-have
+
+{gains-detailed}
+
+**Summary:**
+- **High Priority:** {count-high-gains}
+- **Medium Priority:** {count-medium-gains}
+- **Low Priority:** {count-low-gains}
+
+---
+
+## Design Implications
+
+### What This Means for Design
+
+**Based on this empathy map, we should:**
+
+1. **Prioritize:** {priority-implications}
+
+2. **Avoid:** {avoid-implications}
+
+3. **Focus On:** {focus-implications}
+
+### Feature Prioritization Matrix
+
+| Pain Point | Desired Gain | Design Opportunity | Priority |
+|------------|--------------|-------------------|----------|
+{feature-matrix}
+
+---
+
+## Validation Checklist
+
+- [ ] Empathy map reviewed by users (shows it resonates)
+- [ ] Team alignment achieved (stakeholders understand user perspective)
+- [ ] Design decisions informed by insights (wireframes, features)
+- [ ] Success metrics defined (based on user gains)
+- [ ] Research sources documented (traceable insights)
+
+---
+
+## Next Steps
+
+**Recommended Actions:**
+
+1. **Validate:** Show this empathy map to 3-5 users and ask if it resonates
+2. **Share:** Present to team for alignment on user needs
+3. **Design:** Use insights to inform wireframes and feature decisions
+4. **Measure:** Track success using gain metrics
+5. **Iterate:** Update empathy map as new research emerges
+
+---
+
+## Research Sources
+
+{research-sources-detailed}
+
+---
+
+**Created by:** {creator-name}
+**Created with:** Isla (discovery-empathy-expert) - Convoke v2.0.0
+**Date:** {creation-date}
+**Version:** 1.0
+**Status:** {status}
+
+---
+
+*This empathy map is a living document. Update it as you learn more about your users through ongoing research.*

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-01-define-user.md

@@ -0,0 +1,60 @@
+---
+step: 1
+workflow: empathy-map
+title: Define Target User
+---
+
+# Step 1: Define Target User
+
+Before we create an empathy map, we need to be crystal clear about WHO we're creating it for.
+
+## Why This Matters
+
+An empathy map is only as useful as its specificity. "Users" is too broad. "Mobile app users" is still too broad. "Busy parents managing multiple kids' schedules on mobile" - now we're getting somewhere.
+
+## Your Task
+
+Answer these questions to define your target user:
+
+### 1. Who is this user? (Demographics)
+- Age range?
+- Occupation/role?
+- Location/context?
+- Tech savvy level?
+
+### 2. What is their core job-to-be-done?
+What are they trying to accomplish when they interact with your product/service?
+
+### 3. What context are we focusing on?
+When and where are they using your product? What's happening around them?
+
+### 4. What user research informs this empathy map?
+- Interview transcripts?
+- Survey responses?
+- Observational studies?
+- Analytics data?
+
+## Example
+
+**Target User:** Sarah, a 34-year-old marketing manager at a mid-sized B2B SaaS company. She manages a team of 5 and is responsible for lead generation campaigns.
+
+**Job-to-be-done:** Plan and execute multi-channel marketing campaigns that generate qualified leads for the sales team.
+
+**Context:** Working from home office, juggling multiple campaigns simultaneously, under pressure to hit quarterly lead targets.
+
+**Research Sources:**
+- 3 user interviews (transcripts: INT-001, INT-002, INT-003)
+- Survey of 50 marketing managers
+- 2 hours of screen-recording observation
+
+---
+
+## Your Turn
+
+Please define your target user using the structure above.
+
+## Next Step
+
+When you've defined your target user and I've confirmed the definition is specific enough, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/empathy-map/steps/step-02-says-thinks.md

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-02-says-thinks.md

@@ -0,0 +1,67 @@
+---
+step: 2
+workflow: empathy-map
+title: Says & Thinks
+---
+
+# Step 2: Says & Thinks
+
+Now let's capture what your target user **says out loud** and what they **think privately**.
+
+## Why This Matters
+
+There's often a gap between what people say and what they actually think. Understanding both helps us:
+- Identify unspoken needs
+- Spot contradictions that reveal pain points
+- Understand social pressures influencing their behavior
+
+## What vs. Why
+
+- **SAYS** - Direct quotes from user research ("I check my email first thing every morning")
+- **THINKS** - Inferred thoughts based on behavior and tone ("I'm worried I'll miss something important")
+
+## Your Task
+
+### What They SAY (3-5 direct quotes)
+
+Pull actual quotes from your user research. These should be things they said out loud in interviews, surveys, or conversations.
+
+**Example:**
+- "I don't have time to learn a new tool right now"
+- "My team needs better collaboration features"
+- "I wish I could see all my campaigns in one place"
+
+### What They THINK (3-5 inferred thoughts)
+
+Based on their behavior, tone, and context, what are they thinking but not saying?
+
+**Example:**
+- "If I adopt this tool and it fails, I'll look bad to my boss"
+- "I'm overwhelmed by the number of platforms I already use"
+- "My current process is inefficient but at least it's familiar"
+
+## Tips for Success
+
+**For SAYS:**
+- Use direct quotes (exact words when possible)
+- Include both positive and negative statements
+- Capture the language they use (jargon, metaphors, etc.)
+
+**For THINKS:**
+- Look for hesitation, tone shifts, or contradictions
+- Consider what they DON'T say (conspicuous absences)
+- Infer based on behavior, not speculation
+
+---
+
+## Your Turn
+
+Please provide:
+1. 3-5 things your target user SAYS (direct quotes)
+2. 3-5 things your target user THINKS (inferred thoughts)
+
+## Next Step
+
+When you've captured both SAYS and THINKS, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/empathy-map/steps/step-03-does-feels.md

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-03-does-feels.md

@@ -0,0 +1,79 @@
+---
+step: 3
+workflow: empathy-map
+title: Does & Feels
+---
+
+# Step 3: Does & Feels
+
+Let's capture what your target user **does** (observable actions) and **feels** (emotional states).
+
+## Why This Matters
+
+Actions reveal priorities. Emotions drive decisions. Together, they show us:
+- What users actually do vs. what they say they do
+- Emotional triggers that influence behavior
+- Moments of delight or frustration
+
+## What vs. Why
+
+- **DOES** - Observable behaviors, actions, and habits
+- **FEELS** - Emotional states, reactions, and moods
+
+## Your Task
+
+### What They DO (3-5 observable actions)
+
+What specific behaviors did you observe or did they describe? These are concrete, observable actions.
+
+**Example:**
+- Opens email client before any other app every morning
+- Switches between 6 different tools to check campaign performance
+- Takes screenshots of data to create manual reports in PowerPoint
+- Sets reminders to follow up with leads but often misses them
+- Batch-processes tasks on Friday afternoons to "clear the deck" for Monday
+
+### What They FEEL (3-5 emotional states)
+
+What emotions did they express or did you infer from their tone, body language, or word choice?
+
+**Example:**
+- Frustrated when tools don't integrate with each other
+- Anxious about missing important lead notifications
+- Proud when a campaign performs well
+- Overwhelmed by the volume of data to analyze
+- Relieved when repetitive tasks are automated
+
+## Tips for Success
+
+**For DOES:**
+- Be specific (not "uses social media" but "checks LinkedIn 3x per day")
+- Include frequency/timing when relevant
+- Note workarounds or "hacks" they've created
+- Look for patterns across multiple users
+
+**For FEELS:**
+- Use emotion words (frustrated, anxious, excited, relieved)
+- Link emotions to specific moments or contexts
+- Note intensity (mildly annoyed vs. deeply frustrated)
+- Watch for contradictions (says "it's fine" but looks stressed)
+
+## Connecting Does & Feels
+
+Notice how actions and emotions influence each other:
+- DOES: Switches between 6 tools → FEELS: Frustrated, overwhelmed
+- FEELS: Anxious about missing notifications → DOES: Checks email obsessively
+
+---
+
+## Your Turn
+
+Please provide:
+1. 3-5 things your target user DOES (observable actions)
+2. 3-5 things your target user FEELS (emotional states)
+
+## Next Step
+
+When you've captured both DOES and FEELS, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/empathy-map/steps/step-04-pain-points.md

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-04-pain-points.md

@@ -0,0 +1,87 @@
+---
+step: 4
+workflow: empathy-map
+title: Pain Points
+---
+
+# Step 4: Pain Points
+
+Now let's identify the **obstacles, frustrations, and challenges** your target user faces.
+
+## Why This Matters
+
+Pain points reveal opportunities. Every pain point is a potential solution waiting to happen. Understanding pain points helps us:
+- Prioritize features that solve real problems
+- Avoid building solutions for non-problems
+- Empathize with user struggles
+
+## Types of Pain Points
+
+**Process Pain Points** - Inefficient workflows, too many steps, repetitive tasks
+
+**Support Pain Points** - Lack of help, unclear documentation, slow response times
+
+**Integration Pain Points** - Tools don't talk to each other, data silos, manual data transfer
+
+**Learning Pain Points** - Steep learning curve, unclear UI, inconsistent patterns
+
+**Emotional Pain Points** - Stress, anxiety, fear of failure, overwhelm
+
+## Your Task
+
+### Identify 4-6 Pain Points
+
+For each pain point, capture:
+1. **The Pain** - What's the problem?
+2. **The Impact** - How does it affect them?
+3. **The Evidence** - What research supports this?
+
+**Example:**
+
+**Pain #1: Data Scattered Across 6 Tools**
+- **Impact:** Wastes 2 hours per day switching tools and manually consolidating data
+- **Evidence:** "I feel like I spend more time gathering data than analyzing it" (INT-002)
+
+**Pain #2: Can't See Campaign Performance in Real-Time**
+- **Impact:** Misses opportunities to optimize underperforming campaigns early
+- **Evidence:** Observed user checking analytics 8 times in a 30-minute session (OBS-001)
+
+**Pain #3: No Automated Lead Scoring**
+- **Impact:** Sales team complains about low-quality leads, creating tension between marketing and sales
+- **Evidence:** "Sales always says our leads are junk, but we don't have a good way to prioritize them" (INT-003)
+
+## Tips for Success
+
+**Be Specific:**
+- Not "Bad UX" but "Button to create campaign is hidden in nested menu"
+- Not "Slow" but "Report generation takes 45 seconds, blocking other work"
+
+**Quantify When Possible:**
+- Time wasted
+- Frequency of occurrence
+- Number of steps involved
+
+**Ground in Evidence:**
+- Direct quotes
+- Observed behavior
+- Usage analytics
+
+**Prioritize by Severity:**
+- Which pain points cause the most frustration?
+- Which ones waste the most time?
+- Which ones risk critical failures?
+
+---
+
+## Your Turn
+
+Please identify 4-6 pain points your target user faces. For each pain point, include:
+1. The pain itself
+2. The impact on the user
+3. Evidence from research
+
+## Next Step
+
+When you've documented the pain points, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/empathy-map/steps/step-05-gains.md

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-05-gains.md

@@ -0,0 +1,103 @@
+---
+step: 5
+workflow: empathy-map
+title: Gains
+---
+
+# Step 5: Gains
+
+Let's identify what your target user **wants to achieve** - their desired outcomes, needs, and measures of success.
+
+## Why This Matters
+
+Pain points show us problems. Gains show us aspirations. Together they give us a complete picture:
+- Pain points → What to fix
+- Gains → What to enable
+
+Understanding gains helps us:
+- Design solutions that deliver meaningful value
+- Prioritize features based on desired outcomes
+- Measure success from the user's perspective
+
+## Types of Gains
+
+**Functional Gains** - Tasks completed faster, processes simplified, efficiency improved
+
+**Emotional Gains** - Reduced stress, increased confidence, peace of mind
+
+**Social Gains** - Better collaboration, improved reputation, team alignment
+
+**Aspirational Gains** - Career advancement, skill development, professional growth
+
+## Your Task
+
+### Identify 4-6 Gains
+
+For each gain, capture:
+1. **The Gain** - What do they want to achieve?
+2. **The Value** - Why does this matter to them?
+3. **Success Metric** - How would they know they achieved it?
+
+**Example:**
+
+**Gain #1: See All Campaign Performance in One Dashboard**
+- **Value:** Stop wasting time switching tools; make faster data-driven decisions
+- **Success Metric:** Can check all campaign metrics in under 2 minutes vs. current 15 minutes
+
+**Gain #2: Automated Lead Scoring**
+- **Value:** Send higher-quality leads to sales, improving marketing-sales relationship and conversion rates
+- **Success Metric:** Sales team accepts 80%+ of marketing-qualified leads vs. current 45%
+
+**Gain #3: Predict Campaign Performance Early**
+- **Value:** Optimize underperforming campaigns before budget is wasted; increase ROI
+- **Success Metric:** Adjust campaigns within first 48 hours based on performance signals
+
+**Gain #4: Collaborative Campaign Planning**
+- **Value:** Get team alignment before launch instead of fixing issues after launch
+- **Success Metric:** Team approves campaign plan in 1 meeting vs. current 3-4 rounds of revisions
+
+## Tips for Success
+
+**Link to Pain Points:**
+- Gains often flip pain points into aspirations
+- Pain: "Data scattered across 6 tools" → Gain: "See everything in one dashboard"
+
+**Be Outcome-Focused:**
+- Not "Use our tool" but "Complete campaigns 30% faster"
+- Not "Have more features" but "Reduce manual work by 50%"
+
+**Include Metrics:**
+- Time saved
+- Quality improved
+- Confidence increased
+- Collaboration enhanced
+
+**Distinguish Must-Haves from Nice-to-Haves:**
+- Which gains are critical for user success?
+- Which gains are differentiators vs. table stakes?
+
+## Connecting Gains to Pain Points
+
+Notice how gains address pain points:
+
+| Pain Point | Desired Gain |
+|------------|--------------|
+| Data scattered across 6 tools | Unified dashboard with all metrics |
+| Can't see real-time performance | Live campaign analytics with alerts |
+| Manual lead scoring | Automated lead qualification |
+| Time-consuming report generation | One-click reports with key insights |
+
+---
+
+## Your Turn
+
+Please identify 4-6 gains your target user desires. For each gain, include:
+1. What they want to achieve
+2. Why it matters (the value)
+3. How they'd measure success
+
+## Next Step
+
+When you've documented the desired gains, I'll load:
+
+{project-root}/_bmad/bme/_vortex/workflows/empathy-map/steps/step-06-synthesize.md

package/_bmad/bme/_vortex/workflows/empathy-map/steps/step-06-synthesize.md

@@ -0,0 +1,107 @@
+---
+step: 6
+workflow: empathy-map
+title: Synthesize
+---
+
+# Step 6: Synthesize
+
+Time to bring it all together and create the final empathy map artifact.
+
+## Why This Matters
+
+We've gathered rich insights across 5 dimensions (Says, Thinks, Does, Feels, Pains, Gains). Now we need to synthesize them into a coherent, actionable empathy map that:
+- Tells a compelling story about the user
+- Reveals patterns and insights
+- Guides design and product decisions
+
+## Your Task
+
+### 1. Review All Insights
+
+Look across all the data you've captured:
+- Target user definition (Step 1)
+- Says & Thinks (Step 2)
+- Does & Feels (Step 3)
+- Pain Points (Step 4)
+- Gains (Step 5)
+
+### 2. Identify Key Insights
+
+What patterns emerge? What surprises you? What's most important?
+
+**Example Insights:**
+- "Sarah says she wants more features, but really needs simplification - her current process involves 6 tools"
+- "Biggest pain isn't the tool itself, it's the data silos preventing real-time decisions"
+- "Anxiety about missing notifications drives obsessive email checking - automation would reduce stress"
+
+### 3. Create the Empathy Map
+
+I'll use the template at `empathy-map.template.md` to generate your final artifact.
+
+**Output File:** `{output_folder}/empathy-map-{user-name}-{date}.md`
+
+### 4. Validation Questions
+
+Before we finalize, let's validate:
+
+**Evidence Check:**
+- [ ] Is every insight backed by research (quotes, observations, data)?
+- [ ] Did we avoid speculation and assumptions?
+- [ ] Can we trace each insight back to a specific source?
+
+**Specificity Check:**
+- [ ] Is the target user definition specific enough?
+- [ ] Are pain points concrete and actionable?
+- [ ] Are gains measurable?
+
+**Actionability Check:**
+- [ ] Can designers use this to inform wireframes?
+- [ ] Can product managers use this to prioritize features?
+- [ ] Can developers use this to understand user context?
+
+**Completeness Check:**
+- [ ] Did we capture both positive and negative aspects?
+- [ ] Did we explore emotions, not just behaviors?
+- [ ] Did we understand the WHY, not just the WHAT?
+
+---
+
+## Your Turn
+
+Please review all your insights and identify 3-5 key patterns or surprises that emerged.
+
+Then confirm you're ready for me to generate the final empathy map artifact.
+
+## Output
+
+Once you confirm, I'll create:
+
+**File:** `{output_folder}/empathy-map-{user-name}-{date}.md`
+
+**Contents:**
+- Executive Summary (key insights)
+- Target User Profile
+- Says & Thinks
+- Does & Feels
+- Pain Points (prioritized)
+- Desired Gains (prioritized)
+- Design Implications
+- Research Sources
+
+---
+
+## Vortex Compass
+
+Based on what you just completed, here are your evidence-driven options:
+
+| If you learned... | Consider next... | Agent | Why |
+|---|---|---|---|
+| Multiple artifacts ready for synthesis | research-convergence | Mila 🔬 | Converge empathy findings into problem definition (HC1) |
+| Pain points need validation | lean-experiment | Wade 🧪 | Test if pain points drive real behavior |
+| Deeper understanding needed | user-interview | Isla 🔍 | Follow up with targeted interviews |
+
+> **Note:** These are evidence-based recommendations. You can navigate to any Vortex agent
+> at any time based on your judgment.
+
+**Or run Max's [VN] Vortex Navigation** for a full gap analysis across all streams.