A critical path is the logical consequence of a schedule model; its credibility can never exceed the credibility of the assumptions inside that model.
Executives are often shown a line of red activities and told that it is the critical path. The implication is reassuring: the project team knows what drives completion, resources can be focused and the finish date can be defended.
But a critical path is not discovered in the project like a physical constraint. It is calculated from a model. If work is missing, dependencies are artificial, durations are optimistic, calendars are wrong or resources are assumed to exist in two places at once, the calculation can be precise and misleading.
The leadership task is therefore not to accept the red line. It is to understand what must be true for that line—and the promised date—to remain credible.
The Strategic Context
A reliable schedule translates authorised scope into time-based logic. Activities represent work. Dependencies explain sequence. Durations and calendars convert work into forecast dates. Milestones mark significant events. A baseline provides the approved reference against which progress and forecast movement can be assessed.
Critical-path analysis adds an important insight: which sequence of work currently determines the earliest modelled completion date. The US Government Accountability Office Schedule Assessment Guide treats a valid critical path, logical sequencing, reasonable duration, resource consideration, a baseline and schedule risk analysis as connected characteristics of a reliable schedule.
The connection matters. Critical-path calculation is not a substitute for schedule quality. It depends on it.
What Leaders Commonly Misread
The first misreading is that critical means strategically important. An activity may have zero float because of schedule logic while contributing little to enterprise value. A strategically vital activity may have float today but carry safety, regulatory or benefit risk that deserves executive attention.
The second is that the critical path is permanent. Progress, delays, approved changes, resource availability and revised logic can move criticality from one path to another. Near-critical paths can become critical with little warning.
The third is that zero float proves realism. Hard constraints and imposed dates can produce zero or negative float without a feasible execution plan. The schedule may be measuring the distance from a demanded date, not calculating a credible forecast.
The fourth is that milestone status explains schedule health. Milestones compress complexity for leadership, but a green milestone can conceal shrinking float, deferred work, unresolved dependencies or a future convergence of risk.
Reframing the Issue
The critical path should be treated as a conditional forecast:
If the represented scope is complete, the logic is valid, the durations are achievable, the resources are available and the stated calendars apply, this sequence currently determines the earliest finish.
This statement is less convenient than a promised date, but more useful. It directs attention to the quality of the model and the conditions leadership can influence.
A Schedule Begins with Complete Scope
Critical-path analysis cannot find work that is absent. The schedule must be traceable to the work breakdown structure and include more than visible production activity.
Frequently omitted work includes:
- approvals and decision lead times;
- procurement and logistics;
- design reviews and assurance;
- testing, defect correction and retesting;
- data preparation and migration;
- operational training and readiness;
- external interfaces;
- handover documentation; and
- regulatory or customer acceptance.
When this work is added late, the project appears to suffer new delay even though the exposure existed from the beginning.
Related article: The Work Breakdown Structure Is a Control Architecture
Dependencies Are Management Assumptions
A dependency should describe a real relationship, not a preferred sequence or a convenient presentation. The common finish-to-start relationship means one activity must finish before another begins. Other relationships allow overlap or link starts and finishes, but they require clear rationale.
Poor schedules often contain two opposite errors.
Missing logic: Activities float independently, so delays do not propagate to completion. The model cannot forecast consequence.
Excessive constraint: Dates are manually fixed to match a target, so logic cannot reveal what actually drives them. The model becomes a calendar of intentions.
Leads and lags require particular care. A lag such as “wait 20 days” hides the nature of the work or condition. If the period represents curing, regulatory review or shipping, a named activity usually creates better ownership and visibility.
Duration Is Not Effort
An activity requiring 200 hours of work does not automatically take five people one week. Duration depends on how work can be divided, resource productivity, hand-offs, working calendars, access constraints and uncertainty.
Adding people may reduce duration where work is divisible and coordination costs are low. It may have little effect where specialist judgement, physical sequence or learning dominates. In some work, additional resources increase communication and rework.
Executives should challenge long durations because they hide detail and short durations because they may be administratively impossible to monitor. Neither is inherently wrong. The question is whether the duration reflects executable work and produces useful control signals.
Float Is Strategic Information—With Caveats
Total float represents the amount an activity can move before affecting the modelled completion date, given the current logic. It is not spare time owned by a team or supplier. Using it changes the flexibility available to the whole system.
Free float is narrower: movement possible without affecting the early start of a successor. Both measures can help leaders distinguish immediate drivers from work that has flexibility.
But float is sensitive to constraints, calendars, progress and imposed dates. Negative float can indicate that the schedule cannot meet a required date under current assumptions. Large positive float can reveal missing logic rather than genuine flexibility.
Leadership should therefore ask not only “What is the critical path?” but also:
- Which paths are near-critical?
- Where is float being consumed fastest?
- Which constraints manufacture the result?
- Which interface has no contingency?
- What changes when resources are levelled?
Milestones Should Mark Decisions and Outcomes
Milestones are zero-duration events. They are useful when they represent a consequential point: approval granted, design accepted, site available, regulatory evidence submitted or operational readiness demonstrated.
They are less useful when used as decorative reporting markers. “Phase complete” has little control value if completion criteria are ambiguous.
Executive milestones should connect to decisions. A gate should state the evidence required, the authority deciding and the consequences of approval, conditional approval or rejection. This converts the schedule from a presentation of dates into a sequence of commitments.
Baselines Must Remain Stable and Legitimate
A baseline records an approved plan. It permits the organisation to distinguish performance variance from authorised change. Without stability, every delay can be absorbed into a new plan and historical accountability disappears.
Stability does not mean immobility. Material scope changes, external decisions or formally governed resets may justify baseline change. The change should preserve an audit trail: what changed, why, who approved it, which assumptions moved and how future performance will be measured.
The forecast and baseline also serve different purposes. The baseline records commitment. The current schedule should show the best available forecast. Forcing the forecast to remain equal to the baseline hides reality; constantly changing the baseline hides performance.
Related article: Change Control Is Capital Allocation in Disguise
Decision Framework
Leaders can test schedule credibility through eight questions.
| Test | What to examine |
|---|---|
| Scope | Is all delivery, interface, assurance and transition work represented? |
| Logic | Do dependencies describe real physical, technical or decision relationships? |
| Duration | Are estimates supported by work, resources, calendars and evidence? |
| Resources | Can constrained people and assets execute the plan? |
| Criticality | Are critical and near-critical paths plausible? |
| Float | Is flexibility real, traceable and protected from artificial constraints? |
| Baseline | Is the approved reference stable while the forecast remains current? |
| Risk | Has uncertainty been analysed rather than hidden in padding? |
No software indicator can replace these tests. A scheduler can calculate the model; accountable leaders must judge whether it represents reality.
From Strategy to Execution
Immediate action: Request a schedule-quality review before accepting the completion date. Examine open ends, constraints, long activities, resource assumptions, near-critical paths and missing acceptance work.
Medium-term capability: Establish schedule coding and governance standards across the portfolio. Require traceability to WBS, risk, cost and decision milestones. Develop competent planners who can explain logic rather than merely operate software.
Long-term positioning: Use integrated schedules to coordinate programs and portfolios. Major dependencies should connect across project boundaries so leaders can see where one initiative controls the benefits of another.
Signals to Monitor
- The critical path runs through generic management or summary activities.
- It changes dramatically after routine status updates.
- Most activities have the same duration or finish on reporting dates.
- Large numbers of hard constraints force the target finish.
- Resource levelling is absent despite shared specialists.
- Milestones remain green while float collapses.
- Completed work is recorded without objective evidence.
- The forecast date never moves even when critical work is late.
Questions for the Leadership Team
- What must be true for the current critical path to remain valid?
- Which omitted activity is most likely to appear late?
- What near-critical path could become the real driver next month?
- Which imposed constraint is shaping the forecast?
- Are scarce resources reflected in the model or assumed to be unlimited?
- What decision milestone lacks explicit entry and acceptance evidence?
- Does the current schedule show our best forecast or merely repeat the baseline?
Closing Perspective
The critical path is powerful because it converts thousands of activities into a view of schedule consequence. It becomes dangerous when its apparent precision discourages leaders from examining the model beneath it.
Executives should not ask planners for certainty they cannot provide. They should demand transparent logic, evidence-based assumptions and a forecast that changes when reality changes. The date is not the control system. The quality of the reasoning behind it is.
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.