I’ll need to provide context, first noting that problem ‘handling’ was stressed as opposed to problem ‘solving’. Why? Because ‘solving’ may give the impression that one swing of the bat and, check, problem solved.
Over the 3.5 days we had four groups from two production lines, four leaders in each, the leaders being a mix of TLTs (Team Lead Trainers), Supervisors and Value Stream Managers. Each group had a focus operation (or operations), the pre-requisite being work standards had been developed and were robust. (There’s no point in practicing problem handling where standards are unclear as very likely that will be a major contributing cause.)
The morning of Day 1 we had the four groups in the room plus quite a number of operations, maintenance and site senior leaders. The purpose for our 3.5 days was set, definitions fleshed out. The afternoon of Day 1 the four groups practiced problem handling on a simulated manufacturing system. We finished with confirming the four groups focus operations and how they’d start Day 2 – a comparison of what’s actually happening compared to ‘normal’ (as described in their work standards) then get going with problem handling practice.
Day 2 and Day 3 were just that – several rounds of ‘at focus operation’ practice, return to our training room and updating all, then back out to the focus operation. Much of the practice time was spent, Planning, Doing, Checking then Adjusting. The morning of the Day 4 site senior leaders came back in the room for an update on what had happened and to learn of key things that had arisen.
Now to the three significant learning moments …
The first
On the morning of Day 3 Jennifer Myers (TLT), as I opened the morning, said “Can I say something please?”
“Of course.” (Even if I’d not wanted her to, I wasn’t going to stop Jennifer!)
“As a lot of you know, I’m usually late to most things. Yesterday evening I planned to change my routine to leave earlier this morning. I did change my routine, I checked what time I got here, I was on time, so now, given what I learned, I’ll do the same thing tomorrow. This PDCA thing is something we do outside of work all the time, we just don’t realise it.”
What Jennifer said was gold. My response was “Exactly, we’re not asking you to do something new here, something you’ve never done before. We’re just seeking to help you become more intentional and deliberate about it while at work.”
The second
During the Day 4 morning session with senior site leaders the workshop participants explained the adjustment to their Leader Standard Work for the next two weeks. (Their purpose being to maintain reasonable momentum in continuing to practice problem handling.) Hunter McKee (VP Operations) responded with “I’m going to change a question I ask when out on our production floor. Instead of asking what problems there are, I’m going to say ‘what problem are you working on and what are we learning about it?’
It was fantastic to hear Hunter say this; it being a small but tremendously powerful adjustment from a senior leader that can only have a positive effect on site culture.
The third
This I didn’t respond to well at the time.
In the Day 1 morning session there was some debate as to whether ‘standardize’ should be explicitly stated within the PDCA cycle. At the time I essentially said it was implicit and left it at that. I thought about it afterwards, that wasn’t good enough, so I contacted the person who raised the point and said what follows.
First, ‘standardized’ needs to be defined. Standardized is a condition. It’s the condition that exists when what’s happening in the workplace matches what is required (stated in a work standard for example). Once the ‘best state’ has been determined through experimenting and there is a need to standardize, doing so is not one action … One needs to:
- Plan to standardize – adjust a document maybe; communicate the change; train those who do the work; other?
- Do – do as planned.
Don’t now assume ‘standardization’. That’s what we usually do.
- Check – does what’s now happening in the workplace match what is required? (My experience has been sometimes there’s still not a match. Standardization can take more than one go around …) So, what was learned?
- Adjust – may or may not be necessary!
To summarize the point, the act of standardizing is itself best considered a PDCA cycle.
It was a very good 3.5 days, the feedback was very positive, those above are key learnings. As I said early on, they were the ‘notables’ of many. Thank you McKee Foods Collegedale, it took quite a bit of preparation and commitment of people’s time during the week.