SlideShare una empresa de Scribd logo
1 de 10
Descargar para leer sin conexión
6 reasons
standards fail
Created by Tom Curtis 2012
Blog: www.onimproving.blogspot.com
Presentations: on www.slideshare.net/onimproving
Email: ideamerchants@gmail.com
Twitter: @onimproving
Standards often fail. If we can recognize major
reasons why, we can help them thrive and reap the
benefits of solid standards. To not do so creates or
   at minimum allows waste. What follows are 6
 reasons they fail. Let us learn them and keep our
   standards solid. The success of our standards
                    depends on it.
Standards fail because...
they are not
                               standards
  If it is not the agreed upon current best and safe way
 something is to be done, it is not a standard. To want
 something to be done a certain way does not make it a
 standard. “Standards” are sometimes written without
the involvement of those who are to follow them. Such
  are not standards. If we think are standards, but do
 not meet the definition above, they are not standards.
they are not
                              important
If we do not make and keep standards important they
will fail. We show in our time, focus, and maintenance
whether standards are important. If we say one thing
 and do another there is no standard. Standards that
  are important are talked about, updated, kaizened,
trained, checked and used. Non important standards
  create waste in processes and frustration in people.
they are not
                                  trained
To not train affected individuals in the standard almost
    guarantees failure. Not training will leave some
 individuals unaware of the standard and others with
   less than full understanding. A standard must be
 trained to introduce and trained routinely to remind
   and correct deviation. Remember telling without
practice along side, will leave the gap between training
    and action wide. We must train and train again.
they are not
                                   alive

 Standards that are alive are current and in use. They
  are updated upon kaizen or process change and the
  affected employees are retained. This is not the case
for dead standards. Dead standards are like plants that
   are not watered, they may still be there, but are no
        longer performing their original function.
they are not
                                checked

   If we do not check and audit frequently and then
correct, standards will erode. Checking may come in
 many forms: auditing, visual control, or poke yoke.
Each of our activities may require something different
or a consistent approach may best suit our needs. The
       important thing is to do it and do it often.
they are not
                                      kept
 When we think about Standards failing, this is where
 many of us start. There is a reason this is number six.
This is often caused by the the prior five. This is not to
     say this is not an issue, but it is rarely the most
  important root cause. If we fix the more significant
   reasons we will be properly positioned to help our
employees succeed in keeping the Standards. They will
 feel respected, understand why, and have ownership.

Más contenido relacionado

Más de Tom Curtis

Required Ahead
Required AheadRequired Ahead
Required Ahead
Tom Curtis
 

Más de Tom Curtis (20)

I.C.E.: Model for Better Meetings
I.C.E.: Model for Better MeetingsI.C.E.: Model for Better Meetings
I.C.E.: Model for Better Meetings
 
Aligning language for creativity cultivation
Aligning language for creativity cultivationAligning language for creativity cultivation
Aligning language for creativity cultivation
 
PRESENT: a model to aid presentation
PRESENT: a model to aid presentationPRESENT: a model to aid presentation
PRESENT: a model to aid presentation
 
a baker's dozen on basics
a baker's dozen on basicsa baker's dozen on basics
a baker's dozen on basics
 
Lean License Plates
Lean License PlatesLean License Plates
Lean License Plates
 
FACES: questions for effective visual boards
FACES: questions for effective visual boardsFACES: questions for effective visual boards
FACES: questions for effective visual boards
 
8 ways to earn simplicity
8 ways to earn simplicity8 ways to earn simplicity
8 ways to earn simplicity
 
50 Roles of a Father
50 Roles of a Father50 Roles of a Father
50 Roles of a Father
 
COACH: a model to aid improvement
COACH: a model to aid improvementCOACH: a model to aid improvement
COACH: a model to aid improvement
 
RCCA
RCCARCCA
RCCA
 
The Hidden Impacts of Small Errors
The Hidden Impacts of Small ErrorsThe Hidden Impacts of Small Errors
The Hidden Impacts of Small Errors
 
Leanrequiresscriptiocontinua
LeanrequiresscriptiocontinuaLeanrequiresscriptiocontinua
Leanrequiresscriptiocontinua
 
6 Word Lean Wisdom Gems
6 Word Lean Wisdom Gems6 Word Lean Wisdom Gems
6 Word Lean Wisdom Gems
 
ABC's to Kaizen on
ABC's to Kaizen onABC's to Kaizen on
ABC's to Kaizen on
 
Lean Proverbs
Lean ProverbsLean Proverbs
Lean Proverbs
 
Required Ahead
Required AheadRequired Ahead
Required Ahead
 
Jr Bird Color Riddles
Jr Bird Color RiddlesJr Bird Color Riddles
Jr Bird Color Riddles
 
Jr Bird Shape Riddles
Jr Bird Shape RiddlesJr Bird Shape Riddles
Jr Bird Shape Riddles
 
andon line stops drive...
andon line stops drive...andon line stops drive...
andon line stops drive...
 
Lean Birds Speak on Kaizen
Lean Birds Speak on KaizenLean Birds Speak on Kaizen
Lean Birds Speak on Kaizen
 

Último

Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo DiehlFuture Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
Peter Udo Diehl
 

Último (20)

Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo DiehlFuture Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl
 
IoT Analytics Company Presentation May 2024
IoT Analytics Company Presentation May 2024IoT Analytics Company Presentation May 2024
IoT Analytics Company Presentation May 2024
 
Designing for Hardware Accessibility at Comcast
Designing for Hardware Accessibility at ComcastDesigning for Hardware Accessibility at Comcast
Designing for Hardware Accessibility at Comcast
 
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdfSimplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
 
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdfWhere to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
 
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
 
The Metaverse: Are We There Yet?
The  Metaverse:    Are   We  There  Yet?The  Metaverse:    Are   We  There  Yet?
The Metaverse: Are We There Yet?
 
Strategic AI Integration in Engineering Teams
Strategic AI Integration in Engineering TeamsStrategic AI Integration in Engineering Teams
Strategic AI Integration in Engineering Teams
 
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone KomSalesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom
 
Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)
Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)
Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)
 
Oauth 2.0 Introduction and Flows with MuleSoft
Oauth 2.0 Introduction and Flows with MuleSoftOauth 2.0 Introduction and Flows with MuleSoft
Oauth 2.0 Introduction and Flows with MuleSoft
 
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...
 
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdfHow Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
 
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...
 
Google I/O Extended 2024 Warsaw
Google I/O Extended 2024 WarsawGoogle I/O Extended 2024 Warsaw
Google I/O Extended 2024 Warsaw
 
Speed Wins: From Kafka to APIs in Minutes
Speed Wins: From Kafka to APIs in MinutesSpeed Wins: From Kafka to APIs in Minutes
Speed Wins: From Kafka to APIs in Minutes
 
WSO2CONMay2024OpenSourceConferenceDebrief.pptx
WSO2CONMay2024OpenSourceConferenceDebrief.pptxWSO2CONMay2024OpenSourceConferenceDebrief.pptx
WSO2CONMay2024OpenSourceConferenceDebrief.pptx
 
Optimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through ObservabilityOptimizing NoSQL Performance Through Observability
Optimizing NoSQL Performance Through Observability
 
PLAI - Acceleration Program for Generative A.I. Startups
PLAI - Acceleration Program for Generative A.I. StartupsPLAI - Acceleration Program for Generative A.I. Startups
PLAI - Acceleration Program for Generative A.I. Startups
 
A Business-Centric Approach to Design System Strategy
A Business-Centric Approach to Design System StrategyA Business-Centric Approach to Design System Strategy
A Business-Centric Approach to Design System Strategy
 

6 Reasons Standards Fail

  • 2. Created by Tom Curtis 2012 Blog: www.onimproving.blogspot.com Presentations: on www.slideshare.net/onimproving Email: ideamerchants@gmail.com Twitter: @onimproving
  • 3. Standards often fail. If we can recognize major reasons why, we can help them thrive and reap the benefits of solid standards. To not do so creates or at minimum allows waste. What follows are 6 reasons they fail. Let us learn them and keep our standards solid. The success of our standards depends on it.
  • 5. they are not standards If it is not the agreed upon current best and safe way something is to be done, it is not a standard. To want something to be done a certain way does not make it a standard. “Standards” are sometimes written without the involvement of those who are to follow them. Such are not standards. If we think are standards, but do not meet the definition above, they are not standards.
  • 6. they are not important If we do not make and keep standards important they will fail. We show in our time, focus, and maintenance whether standards are important. If we say one thing and do another there is no standard. Standards that are important are talked about, updated, kaizened, trained, checked and used. Non important standards create waste in processes and frustration in people.
  • 7. they are not trained To not train affected individuals in the standard almost guarantees failure. Not training will leave some individuals unaware of the standard and others with less than full understanding. A standard must be trained to introduce and trained routinely to remind and correct deviation. Remember telling without practice along side, will leave the gap between training and action wide. We must train and train again.
  • 8. they are not alive Standards that are alive are current and in use. They are updated upon kaizen or process change and the affected employees are retained. This is not the case for dead standards. Dead standards are like plants that are not watered, they may still be there, but are no longer performing their original function.
  • 9. they are not checked If we do not check and audit frequently and then correct, standards will erode. Checking may come in many forms: auditing, visual control, or poke yoke. Each of our activities may require something different or a consistent approach may best suit our needs. The important thing is to do it and do it often.
  • 10. they are not kept When we think about Standards failing, this is where many of us start. There is a reason this is number six. This is often caused by the the prior five. This is not to say this is not an issue, but it is rarely the most important root cause. If we fix the more significant reasons we will be properly positioned to help our employees succeed in keeping the Standards. They will feel respected, understand why, and have ownership.