From funding to delivery: ensuring alignment from start to finish
summary
Case study of a $300M, three‑year government program shows how traceability uncovers unvalidated blueprints and weak tech assumptions, then fixes them with a Miro traceability map that links business case, roadmap, epics, touchpoints and capabilities. Teams create product summary tiles for PI planning, introduce a lightweight delivery readiness tool, appoint service design leads and a research‑ops practice, and double down on targeted research. Result: higher confidence to start builds, artifacts reused for two years.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 1:28Case study overview
- 3:35Discovery and initial challenges
- 5:20Key deliverables and alignment
- 8:10Government artifacts and traceability
- 12:25Traceability exercise approach
- 15:15Product summary tiles creation
- 17:19Readiness for delivery
- 18:21Delivery Readiness tool
- 20:24Sustainable work practices
- 22:28Team structure models
- 23:31Key takeaways and lessons
- 29:29Conclusion and future application
related talks
28mJourney from Design Afterthought to Design First
34mThe Value of Structure and Transparency
47mThe product confidence trap
43mBeyond Discovery: A Service Designer's Guide to Agile Delivery
41mCreating the Right Product Using Impact Mapping and Agile Guerrilla Techniques
42mDeliver Undeniable Impact: Establishing a High-Value UX Research Practice
43mDesign Beyond Deliverables
33mProduct Discovery hacks