What is the Critical Path?

Critical Path in Practice

Simple example: a website project has these tasks with these durations and dependencies:

Identifying the Critical Path

In the example above, two paths exist:

Path A: Discovery → Wireframes → Design → Development → Testing = 1+1+2+3+1 = 8 weeks

Path B: Discovery → Content writing → SEO setup = 1+2+1 = 4 weeks

Path A is the critical path — it's the longest at 8 weeks, so the project minimum duration is 8 weeks. Path B has 4 weeks of float (it could take up to 8 weeks total without delaying the project end date).

Any delay to Design, Development, or Testing delays the project. A delay to Content writing only matters if it exceeds 4 weeks of float.

How to Protect the Critical Path

Project managers protect the critical path by:

Prioritizing resources — assign your best people to critical path tasks, not the most interesting tasks.

Buffering — add a small time buffer to critical path tasks that have high uncertainty.

Fast-tracking — perform critical path tasks in parallel where possible (start development in a phase that's done while other phases continue).

Crashing — add resources to critical path tasks to reduce their duration when the project is behind schedule. This costs more but reduces time.

Early warning — track critical path tasks more closely than other tasks. A one-day slip today may cascade into a one-week delay at the end.

Finding the Critical Path: Step-by-Step

Identifying the critical path is a systematic process, not a guess.

Step 1: List all project tasks. Work from your WBS or task list.

Step 2: Identify dependencies between tasks. For each task, ask: what must be finished before this can start?

Step 3: Estimate duration for each task. Use historical data if available — your time tracker's data on previous similar projects is the most reliable source.

Step 4: Draw the network diagram. Connect tasks with arrows representing dependencies. You'll see paths forming — sequences of connected tasks from project start to project end.

Step 5: Calculate the duration of each path. Add up the durations of all tasks on each path from start to finish.

Step 6: The longest path is the critical path. Any delay to any task on this path delays the project end date by the same amount.

For most agency projects with 20-50 tasks, this can be done in a spreadsheet or project management tool in an hour.

• Step 1: List all tasks from your WBS or project plan
• Step 2: Define finish-to-start dependencies between tasks
• Step 3: Estimate duration per task using historical data or owner estimates
• Step 4: Map the network — draw or model all task connections
• Step 5: Calculate total duration of each path through the network
• Step 6: The longest path = the critical path = the project's minimum duration

Critical Path in Multi-Team Projects

When multiple teams work in parallel on the same project, the critical path becomes more complex and more important. Each team has its own work sequences, but the critical path spans all of them — it's the longest chain of dependencies across the entire project.

The most common problem: each team manages its own workstream but nobody owns the cross-team critical path. Team A finishes on time. Team B finishes on time. But the integration step where both pieces come together is blocked because nobody tracked the dependency between them.

For a 10-person agency running a project with a design team and a development team, the critical path typically looks like: Discovery → Wireframes → Design approval → Development → QA → Launch. The design-to-dev handoff and the client approval step are where multi-team critical path failures most often occur.

Practical management requires one person owning visibility across all workstreams — typically the project manager. Their job is not to manage each team's internal tasks, but to track handoffs and flag when a cross-team dependency is at risk.

• The critical path spans all teams — it's not just within one team's work
• Handoff points between teams are the highest-risk nodes on the critical path
• One person (typically PM) must own visibility across all workstreams
• Weekly cross-team standup focused on handoffs is more useful than per-team standups

Critical Path vs Critical Chain

Critical Path Method (CPM) and Critical Chain Project Management (CCPM) both identify the longest sequence of tasks in a project, but they handle uncertainty differently.

Critical Path Method treats task duration estimates as fixed. In practice, people add safety margin into their individual task estimates to protect against uncertainty — so the schedule is padded everywhere, and projects still run late because people use the padding they were given.

Critical Chain Method removes individual task padding and consolidates it into project buffers placed at strategic points — at the end of the critical chain. Individual tasks look aggressive, but the project has explicit buffers to absorb variation.

For teams of 4-25 people running projects under 3 months, CPM is generally sufficient. CCPM delivers its biggest advantages on large, complex projects where individual padding compounds across hundreds of tasks into significant schedule bloat.