HKSM

A technique to compare feasible options for addressing performance gaps or making control decisions. It evaluates impacts such as cost, schedule, risk, and value to choose the most effective response. It supports governance by enabling transparent, criteria-based choices.

Key Points

• Used when performance deviates from plan or a decision is needed on corrective, preventive, or recovery actions.
• Compares multiple viable options against clear criteria like time, cost, risk, quality, and value.
• Facilitated collaboratively to surface assumptions, constraints, and trade-offs.
• Relies on current data and thresholds from the governance framework.
• Produces a documented, traceable recommendation for approval and implementation.

Purpose of Analysis

Choose the option that best restores control, optimizes outcomes, and aligns with objectives and constraints.

• Identify the most effective response to variances and emerging risks.
• Balance trade-offs across cost, schedule, scope, quality, and compliance.
• Provide evidence to justify change requests and updates to plans.
• Enable timely, defensible decisions within governance thresholds.

Method Steps

• Frame the decision: define the problem, objectives, constraints, and decision horizon.
• Gather data: performance reports, forecasts, risks, dependencies, and resource availability.
• Generate alternatives: brainstorm with SMEs, consider do nothing, minimal change, and bold options.
• Shortlist feasible options: remove those that violate constraints or policies.
• Define evaluation criteria and weights with stakeholders.
• Analyze impacts: estimate cost, schedule, risk exposure, quality, benefits, and compliance for each option.
• Run trade-off techniques: decision matrix, what-if scenarios, and sensitivity checks.
• Select and justify: recommend the top option with rationale and assumptions.
• Seek approval per governance process, then implement and monitor results.

Inputs Needed

• Approved baselines for scope, schedule, and cost.
• Performance data, variances, and forecasts.
• Risk register, issue log, and dependencies.
• Resource availability and budget constraints.
• Quality metrics, acceptance criteria, and compliance requirements.
• Organizational policies, decision thresholds, and escalation paths.
• Stakeholder priorities and success criteria.

Outputs Produced

• Recommended action with trade-off rationale and assumptions.
• Change requests for corrective, preventive, or defect repair actions.
• Updates to plans, forecasts, and baselines as approved.
• Decision log entries and communication updates.
• Risk and issue updates reflecting chosen option.
• Lessons learned for future decision-making.

Interpretation Tips

• Use weighted criteria to reflect what matters most to sponsors and customers.
• Quantify impacts where possible; use ranges when uncertainty is high.
• Check alignment with strategic goals and compliance obligations.
• Consider opportunity cost and long-term maintainability, not just the immediate fix.
• Run sensitivity analysis to see if small estimate changes flip the decision.
• Document why options were rejected to maintain auditability.

Example

A project is six weeks behind due to a vendor delay. The team considers four options: crash critical activities with overtime, fast-track by overlapping testing and development, defer a low-value feature to a later release, or accept the delay.

• Criteria and weights are set: schedule recovery 40 percent, cost impact 25 percent, risk 25 percent, customer value 10 percent.
• Scoring shows fast-tracking plus deferring a low-value feature yields a four-week gain with moderate risk and minimal cost increase.
• The PM recommends this option, submits a change request, updates forecasts, and records the decision rationale.

Pitfalls

• Generating too few options and missing a better path.
• Basing decisions on outdated or biased data.
• Ignoring risk exposure and downstream quality impacts.
• Over-analyzing and delaying action when time-boxing is needed.
• Using criteria that do not reflect sponsor priorities.
• Failing to document assumptions and constraints.

PMP Example Question

During control activities, the team identifies a significant cost overrun risk for a critical work package. What should the project manager do first to select the best response?

1. Approve the least expensive option to minimize further overruns.
2. Ask the sponsor to choose an option based on strategic priorities.
3. Conduct alternative analysis using agreed criteria and current data to compare feasible options.
4. Escalate immediately and halt the work until a decision is made.

Correct Answer: C — Conduct alternative analysis using agreed criteria and current data to compare feasible options.

Explanation: The PM should lead a structured comparison of viable responses before selecting one. This ensures a transparent, criteria-based decision aligned with governance and current performance data.