HKSM

Decision making is a technique for selecting a course of action from alternatives using defined criteria, evidence, and professional judgment. In projects it aims to choose options that best support objectives while managing constraints and risks.

Key Points

• Uses clear, agreed criteria to compare alternatives and justify choices.
• Can be individual, consultative, collaborative, or use structured tools like multi-criteria decision analysis.
• Balances value, cost, schedule, risk, and stakeholder impact to support project objectives.
• Requires the right participants, decision rights, and timeboxing to avoid delays.
• Documentation of rationale, assumptions, and supporting data increases transparency and auditability.
• Bias awareness and data quality materially affect decision quality and outcomes.

Decision Criteria

• Expected value or benefits delivered.
• Total cost and affordability within budget.
• Schedule impact and urgency.
• Risk exposure and uncertainty.
• Feasibility, complexity, and capability fit.
• Compliance, standards, or regulatory requirements.
• Resource availability and skills.
• Dependencies and impact on other work.
• Stakeholder satisfaction and user experience.
• Reversibility and long-term maintainability.

Method Steps

• Frame the decision: define the problem, decision owner, and decision deadline.
• Identify feasible alternatives and clarify the option to do nothing if applicable.
• Define evaluation criteria and, if useful, assign weights with stakeholder input.
• Gather relevant data, estimates, risks, and assumptions for each option.
• Evaluate alternatives using appropriate techniques (e.g., scoring model, decision tree, cost-benefit, or MoSCoW).
• Facilitate discussion, test for biases, and seek sufficient consensus or apply the decision right (e.g., product owner, sponsor).
• Decide, document the rationale and assumptions, and record in the decision log.
• Communicate the decision, implement actions, and set a review trigger if conditions change.

Inputs Needed

• Problem statement and desired outcomes.
• Project objectives, constraints, and success criteria.
• List of alternatives and scope implications.
• Cost, schedule, benefit, and risk data for each option.
• Stakeholder requirements and priorities.
• Organizational policies, standards, and governance thresholds.
• Expert judgment, lessons learned, and historical data.

Outputs Produced

• Selected option and approval status.
• Decision log entry with rationale, criteria, and assumptions.
• Updated plans, backlog, or scope baseline as needed.
• Action items, owners, and implementation timeline.
• Communications to stakeholders and teams.
• Risk updates and, if required, change requests.

Trade-offs

• Speed versus analytical depth.
• Inclusiveness versus confidentiality and decisiveness.
• Short-term gains versus long-term sustainability.
• Flexibility to pivot versus commitment and stability.
• Quantitative rigor versus effort and data availability.
• Consensus building versus clear authority and accountability.

Example

A project team must choose between three vendors for a critical component. They agree on criteria: total cost of ownership (30%), delivery lead time (25%), quality history (25%), and scalability (20%). Each vendor is scored 1–5 against each criterion and weighted. The top-scoring vendor offers moderate cost, fast delivery, and strong quality, edging out a cheaper vendor with longer lead times. The decision, rationale, scores, and assumptions are recorded in the decision log, stakeholders are informed, and a contract negotiation action is assigned.

Pitfalls

• Unclear decision rights leading to delays or rework.
• Poorly defined or shifting criteria that distort outcomes.
• Anchoring, groupthink, or confirmation bias influencing conclusions.
• Overanalysis that misses the decision window.
• Ignoring dependencies, compliance needs, or long-term impacts.
• Failure to document and communicate the rationale and assumptions.
• Not revisiting decisions when significant new information emerges.

PMP Example Question

Your cross-functional team cannot agree on two design options. The sponsor wants a fast decision, but stakeholders have different priorities. What should the project manager do next?

1. Choose the lower-cost option to save budget.
2. Escalate the decision to the sponsor immediately.
3. Facilitate a structured decision using agreed criteria and weighted scoring.
4. Delay the decision until more data is available.

Correct Answer: C — Facilitate a structured decision using agreed criteria and weighted scoring.

Explanation: Establishing and applying transparent criteria enables a timely, justifiable choice aligned to objectives. It reduces bias and supports stakeholder buy-in without unnecessary escalation.