@c0x12c/ai-toolkit 1.15.0

package/frameworks/02-design-sprint.md

@@ -0,0 +1,304 @@
+# Design Sprint Framework
+
+## Overview
+The Design Sprint is a 5-day process developed at Google Ventures (now GV) by Jake Knapp. It's designed to answer critical business questions through rapid prototyping and user testing. The sprint compresses months of work into a single week, helping teams shortcut the endless debate cycle and validate ideas with real users.
+
+## When to Use
+- Kick off a new product or feature
+- When facing a critical business challenge
+- Need to make a major decision quickly
+- Want to explore new opportunities
+- Before investing significant resources
+- When team alignment is needed
+
+## The 5-Day Process
+
+### Monday: Map & Target
+**Goal**: Understand the problem and pick a target
+
+**Activities**:
+1. **Start at the End**: Define long-term goal and sprint questions
+2. **Map**: Create a simple map of the customer journey
+3. **Ask the Experts**: Interview stakeholders and experts
+4. **Target**: Choose a specific target customer and moment to focus on
+
+**Key Outputs**:
+- Long-term goal
+- Sprint questions
+- Customer journey map
+- Target for the sprint
+
+**Time Breakdown**:
+- 10am: Introductions and sprint overview
+- 10:30am: Long-term goal
+- 11:30am: Sprint questions
+- 1pm: Map
+- 2pm: Ask the Experts
+- 4pm: Target
+
+### Tuesday: Sketch
+**Goal**: Generate solutions
+
+**Activities**:
+1. **Lightning Demos**: Look at existing solutions for inspiration
+2. **Divide or Swarm**: Choose to work on one piece or all together
+3. **Four-Step Sketch**:
+   - Notes (20 min)
+   - Ideas (20 min)
+   - Crazy 8s (8 min)
+   - Solution sketch (30-90 min)
+
+**Key Outputs**:
+- Collection of solution sketches
+- Detailed storyboards from each team member
+
+**Time Breakdown**:
+- 10am: Lightning Demos
+- 12pm: Divide or Swarm
+- 1pm: Four-step sketch begins
+- 4pm: Solution sketches complete
+
+### Wednesday: Decide
+**Goal**: Choose the best solutions and create a storyboard
+
+**Activities**:
+1. **Art Museum**: Display all solutions
+2. **Heat Map**: Silent voting on interesting parts
+3. **Speed Critique**: Quick discussion of highlights
+4. **Straw Poll**: Everyone picks their favorite
+5. **Supervote**: Decider makes final choice
+6. **Storyboard**: Create step-by-step plan for prototype
+
+**Key Outputs**:
+- Winning solution(s)
+- Detailed storyboard for prototype
+
+**Time Breakdown**:
+- 10am: Sticky Decision
+- 11:30am: Speed Critique
+- 1pm: Straw Poll
+- 1:30pm: Supervote
+- 2pm: Storyboard
+
+### Thursday: Prototype
+**Goal**: Build a realistic prototype
+
+**Activities**:
+1. **Assign Roles**:
+   - Maker(s): Build the prototype
+   - Stitcher: Ensure consistency
+   - Writer: Create realistic copy
+   - Asset Collector: Gather needed materials
+   - Interviewer: Prepare for Friday's tests
+2. **Build the Prototype**: Focus on the customer-facing surface
+3. **Stitch it Together**: Make sure everything flows
+4. **Trial Run**: Test internally
+
+**Key Outputs**:
+- Realistic prototype
+- Interview script
+- Testing logistics confirmed
+
+**Tools Often Used**:
+- Figma/Sketch (design)
+- InVision/Marvel (clickable prototypes)
+- Keynote/PowerPoint (quick and dirty)
+- Squarespace/Webflow (landing pages)
+
+### Friday: Test
+**Goal**: Learn from target customers
+
+**Activities**:
+1. **Interviews**: 5 one-on-one interviews
+2. **Observe**: Watch customers use the prototype
+3. **Take Notes**: Capture reactions and feedback
+4. **Learn Together**: Identify patterns
+5. **Next Steps**: Decide what to do next
+
+**Key Outputs**:
+- Customer feedback patterns
+- Validated/invalidated assumptions
+- Clear next steps
+
+**Interview Schedule**:
+- 9am: Interview #1
+- 10am: Interview #2
+- 11am: Interview #3
+- 1pm: Interview #4
+- 2pm: Interview #5
+- 3pm: Debrief
+
+## Key Roles
+
+### Decider
+- CEO, product manager, or whoever has decision authority
+- Makes final calls when team is stuck
+- Commits to sprint outcomes
+
+### Facilitator
+- Runs the sprint process
+- Keeps team on track
+- Manages time and energy
+
+### Team Members (5-7 total)
+- Designer
+- Engineer/Developer
+- Product Manager
+- Marketing
+- Customer Service
+- Finance (if relevant)
+
+## Essential Supplies
+
+### Physical
+- Whiteboards (lots of them)
+- Sticky notes (various colors)
+- Markers (thick and thin)
+- Dot stickers (for voting)
+- Timer
+- Snacks and coffee
+
+### Digital
+- Prototyping tools
+- Video conferencing (for remote)
+- Digital whiteboard tools (Miro, Figma)
+- Calendar blocking
+
+## Sprint Questions Examples
+
+Good sprint questions help focus the week:
+- "Will customers understand our value proposition?"
+- "Can we simplify the onboarding process?"
+- "Will enterprise customers pay for this feature?"
+- "Can we make this 10x better than competitors?"
+
+## Common Variations
+
+### Design Sprint 2.0
+- Shortened to 4 days
+- Monday activities condensed
+- More emphasis on recruiting users early
+
+### Remote Design Sprint
+- All activities adapted for video conferencing
+- Digital collaboration tools
+- Asynchronous elements where possible
+
+### Enterprise Design Sprint
+- Extended timeline (2-3 weeks)
+- More stakeholders involved
+- Additional validation rounds
+
+## Best Practices
+
+### Before the Sprint
+1. **Get buy-in**: Ensure leadership support
+2. **Clear calendars**: No other meetings
+3. **Recruit users**: Start early (2 weeks before)
+4. **Prepare space**: Dedicate a war room
+5. **Set expectations**: This is about learning, not perfection
+
+### During the Sprint
+1. **No devices**: Laptops closed except when needed
+2. **Time box everything**: Stick to the schedule
+3. **Defer discussions**: Use a "parking lot"
+4. **Trust the process**: Even when skeptical
+5. **Document everything**: Photos, notes, recordings
+
+### After the Sprint
+1. **Share results immediately**: Strike while iron is hot
+2. **Plan next steps**: Don't lose momentum
+3. **Archive materials**: Future reference
+4. **Celebrate**: Acknowledge the team effort
+
+## Common Mistakes
+
+1. **Wrong challenge**: Picking something too big or too small
+2. **Missing decider**: No authority to implement results
+3. **Too many people**: More than 7 slows progress
+4. **Skipping steps**: Each day builds on the previous
+5. **Perfect prototype**: Good enough beats perfect
+6. **Wrong test users**: Must match target customer
+7. **Leading questions**: Let users show you
+8. **Ignoring results**: Must act on learnings
+
+## Measuring Success
+
+Success isn't just a validated prototype:
+- **Team alignment**: Everyone understands the direction
+- **Fast learning**: Months of debates resolved in days
+- **Clear next steps**: Know exactly what to do
+- **Risk reduction**: Avoided costly mistakes
+- **Energy boost**: Team excited about path forward
+
+## Tools and Resources
+
+### Books
+- "Sprint" by Jake Knapp
+- "Design Sprint" by Richard Banfield
+
+### Online Resources
+- designsprintkit.withgoogle.com
+- sprintstories.com
+- ajsmart.com/design-sprint
+
+### Software
+- Figma (collaborative design)
+- Miro (digital whiteboard)
+- Calendly (user recruiting)
+- Zoom (remote testing)
+
+## When NOT to Use Design Sprint
+
+- Problem is already well-understood
+- Solution is obvious or mandated
+- Can't get the right people
+- No budget/authority to implement
+- Timeline doesn't allow for it
+
+## Design Sprint vs Other Methods
+
+### vs Lean Startup
+- Design Sprint: 5 days, high fidelity prototype
+- Lean Startup: Ongoing, multiple experiments
+
+### vs Agile
+- Design Sprint: Upfront validation
+- Agile: Iterative development
+
+### vs Design Thinking
+- Design Sprint: Time-boxed, specific process
+- Design Thinking: Flexible, longer timeline
+
+## Real-World Examples
+
+### Slack
+Used design sprints to redesign onboarding, resulting in 30% improvement in activation.
+
+### Uber
+Validated new driver app features before development.
+
+### Blue Bottle Coffee
+Tested online subscription service concept.
+
+### KLM
+Improved booking flow, increasing conversions by 25%.
+
+## Modified Sprint Formats
+
+### 3-Day Sprint
+- Day 1: Map and Sketch
+- Day 2: Decide and Prototype
+- Day 3: Test
+
+### Concept Sprint
+- Focus on exploring multiple concepts
+- Less emphasis on detailed prototype
+- More breadth, less depth
+
+### Validation Sprint
+- Start with existing prototype
+- Focus entirely on testing variations
+- Iterate based on feedback
+
+The Design Sprint is powerful because it compresses time, focuses effort, and delivers clear results. It's not right for every situation, but when you need to move fast and reduce risk, it's one of the best tools available.

package/frameworks/03-foundation-sprint.md

@@ -0,0 +1,337 @@
+# Foundation Sprint Framework
+
+## Overview
+The Foundation Sprint is a collaborative workshop process designed to align teams on product vision, strategy, and roadmap before diving into development. Created by the team at Voltage Control, it focuses on establishing a solid foundation for product development by ensuring all stakeholders share a common understanding of the problem space, target users, and success metrics.
+
+## When to Use
+- Starting a new product or major initiative
+- When team lacks alignment on product direction
+- Before significant investment in development
+- When multiple stakeholders have different visions
+- Establishing product strategy and roadmap
+- Creating shared mental models across teams
+
+## Core Components
+
+### Duration
+Typically 2-5 days, depending on complexity and team size
+
+### Key Principles
+1. **Diverge then Converge**: Explore many options before narrowing
+2. **Inclusive Participation**: All voices matter
+3. **Visual Thinking**: Make abstract concepts concrete
+4. **Bias Toward Action**: Move from talk to tangible outputs
+5. **Shared Understanding**: Align on fundamentals
+
+## The Foundation Sprint Process
+
+### Pre-Sprint Preparation
+1. **Stakeholder Interviews**: Understand different perspectives
+2. **Research Synthesis**: Compile existing knowledge
+3. **Participant Selection**: Ensure right people in room
+4. **Logistics Planning**: Space, materials, schedule
+5. **Pre-work Assignment**: Background reading/research
+
+### Day 1: Discover & Define
+
+#### Morning: Problem Space
+- **Welcome & Introductions**: Set collaborative tone
+- **Sprint Goals**: What success looks like
+- **Problem Statement Workshop**: Define the core problem
+- **Stakeholder Mapping**: Identify all affected parties
+- **Current State Journey Mapping**: How things work today
+
+#### Afternoon: User Understanding
+- **Persona Development**: Create detailed user profiles
+- **Empathy Mapping**: Understand user thoughts/feelings
+- **Jobs to be Done**: What users are trying to accomplish
+- **Pain Points Prioritization**: Rank biggest frustrations
+
+### Day 2: Envision & Explore
+
+#### Morning: Solution Space
+- **Vision Statement**: Craft inspiring future state
+- **Success Metrics Definition**: How we'll measure progress
+- **Competitive Landscape**: What others are doing
+- **Capability Assessment**: What we can build on
+
+#### Afternoon: Ideation
+- **How Might We**: Reframe problems as opportunities
+- **Crazy 8s**: Rapid idea generation
+- **Solution Sketching**: Detailed concept development
+- **Concept Clustering**: Group similar ideas
+
+### Day 3: Prioritize & Plan
+
+#### Morning: Decision Making
+- **Concept Presentation**: Share developed ideas
+- **Assumption Mapping**: What we believe vs know
+- **Risk Assessment**: Identify biggest uncertainties
+- **Prioritization Matrix**: Effort vs impact analysis
+
+#### Afternoon: Roadmapping
+- **MVP Definition**: Minimum viable product scope
+- **Feature Prioritization**: Must-have vs nice-to-have
+- **Timeline Development**: Realistic phases
+- **Resource Planning**: What we need to succeed
+
+### Day 4: Validate & Refine (Optional)
+
+#### Morning: Testing Prep
+- **Prototype Planning**: What to test
+- **Research Questions**: What we need to learn
+- **Participant Recruiting**: Find target users
+
+#### Afternoon: User Feedback
+- **Concept Testing**: Share ideas with users
+- **Feedback Synthesis**: Identify patterns
+- **Iteration Planning**: How to improve
+
+### Day 5: Align & Commit (Optional)
+
+#### Morning: Final Refinements
+- **Incorporate Feedback**: Update based on learning
+- **Final Presentations**: Polished concepts
+- **Decision Time**: Go/no-go/pivot
+
+#### Afternoon: Next Steps
+- **Action Planning**: Who does what when
+- **Communication Plan**: How to share outcomes
+- **Success Criteria**: Clear definition of done
+- **Team Charter**: Working agreements
+
+## Key Deliverables
+
+### Strategic Outputs
+1. **Product Vision Statement**: Clear, inspiring direction
+2. **Problem Statement**: Well-defined challenge
+3. **Success Metrics**: Measurable goals
+4. **Strategic Priorities**: What matters most
+
+### Tactical Outputs
+1. **User Personas**: Detailed target profiles
+2. **Journey Maps**: Current and future state
+3. **Feature Roadmap**: Phased development plan
+4. **MVP Scope**: First release definition
+
+### Team Outputs
+1. **Shared Vocabulary**: Common language
+2. **Aligned Understanding**: Same mental models
+3. **Team Charter**: How we work together
+4. **Decision Framework**: How choices get made
+
+## Facilitation Techniques
+
+### Divergent Thinking Tools
+- **Brainstorming**: Classic idea generation
+- **Mind Mapping**: Visual exploration
+- **SCAMPER**: Systematic creativity
+- **Six Thinking Hats**: Different perspectives
+
+### Convergent Thinking Tools
+- **Dot Voting**: Democratic prioritization
+- **MoSCoW**: Must/Should/Could/Won't
+- **Impact/Effort Matrix**: Strategic prioritization
+- **Paired Comparison**: Systematic ranking
+
+### Visual Tools
+- **Storyboarding**: Narrative sequences
+- **Service Blueprints**: System visualization
+- **Concept Models**: Abstract relationships
+- **Wireframing**: Basic interfaces
+
+## Roles and Responsibilities
+
+### Facilitator
+- Guide process
+- Manage time and energy
+- Ensure participation
+- Synthesize outputs
+
+### Product Owner/Sponsor
+- Provide vision
+- Make key decisions
+- Remove blockers
+- Champion outcomes
+
+### Core Team Members
+- Active participation
+- Domain expertise
+- Creative input
+- Commitment to outcomes
+
+### Subject Matter Experts
+- Specific knowledge
+- Reality checks
+- Technical feasibility
+- Constraint awareness
+
+## Common Variations
+
+### Mini Foundation Sprint (1-2 days)
+- Compressed timeline
+- Focus on critical elements
+- Smaller team
+- Clear constraints
+
+### Extended Foundation Sprint (1-2 weeks)
+- More research integration
+- Multiple stakeholder groups
+- Complex products
+- Detailed planning
+
+### Remote Foundation Sprint
+- Digital collaboration tools
+- Asynchronous elements
+- Shorter sessions
+- More breaks
+
+## Success Factors
+
+### Before the Sprint
+1. **Leadership Buy-in**: Commitment to outcomes
+2. **Right Participants**: Decision makers present
+3. **Clear Scope**: Bounded problem space
+4. **Research Ready**: Background information available
+
+### During the Sprint
+1. **Full Participation**: No multitasking
+2. **Open Communication**: Psychological safety
+3. **Visual Documentation**: Capture everything
+4. **Time Management**: Stay on schedule
+
+### After the Sprint
+1. **Quick Follow-through**: Maintain momentum
+2. **Broad Communication**: Share outcomes
+3. **Regular Check-ins**: Track progress
+4. **Iteration Cycles**: Refine as you learn
+
+## Common Pitfalls
+
+1. **Too Broad Scope**: Trying to solve everything
+2. **Missing Stakeholders**: Key voices absent
+3. **Rushing Process**: Not allowing divergence
+4. **Analysis Paralysis**: Over-thinking decisions
+5. **Poor Follow-through**: Losing momentum after
+6. **Skipping Research**: Not grounding in reality
+7. **Dominating Voices**: Loudest person wins
+
+## Measuring Success
+
+### Short-term Indicators
+- Team alignment score
+- Clarity of outputs
+- Stakeholder satisfaction
+- Actionable next steps
+
+### Long-term Indicators
+- Product success metrics
+- Team velocity
+- Reduced pivots/rework
+- Time to market
+
+## Integration with Other Methods
+
+### With Design Sprint
+- Foundation Sprint first for strategy
+- Design Sprint for specific features
+- Complementary approaches
+
+### With Lean Canvas
+- Use canvas as input/output
+- Foundation Sprint adds depth
+- More collaborative process
+
+### With Agile Development
+- Foundation Sprint sets vision
+- Agile executes iteratively
+- Regular realignment
+
+## Tools and Resources
+
+### Physical Tools
+- Wall space/whiteboards
+- Sticky notes (lots!)
+- Markers and pens
+- Dot stickers
+- Timer
+- Camera
+
+### Digital Tools
+- Miro/Mural (virtual whiteboard)
+- Figma (collaborative design)
+- Notion (documentation)
+- Zoom (remote facilitation)
+
+### Templates
+- Journey map templates
+- Persona templates
+- Roadmap templates
+- Vision canvas
+
+## Real-World Applications
+
+### Startup Examples
+- **Early Stage**: Define product direction
+- **Pivot Point**: Realign on new direction
+- **Scale Phase**: Align growing team
+
+### Enterprise Examples
+- **Innovation Projects**: New venture development
+- **Digital Transformation**: Modernization efforts
+- **Cross-functional Initiatives**: Break down silos
+
+### Non-profit Examples
+- **Program Development**: New initiative planning
+- **Strategic Planning**: Organization direction
+- **Stakeholder Alignment**: Board and staff unity
+
+## Customization Guidelines
+
+### By Industry
+- **B2B Software**: Focus on workflow and ROI
+- **Consumer Apps**: Emphasize user delight
+- **Healthcare**: Include compliance/safety
+- **Education**: Consider all stakeholders
+
+### By Stage
+- **Idea Stage**: Heavy on exploration
+- **Growth Stage**: Focus on optimization
+- **Enterprise**: Include change management
+
+### By Team
+- **Small Teams**: More informal, faster
+- **Large Teams**: More structure needed
+- **Distributed Teams**: Async elements
+
+## Facilitator Tips
+
+1. **Energy Management**: Plan breaks and energizers
+2. **Inclusive Techniques**: Draw out quiet voices
+3. **Visual Preference**: Make everything visible
+4. **Parking Lot**: Capture off-topic items
+5. **Flexibility**: Adapt to team needs
+6. **Documentation**: Photograph everything
+7. **Time Boxing**: Keep things moving
+
+## Next Steps After Sprint
+
+### Immediate (Week 1)
+- Compile all outputs
+- Share with stakeholders
+- Schedule follow-ups
+- Begin quick wins
+
+### Short-term (Month 1)
+- Execute on roadmap
+- Test key assumptions
+- Regular check-ins
+- Iterate based on learning
+
+### Long-term (Quarterly)
+- Measure against success metrics
+- Reassess priorities
+- Team retrospectives
+- Plan next foundation work
+
+The Foundation Sprint provides the strategic clarity and team alignment necessary for successful product development. By investing time upfront to build shared understanding, teams can move faster and with more confidence throughout the development process.