liveBook · Manning

Chapter 3: Reading the context

What you will learn in chapter 3 of Decision Engineering

This introduction explains why requirements alone do not determine the right technical choice and identifies the system, team, and company contexts that also shape it.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction explains why requirements alone do not determine the right technical choice and identifies the system, team, and company contexts that also shape it.

Key terms: requirements, context, decision framing, system context, team context, company context

3.1 System context

This section explains why decisions that change an existing system must account for its constraints after the problem and requirements are understood.

Key terms: existing system context, historical complexity

3.1.1 The 5W questions

The section introduces five questions for investigating an existing system before a significant decision and explains how AI can help with the investigation if crucial findings are verified.

Key terms: 5W questions, system context, assumptions, internal submarine usage, AI-assisted analysis, initial exploration, verified

3.1.2 What exists in the system today?

This section explains how to inspect a component’s current condition and check for existing solutions elsewhere in the organization before making a change.

Key terms: code quality analyses tools, AI insights, operational metrics, existing design choices, test-covered, tech debt, outdated dependencies, horizontal axis, reuse, global channel

3.1.3 Where is the component used?

This section shows how to find where a component is actually used, map a change’s blast radius, and match the decision process to that impact.

Key terms: consumers, hidden dependencies, production traffic, use and dependency tracing, blast radius, coupling, organisational boundaries, cascading impact, lightweight process, one-way door decision

3.1.4 When was it built?

This section shows how the circumstances in which a component was built can explain puzzling design choices and change how an engineer approaches them today.

Key terms: when question, technology context, team's constraints, CSS grid, custom properties, current CSS primitives, modernization candidate

3.1.5 Why is it the way it is?

This section shows how the original reasons for a design help explain its current shape and reveal when it may be worth revisiting.

Key terms: ADRs, historical constraint, Conway's Law, original constraints, decision context assumptions, Google Web Toolkit (GWT)

3.1.6 Who owns it, who knows it deeply, and who has the historical context?

This section shows how to identify the people who can explain a component, recognize concentrated knowledge as a risk, and check findings with someone who knows the software deeply.

Key terms: owner, historical context, who knows it deeply, bus factor, load-bearing component, assumptions, findings, who knows it

3.1.7 Understanding whether your findings are solid enough

The section explains how to judge the reliability of findings about an existing system and verify weaker sources before relying on them.

Key terms: primary source, secondary source, runtime evidence, AI analyses of the code, direct testimony, primary documents, leads, primary evidence, runtime logs, API credentials

3.2 Team context

This section explains why a technology choice must be judged in the context of the team that will adopt and operate it.

Key terms: team context, team knowledge, talent pool, technology preference

3.2.1 Team knowledge

This section explains how to assess a team’s relevant technology knowledge by looking at hands-on operations, comparable experience, and expertise across the organization.

Key terms: direct experience, under load, recover, comparable technologies, self-hosted solutions, managed services, shared operational concerns, earlier roles, peer learning session, team autonomy

3.2.2 Talent availability

Technology choices shape future hiring, so their technical benefits must be weighed against the talent a team can realistically recruit and develop.

Key terms: talent pool, niche technology, technical case, hiring case, remote-first organisations, background match, ramp-up

3.2.3 On-call setup

This section explains how the people responsible for incidents constrain which technologies a team can operate reliably.

Key terms: team-owned, shared rotation, Network Operations Center (NOC), runbooks, operational stack, shared operational stability, local implementation productivity, debug, managed service

3.2.4 Team preferences

This section explains how to account for team preferences in technical decisions without mistaking enthusiasm or familiarity for evidence of fit.

Key terms: team preference, team's experience, technical judgement, selective reasoning, motivated reasoning, fit, prior experience, competent engineer outside this team, big tech companies

3.2.5 Understanding which forces are binding

This section explains how to identify the team-context forces that actually constrain a decision and account for them when framing it.

Key terms: binding constraint, team context, on-call rotation, framing, option set

3.3 Company context

This section explains why company context changes which technical decisions are realistic and introduces four forces whose influence varies by decision.

Key terms: team context, company context, scale, industry, business context, technology strategy, guardrails, four forces, company scale, industry context

3.3.1 Business strategy

This section shows how a capability’s role in business strategy should shape technology decisions, even when its immediate requirements are clear.

Key terms: differentiating capabilities, enabling capabilities, strategic role, capability headroom, initial requirements, strategic context, investment depth, choice of standards, tolerance for novelty

3.3.2 Technology strategy

This section explains how technology strategy shapes technical decisions through organizational guardrails and changing priorities without taking decisions away from teams.

Key terms: technology strategy, guardrails, shared standards, priorities, speed to market, change agility, reliability and resilience, cost efficiency, navigation system, meaningful autonomy

3.3.3 Company scale

The section shows how startup, scale-up, and enterprise dynamics change technical trade-offs, and why those dynamics must be read in the specific decision context rather than assigned as fixed company labels.

Key terms: startup, product-market fit, learning speed, managed cloud services, SaaS, premature optimization, scale-up, foundational trade-offs, decision space, cargo-culting

3.3.4 Industry norms

This section shows how industry norms shape technical trade-offs and how engineers can uncover norms that are rarely written down.

Key terms: maintainability versus immediate performance, regulatory exposure, ship cadence, calendar constraints, player experience, re-validation, re-certification, safety-critical, technical debt, peak windows

3.4 Reading context: a worked example

The section uses a data-ingestion decision to show how system, team, and company context narrow the options worth evaluating without choosing a solution.

Key terms: system context, team context, company context, legacy ETL, bus factor, context assessment, managed SaaS solutions, build-vs-buy, connector coverage, existing ecosystem

3.5 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: Understanding the problem Chapter 4: Evaluating external technologies →

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.