If you’re not sure how to get trained up on BPMN – or BPM – Bruce Silver’s training is a good place to start:
All this hubbub about BPMN and case management, would doctors and lawyers use it, and other nonsense… They could learn to do it, but that’s not the intended audience. And it would probably surprise some to know that technical developers are not the primary audience, either. So who exactly is BPMN for, and why do they use it?
In my experience, the main purpose of BPMN is to document, analyze, and improve business processes. The process improvement, if it’s taken that far, is not necessarily automation in a BPMS. Well less than half of my students are looking to automate their processes. The people who use it call themselves BPM project team members, business analysts, architects, and consultants. They often live in the IT organization but their perspective is that of the business. They are not technical. And they don’t need to be.
BPMN is a visual language for describing “process logic” in a diagram. Process logic simply means the order of the steps, the various paths possible from process start to end. It doesn’t describe other useful information about the process, such as the data, the systems, the forms and screenflows, the business rules, problems and goals, or KPIs. Process modelers are often interested in those things, too, and many BPMN tools let you model them, but each in their own way. The point of BPMN – the process logic part – is that the meaning of the diagram is independent of the tool used to create it. It’s a standard, supported by many tools.
Bruce’s training is still the gold standard. There’s much more in his post than what is quoted here, go read it!