Critical Path
The specific sequence of tasks in a project schedule that determines the shortest possible time the whole project can take: a delay to any task on this path delays the entire project's finish date, while delays to other tasks might not.
Why it matters
Not every delay is equal. Understanding which tasks are actually on the critical path is what tells a project team where to focus their attention when something starts slipping, instead of treating every schedule hiccup as equally urgent.
On a real project
A scheduler's software shows that framing, drywall, and final inspection form the critical path on a project, while landscaping, which can happen anytime before closeout, has weeks of flexibility. A three-day rain delay to framing pushes the whole project back three days; the same delay to landscaping might not move the finish date at all.
Who this matters most to
A Scheduler builds and maintains the schedule logic that identifies exactly which tasks are critical, updating it as the project actually progresses. A Project Manager uses that critical path analysis to decide where to spend money on overtime or extra crews when the project needs to catch up.
Where this goes wrong
A project manager throws extra crews and weekend overtime at a task that's running behind, without checking whether it's actually on the critical path. The task catches up, but the project's finish date doesn't move at all, because a different task the team never looked at was the one actually driving the completion date the whole time; the extra money was spent on the wrong problem.
Explore next