LEARN. PRACTICE. GROW.Build executable options
An approved response can remain infeasible if it needs a team already committed to another delivery. In this workshop, treat money, people, window, and access as distinct constraints. The proposal should state action, expected mechanism, owner, duration, cost, and dependencies. Extra resources can reduce delay but also remove capacity from recovery rehearsal. Check the combination with those providing and receiving the service. In an international project, “two available days” needs a calendar and time zone, not merely a spreadsheet sum. Before comparing benefits, exclude options violating mandatory criteria without authority. Do not use a benefit score to silently offset an integrity constraint. When two teams disagree, expose the trade-off between objectives and bring a concrete decision to the agreed authority, with alternatives and the consequence of waiting.
Enumerate a small combination set
The example has a nine-thousand budget and four capacity days. A costs six thousand, needs three days, and reduces expected loss by twelve thousand. B costs five thousand, needs two days, and reduces it by nine thousand. C costs four thousand, needs two days, and reduces it by eight thousand. We assume incremental reductions without overlap and tasks fitting the calendar; a real service would require evidence for those conditions. There are eight subsets, including no response. A offers expected net benefit six thousand. B and C together cost nine thousand, use four days, and offer expected net benefit eight thousand, the highest among feasible subsets. Selecting only the largest gross benefit would miss this combination. Record rejected options too: A+B and A+C exceed the initial budget and require five capacity days.
Protect assumptions and opportunities
Do not add two loss reductions that remove the same consequence. If B and C share the same mechanism, their seventeen-thousand gross benefit may be overstated. Recalculate the combined effect and retain the previous version to explain the change. For opportunities, identify incremental benefit and who can realize it. Automation can release hours, but that does not equal realized financial savings if costs remain. Sharing execution with a specialist team can make the benefit accessible, with explicit responsibilities and conditions. Improving the chance of a gain does not make it certain. Do not introduce optional work merely to justify already reserved budget. Compare benefits and consequences over the same horizon, confirm what will be measured, and retain an acceptable option when the gain does not materialize.
Lead the decision and track effects
Produce a worksheet of feasible options, resource consumption, expected net benefit, assumptions, and validation owner. For the example, recommend B+C only within the supplied conditions; if budget rises to ten thousand and capacity to five days, A+C offers ten thousand net and beats the earlier proposal. A constraint change can alter the choice without invalidating the earlier analysis. After authorization, confirm owner commitments and execution criteria. If an L3 incident removes the team from the window, update feasibility before retaining old dates in reporting. At closure, distinguish completed action, observed effect, and actually realized benefit. The workshop ends with peer review and a justified decision; the code does not validate real dependencies, reserve resources, or authorize production changes.
// Original educational enumeration of three fictional responses, not a production optimizer.
const responses=[{id:'A',cost:6,days:3,benefit:12},{id:'B',cost:5,days:2,benefit:9},{id:'C',cost:4,days:2,benefit:8}];
function combinations(budget,days){
if(![budget,days].every(x=>Number.isFinite(x)&&x>=0))throw Error('Invalid limits');
const feasible=[];
for(let mask=0;mask<8;mask++){const picked=responses.filter((_,i)=>mask&(1<<i));const sum=k=>picked.reduce((n,r)=>n+r[k],0),cost=sum('cost'),used=sum('days');if(cost<=budget&&used<=days)feasible.push({ids:picked.map(r=>r.id).join('+')||'none',cost,days:used,net:sum('benefit')-cost});}
return feasible.sort((a,b)=>b.net-a.net||a.cost-b.cost||a.ids.localeCompare(b.ids));
}
console.log(JSON.stringify({initial:combinations(9,4),expanded:combinations(10,5)}))With nine thousand and four days, B+C offers eight thousand expected net benefit. With ten thousand and five days, A+C offers ten thousand. The recommendation depends on constraints and the assumption of incremental benefits without overlap.
Common pitfalls
Ranking only by gross benefit, adding overlapping reductions, treating budget as human capacity, counting released hours as saved cash, and retaining a choice after a constraint changes.
Related topics: Compare options and size reserves · Quantitative decisions and value of information · Analyze evidence and priorities
Compare feasible combinations and incremental consequences over the same horizon. The model’s best combination still depends on evidence, authority, and actual resource commitment.
Reference: Collaborative tools and techniques to build the project risk plan · PMI-RMP five-domain ECO, updated-2024 public document