The Art of CTO Decision Velocity Framework classifies engineering decisions by reversibility and impact scope, diagnoses organizational bottlenecks, and generates delegation models that match decision authority to the right level.
Frequently Asked Questions
What is the difference between Type 1 and Type 2 decisions?
Amazon popularized this framework: Type 1 decisions are irreversible and high-impact — they require careful analysis and senior decision-makers. Type 2 decisions are reversible — they should be made quickly by individuals closest to the context. Most organizations treat too many decisions as Type 1, creating bottlenecks. The fix is explicit classification: "Can we reverse this easily? Then just decide." High-performing organizations push 80%+ of decisions to Type 2 and reserve Type 1 process for the 10-20% that truly warrant it.
How do you reduce decision bottlenecks in engineering?
Three strategies: (1) Document decision authority — create a clear matrix showing which roles decide what, eliminating the "ask the CTO" default. (2) Implement async decision processes — RFCs and ADRs let teams propose and decide without scheduling meetings. (3) Set decision SLAs — if a decision is not made within the SLA, the proposer is authorized to proceed. Most decision delays come from unclear authority, not from the decisions being genuinely hard.