Stop 04 · Process Modeling & AnalysisTopics · 1/9

Business Process Modeling Basics

Part of the Business Analyst Roadmap

In short

Ask five people how a leave request gets approved and you'll get five answers. Drawing the process turns those guesses into one picture everyone can point at and argue about.

Visually representing how a business process actually works — the sequence of steps, decisions, and handoffs — making an abstract workflow concrete enough to analyze and improve.

The purple blob rides a bicycle carrying a tall stack of tiffin boxes.

Think of it like this

The dabbawala system

A tiffin is picked up from a home, sorted at the station, carried by train, sorted again and delivered to an office desk. Each step has an owner and a handoff. Drawing that chain is process modelling: who does what, in what order, and where it can slip.

Watch it happen

The building blocks of any process

Trigger
Activity
Handoff
Decision
Outcome

1/5Every process starts with a trigger: an employee submits a leave request.

The big ideas

What you need to know

Clear start and end

Name the trigger and the outcome first. If you can't say where the process starts and stops, the diagram will sprawl.

Who does each step

Every activity has an owner, a person, team or system. Missing owners are often where work gets stuck.

Decisions and exceptions

Show the yes and no paths. The 'no' paths are where most real complaints and rework live.

Model reality first

Draw how it really works today, workarounds included, before drawing how it should work.

Save yourself the pain

Common mistakes

Oops

Drawing the process from the policy manual alone.

Do this instead

Walk it with the people who do it. Their version, with workarounds, is the one you need to improve.

Oops

Cramming 60 boxes onto one page.

Do this instead

Keep the top level to about 5 to 15 steps. Break big steps into their own sub-process diagrams.

Your mission

Model your morning order

~20 min

Quick check

Where do delays most often hide in a business process?

Go deeper

  1. 1Map a simple process you're familiar with (e.g. a purchase approval flow) step by step.
  2. 2Learn why visualizing a process often surfaces inefficiencies invisible in a text description.
  3. 3Practice identifying decision points versus simple sequential steps in your map.

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