The missing link between business need and software development: product design
summary
Argues that participatory product and service design closes the gap between buyer requirements and working software by creating executable prototypes, not specs. Uses paper mockups, cardboard labs, staged role‑play and service blueprints to simulate end‑to‑end processes, run rapid iterations (often four rounds in a day or two), and capture validated user behavior, edge cases and empathy. Demonstrations include a library kiosk, a wearable trainer and a hospital ward; outcomes are cheaper learning, stronger ownership and prototypes that actually work in context.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:08What is Kozai
- 2:01Who is Kozai
- 3:06Agenda
- 3:43The problem
- 5:46The disconnect between buyer and better
- 6:39Example of a disconnect
- 8:53Complexity
- 10:20Outsourcing ownership
- 11:51Requirements gathering
- 13:05Agile software development
- 13:32Designing feedback
- 13:44Design
- 15:44Ethnography
- 17:23Knowledge
- 18:04A naive waterfall
- 19:40Initial product owner
- 20:44Prototypes
- 22:15Design Cloud
- 23:11Participatory design
- 24:23Prototyping
- 25:36User Interfaces
- 26:56Library
- 28:00Sport
- 30:05User Story Map
- 35:15Cardboard Hospital
- 35:57Advantages of participatory design
- 38:12Empathy
- 39:16Questions Comments
- 47:31Conclusion
