Monitor the impact of your Design Delivery (small scope) and measure if it achieved the expected results.
Ensure you have:
改善 (Kaizen) requires measurement:
Ship → Monitor → Learn → Improve → Ship...
↑
You are here!
Without measurement, you're just guessing!
From Design Delivery file:
metrics:
measurement_period: '2 weeks after release'
See: data/monitoring-templates.md for Metrics Tracking Dashboard
Monitor multiple channels:
See: data/monitoring-templates.md for Qualitative Feedback template
Create: analytics/DD-XXX-impact-report.md
See: data/monitoring-templates.md for Impact Report template
Key sections:
Communicate impact to team:
See: data/monitoring-templates.md for Team Results Communication template
Final update to deliveries/DD-XXX-name.yaml:
delivery:
status: 'measured'
measurement_complete: '2024-12-28T10:00:00Z'
impact_report: 'analytics/DD-XXX-impact-report.md'
result: 'success'
metrics_achieved:
- 'Feature X usage: 58% (target: 60%)'
learnings:
- 'Onboarding matters for complex features'
After monitoring and learning:
[M] Return to Activity Menu — see also data/kaizen-iteration-guide.md
✅ Measurement period complete ✅ All metrics tracked ✅ Qualitative feedback gathered ✅ Impact report created ✅ Results shared with team ✅ Learnings documented ✅ Next opportunity identified
❌ Not measuring impact ❌ Ending measurement too early ❌ Ignoring qualitative feedback ❌ Not documenting learnings ❌ Not sharing results ❌ Not identifying next opportunity
Be patient: Give changes time to work, don't end measurement early
Be thorough: Track all metrics, gather qualitative feedback, document learnings
Be honest: Report actual results, acknowledge what didn't work
Don't cherry-pick: Report all metrics, not just good ones
Don't stop measuring: Kaizen requires continuous measurement
Don't skip sharing: Team needs to know results
Remember: Measurement turns improvements into learnings. Learnings drive the next cycle!