Purpose

Translate structured project logic into a visual system.

When to create a diagram

Create a diagram when:

• there are multiple phases
• there are multiple stakeholders
• there are dependencies across workstreams
• the project includes systems, flows, or architecture logic
• visual clarity would accelerate alignment

When NOT to create a diagram

Do not create a diagram when:

• the structure is still too vague
• the output is not yet organized
• there isn’t a clear flow or system to map

Diagram quality rules

A good diagram should:

• be easy to scan
• reflect the real structure
• reduce confusion
• show flow, sequence, or relationships clearly