The Art of Technical Decision Making
summary
Argues for aiming at a good decision not a perfect one and shows a repeatable process used to choose whether to adopt a new technology: three 1.5‑hour workshops using whiteboard + stickies, list goals, map benefits/risks, and run five‑dot voting and a consensus check; where disagreement appears, counsels a mutually beneficial fallback such as a prototype spike or hackathon. Gives concrete bounds — a couple of months for irreversible language choices (Flutter example) and a 40‑minute catastrophic failure risk (high‑frequency trading) — and insists on documenting and sleeping on the result.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:10The Art of Technical Decision Making
- 3:58Mindset
- 4:58Uncertainty
- 5:29Simplify
- 6:03Conflict
- 6:58Fear of losing
- 8:21Personal Decisions
- 10:05Technical Decisions
- 12:25Team Decision Making
- 14:37Team argumentation styles
- 17:04Consensus is not coercion
- 19:46Opensource collectives
- 21:57Collaborative Process
- 23:02Questions to Ask
- 25:32How Long to Take
- 26:23Check In With Our Emotions
- 28:16Example
- 29:19Step 4 Evaluate
- 30:02Common elements
- 31:40Build consensus
- 34:51Resources
- 35:20Thank you
- 36:05Questions
related talks
32mThe Art of Technical Decision Making
12mHow to make the perfect decision
27mStrategies for making impossible decisions
42mDecision-making for developers
43mKeynote: Decision-making for Software Development Teams
19mHow to make technical decisions?
25mThinking Architecturally
02mA young lady's illustrated primer to technical decision making