Technical decision conversation guide
A compact structure for architecture, platform, vendor, and build-versus-buy decisions.
Designed for
- Founders
- Technical leaders
- Product and procurement teams
The working prompts
- 01
What product or business decision requires a technical choice now?
- 02
Which constraints are fixed, and which are current assumptions?
- 03
What happens if the team postpones the choice?
- 04
Which options are credible, including keeping the current system?
- 05
How does each option affect users, delivery, operations, security, cost, and future change?
- 06
Which consequence would be expensive or difficult to reverse?
- 07
What evidence supports the recommendation, and what remains unknown?
- 08
Who owns implementation, operation, and recovery?
- 09
When should the decision be reviewed, and what new evidence would reopen it?