Decision making
Decision making is the process of selecting an action, outcome, or judgment from available alternatives based on information, objectives, or constraints.
Lead Developer Career Guide
The process of selecting an action or resolution from available alternatives.
- How it is used
- Guides lead developers in choosing and carrying out project plans while remaining accountable to the team.
- How deep it goes
- Develops a practical cycle of assessing risk, planning, gathering feedback, checking progress, and correcting course; does not prescribe a formal method.
- Examples
- Contrasts a feature-versus-bug compromise with a delayed choice among technical approaches on a late project.
- What you can do after
- Practice/perform it by weighing risks, seeking input, choosing a plan, and checking whether execution stays on track.
Read how Lead Developer Career Guide explains decision making →
Interview Speak
The process or competency of selecting a course of action among alternatives.
- How it is used
- Demonstrates how you analyze difficult workplace choices in interview answers.
- How deep it goes
- Walks through context, constraints, options, trade-offs, rationale, and outcomes rather than merely naming a decision.
- Examples
- Uses firing and reduction-in-force scenarios to contrast human concerns, business needs, analysis, communication, and business benefit.
- What you can do after
- Practice/perform a concise interview narrative that makes decision analysis and impact visible.
Think Like a Software Engineering Manager
The process of selecting an action or outcome from available alternatives, including authority, criteria, methods, timing, and feedback.
- How it is used
- Guides engineering managers through collaborative choices, urgent trade-offs, conflict resolution, and accountable implementation.
- 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 you can do after
- Apply it via a documented process that assigns authority, weighs criteria, gathers input, resolves conflict, communicates outcomes, and reviews consequences.
Read how Think Like a Software Engineering Manager explains decision making →
Collaborative Software Design: How to facilitate domain modeling decisions
A decision is a conscious choice between two or more alternatives that irrevocably allocates resources such as time, money, or energy.
- How it is used
- Frames collaborative software design as a sequence of resource-committing choices that must remain sustainable under uncertainty.
- How deep it goes
- Defines choices, alternatives, resources, information, preferences, and analysis, then extends them into styles, documentation, and feedback loops.
- Examples
- Uses New Year’s resolutions, software design choices, collaborative modeling, formalized consequences, and ADRs as teaching artifacts.
- What you can do after
- Apply it via problem statements, alternatives, information gathering, explicit resource commitment, documented consequences, and iterative feedback.
Causal AI
Decision-making is the process of selecting actions or policies among alternatives, including selection performed by automated systems.
- How it is used
- Frames statistical decision theory, bandits, and reinforcement learning as problems of choosing actions for favorable consequences.
- How deep it goes
- Develops interventions, expected utilities, policy bias, causal DAGs, Bellman-equation analogs, and counterfactual policy evaluation.
- Examples
- Uses streaming content deals, portfolio backtests, game replays, poker outcomes, and Newcomb’s paradox to contrast causal and noncausal choices.
- What you can do after
- Apply causal models, counterfactual simulations, Pyro, or pgmpy to evaluate policies and automate decisions under uncertainty.
Think Like a CTO
A decision is a choice among alternatives that commits a person or organization to a course of action.
- How it is used
- Frames decision making as an executive partnership responsibility involving the CEO and organization.
- How deep it goes
- Provides guidance on data-backed recommendations, escalation of hard choices, and delaying immediate answers; it does not detail formal models.
- Examples
- Uses hiring, project approval, and no-good-path scenarios to expose productivity, financial, and consequence trade-offs.
- What you can do after
- Apply it through data-backed proposals, consequence comparisons, CEO involvement, and deliberate response timing.
Related concepts
- common sensehas part · Common sense is ordinary background knowledge and practical judgment used to interpret everyday situations and draw plausible conclusions about entities, events, relationships, and consequences.
- mathematical calculationkind of · A mathematical calculation is an operation or expression that derives a result from one or more input values.
- capabilitykind of · A capability is an ability or permitted function that enables a person, organization, or system to perform an activity or achieve an outcome.
- continuous improvementpart of · Continuous improvement is an ongoing process of evaluating outcomes and making successive changes to improve a system, process, or result.
- data-driven approachused by · A data-driven approach bases decisions, conclusions, or system behavior substantially on collected or observed data rather than primarily on intuition or assumptions.
- consensususes · Consensus is sufficient agreement among participants or processes on a shared decision, value, state, assessment, or outcome.
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.