Ready to map out your project? Follow these steps to build an effective PERT chart.
The first step is breaking down the project during the project planning stage. Start with the final deliverable and work backwards to identify every major milestone and the tasks needed to achieve them. Engaging all project stakeholders early is key to setting expectations, aligning on goals, and agreeing on the overall project outcome.
Task dependencies are tasks that can’t begin until another task is complete. Identify which tasks must happen in sequence and which can run independently. For example, content teams may review personalised net new content to ensure it meets brand standards and legal compliance requirements. Task dependencies can also be incorporated into work breakdown structures. PERT charts map out these dependencies to show how tasks relate to one another.
Apply the expected time formula to each task. Consult the teams contributing to each task to understand their expected timelines. Once you’ve engaged the relevant teams, share those time frames with executive leaders to align on project execution. Teams can also use the critical path method (CPM), which identifies key activities in a process and assesses the time needed to complete them.
Start building the chart by placing each task and milestone on a large diagram, using nodes to represent each task. Keep in mind that you may need to reposition the nodes as you work through the next step, so sketching the layout on a whiteboard or in a computer program first will make this much easier.
Using your notes on task prerequisites and interdependencies, draw arrows between your nodes to show which tasks form dependent chains. Bear in mind that parallel chains are possible where some tasks don’t affect others. Adding time estimates to the nodes or the connecting arrows will also help you calculate the total project timeline further down the track.
Once the diagram is complete, calculate the total time for each path and identify the critical path — the longest one. Look for opportunities to break up lengthy tasks or shift resources to parallel workflows to optimise the schedule. For example, teams might spot bottlenecks that are slowing task progress. Reducing the number of steps within a project and limiting the number of contributing teams can help keep projects on track.