I have to admit that I love process maps :). Creating a clear and understandable one can be surprisingly difficult, but once you master this skill, it will help you enormously as a business analyst.
Today, I am not going to explain how to create a process map from beginning to end. That deserves a separate article. Instead, I want to focus on one simple detail that junior analysts often overlook.
They study the methodology, learn the correct notation, select the right shapes, and connect everything properly. Then they send me a process map that looks perfectly fine at first glance … but one important feature is usually missing:
Unique reference number.
It may sound obvious, but numbering transforms a process map from a picture into a practical working document.
Imagine that you need to discuss the map with a colleague or link one of its steps to more detailed documentation. Without numbers, you might say:
“The email address must be mandatory in the personal information step.”
A numbered step makes the requirement much clearer:
“In Step 6 – Enter Personal Information, the email address must be mandatory.”
Now everyone knows exactly which part of the process you are referring to.
Step numbers also allow you to connect your process map to:
detailed requirements and business rules,
user stories and development tasks,
meeting notes and decisions,
test cases,
supporting documentation,
and future change requests.
You can use simple numbers such as 1, 2, 3, or identifiers such as S01, S02, S03. For processes with multiple branches, you can use identifiers such as S04A and S04B. The format is less important than consistency.
So, next time before sending your process map to team, ask yourself one simple question:
Can everyone refer to any step without pointing at the screen?
A process map is not only something people look at. It is something the team must be able to discuss, document, test, and maintain.
Well written, clear, and easy to understand. The flow is good and user-friendly.