What it means
Big projects die in the gaps between tasks. PERT, the Program Evaluation and Review Technique, was built by the US Navy in the 1950s to manage the Polaris missile programme, where thousands of contractors had to finish in the right order.
A PERT chart draws the project as a network, with nodes as tasks or milestones, arrows showing which tasks must finish before others can start, and duration estimates on each task. Its signature feature is probabilistic time estimation: instead of one duration, planners estimate optimistic, most likely, and pessimistic times for each task, then combine them into a weighted expected duration.
Estimating three durations per task also disciplines teams to think about uncertainty explicitly, and the gap between optimistic and pessimistic estimates flags the risky tasks before a single day is lost. The chart's payoff is the critical path: the longest connected chain of dependent tasks.
Any delay on that path delays the whole project, while tasks off the path carry slack and can slip without consequence. This distinction changes where management attention goes, as resources flow to critical tasks and managers stop panicking about delays that sit comfortably inside slack.
PERT's sibling is CPM, the critical path method, developed around the same era with deterministic durations. Modern project software blends the two, and the Project Management Institute treats network diagrams and critical path analysis as core scheduling knowledge.
The technique shines on one-off projects with uncertain durations, such as construction, product launches, events, and system migrations, while routine repetitive work needs simpler tools. For a non-finance manager, the practical use is the conversation the chart forces: list every task, admit dependencies honestly, estimate ranges instead of false precision, and find out which three tasks actually decide your deadline.
The chart also needs maintenance to stay useful, because as tasks complete and estimates firm up, the critical path can jump to a different chain, and managers who draw the diagram once and frame it miss the shifts entirely.
In practice
Real-world examples.
Example
A construction manager discovers through PERT analysis that foundation curing time, not material deliveries, forms the critical path, and resequences interior work around it. Resequencing work around a slow critical task is often worth more than any amount of hurry elsewhere.
Example
A product team estimates testing at optimistic two weeks, likely four, pessimistic nine; the weighted estimate of four and a half weeks feeds the schedule honestly.
Example
Weekly reviews track only critical-path tasks in detail, while tasks with six weeks of slack are monitored at a summary level.
Formula
Calculation
Expected task duration equals the optimistic estimate plus four times the most likely estimate plus the pessimistic estimate, all divided by six. Project duration is the sum of expected durations along the critical path, the longest dependent chain through the network.
Worked example of one task. Testing is estimated at 2 weeks optimistic, 4 weeks most likely and 9 weeks pessimistic. The expected duration is (2 + 4 x 4 + 9) / 6 = 27 / 6 = 4.5 weeks. A common spread measure is (pessimistic - optimistic) / 6 = 7 / 6, or about 1.2 weeks.
Worked example of a network. Chain one runs design (3 weeks), build (6 weeks) and testing (4.5 weeks), which totals 13.5 weeks. Chain two runs procurement (5 weeks) and installation (4 weeks), which totals 9 weeks. The longest chain is chain one, so the critical path is 13.5 weeks, and chain two has 13.5 - 9 = 4.5 weeks of slack.Case study
Seen in the real world.
This case study is fictional and illustrative. A made-up events company in Melbourne is given eleven weeks to stage a 5,000-delegate conference. The project lead maps 34 tasks into a PERT network: venue contracts, staging, speaker bookings, marketing, catering, registration systems, each with optimistic, likely, and pessimistic durations.
The chart exposes a surprise: the critical path runs through the registration platform integration, a task nobody had flagged, with zero slack against the go-live date. The lead reassigns two engineers to it and accepts slip on brochure printing, which carries three weeks of slack. The conference opens on time with 4,900 delegates registered, and the post-mortem credits the network diagram with finding the real bottleneck before it found them.
Watch out
Common mistakes.
- Treating the optimistic estimate as the plan, which builds schedules that only a perfect world could meet.
- Hiding dependencies to make the chart look simple; omitted links between tasks are where projects actually break.
- Managing every task with equal urgency, which starves critical-path work while polishing tasks that had weeks of slack. Priority follows the path, not the noise.
Questions
People also ask.
What is the critical path?
The longest chain of dependent tasks through the network; its total duration sets the earliest possible project finish, and any delay on it delays the project.
How does PERT estimate task duration?
It averages optimistic, most likely, and pessimistic estimates with weights of one, four, and one, divided by six, giving more weight to the likely case.
How is PERT different from CPM?
PERT uses probabilistic three-point duration estimates for uncertain work; CPM uses fixed durations and cost trade-offs, and modern practice blends both. The blend is what most scheduling software computes.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%