chapter one

1 Understanding technical decisions

 

This chapter covers

  • Recognizing decisions that matter
  • What defines good reasoning
  • Why decision-making is a skill to master
  • Introducing the decision lifecycle

Every technical organisation makes plenty of decisions. Which database to use, whether to adopt a new framework, when to split a monolith, whether to build or buy, how to structure the platform documentation. These choices shape what engineers build, how quickly they build it, and if the business gets what it needs. Unlike an algorithmic puzzle, decisions of this kind rarely have a textbook answer. They depend on context, constraints, and people, and they are made under genuine uncertainty.

The need for solid decision-making remains as evident as ever in the age of AI-assisted development. Today, a working prototype can appear in a day. In the engineering work I observe, the bottleneck has shifted from writing code to deciding what and how to build. The impact of architectural choices has remained high and the rate at which those decisions pop up has also risen.

1.1 What is “good” decision-making?

1.1.1 Even good decisions come with uncertainty

1.1.2 Decisions that deserve thinking

1.1.3 Decision-making as its own discipline

1.2 Why decision making is a critical engineering skill

1.2.1 The cost of poor decisions

1.2.2 How decisions change in the age of AI

1.3 The decision lifecycle

1.3.1 Phase 1: Framing the decision

1.3.2 Phase 2: Evaluating and choosing options

1.3.3 Phase 3: Making the decision stick

1.4 Scope and the road ahead

1.5 Summary