ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/devKalla-Fordonscervice/_wds/workflows/8-ongoing-development/steps/step-8.8-iterate.md

9.9 KiB
Raw Blame History

Step 8.8: Iterate (Kaizen Never Stops)

Your Task

Use learnings from this cycle to identify and start the next improvement.

Before You Start

Ensure you have:

  • ✅ Completed step 8.7 (impact measured)
  • ✅ Impact report created
  • ✅ Learnings documented
  • ✅ Results shared with team

The Kaizen Philosophy

改善 (Kaizen) = Continuous Improvement

Ship → Monitor → Learn → Improve → Ship → Monitor → Learn...
                            ↑
                       You are here!

This cycle never stops!

Kaizen vs Kaikaku

Two approaches from Lean manufacturing:

Kaizen (改善) - What You're Doing Now

  • Small, incremental changes (1-2 weeks)
  • Low cost, low risk
  • Continuous, never stops
  • Phase 8: Ongoing Development

Kaikaku (改革) - Revolutionary Change

  • Large, radical changes (months)
  • High cost, high risk
  • One-time transformation
  • Phases 1-7: New Product Development

You're in Kaizen mode! Small improvements that compound over time.

See: src/core/resources/wds/glossary.md for full definitions

Review Your Learnings

From Impact Report

What did you learn?

# Learnings from DD-XXX

## What Worked

1. [Learning 1]
2. [Learning 2]
3. [Learning 3]

## What Didn't Work

1. [Learning 1]
2. [Learning 2]

## Patterns Emerging

1. [Pattern 1]
2. [Pattern 2]

## Hypotheses Validated

1. [Hypothesis 1]: ✅ Confirmed
2. [Hypothesis 2]: ❌ Rejected

## New Questions

1. [Question 1]
2. [Question 2]

Identify Next Opportunity

Three sources for next improvement:

1. Iterate on Current Update

If the update was partially successful:

# Next Iteration: DD-XXX Refinement

**Current Status:**

- Feature X usage: 58% (target: 60%)
- User feedback: "Guide too long"

**Next Improvement:**

- Shorten guide from 5 steps to 3 steps
- Add "Skip" button
- A/B test guide length

**Expected Impact:**

- Feature X usage: 58% → 65%
- User satisfaction: 4.3/5 → 4.7/5

**Effort:** 1 day
**Priority:** Medium

2. Apply Pattern to Similar Feature

If the update was successful:

# Next Opportunity: Apply Pattern to Feature Y

**Learning from DD-XXX:**
"Onboarding increases usage 4x for complex features"

**Similar Problem:**

- Feature Y usage: 20% (low)
- User feedback: "Don't understand Feature Y"
- Similar complexity to Feature X

**Proposed Solution:**
Apply same onboarding pattern to Feature Y

**Expected Impact:**

- Feature Y usage: 20% → 80% (4x increase)
- Based on DD-XXX results

**Effort:** 2 days
**Priority:** High

3. Address New Problem

From monitoring and feedback:

# Next Opportunity: New Problem Identified

**New Data:**

- Feature Z drop-off: 35% (increased from 20%)
- User feedback: "Feature Z is slow"
- Analytics: Load time 5 seconds (was 2 seconds)

**Root Cause:**
Recent update added heavy images, slowing load time

**Proposed Solution:**
Optimize images and implement lazy loading

**Expected Impact:**

- Load time: 5s → 2s
- Drop-off: 35% → 20%

**Effort:** 1 day
**Priority:** High

Prioritize Next Cycle

Use Kaizen prioritization:

Priority = Impact × Effort × Learning

Example prioritization:

# Kaizen Prioritization

## Option A: Refine DD-XXX

- Impact: Medium (58% → 65%)
- Effort: Low (1 day)
- Learning: Low (incremental)
- Priority: MEDIUM

## Option B: Apply to Feature Y

- Impact: High (20% → 80%)
- Effort: Low (2 days)
- Learning: High (validates pattern)
- Priority: HIGH ✅

## Option C: Fix Feature Z Performance

- Impact: Medium (35% → 20% drop-off)
- Effort: Low (1 day)
- Learning: Medium (performance optimization)
- Priority: MEDIUM

**Decision:** Start with Option B (highest priority)

Start Next Cycle

Return to Step 8.1 with your next opportunity:

[C] Return to step-8.1-identify-opportunity.md

Document the cycle:

# Kaizen Cycle Log

## Cycle 1: DD-001 Feature X Onboarding

- Started: 2024-12-09
- Completed: 2024-12-28
- Result: SUCCESS ✅
- Impact: 4x usage increase
- Learning: Onboarding matters for complex features

## Cycle 2: DD-002 Feature Y Onboarding

- Started: 2024-12-28
- Status: In Progress
- Goal: Apply validated pattern to similar feature
- Expected: 4x usage increase

The Kaizen Mindset

Small Changes Compound

Example trajectory:

Month 1:
- Cycle 1: Feature X onboarding (+40% usage)

Month 2:
- Cycle 2: Feature Y onboarding (+60% usage)
- Cycle 3: Feature Z performance (+15% retention)

Month 3:
- Cycle 4: Feature X refinement (+7% usage)
- Cycle 5: Onboarding component library (reusable)
- Cycle 6: Feature W onboarding (+50% usage)

Month 4:
- Cycle 7: Dashboard performance (+20% engagement)
- Cycle 8: Navigation improvements (+10% discoverability)
- Cycle 9: Error handling (+30% recovery rate)

Result after 4 months:
- 9 improvements shipped
- Product quality significantly improved
- User satisfaction increased
- Team learned continuously
- Competitive advantage built

Each cycle takes 1-2 weeks. Small changes compound!

Kaizen Principles to Remember

1. Focus on Process, Not Just Results

Bad:

  • "We need to increase usage!"
  • (Pressure, no learning)

Good:

  • "Let's understand why usage is low, test a hypothesis, measure impact, and learn."
  • (Process, continuous learning)

2. Eliminate Waste (Muda 無駄)

Types of waste in design:

  • Overproduction: Designing features nobody uses
  • Waiting: Blocked on approvals or development
  • Transportation: Handoff friction
  • Over-processing: Excessive polish on low-impact features
  • Inventory: Unshipped designs
  • Motion: Inefficient workflows
  • Defects: Bugs and rework

Kaizen eliminates waste through:

  • Small, focused improvements
  • Fast cycles (ship → learn → improve)
  • Continuous measurement
  • Learning from every cycle

3. Respect People and Their Insights

Listen to:

  • Users (feedback, behavior)
  • Developers (technical insights)
  • Support (pain points)
  • Stakeholders (business context)
  • Team (observations)

Everyone contributes to Kaizen!

4. Standardize, Then Improve

When you find a pattern that works:

  1. Document it

    # Pattern: Onboarding for Complex Features

**When to use:**

- Feature has low usage (<30%)
- User feedback indicates confusion
- Feature is complex or non-obvious

**How to implement:**

1. Inline tooltip explaining purpose
2. Step-by-step guide for first action
3. Success celebration
4. Help button for future reference

**Expected impact:**

- Usage increase: 3-4x
- Drop-off decrease: 50-70%
- Effort: 2-3 days

  2. Create reusable components

    D-Design-System/03-Atomic-Components/
├── Tooltips/Tooltip-Inline.md
├── Guides/Guide-Step.md
└── Celebrations/Celebration-Success.md

  3. Share with team

    • Document in shared knowledge
    • Train team on pattern
    • Apply consistently

  4. Improve the pattern

    • Learn from each application
    • Refine based on feedback
    • Evolve over time

Kaizen Metrics

Track your improvement velocity:

# Kaizen Metrics Dashboard

## This Quarter (Q1 2025)

**Cycles Completed:** 9
**Average Cycle Time:** 10 days
**Success Rate:** 78% (7/9 successful)

**Impact:**

- Feature usage improvements: 6 features (+40% avg)
- Performance improvements: 2 features (+15% avg)
- User satisfaction: 3.2/5 → 4.1/5 (+28%)

**Learnings:**

- 12 patterns documented
- 8 reusable components created
- 3 hypotheses validated

**Team Growth:**

- Designer: Faster iteration
- Developer: Better collaboration
- Product: Data-driven decisions

When to Pause Kaizen

Kaizen never stops, but you might pause for:

1. Major Strategic Shift

  • New product direction
  • Pivot or rebrand
  • Complete redesign needed

2. Team Capacity

  • Team overwhelmed
  • Need to catch up on backlog
  • Need to stabilize

3. Measurement Period

  • Waiting for data
  • Seasonal variations
  • External factors

But always return to Kaizen!

Completion

Phase 8 is complete when:

  • ✅ Improvement identified
  • ✅ Context gathered
  • ✅ Update designed
  • ✅ Delivery created
  • ✅ Handed off to BMad
  • ✅ Implementation validated
  • ✅ Impact measured
  • ✅ Next cycle started

But Phase 8 never truly ends - Kaizen is continuous!

Next Steps

You have two paths:

Path A: Continue Kaizen Cycle

[K] Return to step-8.1-identify-opportunity.md
    Start next improvement cycle

Path B: New Product Feature

[N] Return to Phase 4-5 (UX Design & Design System)
    Design new complete user flow
    Then Phase 6 (Design Deliveries)

The Big Picture

You've completed a full Kaizen cycle!

Phase 8.1: Identify Opportunity ✅
Phase 8.2: Gather Context ✅
Phase 8.3: Design Update ✅
Phase 8.4: Create Delivery ✅
Phase 8.5: Hand Off ✅
Phase 8.6: Validate ✅
Phase 8.7: Monitor Impact ✅
Phase 8.8: Iterate ✅ (you are here!)

→ Return to 8.1 and repeat!

Kaizen Success Story

Example: 6 months of Kaizen:

Starting Point:
- Product satisfaction: 3.2/5
- Feature usage: 25% average
- Support tickets: 50/month
- Churn rate: 15%

After 6 Months (24 Kaizen cycles):
- Product satisfaction: 4.3/5 (+34%)
- Feature usage: 65% average (+160%)
- Support tickets: 12/month (-76%)
- Churn rate: 6% (-60%)

Investment:
- 24 cycles × 1.5 weeks = 36 weeks
- Small, focused improvements
- Continuous learning
- Compounding results

Result:
- Product transformed
- Team learned continuously
- Competitive advantage built
- Users delighted

This is the power of Kaizen! 改善

Remember: Great products aren't built in one big redesign. They're built through continuous, disciplined improvement. One cycle at a time. Forever.** 🎯✨🔄