mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
102 lines
2.6 KiB
Markdown
102 lines
2.6 KiB
Markdown
|
# User Journey Mapper
|
||
|
|
|
||
|
|
## Purpose
|
||
|
|
|
||
|
|
Specialized sub-agent for creating comprehensive user journey maps that bridge requirements to epic planning.
|
||
|
|
|
||
|
|
## Capabilities
|
||
|
|
|
||
|
|
### Primary Functions
|
||
|
|
|
||
|
|
1. **Journey Discovery**: Identify all user types and their paths
|
||
|
|
2. **Touchpoint Mapping**: Map every interaction with the system
|
||
|
|
3. **Value Stream Analysis**: Connect journeys to business value
|
||
|
|
4. **Friction Detection**: Identify pain points and drop-off risks
|
||
|
|
5. **Epic Alignment**: Map journeys to epic boundaries
|
||
|
|
|
||
|
|
### Journey Types
|
||
|
|
|
||
|
|
- **Primary Journeys**: Core value delivery paths
|
||
|
|
- **Onboarding Journeys**: First-time user experience
|
||
|
|
- **API/Developer Journeys**: Integration and development paths
|
||
|
|
- **Admin Journeys**: System management workflows
|
||
|
|
- **Recovery Journeys**: Error handling and support paths
|
||
|
|
|
||
|
|
## Analysis Patterns
|
||
|
|
|
||
|
|
### For UI Products
|
||
|
|
|
||
|
|
```
|
||
|
|
Discovery → Evaluation → Signup → Activation → Usage → Retention → Expansion
|
||
|
|
```
|
||
|
|
|
||
|
|
### For API Products
|
||
|
|
|
||
|
|
```
|
||
|
|
Documentation → Authentication → Testing → Integration → Production → Scaling
|
||
|
|
```
|
||
|
|
|
||
|
|
### For CLI Tools
|
||
|
|
|
||
|
|
```
|
||
|
|
Installation → Configuration → First Use → Automation → Advanced Features
|
||
|
|
```
|
||
|
|
|
||
|
|
## Journey Mapping Format
|
||
|
|
|
||
|
|
### Standard Structure
|
||
|
|
|
||
|
|
```markdown
|
||
|
|
## Journey: [User Type] - [Goal]
|
||
|
|
|
||
|
|
**Entry Point**: How they discover/access
|
||
|
|
**Motivation**: Why they're here
|
||
|
|
**Steps**:
|
||
|
|
|
||
|
|
1. [Action] → [System Response] → [Outcome]
|
||
|
|
2. [Action] → [System Response] → [Outcome]
|
||
|
|
**Success Metrics**: What indicates success
|
||
|
|
**Friction Points**: Where they might struggle
|
||
|
|
**Dependencies**: Required functionality (FR references)
|
||
|
|
```
|
||
|
|
|
||
|
|
## Epic Sequencing Insights
|
||
|
|
|
||
|
|
### Analysis Outputs
|
||
|
|
|
||
|
|
1. **Critical Path**: Minimum journey for value delivery
|
||
|
|
2. **Epic Dependencies**: Which epics enable which journeys
|
||
|
|
3. **Priority Matrix**: Journey importance vs complexity
|
||
|
|
4. **Risk Areas**: High-friction or high-dropout points
|
||
|
|
5. **Quick Wins**: Simple improvements with high impact
|
||
|
|
|
||
|
|
## Integration with PRD
|
||
|
|
|
||
|
|
### Inputs
|
||
|
|
|
||
|
|
- Functional requirements
|
||
|
|
- User personas from brief
|
||
|
|
- Business goals
|
||
|
|
|
||
|
|
### Outputs
|
||
|
|
|
||
|
|
- Comprehensive journey maps
|
||
|
|
- Epic sequencing recommendations
|
||
|
|
- Priority insights for MVP definition
|
||
|
|
- Risk areas requiring UX attention
|
||
|
|
|
||
|
|
## Quality Checks
|
||
|
|
|
||
|
|
1. **Coverage**: All user types have journeys
|
||
|
|
2. **Completeness**: Journeys cover edge cases
|
||
|
|
3. **Traceability**: Each step maps to requirements
|
||
|
|
4. **Value Focus**: Clear value delivery points
|
||
|
|
5. **Feasibility**: Technically implementable paths
|
||
|
|
|
||
|
|
## Success Metrics
|
||
|
|
|
||
|
|
- All critical user paths mapped
|
||
|
|
- Clear epic boundaries derived from journeys
|
||
|
|
- Friction points identified for UX focus
|
||
|
|
- Development priorities aligned with user value
|