Turtle Diagrams (via Concentric Management Systems, Inc.)

After reviewing statistics from our website dashboard this morning, we were surprised to see that the #1 driver to our website is a search for the words “Turtle Diagrams”. Special thanks to our friend – the turtle!

For years now we have heard a handful of our customers fight with the concept of using a turtle diagram. Recently, I was in a heated discussion with an Engineering Manager who felt very strong about his position that “…turtle diagrams are a waste of time because they are only used during audits… to help an auditor be more efficient in his audit of us”.

Well… yeah. I mean, PERFECTLY said (and thanks for making the argument easier for me Mr. Resister!). Turtle Diagrams at this organization were often only used by the auditors. But that doesn’t mean that they were intended for the auditors. They were INTENDED for processes owners; a 1-page diagram that should be used to keep them on track with the expected outputs of the process they are responsible for. (Note: I said “process” they are responsible for and not “department” they are responsible for.)

Now, to address the portion of his statement: “…to help an auditor be more efficient in his audit of us”. What’s wrong with being efficient as an auditor? Furthermore, what’s wrong with being efficient and organized as a process owner? The more focused you remain on the key deliverables, and the key resources needed to achieve these deliverables, the better chance you have at meeting the needs of your boss (your BOSS boss and your Customer).

Think of a turtle diagram as a point on the global when you go to Google Earth. Before you start navigating north, east, south or west, you first need to make sure you are on the right continent. From there, you can fine-tune and make adjustments. Start your process definition as a very high level. Gather all of the key resources, evaluate your strengths and weaknesses on the turtle and fine-tune from there.

For those of you who prefer a more mathematical explanation, work instructions are to assembly operators as turtle diagrams are to top managers responsible for the performance of a certain business process. Without identifying key outputs – critical to internal and customer satisfaction – it becomes difficult to align all of your tactical resources (man, machine, method, metrics, measurement systems, etc.) in order to achieve your strategic-level goals.

I encourage each organization that uses or considers using turtle diagrams to step back and evaluate the intent of this tool. Like any tool, turtle diagrams are only valuable if used as intended.

Turtle Diagrams Instructions for Creating a Turtle Diagram A “Turtle Diagram” is a quality tool used to visually display process characteristics such as inputs, outputs (expectations), criteria (metrics) and other high-level information to assist in the effective execution and improvement of key business processes. While there is no requirement per ISO 9001 or TS 16949 to create or manage turtle diagrams, I have worked with organizations who use turtle diagrams … Read More

via Concentric Management Systems, Inc.

Satellite or Baseball?

Does your management system look like a satellite or a baseball?
The following question is meant to challenge management system professionals and their respective organizations.  How are you using your management system?  Is your management system being used as the foundation within your organization to build control, predictability and improvement processes for total performance optimization?  Or is your management system simply a “satellite” that hovers around the organization occasionally communicating back to planet earth?

The following short presentation can be used to prompt these questions and explore the whether you are meeting the INTENT of registration processes such as ISO 9001, ISO/TS 16949, AS9100, etc.

Presentation: http://cmsicharleston.files.wordpress.com/2011/06/asq-presentation-satellite-or-baseball-6-28-11.ppsx

Assessment Worksheet:  http://cmsicharleston.files.wordpress.com/2011/06/priorities-gap-assessment-6-28-11.docx

Lean Documentation

I was asked an interesting question this week from a colleague.  “Should I start over from scratch or fix my current mess of documents?”  This seems to be a theme lately that many of us are seeing.  I’d like to think of it as a very good question and a sign of good things to come.  When businesses start asking questions like this, my hopes are that they are no longer fighting to stay alive, but now in a mode to fight.  I’m hoping this by asking this question, a key player in an organization is taking his or her initial steps towards a lean document system that allows for quick reference to key documents, rather than system that is comparable to a needle in a haystack.  Now on to the answer I gave…

At the most fundamental level, you need to start with standard requirements and/or the intial intent of documents.  What is the purpose?  What do you want to get out of these organized bits of words and wisdom?

Unless there is a special business requirement from a Customer, organizations need to keep in mind that every document created comes at a cost.

I see organizations on a regular basis with hundreds or thousands of different documents claiming to be of value.  Past experience with a “say what you do, do what you say and document it” approach sometimes makes one blind to the original intent.  As an example, ISO 9001 only requires 6 documented procedures. Unless there is a special business requirement from your Customer, organizations need to keep in mind that every document created comes at a cost. The cost can add up quickly in two ways – cost of maintenance and cost of distracting from (or “watering down of”) more important documents.

Start at the highest level possible and create a blank slate for storing the Top 20 procedures (or whatever number makes sense that is less than 20). The “blank slate” could be a fancy database or literally a BLANK SLATE.  From there, clear ownership needs to be assigned for each document, ideally adopted and maintained by each actual process owner within the organization.  Secondary procedures, instructions, forms, etc. can be referenced from there.  We strongly recommend that each document, at all levels, have a parent procedure that is tied back to a specific requirement or business need.  (The preference is a link back to the business need such as a business plan line item or corporate guidance manual.)

Like any 5S exercise, the orphan documents without a home or business need should be sorted out and archived so the valuable documents have the best chance to be used as the valuable business tools that they are.

Follow

Get every new post delivered to your Inbox.

Join 42 other followers