|
Elsmar Cove Forum Sidebar
|
|
|
|
Monitor the Elsmar Forum
|
| Monitor New Forum Posts
|
|
Follow Marc & Elsmar
|
|
|
Elsmar Cove Groups
|
|
|
Sponsor Links
|
|
|
|
|
|
Donate and $ Contributor Forum Access
|
 |
|
Sponsored Links
|
|
|
|
Courtesy Quick Links
|
 Links that Elsmar Cove visitors will find useful in your quest for knowledge:
Howard's International Quality Services
Atul's Symphony Technologies
Marcelo Antunes' SQR Consulting
Bob Doering's Correct SPC - Precision Machining
NIST's Engineering Statistics Handbook
IRCA - International Register of Certified Auditors
SAE - Society of Automotive Engineers
Quality Digest Portal
IEST - Institute of Environmental Sciences and Technology
ASQ - American Society for Quality
|
|
 |

2nd February 2012, 10:51 AM
|
|
Shy Poster (1 to 5 Posts)
Registration Date: Aug 2007
|
|
Posts: 4
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 24 Karma: 10 
|
|
Business Case for Process Mapping
What are some of the tried and tested approaches to successfully "selling" things like 1)process mapping, 2)documentation, and 3)roles and responsibilities definitions to business sponsors who expect immediate and hard financial benefits/savings from process improvement/change professionals and yet do not have the basics in place ?
|

2nd February 2012, 01:28 PM
|
 |
Forum Moderator
Registration Date: Jan 2004
Location: Maine, USA
|
|
Posts: 5,205
Thanks Given to Others: 2,980
Thanked 2,833 Times in 1,625 Posts
Karma Power: 612
|
|
|
Re: Business case for process mapping
The business case is usually avoiding cost of failure. Many examples can be found using Google, including this short list:
Software: The Economic Impacts of Inadequate Infrastructure for Software Testing
Medical, specifically surgery: Prevention of Retained Sponges and Towels Following Surgery
Human resources: High Cost for No Procedure and Confusion over Holiday Pay
Of course not all benefits for planning our work bring immediate reward, and similarly failure from lack of planning isn't immediate either. Consequences of failure can take time while one's luck (or resources) runs out, so to speak. The more complex the work/the more people with which the work is to be done, generally the less time failure takes.
But again, there is no set rule because personal craftsmanship (sheer skill and pride to do work fastidiously) can ward off failure. Of course fastidious craftsmen wouldn't dream of doing critical steps out of sequence or assigning fine work to unskilled people. They just didn't often find it necessary to write all that stuff down. When the assembly line (maybe even dating as far back as the pyramids) craved replacable people doing work without deviation, the need to formally define what they do was realized.
From how your post read I do not envy your position. Are you an employee?
__________________
"If you only have a hammer, you tend to see every problem as a nail." Abraham Maslow
|

2nd February 2012, 01:29 PM
|
 |
Involved in Discussions
Registration Date: Jun 2010
Location: Massachusetts, USA
|
|
Posts: 97
Thanks Given to Others: 24
Thanked 61 Times in 41 Posts
Karma Power: 23
|
|
|
Re: Business case for process mapping
Others may have a different experience here, but I have never seen a successful case for "selling" management on the need to map processes, define roles and such all on its own merit.
What's you're proposing is like telling a person that the foundation of their house has some flaws and needs to be repaired even though the house is in no immediate danger of collapsing. You'll go in, jack the house up, put in a spiffy new foundation, set the house back down and no one will be aware as nothing will be visible. That's a tough sell.
What I have seen however follows this mantra: When you take time to do something over, you prove that you had time to do it correctly the first time.
Reactions to major audit findings, being shut down by a regulatory body (FDA, FAA, etc.) or missed financial results are some of the best "burning platforms" to get the OK to characterize your processes.
What business managers ("leaders") need is a good degree of predictability in their views. If they can't predict or forecast well, they pay the price for it over time. Good process management is foundational to predictability.
So if you are going to try and convince your managers to let you map and characterize, are there any examples within your industry of other companies who have taken these actions after poor audits or missed earnings? Since most managers are money focused, look for companies that started improvement programs after they had poor financial performance.
Hope it helps.
Cheers,
Adam
|

2nd February 2012, 02:16 PM
|
|
Involved in Discussions
Registration Date: Feb 2012
Location: Florida
|
|
Posts: 60
Thanks Given to Others: 12
Thanked 35 Times in 22 Posts
Karma Power: 12 Karma: 185  
|
|
|
Re: Business Case for Process Mapping
If your management hasn't bought into the commitment to quality, you will never sell process mapping, documentation or anything else.
|

3rd August 2012, 05:00 AM
|
 |
Involved in Discussions
Registration Date: Nov 2004
Location: United Kingdom. Oop North.
|
|
Posts: 18
Thanks Given to Others: 1
Thanked 2 Times in 1 Post
Karma Power: 36 Karma: 20 
|
|
|
Re: Business case for process mapping
A Bit of thread neccromancy, but try just doing it for a single process.
Get the buy in of the people in the area.
Ask them to tell you how it works, then map it, and reduce the procedures to the map and some supplementary information (75% reduction in word count is typical)
Make sure it has inputs (parts/materials/requests from other departments) identified
make sure it likewise has outputs identified (deliverables to other departments or the customer)
Think about colour coding it to identify responsibilities for the tasks identified
And take a copy of it and stick it on the wall.
The buy from users will help them to follow the process once published.
This will probably increase productivity/efficiency
The colourful chart will attract attention and interest
the two together will strengthen the argument that the approach should be used else where
then make sure the inputs and the outputs from the different departs ments match each othehr and you've process mapped the whole business!
Simples.....
__________________
Pistonbroke
Quality and Security
|
Lower Navigation Bar
|
|
|
Do you find this discussion thread helpful and informational?
|
Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate Thread Content |
Linear Mode
|
|
Forum Posting Settings
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|