Capital project prioritization often breaks down long before the scoring starts. Maturity, human judgment, and organizational capacity ultimately determine whether the process succeeds or frustrates everyone involved.

This difference leads to different behaviors. In NPV, a higher discount rate reduces the value of future benefits, often favoring projects with earlier returns. In NPC, a higher discount rate reduces the weight of future costs, which can make large, long‑duration, back‑loaded projects appear more attractive. This is why discount‑rate selection is a policy decision that shapes which alternatives rise to the top.

Trusted advisors ask questions that encourage deep reflection and critical thinking in situations of complexity and uncertainty. They help decision makers explore different perspectives and consider various scenarios, enabling them to make more informed decisions.

If the discount rate is set too high, long‑term or multi‑phase projects are distorted. In NPV analysis, a high discount rate suppresses future benefits, making long‑horizon projects appear unattractive. In NPC analysis (common in public‑sector evaluations), a high rate can have the opposite effect: it heavily discounts high costs in the outer years and can make multi‑phase, back‑loaded projects appear artificially inexpensive.

Organizations typically rely on three common techniques to evaluate capital projects. Each has its place, but only one consistently supports sound long-term decisions.

Large projects are usually more important and tend to score or rank highly. However, because of their size, they may score or rank extremely low, as they eliminate many smaller projects that reviewers may consider necessary.

Taking a business case approach, where options ranging from “status quo” to “do everything (merge), is the best approach. Focus early on higher-level evaluations of financials, infrastructure, human resources, and information technology systems.

For project managers, focusing on the six essential visuals within the Illustrate bone of the FINESSE Fishbone Diagram® is very helpful.

The power of systems thinking lies in recognizing that effectiveness comes from integration, not perfection.

My rule of thumb is that 1200 words correlate to 10 minutes of speaking time.

Master plan developers must recognize participants may have vested positions. The goal is not to eliminate divisions, but to foster understanding and leave room for negotiation. This calls for nuance and sequencing.

Empathy creates bridges. It’s what transforms technical expertise into shared understanding.

Shared risk models have been fairly common over the past 5 years in alternative project delivery for managing cost uncertainty while accelerating delivery.

Hurricane Helene's aftermath presents a clear case study of why capital projects can stall before money, permits, and regulatory clarity are aligned.

Above all, you build trust, lead with clarity, and make the challenging aspects of projects run more smoothly.

In our training and workshops, we discuss three things that can be used to avoid ethical issues.

It’s easy for those same leaders to cross the line from responsible oversight into operational program delivery.

According to Google, these are the top six topics we published in the last five years that are surging.

Our approach to Program Development is captured in the 3D's – Decisions, Development, and Delivery.

Outside consultants tend to push organizations in this direction. So do project managers from high-reliability organizations or sectors.