liveBook · Manning

Decision making

As explained in Think Like a Software Engineering Manager

The process of selecting an action or outcome from available alternatives, including authority, criteria, methods, timing, and feedback.

Decision making is the process of choosing an action or outcome from alternatives. Effective decisions make authority, criteria, timing, feedback, and accountability visible. section 9.2.4 section 3.2.6

A practical decision-making process includes:

  • Define who provides input, who makes the final call, and who must be notified. section 9.2.4
  • Set criteria using project goals, deadlines, budgets, and customer requirements. section 9.2.4
  • Choose an appropriate method, such as consensus, delegation, voting, or consultation. section 9.2.4
  • Set a timeline, involve relevant stakeholders, document agreements, and establish a conflict protocol. section 9.2.4
  • Communicate the decision promptly, commit to implementation, and review outcomes through regular reflection. section 3.2.6 section 14.1.4

Reassigning an engineer under pressure

When executives require urgent project support, a manager may reassign a senior engineer from lower-priority operational work. The manager explains the opportunity, seeks cross-functional feedback, and treats performance problems as a coaching opportunity. If disagreement persists, evidence, individual conversations, group discussion, or a neutral third party can help reach alignment. section 3.2.6 section 3.1.3

Figure 3.1 Bring a neutral party to help build alignment in times of conflict.
figure

A neutral party can help conflicting contributors hear feedback, examine trade-offs, and build alignment when direct discussion reaches an impasse. section 3.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Details roles, criteria, methods, timelines, meetings, conflict protocols, documentation, communication, and reflection rather than decision theory.
Examples
Uses urgent engineer reassignment, cross-functional process design, technical disagreement, and flexible-hours policy changes as practical cases.
What it assumes
Assumes responsibility for teams and projects while teaching decision roles, methods, criteria, and feedback practices explicitly.
What you can do after
Apply it via a documented process that assigns authority, weighs criteria, gathers input, resolves conflict, communicates outcomes, and reviews consequences.
How it connects
Connects decision making with delegation, consensus, conflict resolution, feedback, stress management, and strategic planning.

Also explained in

Compare how 6 books explain decision making →

Related concepts

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