Paul Simpson said:
Belatedly here is my attempt at describing how a process interrelationship could look. There are two slides - the first is the overall map. The second is a click through to the new product introduction process. It isn't based on any company and there are many other processes that would be linked from the overall map - never quite as far down as IS management though.
As ever any views gratefully received.
Paul
Dare I ask... what do you see as the benefit of this sort of diagram? Why do you think that people produce them? Is it so that (i) employees can learn something about the organisation they didn't know before, (ii) it will help staff do their job better, or (iii) they can meet some (unexplained) requirement in ISO9001:2000?
How many such pictures have you seen which add value to an organisation?
Just picking up a few points from your example (but similar comments could equally be applied to the vast majority of such maps - by the way, is it better to describe them as "system maps" rather than as "process maps", which as you know I think of as a flowchart of a process?):
1 "Monitoring & Measuring" is often done as an intrinsic part of another process rather than as a separate process. Even if it is a separate process, it will (or should) affect the process(es) being monitored (otherwise why do it?) - so there should be an arrow going up as well.
2 In the same way, "Research and Development" and "Planning and Logistics" may well have an impact on the "Provision of Resources", so there is another arrow or two needed.
3 "Provision of Resources" may impact on "Monitoring & Measuring", so another arrow is needed.
4 "Fulfilling repeat orders" may affect "Enquiry and Order receipt" if the production line can't cope and you have to quote longer delivery times...
My concern is that at the one extreme the system map will have the sort of missing links I mention above, and at the other you will need an n-dimensional picture which is so complex that it would be unusable. I personally don't see any benefit in either, other than just to satisfy an external assessor, which cannot be a good reason for doing it.
In any organisation, "process interaction" is far more involved than this sort of picture can show in any sort of accurate and usable format, and the "sequence of processes" as it is usually depicted makes no reference to the fact that many instances of each process may be happening at the same time. If everything was linear, you probably wouldn't need managers, and certainly not managers who understand what is required for good process management.
An alternative approach? Our customers use a simple numbering system to define a small number of process groups ("2 Getting Work", "3 Doing Work" etc), and processes with each (eg "2-1 Respond to an Enquiry", "2-2 Prepare a Tender") which implies a logical sequence, and define the processes (using "process maps"!) which link to other processes from the relevant tasks. They only draw a picture if they have an unenlightend assessor.
So ... grateful or not?!