When Standards are in Place, Everything is an Experiment
A huge take away from some of the studying of Toyota and case studies I have seen is that everything they do is considered an experiment. Every cycle on the assembly line. Every product development project. Every meeting. Everything is a test to see if they got the expected results from the process. If not, why?
It may seem excessive but it isn’t. If a process is designed to deliver certain results then we are doing ourselves a disservice if we aren’t stopping to ask if the process did deliver the expected results. If not, why? If so, why? What can we learn? Positive or negative.
This can be applied to all work. Many studies state that having an agenda and a plan for a meeting is important to making meetings effective. If that is the case (and it has been in my experience) then afterwards we should ask if we accomplished what we had on the agenda and did we stick to the timeline?
A person example is the agenda I use to conduct improvement (or commonly called kaizen) events. I have a detailed 3-day agenda that is my standard work. Each time I have timing information for every phase of the agenda. During the event, I note the time that I move on to the next phase. After the day is over, I reflect to understand if my experiment is working or not. If something took more time I try to understand why. If it went quickly I try to understand that too.
Approaching each improvement event as an experiment that is testing my standard process has allowed me to learn and create new ways to approach different phases of my agenda. I have discovered quicker and more effective ways to accomplish some of the tasks.
To truly learn and improve a person has to look at everything as an experiment testing our standards. People need to be open to learning with everything they do.