What IS a Process Map?

What IS a 'process map' to you?

  • It illustrates MULTIPLE processes (eg, flowchart, diagram or similar)

    Votes: 14 30.4%

  • It describes MULTIPLE processes (mainly or all text)

    Votes: 3 6.5%

  • It shows MULTIPLE processes (combines graphics/diagram & text descriptions)

    Votes: 14 30.4%

  • Sets out a SINGLE process only, graphically (eg, flowchart etc)

    Votes: 9 19.6%

  • Describes a SINGLE process only, in text

    Votes: 1 2.2%

  • It can show either MULTIPLE processes, or a SINGLE process

    Votes: 15 32.6%

  • I don't really know

    Votes: 1 2.2%

  • I avoid 'process maps'

    Votes: 2 4.3%

  • There's no difference between a 'process map' and a documented 'procedure'

    Votes: 3 6.5%
  • Total voters
    46
J

JaneB

Interesting - a range of viewpoints.

The poll results do seem to indicate some broad agreement on two points - if not total consensus :D

  • A 'process map' can illustrate either a single process or multiple processes
  • It is definitely not an 'all text' thing, though it usually has some text with it (eg, perhaps to explain or identify)

Beyond that... a whole range of different opinions on what it is, or what it 'should' or 'should not' be.

I do think the 'single vs multiple' point is an important one. It helps explain some of the confusion that can arise during discussions of process maps, particularly for the new or inexperienced.

After all, if 'my' mental model of a process map is firmly multiple and 'your' mental model is of a single process only, there's heaps of potential for confusion.

I also agree with Jim but only to a point. I love clear diagrams. But I dislike very busy ones, or ones that are not easy to understand, and in fact require considerable explanation!! So I'd agree that a clearly written description could be better than a poor process map. But then of course, a good process map would also be much better than a verbose and bad description!:lol:
 
B

Bifften

Involved In Discussions
The Basics of Process Mapping by Robert Damelio was also helpful to me:

It suggests there are 3 types of "Process Map"

1) Relationship Map -
Shows supplier-customer relationships (which functions or parts of the organization receive inputs from and provide outputs to one another)

Level of detail: Least

Focus - Organisation Context

Relates pieces of the organisation to one another, answers the question: What does the organisation provide to its internal and external customers?

2) Cross functional Process Map -
Shows functions, steps, sequence of steps, inputs, and outputs for a particular work process

Level of detail: Medium

Focus - Process / People Interface

Shows supplier/ customer linkages for a single process. Answers the question, What steps does the organisation perform to provide outputs to its internal and external customers? And who performs each step?

3) Flowchart -
Shows tasks, sequence of tasks, inputs and outputs for a particular work process

Level of detail: Most

Focus - Process Detail

Shows detailed tasks that make up a process. Does not show supplier-customer linkages. Answers the question, How does the work actually get accomplished?


Personally I am working on producing Flowcharts (3) at the moment in my work, high detail, step by step work flows. In my organisation this is what is commonly refered to as Process Mapping.
 
Peter Fraser

Peter Fraser

Trusted Information Resource
Bifften said:

3) Flowchart -
Shows tasks, sequence of tasks, inputs and outputs for a particular work process

Level of detail: Most

Focus - Process Detail

Shows detailed tasks that make up a process. Does not show supplier-customer linkages. Answers the question, How does the work actually get accomplished?
Click to expand...


Even at the "flowchart" level it subdivides - a "process flowchart" shows what is done, and a "deployment flowchart" shows who does it and who else is involved. And you can use "RACI" (or a variation) to show the type of involvement. It helps get away from this apparent "obsession" that some folk have with finding a "supplier" and a "customer", and "inputs" and outputs", for everything that moves - or at least puts the description of how work is done into terms that the average worker can relate to!
 
I

Intesar

I believe:notme:

Its advantages:

Save time:
just by a quick look at it you understand it & you may be able to locate the critical steps
Easy to correct and improve:
just by editing an arrow or a box


thanks all
 
A

ashwaniraina82

Umang Vidyarthi said:
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 :2cents:
Click to expand...


dear umang,


well said

but sometimes it reveals more than an overview
 
Last edited by a moderator:
N

navalbhawsar

Mapping up of a process in different way perhaps may give simple idea about process map. May be presented graphically with symbols and text to synchronizes a process step by step to indicate input and out put.
 
H

Hondo812

A Process Map provides the details of the the process (aka the steps), the time(s) involved per step, and may include where applicable what department/person is responsible. A basic flowchart only covers the first of these, typically.

Now, to the person that started this thread, the real question is not what a process map is, but rather what do you expect to get out of it? It has been my experience that it provides a baseline from which I can reasonably measure the level of improvements to the process by changes that are implemented. Change is the name of the game to be competitive in manufacturing and as Churchill once said, " To improve is to change, to be perfect is to change often". The process map is one tool used to evaluate change.
 
J

JaneB

Hondo812 said:
A Process Map provides the details of the the process (aka the steps), the time(s) involved per step, and may include where applicable what department/person is responsible. A basic flowchart only covers the first of these, typically.
Click to expand...

Interesting viewpoint & a good illustration of how very differently the term 'process map' is used, and how differently people think about what should/should not be included.

For example, in many if not most processes in service-based firms, it would be absolutely meaningless (and often quite ludicrous) to attempt to put in the 'time involved per step' - whereas I see that it is seen as often critically important in a manufacturing field.
 
Peter Fraser

Peter Fraser

Trusted Information Resource
JaneB said:
For example, in many if not most processes in service-based firms, it would be absolutely meaningless (and often quite ludicrous) to attempt to put in the 'time involved per step' - whereas I see that it is seen as often critically important in a manufacturing field.
Click to expand...

This is at least partly because in manufacturing you want to minimise variation, but in service you are more likely to want to tailor your delivery to meet the circumstances, the customer and even the capability of the person providing the service. (Which is why the ISO9000 definition of a "process" hinders rather than helps in such situations)
 
H

Hondo812

JaneB said:
Interesting viewpoint & a good illustration of how very differently the term 'process map' is used, and how differently people think about what should/should not be included.

For example, in many if not most processes in service-based firms, it would be absolutely meaningless (and often quite ludicrous) to attempt to put in the 'time involved per step' - whereas I see that it is seen as often critically important in a manufacturing field.
Click to expand...


I would strongly disagree with your assessment. I worked with a firm that had a Customer Service department that kept track of the number of calls answered per hour, the average call time, the average wait time, etc. They obviously thought that managing those times was important. I have seen here in the last 2-3 weeks a repair center manager asking specific questions about mapping his process, mention of office processes time study data, and references to this article https://www.ad-mkt-review.com/public_html/air/ai200611.html and how tackling the white collar sector is a task vital to the survival of business.

I have worked at other firms that have addressed some of the soft issues like purchase orders. We mapped the original process, identified area of waste and streamlined the process to yield a cut of approximately 50% in delivery time. The firm that I am with at the moment tracks time for ECO's. Date initiated to date approved. The process is mapped and routinely evaluated to see if there are areas for improvement.

I don't find the notion of looking at service industry processes ludicrous at all.
 
You must log in or register to reply here.

Similar threads

J
Document hierarchy for Process mapping for ISO13485
Replies
7
Views
613
Tidge
T
L
Process Interaction push back during Stage 1
Replies
7
Views
557
qusys
Q
J
SOC 2 information security auditing
Replies
0
Views
1K
john.b
J
E
IATF 16949 QMS in OEM
2 3
Replies
20
Views
2K
Sidney Vianna
Sidney Vianna
D
Review/Recommendations: requirements management tools/software
Replies
1
Views
201
yodon
Y
Top Bottom