"Design in Practice"
summary
Talk argues that design is a set of concrete, repeatable activities not magic and shows specific tools and outputs: add a glossary (one maintained across an eight‑month project), write experiments with a results template before coding, use the decision matrix as a live Google Sheets spreadsheet with colored cells (green/yellow/red) to compare approaches, derive problems from feature requests, and iterate from use‑case sheets to implementation DMs; an implemented example converts Java interop choices into a generated adapter approach that ships.
AI-written summary · about
chapters (22)
- 0:00Design as learnable practice
- 1:09Design team activities and outputs
- 3:39Design as plan for action
- 5:04Precision in language
- 8:38Building glossary for clarity
- 10:23Power of good questions
- 11:46Socratic method for truth
- 14:16Reflective inquiry tracking
- 17:04Project stories with design
- 19:10Design increases understanding
- 23:02Problem through symptoms
- 25:10Diagnose problems to causes
- 31:01Feature requests to problems
- 32:04Delimit problem for solutions
- 34:33Strategy and user objectives
- 36:58Capturing user intentions
- 39:25Decision matrices for choices
- 48:31Evaluating approaches
- 53:25Design as solution planning
- 55:35Implementation decisions
- 58:44Outcomes of rigorous design
- 1:00:08Summary
