Process mapping is a lot about answering questions. The work method is easy, a model creator addresses the questions why, what, how and who, and captures the discussion by gradually creating a model.
The order of the questions is important. It is easier and more effective to create a consensus on why, what and how before moving on to answering who.
By creating an interested party and requirement model we have found a need for investment as well as a requirement.
When we map the process we will focus on WHAT. What is input, what do we do then, what is created etc.
We could also ask what the end result of the process is, and what we need to do to achieve it, i.e. go backwards.
Once we have answered what and the entire flow from the primary need to the result of the process has been completed, we look at the skills required to carry out the different activities.
Who is often described as roles, but can also be defined through positions. You can find more information about the concepts of position and role on the page about organization models.
How is usually an instruction to help the employee to perform an activity. The instruction could be a short text attached to the object or a linked document.
In order to guarantee a high-quality result, information can also be provided next to the activity via a form (Word template, business system or case management system).
Or you could look at How before Who. The downside of describing How before Who is that Who has knowledge about How.
When the process mapping is complete, we have answered why, what, who and how. We have created a clear and visible result, a model. If we have worked in a group with representatives from the interested parties involved, we also get a surplus value by achieving consensus and support. You can find more information about the work method here.