Roy Cobby Researcher with a professional background in marketing and social media management in education and public policy, at business schools, academic journals, and stakeholder-based organizations.

What is a PERT chart and how to make one

9 min read 2627

What Is A PERT Chart And How To Make One

“Can you please draft a PERT chart for next week?”

It happens to the best of us: spend enough time working on a project with a new team, and you’re likely to encounter an unknown term. The tech sector (in truth, any sector) often relies on obscure acronyms to refer to approaches, tools, and methods. That said, PERT charts exist to make your life easier.

In this guide, we’ll define what a PERT chart is, review the technique’s surprising history, and list key benefits of using this approach for product management. We’ll also walk you through a how-to guide and highlight some tools and templates to help you get the most out of your PERT charts.


Table of contents


What is a PERT chart?

A PERT chart is a project management tool designed to help teams visualize tasks and coordinate the timeline of events that must occur during the scope of a project’s lifetime.

PERT stands for Project Evaluation and Review Technique. PERT charts are similar to GANTT charts, but there are key distinctions — namely, that GANTT charts provide an overview of a project’s time dependencies while PERT charts represent task dependencies.

Below is an example of a PERT chart:

PERT Chart Example And Template

What is the purpose of a PERT chart?

In the simplest terms, the purpose of a PERT chart is to help project managers more accurately estimate the amount of time it will take to finish a project.

Using a PERT chart for enables managers and their teams to break down tasks within a project, which makes it easier to schedule tasks and map them to individuals scoped to do the work.

The extraordinary (and secret) history of the PERT chart

Next time you struggle while building your PERT chart, remember that this framework was first developed in the 1950s to manage one of the most delicate projects in military history: Polaris. This codename designated the US-led effort to build a nuclear missile that could be launched from a submarine.

Polaris was part of the Cold War strategy of having a functional deterrent, so it made sense to focus on submarines. Underwater vessels would be too hard to detect and disable by a preventive attack from any nuclear foe.

Polaris gives the Program Evaluation Review Technique (PERT) chart quite an epic origin story. Imagine the complexities involved in such a project. Leaving aside the engineering challenge of designing a missile with the right weight and power, the US Navy also had to contend with the dangers of placing such a weapon within the tight and vulnerable space of a submarine.
Few of us will ever face even a fraction of this challenge in our day-to-day jobs.

In 1957, the Polaris team, led by Special Projects Office Director Willard Fazar, had sought to complete the task in record time. However, existing GANTT charts had shortcomings. They did not reflect how, exactly, stated plans were connected to overall goals, how achievement would be measured against these goals, and how likely it was that goals would be met through the plans.

The top priority for these military engineers? Saving time. If you know how exactly, how strongly and how likely the different components of your project are aligned, you can see immediately where bottlenecks and opportunities lie to advance faster and further. This is exactly how PERT worked in practice, allowing the first shot of Polaris to take place in 1960, barely three years after research had commenced.

PERT charts vs. GANTT charts: Key differences

What are the key differences between the PERT and GANTT approaches? To paint a clearer picture of how each is used for product management today, let’s review here the key features of GANTT vs. PERT charts.

Format

Visually, you’re probably more familiar with GANTT charts. A GANTT chart lists project milestones on the left, which result in various rows that can be assigned precise timelines.

These timelines are graphically represented as “blocks” on the chart itself, whose length represents the time expected to completion (or the actual time it took once completed). Tasks are listed in the order in which they are meant to be completed. Typically, additional details, such as task owners and necessary tools, are expressed through color codes and other visual aids.

PERT charts are more purely visual than GANTT charts. Drafting begins with an initial bubble or node, which represents the starting point for your project. Then, arrows originating there result in supplementary nodes that can have multiple dependencies to ensuing project milestones. If bubbles are aligned, this means they should be completed in parallel as they unlock further milestones.

Timelines are not represented alongside the chart, but are directly listed next to the different nodes. Additional information after completion might include expected versus actual time, which can be added up to assess the overall project.

Effort

GANTT charts are commonly used in organizations across all industries. There are more and better resources out there that ease the learning curve for everybody. For example, there are plenty of templates you can find online that display a GANTT chart’s key features in either Excel or Google Sheets.

In terms of workflow, GANTT is decidedly a team contribution. Even the most self-reliant managers must align with others to draft the chart. This also involves a distribution of responsibilities and a continuous channel of communication to keep track.

Because PERT charts are less commonly used, it can be somewhat more difficult to find an appropriate template (don’t worry; we listed some below). Awareness of the PERT methodology is less widespread across teams, which means you might have to hold one or more extra sessions to familiarize your people with it.

In terms of workflow, the actual drafting of the PERT chart can be conducted individually. The philosophy behind PERT suggests that research be conducted beforehand, considering dependencies ahead of time, to trace development between milestones.

Data points

GANTT charts require the following information:

  • Project milestones
  • Project timeline
  • Resource availability
  • Staff availability
  • Staff skills

PERT charts require:

  • Project milestones
  • Milestone dependencies
  • Hierarchy of dependencies
  • Project timeline

Users can adapt both GANTT and PERT charts to include additional points, but those listed above summarize the essentials.

Project stage

GANTT charts can be drafted at any point in the project but are typically used once development has actually begun. As noted above, GANTT charts are meant to be updated by members of the team as steps are fulfilled to help with time and task management.

PERT charts, on the other hand, are normally built before the project starts. Organizations can use PERT charts to identify all possible complications and essential steps involving a project, regardless of specific time or staff assignments.

Versatility vs. longevity

GANTT charts are versatile by design. This is partly aided by their simplicity: any human effort can be expressed chronologically. At the same time, they are not always suitable for more complex projects.

Think about high-tech projects, such as the nuclear submarine example above. What if the engineers tried different materials in parallel? A breakthrough in one team could completely revolutionize the project, closing one dependency (the now useless material) but opening others. This type of breakthrough is not easy to represent on a GANTT chart, which would simply change without acknowledging the breakthrough.

This is why the PERT chart’s inferior versatility might not be such a big drawback after all. Because they are developed before a project is launched, often for budgetary meetings and other preparatory processes, you might be tempted to suspect PERT analysis is dead after launch. However, this is far from the truth.

The careful consideration of dependencies, causal chains, and critical pathways can actually make PERT charts more evergreen than GANTT charts. Team members can often lose sight of the bigger picture when employing smaller-scale, siloed GANTT charts. A PERT chart operates as a polestar and serves as a useful assessment tool once the project is finished.

When to use PERT instead of GANTT

How do you choose which type of chart to use? It depends on what’s more important to track: time dependencies or task dependences.

GANTT charts are meant to offer a quick overview of a project and its time dependencies. It shows you at a glance how long past, present, and future steps will take. The methodology or data you employed to arrive at your estimates is hidden from view in favor of chronological information and its connection to tasks and team members.

PERT charts, while still reflecting time constraints, are more focused on task dependencies. The position of nodes and the arrows between them emphasize how each milestone contributes to completion.

A PERT chart is almost a reversal of GANTT: you are being transparent about your estimates, showing your target audience why and how you‘ve chosen to display steps in a particular order. In project management language, this entails revealing a clear critical path for your project’s completion.

Reasons to use a PERT chart for product management

The qualities listed below make PERT charts an excellent choice for project and product managers seeking to highlight task dependencies at a more granular level.

Bulletproof

PERT charts demand that every milestone is considered from the perspective of linkages to other crucial steps.

When drafting a PERT chart, you’re forced to gather and analyze research to the highest possible degree of detail. This means your project, at least in its planning stages, starts with very strong foundations.

Speculative

Unlike other time/task-based methods, PERT focuses extensively on causes and consequences.

You can see at a glance how, if certain milestones are unlocked quicker or take longer to complete, the whole process is affected. This means you can test various scenarios and prevent them before they emerge.

Specific

Even the most well-prepared report or presentation can fall prey to imprecision and overextension.

PERT charts are precise by definition, limiting their information to essential steps and their relationship. In both drafting and displaying them, the PERT framework helps viewers focus on what really matters to complete the project.

Cohesive

Unlike GANTT and other approaches, which are usually tailored to the operations of a small team or subteam to be operational, PERT charts can cover a lot of ground.

The arrows linking milestones together are the perfect antidote to siloed mentality because teams responsible for milestones are aware of who is dependent on them to achieve shared success.

Pitfalls of using PERT charts

As handy as they can be for certain types of products, PERT charts aren’t for every team or project. Below are some characteristics that, depending on your goals, capabilities, and product requirements, might make the PERT approach an imperfect fit for your project.

Demanding

Functional PERT chart data requirements are steep. You must do a lot of research before you can portray accurate dependencies on the chart.

Similarly, if you seek to include the time requirements that are reflected on other types of charts, you’ll also have to gather information from a range of teams and managers.

Hard start

With GANTT and other approaches, you only need a broad outline of milestones and the time it might take to complete them. These can even be altered later.

PERT charts require substantial and accurate data at the very beginning, knowing that the diagram will remain more or less unaltered in the foreseeable future. This can be quite paralyzing.

Data access

While PERT charts can certainly be cohesive, this comes at a price. You must already have a good working relationship with all relevant teams and professionals. If not, you’ll have to spend some precious time gaining this trust, which might defeat the purpose.

Bottleneck bias

By design, people who create PERT charts build nodes and connections by considering how steps are vital preconditions to fulfill other milestones. However, agile projects evolve dynamically, which means teams might be closed to new opportunities if they are excessively beholden to a PERT chart.

How to make a PERT chart

There are 10 steps involved in building a PERT chart. Let’s go over the process step by step:

  1. Collect information, information, and more information — You will be unable to complete any of the other points if you lack awareness of milestones, resources, timeframes and any other complementary data that might be relevant to your chart
  2. Open communication channels — Awareness and collaboration between stakeholders are fundamental for any modern organization, big or small, public or private. You should always prioritize building a rapport with teams affected by the PERT chart. They will offer information and you will need their feedback later
  3. Pick a PERT chart drafting tool — There are many options out there, but you can always rely on the classic, tried and true tool set: Excel and PowerPoint if you use Microsoft Office or Sheets and Slides if you use the Google Suite. There are also specialized, freemium, and premium apps available
  4. Define nodes — As with GANTT, it is critical that you list all steps to complete your project. Don’t obsess over the order in which you position them, but make sure all tasks are represented at the end of the exercise
  5. Define dependencies — Now that you have all your nodes in front of you, consider which are vitally attached to each other and which merely possess tangential connections in achieving success. This is where the process diverges from the GANTT approach
  6. Define parallel projects — This is where dependencies are not just established but also sequenced. The idea is that nodes that are positioned in parallel should be completed at the same time. This is because, even if they lack dependencies at the start, they might share them at a future point.
  7. Define a critical path — Now that essential elements are in place, you should be able to see a limited number of ways in which your project can be completed. You should whittle down those options to one and designate your critical path or vital trajectory that constitutes the bare minimum for completion (i.e., define your MVP).
  8. Define timelines — This is often an initial consideration with other models, but with PERT, dependencies and pathways take center stage. It’s only when these are defined that you should distribute available time between project milestones
  9. Share with stakeholders — All stakeholders who were involved at the start should now review your chart to provide comments and reach consensus on your direction
  10. Apply feedback and share the final version — Apply any comments you received and distribute your PERT chart to relevant teams and individuals

PERT chart templates and examples

To help you get started on your PERT journey, let’s review some resources designed to help you execute the PERT methodology effectively with templates and other dynamic features.

Smartdraw

Smartdraw offers a basic template that you can edited online. The tool includes all the elements described above. Best of all, you can examine how it works and even do basic editing without having to register.

Smartdraw PERT Chart Template Example

Adobe

Adobe offers PERT chart templates, but they’re fairly bare-bones and require editing if you want to include more advanced elements.

Adobe PERT Chart Template Example

Creately

Creately offers a simpler version of a PERT chart. The main draw here is that this PERT chart template is accessible for free.

Creately PERT Chart Template Example

Lucidchart

Lucidchart also has a PERT chart template. Lucidchart is rich in features, so it’s no surprise that you need to register to use it.

Lucidchart PERT Chart Template Example

LogRocket helps you speak the same language as your developers

Thanks for reading about Product Ops. This is an ad for LogRocket.

Not sure what we do? We just won Product School's "Proddy" for best Heatmaps & Session Replay, beating out a lot of great solutions that you probably already use. We make it so much easier for you to work with your developers by diagnosing bugs and catching revenue-killing snags in your app's UI.

See what you're missing - try LogRocket today.
Roy Cobby Researcher with a professional background in marketing and social media management in education and public policy, at business schools, academic journals, and stakeholder-based organizations.

Leave a Reply