Step-by-step methods

Prioritised for recurring project work: Make the no-action option explicit, then compare complete expected costs. Keep financial efficiency separate from whether the worst case is tolerable.

Before using it: Describe events, consequences and assumptions before assigning numbers.

Prioritised for recurring project work: Discount each future cash flow to a common date using a consistent period and price basis. Then test the assumptions that drive the result.

Before using it: Define the intended outcome and who will measure it.

Prioritised for recurring project work: The critical path is the longest duration chain through a valid dependency network under the schedule’s assumptions. It can change as durations and logic change.

Before using it: Check dependencies, duration assumptions and resource availability.

Prioritised for recurring project work: Work from usable time and the skills required. Separate effort from elapsed duration and allow for real operational commitments.

Before using it: Keep effort, elapsed duration and skills distinct.

Use when this specific decision arises: First validate the baseline and actual costs. Then choose the forecast assumption that fits the remaining work, rather than the number that best fits the budget.

Before using it: Use a common baseline, measurement boundary and status date.

Use when this specific decision arises: Discuss distinct scenarios before calculating a weighted average. The explanation for the range is often more useful than the middle number.

Before using it: Define scope, units and the evidence behind the range.