Stop 04 · Process Modeling & AnalysisTopics · 3/9

Process Flowcharts

Part of the Business Analyst Roadmap

In short

Not every audience knows BPMN, and that's fine. A simple flowchart with boxes, diamonds and arrows can be read by anyone, from the CEO to a new intern, in under a minute.

A simpler, more universally understood alternative to BPMN — using basic shapes (boxes, diamonds, arrows) to represent steps and decisions, readable even by audiences unfamiliar with formal notation.

The purple blob talks on an old landline phone while following a winding path of arrows on the floor.

Think of it like this

The customer care phone menu

'Press 1 for balance. Press 2 for recharge. If you've already paid, press 3.' Every phone menu is a flowchart: a step, a question, a branch. You follow it without thinking because the logic is laid out clearly.

Watch it happen

Flowchart: what happens after an order

Order placed
Paid?
Yes: pack it
No: send reminder
Ship order
Cancel after 24h

1/4An oval marks the start. Keep labels short and action-based.

The big ideas

What you need to know

Few shapes

Oval for start and end, rectangle for a step, diamond for a decision, arrow for direction. That's usually enough.

One direction

Flow top to bottom or left to right. Avoid arrows crossing over each other wherever you can.

Decisions as questions

Write diamonds as questions with clear answers, like 'Stock available?', and label both exits.

For any audience

Use flowcharts for quick explanations and mixed audiences. Use BPMN when teams need precise, standard detail.

Save yourself the pain

Common mistakes

Oops

Leaving a decision with only the 'yes' path drawn.

Do this instead

Draw every exit. The missing 'no' path is usually where the real requirements hide.

Oops

Writing whole sentences inside every box.

Do this instead

Use short verb phrases like 'Send reminder'. Put extra detail in notes beside the diagram.

Your mission

Flowchart a recharge

~20 min

Quick check

Your flowchart has a diamond 'Payment success?' with only a 'Yes' arrow. What's wrong?

Go deeper

  1. 1Build a flowchart for a simple process using basic shapes, without formal BPMN notation.
  2. 2Learn when a simple flowchart is sufficient versus when BPMN's precision is worth the added complexity.
  3. 3Compare the same process modeled in both formats.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge