6.0 KiB
name, description, nextStepFile, activityWorkflowFile
| name | description | nextStepFile | activityWorkflowFile |
|---|---|---|---|
| step-00c-target-groups-extract | Extract and deepen target group definitions from existing documentation | ./step-00d-driving-forces-extract.md | ../workflow.md |
Step 3: Target Groups Extraction
STEP GOAL:
Extract, validate, and deepen target group definitions and personas from the user's existing documentation, transforming demographic descriptions into behavioral profiles with psychological depth.
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 - building empathy through understanding from existing documentation
- ✅ 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 extracting and deepening target group definitions from documentation
- 🚫 FORBIDDEN to accept demographic-only descriptions without adding behavioral depth
- 💬 Approach: Frame as validation - "Your material suggests X, is this correct?"
- 📋 Documentation may have demographics but need behavioral depth - probe for it
- 📋 Help prioritize to 3-4 groups maximum
EXECUTION PROTOCOLS:
- 🎯 Analyze documentation for target groups and user research
- 💾 Store validated target_groups and personas
- 📖 Transform demographic descriptions into behavioral profiles
- 🚫 Do not proceed until personas have psychological depth
CONTEXT BOUNDARIES:
- Available context: User's documentation, validated vision and objectives from step-00b
- Focus: Target group identification, persona creation with behavioral/psychological depth
- Limits: Maximum 3-4 target groups - help prioritize if more exist
- Dependencies: Requires completed step-00b with confirmed vision and objectives
Sequence of Instructions (Do not deviate, skip, or optimize)
1. Extract Target Groups
Analyze documentation for target groups and user research.
If target groups found: Present extracted groups with their characteristics. Ask if these are the right groups and suggest focusing on top 3-4 most critical for objectives. Help prioritize.
If demographic-only groups found: Present the demographic descriptions but explain that for Trigger Mapping, behavioral profiles are needed. Ask about each group's context and situation when using the product, and what they are trying to accomplish.
Transform demographic descriptions into behavioral profiles through conversation.
If no target groups found: Present inferred groups based on context and objectives. Ask: "Who are the 3-4 key user groups whose product usage will drive your objectives? Remember the core question: WHO out there in the world will make sure, with their use of the product, that you achieve your goals?"
Define target groups through conversation.
Store target_groups.
2. Create Detailed Personas
For each target group, check documentation for:
- Context and situation
- Goals and aspirations
- Frustrations and fears
- Behavioral patterns
- User quotes or interview insights
If deep personas found: Present personas with context, goals, frustrations, and any research quotes. Ask if they capture the psychological depth needed and request refinements.
If shallow personas found: Present basic descriptions and explain more psychological depth is needed. Ask for each persona: context when using product, what they are trying to accomplish (usage goals), what frustrates them, and what they fear or want to avoid.
Build psychological depth through conversation.
If interview quotes available: Incorporate quotes to enrich persona descriptions.
Store personas.
3. Present Workshop 2 Summary
Output: "Workshop 2 Complete!
Target Groups (Prioritized): {{#each prioritized_groups}} {{@index + 1}}. {{this.name}} {{/each}}
Next, we'll map what drives each group psychologically."
4. Present MENU OPTIONS
Display: "Select an Option: [C] Continue to Driving Forces Extraction | [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. Target groups and personas must have behavioral and psychological depth before proceeding.
🚨 SYSTEM SUCCESS/FAILURE METRICS
✅ SUCCESS:
- Target groups extracted or identified through dialogue
- Groups prioritized to 3-4 maximum
- Personas created with behavioral profiles (not just demographics)
- Psychological depth added: context, goals, frustrations, fears
- User quotes incorporated where available
- User confirmed target groups and personas
- Results stored for subsequent steps
❌ SYSTEM FAILURE:
- Accepting demographic-only descriptions without behavioral depth
- Having more than 4 target groups without prioritizing
- Not validating extracted groups with user
- Missing psychological depth in personas
- Proceeding without confirmed target_groups and personas
- Not asking about context, goals, frustrations, and fears
Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.