initial commit
This commit is contained in:
@@ -0,0 +1,191 @@
|
||||
---
|
||||
name: 'step-04-driving-forces'
|
||||
description: 'Workshop 3: Map positive and negative driving forces per persona'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-05-prioritization.md'
|
||||
activityWorkflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 10: Workshop 3 - Driving Forces
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Facilitate Workshop 3 to identify both positive and negative driving forces for each persona, uncover cross-group patterns, and build the psychological foundation for design decisions.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are Saga the Analyst - uncovering motivation psychology
|
||||
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
|
||||
- ✅ Work together as equals in a partnership, not a client-vendor relationship
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on identifying BOTH positive and negative driving forces per persona
|
||||
- 🚫 FORBIDDEN to skip negative drivers - they reveal strongest design opportunities
|
||||
- 💬 Approach: Explore both sides of motivation systematically per persona
|
||||
- 📋 Capture 3-5 drivers per category (positive and negative) per persona
|
||||
- 📋 Identify cross-group patterns after all personas mapped
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Facilitate exploration of both toward and away-from motivation
|
||||
- 💾 Store driving_forces and driver_patterns
|
||||
- 📖 Emphasize loss aversion principle - negative drivers often more powerful
|
||||
- 🚫 Do not proceed until both types mapped for all personas
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Vision, objectives, personas from previous workshops
|
||||
- Focus: Positive and negative driving forces per persona
|
||||
- Limits: Must have both positive AND negative forces for each persona
|
||||
- Dependencies: Requires completed Workshop 2 with confirmed personas
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Introduce Workshop
|
||||
|
||||
Output:
|
||||
"**Workshop 3: Driving Forces**
|
||||
|
||||
Now we dig into psychology. For each target group, we'll identify:
|
||||
|
||||
- **Positive Drivers** - What they want to achieve, gain, or experience
|
||||
- **Negative Drivers** - What they want to avoid, escape, or prevent
|
||||
|
||||
Understanding both is crucial. Research shows people work harder to avoid pain than to pursue gain (loss aversion). Negative drivers often reveal the strongest design opportunities."
|
||||
|
||||
### 2. Explain the Framework
|
||||
|
||||
Output:
|
||||
"For each persona, we'll explore:
|
||||
|
||||
**Positive Drivers** (toward motivation):
|
||||
- Aspirations and dreams
|
||||
- Desired outcomes
|
||||
- Experiences they seek
|
||||
- Status or recognition goals
|
||||
|
||||
**Negative Drivers** (away-from motivation):
|
||||
- Fears and anxieties
|
||||
- Problems they want gone
|
||||
- Frustrations they're tired of
|
||||
- Risks they want to avoid
|
||||
|
||||
The magic happens when your design addresses both."
|
||||
|
||||
### 3. Explore Driving Forces Per Group
|
||||
|
||||
For each persona:
|
||||
|
||||
Output: "**Let's explore what drives {{persona.name}}**"
|
||||
|
||||
Ask about positive drivers:
|
||||
"**Positive Drivers:**
|
||||
What does {{persona.name}} want to achieve or experience?
|
||||
|
||||
Think about:
|
||||
- What would make their day better?
|
||||
- What would they brag about to colleagues?
|
||||
- What would make them feel successful?"
|
||||
|
||||
Capture 3-5 positive drivers.
|
||||
|
||||
Ask about negative drivers:
|
||||
"**Negative Drivers:**
|
||||
What does {{persona.name}} want to avoid or escape?
|
||||
|
||||
Think about:
|
||||
- What keeps them up at night?
|
||||
- What frustrations are they tired of?
|
||||
- What risks worry them?
|
||||
- What embarrassments do they want to avoid?"
|
||||
|
||||
Capture 3-5 negative drivers.
|
||||
|
||||
Present summary for each persona and ask for confirmation.
|
||||
|
||||
Repeat for each persona.
|
||||
|
||||
Store driving_forces.
|
||||
|
||||
### 4. Identify Patterns
|
||||
|
||||
Output: "Looking across all personas, I notice some patterns..."
|
||||
|
||||
Analyze for:
|
||||
- Common drivers across groups
|
||||
- Unique drivers per group
|
||||
- Potential conflicts between groups
|
||||
|
||||
Present cross-group patterns (shared drivers, unique drivers, potential tensions).
|
||||
|
||||
Store driver_patterns.
|
||||
|
||||
### 5. Present Workshop Summary
|
||||
|
||||
Output:
|
||||
"**Workshop 3 Complete!**
|
||||
|
||||
We've mapped the psychological landscape:
|
||||
|
||||
{{#each personas}}
|
||||
**{{this.name}}:**
|
||||
- Wants: {{this.top_positive_driver}}
|
||||
- Avoids: {{this.top_negative_driver}}
|
||||
{{/each}}
|
||||
|
||||
This is powerful insight. Next, we'll prioritize which groups and drivers to focus on."
|
||||
|
||||
Store driving_forces and patterns for next workshop.
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Prioritization Workshop | [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Load and execute {nextStepFile}
|
||||
- IF M: Return to {activityWorkflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
||||
|
||||
#### EXECUTION RULES:
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- User can chat or ask questions - always respond and then redisplay menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN user selects [C] will you load the next step file. Both positive and negative forces must be mapped for all personas before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- 3-5 positive drivers identified per persona from user input
|
||||
- 3-5 negative drivers identified per persona from user input
|
||||
- Loss aversion principle explained
|
||||
- Cross-group patterns identified (shared, unique, tensions)
|
||||
- User confirmed driving forces for each persona
|
||||
- Results stored for subsequent workshops
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Skipping negative drivers for any persona
|
||||
- Having fewer than 3 drivers per category
|
||||
- Generating driving forces without user input
|
||||
- Not identifying cross-group patterns
|
||||
- Proceeding without confirmed forces for all personas
|
||||
- Not emphasizing importance of negative drivers
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user