Have you ever validated a strategic roadmap in an executive committee, only to realize three months later that almost nothing had moved forward?

This is the great paradox of ambitious organizations. You have clarified your vision, identified your growth levers, and structured coherent initiatives. Yet, when it comes to taking action, you hit the wall of reality: limited human resources, constant operational overload, and difficult trade-offs.

Yet, you evaluated the initiatives by the book. You determined priority projects based on their impact on the organization and their ease of implementation. But while this priority matrix may seem perfect on paper, its evaluation often relies on major biases that ruin execution in the field.

Today, I am sharing with you the 5 traps to avoid when evaluating your projects, as well as the method to ensure realistic and effective prioritization.

1. Integrate Pessimistic Scenarios To Neutralize Feasibility Optimism

The feasibility assessment of a project almost always suffers from optimistic blindness within teams.

When evaluating the effort or time required to complete an initiative, we systematically underestimate human and technical complexity. More stakeholders in a project means added risks of friction, delays, or poor communication. The same applies to the adoption of new tools or processes. Behavioral change always takes longer than installing software.

To correct this bias, you must force your team to evaluate feasibility from three distinct angles:

• The optimistic scenario: everything goes smoothly, and change is immediate.
• The realistic scenario: slight delays occur, and adoption requires moderate support.
• The pessimistic scenario: major technical setbacks occur, and key teams lack availability.

Integrating these three visions from the evaluation phase transforms naive estimation into a solid and resilient plan. You can then better track the early warning signs of losing control and intervene proactively.

2. Moderate The Overestimation Of Financial Impacts By Testing Your Hypotheses

It is just as easy to overestimate the positive returns of a project as it is to underestimate its complexity.

When developing a solution, teams tend to present an ideal business model where adoption by clients or teams is total and immediate. However, a theoretical impact calculated in a spreadsheet rarely reflects the reality of operations. Without prior validation of your underlying hypotheses, you risk giving absolute priority to an initiative whose real value will only be a fraction of the initial projections.

Before validating the impact score of a strategic initiative, apply this verification protocol:

• Isolate critical hypotheses: identify the 2 or 3 fundamental conditions without which the financial gain collapses.
• Evaluate the level of evidence: determine if this impact is based on internal historical data, market trends, or mere intuition.
• Require a micro-test: launch a small-scale experiment to validate real receptivity before unlocking the overall budget.

Putting your impact hypotheses to the test will prevent you from investing precious resources in false opportunities. Validating hypotheses will allow you to better master the conditions for success and ensure adequate follow-up.

3. Limit The Number Of Major Initiatives Per Leader

By wanting to do too much at once, your teams end up accomplishing nothing significant.

Strategic priority should not be evaluated in a theoretical vacuum, but based on the teams' real absorption capacity in the field. Project managers do not work full-time on their new initiatives. They must continue to ensure the management of day-to-day business. When you overload a leader with five or six simultaneous strategic projects, their bandwidth collapses, stress increases, and no deliverable reaches the required quality level.

To preserve your organization's execution capacity, implement strict capacity rules:

• The 3-project maximum rule: no manager should lead more than 3 strategic initiatives in parallel.
• Current load inventory: account for regular operational responsibilities before entrusting a new project.
• The “One In, One Out” principle: for every new initiative assigned to a manager, pause or delegate an existing initiative.

Protecting your leaders' time is the sine qua non condition for maintaining a high execution cadence. Ignoring the effective load of teams constitutes a voluntary blindness that eventually affects the ease of implementation.

4. Break Down Any Project Longer Than Two Quarters Into Autonomous Operational Phases

You eat an elephant one bite at a time, and the same goes for your organization's transformation.

Committing resources to a massive project that will only deliver its first results after 12 or 18 months is one of the surest ways to exhaust your teams and lose momentum. Overly vast projects discourage stakeholders, lack intermediate checkpoints, and adapt very poorly to changes in the business context. Conversely, sequencing your deliverables allows you to validate value step by step and adjust course quickly.

If an initiative spans more than two quarters, you must break it down according to this scheme:

• Phase 1 (Quarter 1): development of a prototype or pilot producing measurable value immediately.
• Phase 2 (Quarter 2): expanded deployment and integration of field feedback.
• Phase 3 (Quarter 3+): industrialization, automation, and optimization at the organizational level.

Sequencing your projects into autonomous milestones ensures quick wins that keep team motivation at its peak. Revisit the "small wins" necessary for change management, proposed by John Kotter, to succeed in your transformations.

5. Directly Involve Execution Managers From The Design Phase

Working in silos at the executive committee level guarantees a strategy disconnected from operational reality.

The majority of errors in evaluating feasibility, costs, or deadlines occur because the people who will implement the solution are not consulted during its development. By designing projects in an "ivory tower," you lack perspective on the technical and human details that condition success. Furthermore, imposing a solution designed without them creates natural resistance among teams, which slows down implementation.

To create strong engagement and obtain accurate estimates, adopt this collaborative approach:

• Co-design the solutions: involve operational leaders in drafting execution scenarios.
• Have the effort quantified by the delivery teams: let field teams estimate the deadlines and necessary resources themselves.
• Validate success conditions together: ensure that teams validate and fully adhere to the set objectives.

By involving your teams from the design phase, you transform potential resistance into an execution engine. Work together to understand the issues and optimize the solutions.

Your Checklist For The Next Strategic Review

To ensure that your next prioritization session leads to a realistic and effective action plan, check these 5 boxes before any final decision:

1. The initiatives have been modelled according to optimistic, realistic, and pessimistic scenarios.
2. Financial impact hypotheses have been identified and tested on a small scale.
3. No leader is assigned more than 3 strategic initiatives simultaneously.
4. All projects with a duration of more than 6 months have been broken down into quarterly phases.
5. The teams in charge of implementation participated in defining the solutions.

By mastering these risks upstream, you will considerably increase the precision of your evaluations and the chances of success of your transformation.

It’s your turn. Good strategic action!

​Eric L’Heureux