liveBook · Manning

Chapter 1: Understanding technical decisions

What you will learn in chapter 1 of Decision Engineering

The introduction explains why consequential technical choices require decision-making skill beyond software-building expertise, especially as AI speeds up coding.

After this chapter you will be able to

Section by section

Introduction

The introduction explains why consequential technical choices require decision-making skill beyond software-building expertise, especially as AI speeds up coding.

Key terms: technical decisions, context, constraints, uncertainty, AI-assisted development, bottleneck, architectural choices, decision-making, system design, making decisions stick

1.1 What is “good” decision-making?

The section defines a good technical decision by its business purpose, deliberate trade-offs, transparent reasoning, and follow-through rather than by technical elegance or hindsight alone.

Key terms: business outcome, full spectrum of options, known risks, consequences and alternatives, short and long-term horizon, flag risks, push back, leadership, canceled or revisited, circumstances outside of our control

1.1.1 Even good decisions come with uncertainty

The section explains why good technical decisions should be judged by the reasoning behind them, even when uncertainty remains or outcomes disappoint.

Key terms: decision quality, decision outcome, trade-off analysis, best possible odds, uncertainty, research, prototyping, assumptions

1.1.2 Decisions that deserve thinking

This section explains how reversibility and organizational impact determine which technical decisions deserve structured analysis, and why major commitments should begin with small experiments.

Key terms: one-way door decisions, two-way door decisions, cost of change, two-way door treatment, exploratory validation, pilot cases, impact on the organization, structured thinking, stakeholder involvement

1.1.3 Decision-making as its own discipline

This section treats technical decision-making as a context-dependent discipline that engineers can learn, practise, and apply as technologies change.

Key terms: trade-offs, organizational constraints, context-dependent, decision-making, frameworks, heuristics, processes, deliberate practice, framing problems, challenging assumptions

1.2 Why decision making is a critical engineering skill

This section explains why making technology decisions in an organizational setting is a critical engineering skill that formal training often neglects.

Key terms: mechanics of building systems, architecture decisions, implementation speed, operational cost, long-term maintainability, opportunity cost

1.2.1 The cost of poor decisions

This section shows how poor decision-making can undermine technically sound choices through lack of follow-through, unnecessary complexity, weak support, or overly narrow options.

Key terms: decision stayed on paper, team was not convinced, management was not on board, Overengineering, complex event-driven pipeline, multi-layered abstraction, The one and only alternative, simpler alternatives

1.2.2 How decisions change in the age of AI

AI makes software faster to produce, but engineers still have to make context-aware decisions, understand what is built, and reassess build-versus-buy trade-offs.

Key terms: AI-assisted development, second opinion, trade-offs, context, constraints of our situation, technically sound choice, accountability, comprehension debt, build-vs-buy, in-house

1.3 The decision lifecycle

The section uses a component-library migration to show the three phases of a technical decision, why teams must work through each phase, and how feedback can send them back to earlier choices.

Key terms: decision lifecycle, framing, evaluation, making the decision stick, Web Components, framework-agnostic, Vue-native interface, trial, prioritisation, design and brand refresh

1.3.1 Phase 1: Framing the decision

Framing a technical decision makes the problem, its often-implicit constraints, and its surrounding context explicit before the team chooses a solution.

Key terms: framing, formal requirement, real constraint, implicit inspirations, problem space, context, constraints

1.3.2 Phase 2: Evaluating and choosing options

This section explains how teams compare options, test assumptions before committing, and account for human influences when choosing a technical direction.

Key terms: trade-offs, cost–benefit analysis, decision matrices, staged adoption, phased adoption, prototypes, validate assumptions, stakeholder dynamics, organisational incentives, cognitive biases

1.3.3 Phase 3: Making the decision stick

This section explains why choosing an option is not enough: a technical decision must be documented, carried into practice, and revisited when adoption reveals new constraints.

Key terms: adoption, implementation priorities, one-way door, Architecture Decision Records, reasoning behind a choice, feedback loops, framing, organisational context, framework independence, business sponsorship

1.4 Scope and the road ahead

This section defines the book’s scope and explains why technical decisions must account for organizational constraints and human judgment.

Key terms: leadership, existing infrastructure, product roadmap, cognitive shortcuts, human judgment

1.5 Summary

Where this is used later

Concepts explained in this chapter

Chapter 2: Understanding the problem →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.