F0052: WACC Update & Hurdle Rate Framework

Context

Context: annual planning or rate-shift environments creates recurring decisions where stakeholders interpret WACC, beta, and cost of debt differently. The organization needs a standard way to compare options using capital structure, market risk premium, and credit spreads so that debates do not restart each cycle. Without a common frame, the project acceptance versus risk discipline is decided implicitly and accountability weakens. A shared decision log also helps teams learn which assumptions held and which broke under stress.

Options

• Option A: Preserve the current approach to minimize short-term disruption, accepting limited upside.
• Option B: Run a phased change, validate results against agreed metrics, and scale only after thresholds are met.
• Option C: Redesign the approach end-to-end to pursue larger gains, with higher implementation effort and risk.

Decision

Decision: Choose Option B. Sequence the rollout so early results validate WACC, beta, and cost of debt targets, and stop or adjust if assumptions fail. Assign owners, document constraints, and schedule a review checkpoint to avoid drift.

Rationale

Rationale: Option B balances project acceptance versus risk discipline while preserving flexibility if market conditions move. It allows the team to test capital structure, market risk premium, and credit spreads assumptions and protect against the main risk: using outdated betas that distort project ranking. Phasing also improves organizational buy-in because progress is visible and accountability is explicit. The approach generates evidence that improves the next decision cycle.

Risks

• Weak data quality can obscure changes in WACC, beta, and cost of debt, making it hard to validate the decision.
• Execution drag may delay learning and leave the organization exposed to using outdated betas that distort project ranking longer than planned.

Next

Next: Confirm ownership, finalize the baseline for WACC, beta, and cost of debt, and document capital structure, market risk premium, and credit spreads assumptions in a shared log. Schedule the first review, define stop conditions, and communicate the plan to affected teams. Capture lessons learned so the framework improves with each cycle.