liveBook · Manning

Decision making

As explained in Decision Engineering

The selection among technical alternatives in light of context, priorities, constraints, and uncertainty.

Technical decision making is the selection among alternatives to serve a business outcome under real constraints and uncertainty. Choosing a database, adopting a framework, splitting a monolith, or building rather than buying can change both what a team delivers and how quickly it delivers it. None has a universally correct answer: priorities, team capabilities, costs, risks, and the future all matter. section 1.0 section 1.1.3

A good decision is not necessarily the most elegant architecture or the choice with the best eventual outcome. It is a reasoned choice made with known risks in view to serve what matters to the business. Short-term survival may outweigh long-term maintainability; circumstances may later justify reversing a sound decision. Engineers should make risks clear and challenge a harmful direction, while recognizing that business leadership may weigh those risks differently. section 1.1 section 1.5

A practical decision cycle is:

  • Frame the problem and the desired outcome before arguing for a solution. Check whether the apparent either-or choice excludes simpler alternatives. section 1.2.1 section 1.5
  • Evaluate options against relevant costs, risks, constraints, and uncertainty. Give hard-to-reverse choices more analysis and stakeholder involvement; move faster on reversible choices. section 1.1.3 section 1.5
  • Choose, then make the choice stick in execution. Revisit the frame if a prototype fails or a new constraint appears; revisit the choice if implementation stalls or circumstances change. section 1.2.1 section 1.5

Speed versus foundations

A three-engineer startup pursuing its first paying enterprise customers cut scope—and sometimes scalability foundations—to meet launch dates. Where missing a date could threaten the product, fast, revisable choices served an immediate business need. The same option need not suit a larger organization with more existing systems, teams, and consequences to account for. section 3.3.3 section 1.1

Table 3.1 Scale patterns comparison
Dimension
Startup
Scale-up
Enterprise
Decisions this stage values
Reversible bets where speed matters more than fit
Choices that will sustain the realistic scale for several years
Decisions that survive across team changes and ideally  fit multiple teams
Tolerable uncertainty
High – most decisions can be revisited quick
Moderate – some foundational decisions are hard to revisit cheaply
Low – once shipped, decisions become a of a much  bigger whole
What the decision can lean on
Almost nothing – every choice is greenfield
Some existing systems, some genuine greenfield
An existing platform landscape that constrains the option set
Strategic role of the decision
Surviving long enough to learn
Building the spine the company growth will run on
Leveraging the value of decisions already made and scale
Most likely failure reason
Over-engineering for a future that may never come
Picking the wrong scale – oversimplifying or overengineering
Not taking pragmatic decisions at the excuse to be enterprise-ready

Compare how startup, scale-up, and enterprise conditions change the uncertainty a decision can tolerate, what existing systems constrain it, and which kinds of choices each stage values. Treat these as patterns, not fixed company categories. section 3.3.3

Structure should match the stakes, not become a ritual. Cost–benefit analysis, Architecture Decision Records, and rapid prototyping can help compare alternatives or test assumptions. A technically sound choice can still fail if priorities prevent its adoption, the team is unconvinced, or those controlling budget and resourcing do not support it. The aim is a choice that can be acted on, not merely defended on paper. section 1.1.3 section 1.2.1

How Decision Engineering covers it

How deep it goes
Outlines a repeatable lifecycle and adjustable tools, but leaves detailed treatment of later failure modes beyond this overview.
Examples
Uses database and framework choices, a startup racing to launch, and decisions that fail to gain implementation support.
What it assumes
Assumes competence in building software while teaching structured reasoning about the choices surrounding implementation.
What you can do after
Practice/perform framing, comparing, choosing, and revisiting technical decisions in proportion to their stakes.
How it connects
Connects to trade-off analysis, cost–benefit analysis, Architecture Decision Records, rapid prototyping, stakeholder involvement, and architectural reversibility.

Also explained in

Compare how 9 books explain decision making →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Decision Engineering. The section links point to the parts of the book it draws on.