What IS a Process Map?

[JaneB]

What do you mean by a 'process map'? A few discussions in a couple of recent threads reminded me that this term is often used to mean different things, which can be very confusing for the 'uninitiated'.

I'm interested to see if there's a broad consensus of meaning (or not), and what people think a process map 'should' be / contain / look like.

[William Gr]

It all depends on what you are trying to map! As higher level processes will break off into smaller ones. For example, process mapping new product development. Many areas in the company each with thier own smaller process will become part of the bigger map. On the simpler end is a process map for making the morning coffee, were everything is local and can flow in sequencial events. In both cases. the map should be a step by step recreation of actual events, including decision points.

[Jim Wynne]

In Reply to Parent Post by JaneB

What do you mean by a 'process map'? A few discussions in a couple of recent threads reminded me that this term is often used to mean different things, which can be very confusing for the 'uninitiated'.

I'm interested to see if there's a broad consensus of meaning (or not), and what people think a process map 'should' be / contain / look like.

In general, process maps are confused masses of symbols, arrows and text that purport to explicate the interactions of processes. In most cases they do nothing of the kind and serve mainly to have something shiny and colorful to present to a CB auditor as evidence of understanding process interactions. Give me good ol' logically derived process flow diagrams any time. Or better yet, actually describe in writing how processes interact.

[Stijloor]

In Reply to Parent Post by Jim Wynne

In general, process maps are confused masses of symbols, arrows and text that purport to explicate the interactions of processes. In most cases they do nothing of the kind and serve mainly to have something shiny and colorful to present to a CB auditor as evidence of understanding process interactions. Give me good ol' logically derived process flow diagrams any time. Or better yet, actually describe in writing how processes interact.

I believe that "a picture is worth a thousand words." The problem is that folks developing these process maps are trying to cram way too much information on an 8.5 x 11 (or an A4) piece of paper. The scope of the map is not set right so it becomes indeed a "mass of symbols, arrows and text."

The new AIAG FMEA 4th Ed. manual shows a neat (simple) example of how a process map (high level) can be broken up into separate flow charts (lower level).

But then again, I am a picture guy...

Stijloor.

[joshua_sx1]

process map – is an overall methodology plan of how each major activity within an organization interact or connected with each other…

...then describing the detailed of how each major activity shall be carried-out can be done using flowcharts, procedures and/or working instructions… (and as required) supported by forms to have an evidence that they were performed accordingly…

[Peter Fraser]

In Reply to Parent Post by JaneB

What do you mean by a 'process map'? A few discussions in a couple of recent threads reminded me that this term is often used to mean different things, which can be very confusing for the 'uninitiated'.

I'm interested to see if there's a broad consensus of meaning (or not), and what people think a process map 'should' be / contain / look like.

Jane

About time too, thanks! The use of the term has been causing confusion for far too long - have you ever been in a meeting and discovered after a couple of hours that someone is talking about something different from what you thought, because they are using a term that you thought "everyone knows what that means" but they use it differently? Or (even) reading posts in a forum for years and then suddenly realising that some posters are doing the same!

As is often the case, there is no "right" answer. Deming talked of "operational definitions" - what terms mean in a particular context. The important thing is that the meaning is understood by everyone, and that isn't the case here.

And other examples make it worse ... a "town map" and a "street map" are probably the same thing - ie a map (a visual or diagrammatic representation) of a town, made up of streets. But you wouldn't talk of a "town map" if you meant a map of a country which showed the main towns.

To me, if a "map" is a "visual or diagrammatic representation" of what is mapped, then the ideal would be to call the "picture" of your management system a "system map", and reserve "process map" (or similar) for the description of an individual process.

What is also important is why these various types of "map" are produced - I have seen enough (bad) examples to suggest that many of them confuse rather than clarify, and often they are produced because the author thinks that they have to draw one rather than because their target audience will gain benefit.

[Umang Vidyarthi]

In Reply to Parent Post by JaneB

What do you mean by a 'process map'? A few discussions in a couple of recent threads reminded me that this term is often used to mean different things, which can be very confusing for the 'uninitiated'.

I'm interested to see if there's a broad consensus of meaning (or not), and what people think a process map 'should' be / contain / look like.

A 'Process Map' is a bird's eye view of a process or processes, giving you broad information about the process in one shot. Just like a picture.

BTW the 'uninitiated' also get confused with synonymous terms viz: Process flow diagram, process flow chart, process model etcetra.

Umang

[Bifften]

My understanding and use of the term "Process Map" is something that shows a single process (be it macro (high level) or micro (low level). These maps can include graphics, symbols and text descriptions.

I can and do have several processes which means several "Process Maps" which can all be related / linked.