How to make the perfect decision
summary
Argues there is no perfect decision and the concrete rule is code wins arguments: build a spike or minimal implementation, get it into an environment that yields real feedback, and iterate. Recommends prioritising choices by delivery speed, product cost and technical risk, breaking big decisions into many small ones, using ADRs and public docs to surface constraints, and favouring fast and wrong is better than slow and correct to reduce unknowns and close the loop.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:14Making decisions all the time
- 1:04Design thinking squiggle
- 1:46Making decisions
- 2:30Its hard
- 4:52Bringing it all together
- 8:08Software is deterministic
- 8:27Wicked problems
- 8:42Decision definition
- 8:53Code wins arguments
- 9:17Close the loop
- 9:29Execution
- 10:08Best way to do this
- 10:30Best things to prioritize
- 11:04Focus on small decisions
- 11:15Conclusion
related talks
39mThe Art of Technical Decision Making
27mStrategies for making impossible decisions
26mIndecisions Are Not All Bad
01h 06mDecisions, Decisions — Dan North on Trade-offs in Software
22mDecide Like a Pro: Navigate the Time-Quality-Cost Trifecta
32mThe Art of Technical Decision Making
42mDecision-making for developers
01h 02mDecision Dials