I didn’t expect you to “get it”.
Check out this Factual Facts post “In 2005 in Turkey, a suicide sheep jumped off a cliff and 1500 sheep followed the first one” .
Now, before you go away, I need to very quickly make an important connection.
Many process maps get prepared on paper, are then filed, and are never referred to again.
If this is what happens to the maps you prepare, you might as well prepare them and throw them off a cliff.
My point is. . . .
For any process that has complex steps, connected sometimes in complex ways, with multiple decision box branching points, where different skilled persons must perform different steps, where different steps require the collection of different data, where you want to carry out data mining after-the-fact . . . .
there is NO way instances of your process templates can be “managed” by staring at a paper map and NO way, however long staff might stare at such maps, that you will be able to have process instances performed properly (doing the right things, the right way, at the right time, using the right resources, collecting the right data).
Remedy . . . .
Map your process maps on an e-canvas, compile them, roll them out for modeling/simulation, improve your process maps, then roll them out again so they can provide real-time orchestration within a Case run-time environment.
Otherwise, see you at the bottom of the cliff.