bi-agents/_bmad/wds/workflows/2-trigger-mapping/data/key-insights-structure.md

Key Insights Document Structure Guide

Complete template for generating 05-Key-Insights.md

---

1. Header

# Key Insights & Strategic Implications

> How the Trigger Map informs design and development decisions

**Document:** Trigger Map - Key Insights
**Created:** [Date]
**Status:** COMPLETE

---

2. The Flywheel Section

## The Flywheel: [X] [Champions] Drive Everything

**THE ENGINE (Priority #1):**
- [X] [champions] are THE PRIMARY GOAL
- Timeline: [X] months
- These [description of what makes them champions]
- They create the flywheel that drives ALL other objectives

**[Product] Adoption (Priority #2):**
- Driven BY the [X] [champions] spreading the word
- [List key adoption targets with numbers]
- Timeline: [X] months
- Focus: [What this tier achieves]

**Community Opportunities (Priority #3):**
- Real-world benefits FOR community members
- [List key opportunities]
- Timeline: [X] months
- **Key benefit**: [How members' lives/careers improve]

---

3. Primary Development Focus

## Primary Development Focus

1. **Create Awesome [Users] Who Become [Champions]** - [Primary persona] is the profile who becomes one of the [X]
2. **[Key Transformation Need]** - Address [primary persona]'s core need to move from [before] to [after]
3. **[Core Capability Building]** - [Specific approach to building confidence/skill]
4. **[Validation Need]** - Show [secondary persona] how [product] delivers [value]
5. **[Support Need]** - Prove to [tertiary persona] that [benefit] reduces [pain]

---

4. Critical Success Factors

## Critical Success Factors

- **[Factor 1]**: [Description] (the [key element] in action)
- **[Factor 2]**: [Clear steps description]
- **[Factor 3]**: [Proof element] ([specific example])
- **[Factor 4]**: [Access description]
- **[Factor 5]**: [Scope description] (not just [limitation])

---

5. Design Implications

## Design Implications

### Content Priorities Based on Triggers:

**[Section 1] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 2] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 3] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 4] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 5] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

---

6. Emotional Transformation Goals

## Emotional Transformation Goals

- **[Goal 1]**: "[First-person statement of transformation]"
- **[Goal 2]**: "[First-person statement about capability]"
- **[Goal 3]**: "[First-person statement about confidence]"
- **[Goal 4]**: "[First-person statement about impact]"
- **[Goal 5]**: "[First-person statement about identity]"

---

7. Design Focus Statement

## Design Focus Statement

**The [Product] [Page/Experience] transforms [target users] from [before state] into [after state] who [key transformation] as a [metaphor], not a [negative metaphor].**

**Primary Design Target:** [Primary Persona Name] ([Role])

**Must Address (Critical for Conversion):**
1. [Fear 1] → [Solution approach]
2. [Fear 2] → [Solution approach]
3. [Fear 3] → [Solution approach]
4. [Want 1] → [Delivery approach]
5. [Want 2] → [Delivery approach]

**Should Address (Supporting Conversion):**
1. [Secondary persona] needs [thing] → [Approach]
2. [Tertiary persona] needs [thing] → [Approach]
3. [Community proof element] → [Approach]
4. [Learning curve concern] → [Approach]
5. [Integration concern] → [Approach]

---

8. Development Phases

## Development Phases

### **First Deliverable: [Product Name] [Initial Release]**
Focus on empowering [primary persona] from [before] to awesome [after] who naturally becomes [champion]:
- **[Section 1]** - [Key message/approach]
- **[Section 2]** - [Key message/approach]
- **[Section 3]** - [Key message/approach]
- **[Section 4]** - [Key message/approach]
- **[Section 5]** - [Key message/approach]
- **[Section 6]** - [Key message/approach]
- **[Section 7]** - [Key message/approach]

### **Future Phases: Additional Content**
- **Phase 2**: [Next priority]
- **Phase 3**: [Next priority]
- **Phase 4**: [Next priority]
- **Phase 5**: [Next priority]

---

9. Related Documents Footer

## Related Documents

- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
- **[01-Business-Goals.md](01-Business-Goals.md)** - Objectives and metrics
- **[02-[Primary].md](02-[Primary].md)** - Primary persona
- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
- **[06-Design-Implications.md](06-Design-Implications.md)** - Detailed design requirements [if exists]

---

_Back to [Trigger Map](00-trigger-map.md)_

---

Template Guidelines

Tone:

• Actionable and specific
• "Create awesome" language throughout
• Links back to workshop outputs

Focus:

• PRIMARY persona gets most attention in "Must Address"
• Secondary and tertiary get "Should Address"
• Transformation is central theme

Design Implications:

• Organized by page/experience sections
• Each section has clear "must do" items
• Tied to specific fears/wants from personas

Emotional Goals:

• First-person statements
• Show identity shift
• Positive and empowering

Expected Length:

• ~145-150 lines for complete document
• Use specific examples from trigger map
• Keep actionable and scannable

---

Complete structure guide for Step 04: Generate Key Insights