What Is Activity on Node? | The Project Planner’s Secret

AON is a project scheduling method that represents each task as a box (node) and uses arrows to show how tasks depend on each other.

Most project planning starts with a to-do list — a flat list of tasks that never truly captures the mess of real dependencies. You know the scenario: Task B can’t begin until Task A finishes, but Task A is waiting on an approval that’s tied to Task C. A simple list won’t cut it.

That’s where Activity on Node (AON) enters the picture. It’s the visual language project managers use to map out logical sequences without drowning in complexity. Instead of arrows or events carrying the load, each task gets its own box — and the arrows simply show what needs to happen before the next box opens.

How AON Replaces Guesswork With Structure

AON diagrams are the default method inside most scheduling software and are central to the Critical Path Method (CPM) and PERT techniques. Each activity in your project gets a box, and arrows between boxes show dependencies. Read the diagram left to right — left side of a node is the start; right side is the finish.

The real power is in spotting bottlenecks. If one task sits in a chain with no parallel work, that chain is your critical path — any delay there pushes the whole project. AON makes that chain obvious at a glance.

An AON network diagram is a graphical representation of the logical relationship (dependencies) among project schedule activities, according to Csuohio’s project management textbook. Without this structure, even medium-sized projects can spiral into confusion.

Why Project Managers Choose AON Over Alternatives

Not all diagram methods draw tasks the same way. AON’s closest cousin — Activity on Arrow (AOA) — flips the roles: arrows become tasks and nodes become events. That difference shapes how you read each diagram and which projects it suits best.

• AON (precedence diagramming): Each task is one box. Arrows only show dependencies. Easy to add new tasks without redrawing arrows. Preferred by most modern project management software.
• AOA (arrow diagramming): Tasks live on arrows, and nodes mark start/end events. Better for complex dependency webs but harder to modify once drawn. Uses dummy activities to maintain logic.
• Common use cases: AON works well for construction, software development, and event planning. AOA appears more in academic settings or projects with highly intricate interdependencies.
• Learning curve: AON is more intuitive for new project managers. You can sketch one on a whiteboard in minutes. AOA requires more practice to avoid dummy-activity errors.
• Software support: Microsoft Project, Smartsheet, Jira, and Monday.com all use AON-style node-and-arrow logic. AOA diagrams are rarely natively supported.

Both methods serve the same purpose — mapping task logic — but AON’s node-centric design has become the industry norm. If you’re studying for the PMP exam or starting a project next week, AON is the technique you’ll use most.

Anatomy of an AON Diagram

A basic AON diagram has just two building blocks: nodes and arrows. Nodes are rectangles that contain the activity name, duration estimate, and sometimes early/late start dates. Arrows connect nodes to show four dependency types — finish-to-start being the most common.

Make a network diagram by listing all activities, determining their immediate predecessors, then drawing boxes in sequence. Csuohio’s AON network diagram chapter walks through a full example with activity lists and sequencing rules. The chapter also covers how to handle dummy activities when a dependency doesn’t fit a clean line.

Once the diagram is drawn, you calculate forward pass (earliest start/finish) and backward pass (latest start/finish) to identify float and the critical path. That’s where raw task logic turns into a schedule you can manage.

Each dependency type gives you flexibility to model real workflows — not just linear chains. The four types let you represent overlapping work, phased approvals, and parallel tracks accurately.

Building Your First AON Network Diagram in Five Steps

Creating an AON diagram from scratch doesn’t require special software. A whiteboard or spreadsheet works fine for the first draft. The process forces you to think through your project’s hidden dependencies.

1. List all project activities: Break your project into individual tasks. Each task should have a clear deliverable and estimated duration. Aim for 10-20 activities for a first project.
2. Identify immediate predecessors: For every task, answer “what must finish before this can start?” If nothing, it’s a starting activity. If multiple, that’s a merge point.
3. Draw nodes in sequence: Place each activity in a box. Arrange boxes left to right based on predecessors. Use columns for each layer of dependency.
4. Connect with arrows: Draw an arrow from each predecessor to its dependent. Label arrows with the dependency type (most will be finish-to-start).
5. Calculate forward and backward pass: Compute earliest and latest start/finish dates. Identify the critical path — the longest path through the diagram with zero float.

The first diagram you draw will likely reveal missing tasks or forgotten dependencies. That’s the point. AON’s value isn’t the final picture — it’s the thinking that happens while building it.

Real-World Applications Beyond the PMP Exam

AON diagrams aren’t just a certification checkbox. They show up in construction project schedules, software release planning, event coordination, and product launch timelines. Any multi-task effort with external dependencies benefits from this structure.

The Project Management Knowledge site’s AON definition notes the method is primarily used alongside CPM and PERT — both of which require accurate dependency maps to calculate timelines. Without AON, your CPM analysis is guesswork.

For teams using Jira or Azure DevOps, the underlying logic of issue links and task dependencies is effectively an AON model. Even if you never draw boxes on a whiteboard, the same precedence-diagramming principles run behind your sprint board. Understanding AON helps you untangle messy task boards and spot blockers early.

The Bottom Line

Activity on Node gives you a map of your project’s logic — not just a list of tasks. It reveals the critical path, surfaces hidden dependencies, and helps you see which delays will actually wreck the timeline. For anyone managing projects with more than a handful of tasks, AON is the difference between reactive firefighting and deliberate scheduling.

For hands-on practice, grab a simple project (like planning a two-day conference) and build an AON diagram on a whiteboard or using Microsoft Project’s built-in network diagram view — the node-and-arrow logic will click once you draw the first few dependencies yourself.