Cycle, pyramid, hub and Venn: choosing a process diagram

Not every process is a sequence of steps with decisions. Some repeat forever. Some build in layers. Some radiate from a central team. Some are about where two areas overlap. A flowchart can technically show all of these, but it hides the shape of the idea.

Cycle, pyramid, hub-and-spoke and Venn diagrams each carry a meaning before anyone reads a label. That is their strength and their risk: pick the wrong one and the shape tells readers something untrue. This article covers what each type implies, when it fits, and how to draw it cleanly.

First, check whether you need a flowchart

Ask one question: does the reader need to follow a path and make choices along it? If yes, a flowchart or process map is the right tool, and how to create a process map covers that work. If the reader instead needs to grasp a structure (a loop, a hierarchy, a centre, an overlap), one of the four types below will usually say it faster.

Cycle diagrams

A cycle shows stages that repeat, with the last stage feeding back into the first. Common examples:

• a monthly close: collect, reconcile, review, report, then start again
• a product feedback loop: release, measure, learn, plan
• a hiring pipeline that is reviewed and refined every quarter

What it implies: there is no real start or end, every stage happens every time, and the order is fixed.

When it misleads: if some stages are skipped in some rounds, or the process ends after one pass, a cycle overstates the regularity. Use a flowchart with a loop instead.

Drawing it well:

• Use four to six stages. Fewer looks trivial; more becomes hard to follow around the circle.
• Place the stage people consider the “beginning” at the top, and run clockwise.
• Keep labels outside or inside the ring consistently, not a mix.
• If one stage is the subject of the discussion, give it the only accent colour.

If the cycle is going into a deck, starting from a cycle diagram slide saves time spacing the stages and arrows evenly.

Pyramid diagrams

A pyramid shows layers, where each level rests on the one below. It suits foundations and priorities: data quality under reporting under decisions, or basic training under specialist skills under leadership.

What it implies: the bottom is the widest and most fundamental, upper levels depend on lower ones, and there is less of each thing as you rise.

When it misleads: if the levels are simply a list of equal items, or if the “top” isn’t actually smaller or dependent, the pyramid invents a hierarchy. Many pyramids in business slides are really ranked lists, and a numbered list would be more honest.

Drawing it well:

• Three to five levels is plenty.
• Put the label inside each band, with a short note to the side if needed.
• Keep band heights equal unless the difference in height means something you will explain.
• Say in the title which way the reader should read it: “Reliable reporting starts with clean source data” invites a bottom-up reading.

Hub-and-spoke diagrams

A hub shows a central element connected to several others. It works for a shared service and the teams it supports, a platform and its users, or a project lead and the workstreams they coordinate.

What it implies: the centre is the point of connection, each spoke relates mainly to the hub, and the spokes don’t depend much on each other.

When it misleads: if the outer elements work closely with one another, a hub hides those relationships. If the centre is just one participant among equals, the layout overstates its importance. A swimlane or network diagram may suit better.

Drawing it well:

• Keep spokes to between four and eight.
• Space them evenly so none looks more important by accident.
• Label the connections if they differ (“sends data”, “requests approval”); leave them unlabelled if they are all the same kind.
• Make the hub visibly different in size or colour, but not so large it crowds the labels.

Venn diagrams

A Venn diagram shows overlap between two or three sets: skills that two roles share, customers who use both products, responsibilities that sit with more than one team.

What it implies: the circles are groups, the overlap contains things that belong to both, and the size of the overlap means something.

When it misleads: readers tend to read area as quantity. If the overlap is drawn large but contains one item, the picture contradicts the content. Venns with four or more sets become very hard to read; use a table instead.

Drawing it well:

• Two or three circles only.
• Put a few items in each region, or a short label for the region itself, never long sentences.
• Keep circle sizes equal unless they represent real sizes you can stand behind.
• Use transparent fills so the overlaps show clearly.

For a presentation, Venn diagram slides with the circles already aligned are a quicker start than drawing them by hand.

A quick way to choose

If the idea is…	Use	Avoid when…
Stages that repeat in order	Cycle	Stages are skipped or the process ends
Layers that build on each other	Pyramid	The levels are really a flat list
One centre linked to several parts	Hub and spoke	The parts depend on each other
Overlap between groups	Venn	There are more than three groups
A path with choices	Flowchart	You only need to show structure

Keep the shape honest

These diagrams are persuasive because the shape speaks first. Before you use one, describe the idea in a sentence without naming the diagram: “Our reporting depends on clean data, which depends on agreed definitions.” If the sentence describes layers, a pyramid is honest. If it describes a path with a decision, go back to a flowchart.

That sentence is also the best brief for the diagram itself, whether you draw it by hand or describe it to DiagramsPro.