6.7 KiB

Raw Blame History

Phase 8: Ongoing Development (Kaizen) Workflow

Continuous improvement through strategic, incremental changes

Purpose

Phase 8 is about Kaizen (改善) - the Japanese philosophy of continuous improvement.

Two contexts for Phase 8:

Entry Point for Existing Products - Jump into an existing product as a linchpin designer
Continuous Improvement - After initial launch, keep improving through small, strategic changes

Lean Manufacturing Philosophy

Kaizen (改善) vs Kaikaku (改革)

Two approaches to improvement from Lean manufacturing:

Kaizen (改善) - Continuous Improvement

改善 = Change (改) + Good (善)

Definition: Small, incremental, continuous improvements over time.

Characteristics:

Small changes (1-2 weeks each)
Low cost, low risk
Everyone participates
Continuous, never stops
Gradual improvement
Process-focused
Bottom-up approach

In product design:

Ship → Learn → Improve → Ship → Repeat
Small updates beat big redesigns
User feedback drives improvements
Data informs decisions
Quality improves gradually
Team learns continuously

Example:

Add onboarding tooltip to improve feature usage
Optimize button color for better conversion
Improve error message clarity

Phase 8 uses Kaizen approach!

Kaikaku (改革) - Revolutionary Change

改革 = Change (改) + Reform (革)

Definition: Radical, revolutionary transformation in a short period.

Characteristics:

Large changes (months)
High cost, high risk
Leadership-driven
One-time event
Dramatic improvement
Result-focused
Top-down approach

In product design:

Complete redesign
Platform migration
Architecture overhaul
Brand transformation
Business model pivot

Example:

Complete product redesign
Migrate from web to mobile-first
Rebrand entire product
Change business model

Phases 1-7 can be Kaikaku (greenfield projects)!

When to Use Each

Use Kaizen (改善) when:

✅ Product is live and working
✅ Need continuous improvement
✅ Want low-risk changes
✅ Team capacity is limited
✅ Learning is important
✅ Phase 8: Ongoing Development

Use Kaikaku (改革) when:

✅ Starting from scratch (greenfield)
✅ Product needs complete overhaul
✅ Market demands radical change
✅ Current approach is fundamentally broken
✅ Have resources for big change
✅ Phases 1-7: New Product Development

The Balance

Best practice: Kaikaku to establish, Kaizen to improve.

Kaikaku (改革): Build product v1.0 (Phases 1-7)
    ↓
Launch
    ↓
Kaizen (改善): Continuous improvement (Phase 8)
    ↓
Kaizen cycle 1, 2, 3, 4, 5... (ongoing)
    ↓
(If needed) Kaikaku: Major redesign v2.0
    ↓
Kaizen: Continuous improvement again

Phase 8 embodies Kaizen philosophy!

Workflow Architecture

This uses micro-file architecture for disciplined execution:

Each step is a self-contained file with embedded rules
Sequential progression with user control at each step
Iterative improvement cycles

Phase 8 Micro-Steps

Context 1: Existing Product Entry Point

Phase 8.1: Identify Strategic Challenge
    ↓ (What problem are we solving?)
Phase 8.2: Gather Existing Context
    ↓ (Understand current state)
Phase 8.3: Design Critical Updates
    ↓ (Targeted improvements, not complete redesign)
Phase 8.4: Create Design Delivery
    ↓ (Package changes as DD-XXX for BMad)
Phase 8.5: Hand Off to BMad
    ↓ (Touch Point 2: WDS → BMad)
Phase 8.6: Validate Implementation
    ↓ (Touch Point 3: BMad → WDS)
Phase 8.7: Monitor and Learn
    ↓ (Gather data, identify next improvement)
Phase 8.8: Iterate
    ↓ (Repeat cycle for next challenge)

Context 2: Continuous Improvement (Post-Launch)

Phase 8.1: Monitor Product Performance
    ↓ (Analytics, feedback, issues)
Phase 8.2: Identify Improvement Opportunity
    ↓ (What's the next most valuable change?)
Phase 8.3: Design Incremental Update
    ↓ (Small, focused improvement)
Phase 8.4: Create Design Delivery
    ↓ (Package changes as DD-XXX for BMad)
Phase 8.5: Hand Off to BMad
    ↓ (Touch Point 2: WDS → BMad)
Phase 8.6: Validate Implementation
    ↓ (Touch Point 3: BMad → WDS)
Phase 8.7: Monitor Impact
    ↓ (Did it improve the metric?)
Phase 8.8: Iterate
    ↓ (Repeat cycle - Kaizen never stops!)

When to Enter Phase 8

Scenario 1: Existing Product Entry Point

You're brought in as a linchpin designer to improve an existing product:

Product Manager: "We have a product with 60% onboarding drop-off.
                  We need a designer to fix this critical issue."

You: "I'll use WDS Phase 8 to make strategic improvements."

Start with: steps/step-8.1-identify-challenge.md

Scenario 2: Post-Launch Continuous Improvement

Your product is live and you're iterating based on data:

Analytics: "Feature X has low engagement (15% usage)"
User Feedback: "Users don't understand how to use Feature X"

You: "Time for a Kaizen cycle to improve Feature X."

Start with: steps/step-8.1-monitor-performance.md

Execution

Load and execute the appropriate step file based on your context:

Existing Product Entry Point:

steps/step-8.1-identify-challenge.md

Continuous Improvement:

steps/step-8.1-monitor-performance.md

Note: Each step will guide you to the next step when ready.

Resources

Limited Project Brief: A-Project-Brief/limited-brief.md
Existing Context: A-Project-Brief/existing-context/
Design Deliveries: deliveries/DD-XXX.yaml (all improvements use DD-XXX)
Test Scenarios: test-scenarios/TS-XXX.yaml
Analytics: analytics/
User Feedback: feedback/

Key Differences from Phases 1-7

Phase 8 is NOT about:

❌ Complete redesigns
❌ Designing full user flows from scratch
❌ Starting with blank canvas
❌ Defining tech stack (already decided)

Phase 8 IS about:

✅ Strategic, targeted improvements
✅ Updating existing screens and features
✅ Incremental changes that compound
✅ Working within existing constraints
✅ Continuous improvement (Kaizen)

The Kaizen Cycle

Ship → Monitor → Learn → Improve → Ship → Monitor → Learn → Improve...

This cycle never stops!

Each cycle:

Takes 1-2 weeks (small changes)
Focuses on one improvement
Ships to production
Measures impact
Informs next cycle

Over time:

Small improvements compound
Product quality increases
User satisfaction grows
Team learns continuously
Competitive advantage builds

Phase 8 is where products become great - through continuous, disciplined improvement! 🎯✨

6.7 KiB Raw Blame History