You can learn BPMN 2.0 properly in about a fortnight.
Tasks, sequence flows, exclusive gateways, parallel gateways, start events, message events, pools, lanes.
Maybe 12 elements cover most real world maps.
The notation is well documented, widely understood, consistent from one organisation to the next.
Which means it isn’t what separates a process analyst who delivers from one who doesn’t.
Anyone can put a diagram together.
The difficulty is getting the information that goes into it, from people who have no particular reason to give you their time.
💬 What a client actually noticed
I was sent a testimonial recently after a long program.
It’s worth quoting, since what it praises isn’t the modelling.
“What has stood out most working with is not just the sheer volume of work he’s delivered, but how he delivered it. He has an exceptional ability to work with people across all levels of an organisation, quickly building trust and making complex process discussions feel practical and collaborative rather than painful. He has consistently brought a calm, solutions-focused approach, strong attention to detail, and a genuine willingness to help others.”
Nothing there about notation.
Nothing about swimlanes, gateway logic, or modelling standards.
It’s all about how the conversations felt.
That’s not a coincidence, it’s the actual job.
🤝 Trust comes before the map
People give accurate process information to people they’re comfortable with.
Someone who trusts you tells you about the workaround they built.
The step they skip when it’s busy.
The approval they’ve been getting verbally for 2 years, which appears nowhere in the system.
Someone who doesn’t trust you describes the version in the procedure manual.
Both conversations take 30 minutes.
Only one produces a map worth building a system from.
So the first 10 minutes go on things that aren’t the process.
What their week looks like, when month end lands, which system they’ve been complaining about longest.
Then say plainly that you’re not there to audit anyone, just to write down what really happens.
Most people visibly relax once that’s been said out loud.
😌 Calm is a technical skill
Process discussions get tense more often than people expect.
Two teams describe the same process differently, both correctly.
Someone realises the mapping might expose how long their part takes.
A manager hears their team described in a way that doesn’t match what they believed.
The instinct when it gets heated is to argue faster.
More facts, more evidence, more explanation.
That never works, because facts don’t land on someone who feels unheard.
Slowing down does work.
Steady pace, shorter sentences, longer pauses.
Repeat back what the person said before responding to it.
Then check whether you’ve understood.
“So the concern is this adds an approval step for your team, without removing the manual check at the other end.”
If the answer is “that’s right”, you’re finally in the same conversation.
If it’s “not quite”, you’ve avoided solving the wrong problem.
Calm isn’t a personality trait here, it’s a technique that produces better maps.
🎯 Making complex discussions feel practical
Process conversations become painful when they’re abstract.
Someone puts a blank wall in front of 10 people, asks them to describe the process, then 3 hours disappear.
The fix is preparation.
Turn up with a draft map built from old procedures, system screens, whatever exists.
Make it visibly rough, because a polished diagram invites polite agreement while a messy one invites correction.
Then ask specific questions rather than broad ones.
- Walk me through the last one you did, not the standard version
- At this point, what makes it go one way rather than another?
- What do you have open on screen while doing this?
- Who does this next, then how do they know it’s their turn?
- What happens when the system’s down?
- Which part causes the most complaints?
Specific questions get specific answers.
They also signal you’ve done some homework, which changes the tone immediately.
You’re asking people to correct you rather than educate you.
Most people quite enjoy correcting you.
🔍 Attention to detail, in the right place
Detail matters, though not evenly.
A beautiful map with perfect notation, missing the exception that occurs 200 times a month, is a failure.
A slightly untidy map capturing every real path is useful.
So spend the detail where it counts.
- Gateway conditions, written precisely rather than as “if approved”
- Volumes on each path, since a 1% branch deserves less design effort
- Handoff points, because that’s where work sits waiting
- Exception paths, which is what most maps quietly skip
- Task IDs that stay stable when task names change
That last one saves considerable pain later, when work instructions get linked back to the map.
🙋 Willingness to help
There’s a version of this role that’s purely extractive.
You take information from people, produce a document, move on.
It’s technically adequate, though it makes every subsequent request harder.
The better approach costs very little.
Send people the finished map.
Tell them what changed because of their input.
Thank them somewhere their manager can see it.
Answer the question that’s outside your scope, if it takes 5 minutes.
Do that consistently across a long program, then people start volunteering things.
That’s when the work gets genuinely accurate.
✅ What this means for a process analyst
Learn BPMN 2.0 properly, obviously.
A map nobody can read fails at the first hurdle.
Just don’t mistake it for the hard part.
The hard part is being someone people don’t mind seeing in their calendar.
Everything else is notation.
About the author
Aiver Ilaya is an IT consultant based in Melbourne. For 19 years he’s worked on enterprise digital transformation programs.
His experience spans ITSM, HRIS, ERP, CRM, POS, KMS and EDRMS platforms, plus workflow automation.
He has worked across government, healthcare, science and medical research, finance, education, telecommunications, infrastructure, aviation, construction and property, technology, retail, logistics, pharmacy, insurance and professional services.
His work covers business analysis, process optimisation, technical writing, knowledge management and UI / UX design. He has worked on multi-million dollar programs running years at a time, for national organisations and global firms, reaching millions of end users.
He has run his own consultancy for 12 years and works with a small number of clients at a time. Available for remote and hybrid contracts.
alisodigital.com


