Beyond the Critical Path: Why Projects Need an Execution Perspective

Beyond the Critical Path: Why Projects Need an Execution Perspective

By Dariusz Wołejszo & David Wallach

Anyone who has spent time in serious project planning meetings will recognise a particular moment.

The schedule is on the screen. The team is reviewing activities one by one. Engineers, construction managers, planners, operations representatives and project managers are gathered around the table, discussing how the project will unfold.

At first, everything looks fine.

The logic flows correctly.

Durations seem reasonable.

The Critical Path is clearly visible.

From a scheduling perspective, the plan appears solid.

But then the discussion slows down around a particular part of the project.

Someone points at a sequence of activities and says quietly:

"This part will be difficult."

No formula in the schedule produced that conclusion.

No indicator highlighted the issue.

The comment comes from experience.

Perhaps the activity involves integrating several systems delivered by different contractors, where even a small coordination failure could stop progress across multiple work fronts.

Perhaps a sequence of activities must be executed within a very narrow operational window, where engineering completion, material delivery, construction readiness and operations availability all have to align almost perfectly.

Perhaps the work depends on a limited number of highly specialised experts whose availability cannot easily be replaced.

Or perhaps several technically independent activities suddenly become tightly coupled during execution, meaning that delays or coordination issues in one area immediately propagate into several others.

Situations like these are common in complex projects. They are not simply questions of duration or schedule logic. There are questions of how demanding the work becomes for the organisation responsible for delivering it.

Everyone in the room understands that such phases of the project will require far more coordination, preparation and management attention than others.

Yet when you look at the schedule itself, these differences are almost invisible.

For more than half a century, the Critical Path Method (CPM) has helped project teams understand how time flows through a project. It remains one of the most powerful ideas in project management and a fundamental tool for planning complex work.

CPM answers a critical question extremely well:

Which activities determine when the project will finish?

But in complex projects, another question often proves just as important:

Which parts of the project will be the hardest to execute?

And it is precisely this difference—between what is critical in time and what is difficult in execution—that often determines whether a project runs smoothly or struggles during delivery.

The Missing Perspective in Project Planning

Traditional schedule analysis focuses primarily on time relationships. Durations, logic links, and float calculations help planners understand how delays propagate through the network and which activities determine the completion date.

This perspective is essential and remains the foundation of modern scheduling practice.

However, large engineering and infrastructure projects rarely fail because planners misunderstood the schedule logic. More often, difficulties arise because the complexity of execution was underestimated.

Activities that appear simple in the schedule may, in reality, involve significant coordination challenges. A commissioning activity might require multiple disciplines—automation engineers, electrical teams, vendors and operations personnel—to work in tight coordination. A shutdown intervention may depend on strict safety procedures, narrow operational windows, and precise task sequencing.

These realities are well understood by experienced project teams, yet they are rarely represented explicitly in the schedule model itself.

As a result, schedules may appear technically correct while still containing areas where execution becomes extremely demanding.

Introducing the Critical Effort Method™

The Critical Effort Method™ (CEM) was developed from years of practical experience in project management and project controls environments where execution complexity repeatedly shaped project outcomes.

The idea behind the method is straightforward.

If planners can analyse time sensitivity using the Critical Path Method, they should also be able to analyse execution difficulty within the schedule.

CEM introduces a structured way to evaluate the demand different activities place on the project organisation responsible for delivering them.

Rather than replacing CPM, the method complements it. CPM identifies activities that control the project's completion date, while CEM highlights areas where the project team may face the greatest operational pressure.

At the core of the method is the evaluation of several Effort Drivers, including:

• technical complexity
• coordination requirements between disciplines
• interface density between teams and systems
• dependency on specialised resources
• approval and governance constraints

These factors reflect the practical conditions that make certain activities more challenging to execute than others.

By evaluating these drivers during planning workshops, project teams can identify where execution difficulty is likely to concentrate within the schedule—long before the project reaches those phases.

When Execution Difficulty Is Discussed Early

Introducing an execution perspective changes the nature of planning discussions.

Instead of focusing exclusively on durations and logic links, teams begin to explore how the work will actually be delivered.

Questions start to emerge naturally.

How many parties must coordinate during this activity?

Do we depend on scarce expertise?

Are there operational constraints that may affect sequencing?

Will approvals or external stakeholders influence the timing of the work?

These discussions often lead to more realistic planning decisions.

Activities that involve significant execution complexity benefit from greater planning detail and closer monitoring. Routine tasks can remain simpler.

In this way, planning effort is focused where complexity truly exists, helping organisations achieve a more balanced, practical level of schedule detail.

Earlier Risk Recognition

Execution difficulty is closely connected to project risk.

Activities that require intensive coordination, constrained work environments, or specialised expertise are often the same activities in which delays or operational conflicts may arise.

When effort drivers are evaluated early in the planning process, potential risks become visible much sooner.

This often leads to stronger risk identification workshops and more meaningful risk registers. Instead of relying solely on theoretical scenarios, teams can link risks directly to activities that already indicate elevated execution complexity.

As a result, mitigation strategies can be developed earlier and with greater clarity.

Stronger Interface Management

Complex projects frequently struggle with interface management. Multiple contractors, engineering disciplines and operational teams must align their work, and misunderstandings can easily occur.

One of the dimensions examined in CEM is interface density—the number of interactions required among teams or systems to complete an activity.

When this aspect is analysed during planning, interface challenges become visible much earlier.

Activities with high interface density naturally prompt discussions about ownership, communication pathways and coordination mechanisms. This early clarity allows project teams to define responsibilities before execution begins.

In large multidisciplinary projects, improving interface clarity alone can significantly reduce coordination failures later in the project.

A More Predictable Project Environment

Many project tensions arise from uncertainty.

Unexpected coordination problems, underestimated technical complexity or late discovery of operational constraints can create significant pressure across the project team.

When execution difficulty is discussed openly during planning, teams are simply better prepared.

Expectations become clearer.

Complex phases receive appropriate attention.

Communication improves.

In many cases, this results in a more predictable working environment and reduces the stress that often accompanies poorly understood phases of a project.

What Organisations Gain from an Execution Perspective

When organisations introduce an execution perspective into planning, several practical benefits begin to emerge.

Project plans tend to become more realistic as discussions move beyond durations and focus on how work will actually be performed.

Risk identification improves as complex activities attract earlier attention during planning workshops.

Teams also gain a clearer sense of the appropriate level of schedule detail, focusing analytical effort on activities where coordination complexity truly matters.

Interface management becomes more structured because dependencies between teams are identified earlier.

Most importantly, projects gain something that matters greatly to senior management: a higher probability of project success.

When execution difficulty is considered early in the planning process, the project team develops a more realistic understanding of what it will actually take to deliver the work. Coordination challenges are anticipated earlier, risks are addressed sooner, and the schedule reflects not only when activities should occur but also how demanding they will be to execute.

As a result, the project is far more likely to achieve the objectives defined at the beginning—delivering the expected scope within the planned time and cost boundaries.

For senior leadership, this visibility is extremely valuable. Instead of reacting to emerging problems during execution, organisations can anticipate where attention, coordination and leadership will be needed most.

CPM and CEM: Complementary Perspectives

The Critical Effort Method does not attempt to change the mathematical foundation of project scheduling.

The Critical Path Method remains essential for understanding time dependency and forecasting completion dates.

What CEM adds is another perspective.

CPM answers the question:

Which activities determine when the project will finish?

CEM asks a different question:

Where will the project require the greatest execution effort?

Together, these perspectives create a far more complete understanding of project delivery.

The schedule reveals not only how time flows through the work, but also where operational complexity and coordination pressure are likely to concentrate.

A Shift in How Projects Are Planned

In many ways, the Critical Effort Method represents a shift in planning perspective rather than simply another analytical tool.

Experienced planners have always recognised that some activities are harder to deliver than others. Until now, that knowledge has often existed only in conversations, workshops and personal experience.

CEM attempts to bring that practical knowledge directly into the planning framework.

By making execution difficulty visible early, project teams can prepare more intelligently for the most demanding parts of their work.

And in complex projects, preparation is often the difference between a schedule that exists on paper and a project that can actually be delivered.

The full Critical Effort Method™ framework, including its analytical indicators and implementation approach, is described in the authors’ methodology paper. The authors encourage discussion, experimentation and practical application of the concept within the global project management and project controls community.

Because in real projects, understanding when work must occur is only part of the story.

Understanding how difficult that work will be to execute may be just as important.