Does the Shewhart cycle still do the job?

Does the Shewhart cycle still do the job?

Every improvement project at some point refers to the Shewhart cycle: Plan, Do, Check, Act. I have used it extensively myself, but never been fully comfortable with the language of the last two points in the cycle, and the actions that the language implies.

Plan, Do, Check, Act.

Plan. Planning is essential, it is a fundamentally important part of any project, no matter how big, or small. If nothing else, a plan articulates the points of departure as the journey progresses.

Do. Again, doing is essential, without the doing, the planning is just a dream, someone’s illusion of activity.

Check. This is the point where I start to have problems. The word has two unfortunate connotations. The first is to ‘Stop’, not a good idea in a continuous improvement process. The second, its use in the context of checking someone’s ‘homework’, have they done what they said they would do, by the time agreed? Again, this is necessary, but in my experience in a supposedly collaborative group, when the ‘leader’ is doing the checking, the dog gets busy with the homework. It is better for those in the group to self-manage their commitments to each other and let the group dynamics take care of the laggards. It is the leader’s job to encourage the evolution of the ‘group culture’ that enables this to happen. Therefore, I will propose we replace ‘Check’ with ‘Review’. When we review progress in a regular meeting, or by whichever method is used, the review will ensure that the work is done as agreed. However, review has a wider meaning which makes it way more valuable. It implies that not only does the group review the work to date, and review the reasons for variations, it encourages a wider review of the context and causes of those unexpected outcomes, and variations from the planning hypothesis.

Act. The final step. Act can sometimes feel disconnected from the previous step of Check. It is even more distant if we alter the naming of the previous step to ‘Review’. I would therefore propose we change the ‘Act’ to ‘Adjust’. This change implies that based on the outcomes of the ‘review’ process, we have now ‘Adjusted’ our actions appropriately. We can then repeat the process, starting again at plan, as we now have a more robust set of data to work with as we evolve more informed hypotheses to test.

Plan, Do, Review, Adjust.

Replace the PDCA cycle with the PDRA cycle?

Perhaps a bit presumptuous of me to suggest such heresy, but working with those SME’s that make up the bulk of my client base, it makes sense both to me, and more importantly, to them.

It is a little thing, just two words, but little things are cumulative, and do eventually can make a significant contribution.

A marketer’s explanation of Standardisation and Continuous Improvement.

A marketer’s explanation of Standardisation and Continuous Improvement.

Anyone who has read ‘The Goal’ by Eli Goldratt, the original brain behind the theory of constraints, will remember the story in the book about Herbie, the slowest walker in a scout group in a cross-country walk. Herbie was the bottleneck, in that he set the pace of the others, as the group did not want to leave Herbie behind in the woods.

One solution would have been to just get Herbie to walk faster, but that would have moved the ‘bottleneck’ position previously held by Herbie to the next slowest walker.

Whatever they did, the line of walking scouts would spread out, particularly going uphill, and then squeeze back in, going downhill. A walking accordion.

How do you prevent such a hard to manage outcome?

You get everybody to walk at the same cadence, with the same step length.

Standardisation of all aspects of the stride of each scout and the distance between each, would ensure that they stayed exactly together, in unison.

Armies call it ‘marching’.

I call it ‘Standardisation’ when applied to any context other than ‘walking’.

Marching enables groups of soldiers to arrive at a destination at the same time, in unison, that both gives the soldiers a sense of ‘belonging’ and looks intimidating to any opposition who might turn up to fight. Remember the opening scenes of the movie ‘Gladiator’? The Romans were in their ‘Centuria’ operating as one, but in coordination with the Centuria around them. The ‘barbarians’ who substantially outnumbered the Romans fought as individuals. You know who won. (I know it was a movie, but the lesson remains)

Standardisation to a cadence is the best way to finish the most work in any given time, as the variation and resulting shortages and backlogs are eliminated. ‘Flow’ through the system is optimised.

When you want to evaluate something new, you have a standardised system to test it on, and can therefore see the results of the change of one variable to the outcome. If favourable, you can then apply the single change to the entire system to improve it.

Going back to marching. The US army marching cadence is a standardised 30 inches for each step. Every soldier steps 30 inches every time. If the standard step was 31 inches, and the cadence of the march remained unchanged, it would represent a 3.3% increase in the distance marched in any given time.

Standardisation and continuous improvement, an essential element in optimising the performance of your business.

PS. 24 hours after publishing, I stumbled across this article by Brian Potter which goes into a heap of detail on exactly the topic of this post. For those who want a deep dive, I recommend it.

 

 

 

 

 

The ‘why’ and ‘how’ of a successful daily huddle

The ‘why’ and ‘how’ of a successful daily huddle

 

Chasing improvements in an enterprise comes down to doing the small things well, every time, and continuously improving, generating a compounding effect.

The best way to achieve this is for everyone involved to be engaged in the process, have a stake in outcomes, and understand how they impact on others.

At every level, this is achieved, not by memo, or strategic planning, but by consistent, focussed verbal communication backed by facts.

Best way to do this is to communicate often.

Not a lot at one time, but small bite-sized chunks regularly.

Daily, weekly, monthly, and so on.

At the ‘coalface’, it should be daily, which leads us to the daily stand-up, huddle, group chat, or as one of my clients call it, ‘toolbox’. Whatever you choose to call it in your workplace, it plays a crucial role in performance management.

This is a daily meeting at the beginning of a day, shift, or whatever the work cycle is, that reviews the day to come, in the light of what happened yesterday, with some acknowledgement of what will be coming tomorrow, and perhaps the next day.

Why it works

  • Daily communication keeps everyone on the same page, enables problems to be surfaced and addressed before they really hurt, escalated as necessary, and contributes enormously to a culture of communication and collaboration.
  • They replace the one-to-one conversations that need to happen many times, with a one-to-many conversation. This saves time and energy, while ensuring the communication is the same to all parties.
  • It enables focus on the priority activities, removing some of the day-to-day firefighting and craziness that always occurs.
  • It also enables quick updates to larger objectives and relevant projects to be delivered, which removes the always present rumour mill. This works equally well for the positive things as it does for the negative.
  • They lead to significantly engaged employees, as not only are they heard, but they can see the outcomes of their ideas and suggestions.

In these days of increasingly remote workforces, this daily get together takes on a much wider role, in reminding everyone that they are a part of a team, and others are relying on them.

What makes them work

  • Same time, same place. Having the huddle, stand-up, whatever you choose to call it at the same time, in the same place, every day creates a cadence that drives activity. Start on time, finish on time.
  • Sitting down will elongate the meeting, so stand. It might be in the workplace, often it is just outside the workplace, which adds credibility to the process.
  • As short as possible, no more than 15 minutes should be an iron rule.
  • Everyone gets a say. Engagement comes with being heard, and the chairman must ensure everyone is explicitly given the chance to have a say.
  • This can take many forms and will vary with the level of the huddle. At the coal face, a whiteboard is usually sufficient, with perhaps a photo or copy taken and kept for reference for a short time. At higher levels, the recording will vary.
  • Be on time, do not ramble when it is your turn to speak. Take any follow up or extended conversation offline, the huddle is to identify problems, address the molehills, but the mountains are for another place.
  • Be respectful of time, others and the process. Be attentive, with no side conversations, or banter.
  • Meeting chair. Someone must lead the meeting, have control of the conversations and agenda. That may be the same person every day, or it might rotate, which in my experience is the better way.

Usually very quickly there is a sense of team effort, and even the small wins become evident and can be celebrated. It is an incremental process, which once the ball is rolling, picks up momentum that is very hard to stop, even if you wanted to.

 

 

‘Lean’ is simple: Here’s how

‘Lean’ is simple: Here’s how

 

An application of Occam’s Razor to all the fluff and consulting clichés around lean thinking and implementation, brings lean back to its simplest form possible.

It has only 2 elements.

Learn to see waste.

Once you teach yourself to observe the waste in a process, you see it everywhere, from the big things in your work life, to the simple things. Ever lose your car keys at home? It takes some time and frustration as you try and remember where you left them? Waste. Put a hook, or bowl, or have specific place that you deliberately put your keys in every time you walk in the door, and you will not lose them again. After a short time, it becomes an automatic action. Fail to do it one day, and the frustration at the wasted time and effort in finding them comes home big time.

Eliminate waste by continuous improvement.

Once seen, take some action that reduces the waste. In the keys example above, it may be that you try the hook, but from time to time, you come into the house with armfuls of shopping. It is hard to reach a hook with an armful of shopping, so you adjust by putting a bowl on the hall table specifically for the keys, which is waist height, so more accessible. In time, it may be that one set of keys near the front door adds extra walking when you need to go out the back door, so you add a specific back door key to a bowl next to the back door.

Continuous improvement, to everything you do.

Incrementally improving a range of these small things, bit by bit, creates momentum and delivers compounding results.

Everyone knows about the race to the South Pole between Scott and Amundsen. They also know that Amundsen won the race, and lived to talk about it, while Scott and all his party perished. What few know is the manner in which the two parties attacked the challenge. There were significant differences in the logistic tactics used by each party, and many played a role in the eventual outcome, but one is not always quoted in the literature, which may have played a key, but little understood role.  ‘Continuous compounding’

Amundsen broke camp each day early, and was travelling by dawn, and every day, he covered 15 nautical miles (28km) sleet, blizzard, or sunshine. At that point he made camp, even if it was still early in the day, preserving the stamina of his men and dogs. This created a rhythm that converted to momentum, every day getting closer to the goal, to win the race and return safely.

Scott did neither.

By contrast he made a choice each day, to hunker down in bad weather, or at the other extreme, travel 30 miles, or more, creating no cadence or momentum to the task of achieving the twin goals. There are many other ‘lean’ lessons in the race that are relevant. For example, Amundsen used dogs, which could eat the abundant penguin and seal meat collected on the way.  Scott used ponies, which required much more looking after as they sweat with effort, and eat only the grain that had to be hauled.

Little things removed, add up very quickly to big things, and when combined with organisational cadence, create momentum.

How long would it take for you to change a tyre on your car? 20 minutes? an hour? 2 hours after waiting for the NRMA to turn up?

The F1 record for four tyres is 1.8 seconds. Over the course of a race, often won or lost by hundredths of seconds, a few tenths several times during the race can mean the difference between a podium, and a straggler. All the F1 titleholders have done is remove waste, and work as a team, with a few tools to automate the repetitive actions.

‘Lean thinking’ has been turned into a complex toolbox by many, requiring expensive services to implement. However, in its most basic form, it is really just critical thinking, common sense, and simplicity.

Header photo credit: Tim Chong

The huge benefit of the giant Corona jolt

The huge benefit of the giant Corona jolt

For years I have been a proponent of what is loosely described as ‘Lean thinking’.

In effect it is a continuous process of removing waste by a combination of critical thinking and continuous improvement.

The biggest impediment to a lean process is always the mind set of those who need to change in order to reap the benefits. Change is really hard, especially when the existing state is comfortable. It usually takes a jolt of some sort to gain any sort of traction. There have been times when I have applied that jolt myself, as a means to remove complacency.

However, we are currently in the middle of a giant jolt delivered by the bug, which should have created the greatest potential for lean traction I have seen in many years.

A lean process will progressively remove any activity that does not add value to the end customer, and seek to compress the time it takes to deliver that value.

In other words, if it is essential it stays, non essential, it is on the list to be dumped.

Suddenly we are all looking at the services we saw as  part of life and re-evaluating them with the question: ‘Is that essential, how does it add value?’

We are involuntarily applying a critical eye to everything we do, seeking to identify and line up for removal, anything that is not essential, that is just consuming time and resources for little or no value.

To use lean parlance, the ‘Current state’ as it was pre Corona is recognised as no longer an option, and we are by necessity experimenting with the elements we need to survive commercially. In that process, will seek to understand how the ‘Future state’ might  look. In every case, you can make some assumptions, and apply them as guiding principles to  the things you are considering.

For example, will it be part of the ‘future state’ for office workers to commute, often multiple hours a day, to sit in expensive offices in a CBD to do their work? For the last 20 years, despite the amazing communication tools suddenly available, it has been for most. The dominating management culture, mostly the child of old white guys like me, who substituted a bum in a seat for useful outcomes, said it was so.

This current experiment with remote working has demonstrated the nonsense of this formerly dominating view. We do need however, to substitute the humanity of the casual conversation and social networks built from personal contact.

We can save ourselves a lot of time and money by working from home, partly from home, or perhaps decentralised mini-offices. Reducing commuting time is like reducing machine changeover time: it releases capacity otherwise being wasted. For no cost beyond a change of mindset and perhaps a few modest enabling tools, we can free up huge amounts of potentially productive time.

Ask yourself the Question; ‘how much time per person can  we save by the removal of the necessity to commute’? When you have answered it, ask if there was a better way, for the people concerned, and the stakeholders in your business, to have spent that time.

 

 

Header photo courtesy Dominic Freeman

How do you trouble shoot flow?

You never get this process of articulating flow right first time, or second, maybe third for simple tasks. People are always people, they are in a hurry, forgetful, negligent, or new to the task, so it has to be made as easy as possible.

Toyota pioneered this idea of flow in a manufacturing environment, but whether you are in a factory, or in an office, the process is the same. There has to be a process for continuous improvement, or at the least one to identify and remove impediments to orderly and consistent flow, in any organisation that aspires to survive and prosper. It results in the optimisation of the process, which is usually radically different to what is required to encourage innovation, which is by its nature more ‘scrappy’ and disorganized, as the activity seeks to test its viability and grow.

Improvement only comes from a stable environment, where things happen in a consistent and predictable manner. When you have stability, you are in a position to experiment, and observe quantitatively the result of the experiment. Was it beneficial, is it worth incorporating into the standard process? If so, then the process check list is changed to incorporate the change as the new standard procedure. If not, a note is made so that at a later time someone can review and know the change has been tested, or indeed, use it as the base for construction of a hypothesis and further experiment that takes the change one step further to where it may make the difference.

A client some time ago installed a coffee machine in the tea room. An expensive unit, that took beans, ground them and dispensed with hot water and milk on demand. The unit has three  things that needed to be done. Beans added to the container, water added to its dispenser, and the line from the milk bottle, held in a small refrigerated unit on the side, needed to be removed and cleaned each day.

These seemingly simple things caused a lot of problems, and really shitty coffee. Water was put into the bean dispenser, (strangely perhaps, beans did not seem to find their way into the water dispenser) requiring an extensive service (twice) and the milk line seemed immune to any cleaning.

To address this challenge, we engaged the staff in a bit of a game, using a fishbone diagram and post it notes. 

Within a few days, the diagram was covered in suggestions, which at a lunchtime meeting we ‘workshopped’ down to those that the people using the machine thought were the best. We wrote a checklist, or standard operating procedure  for the coffee machine, which was tested over a few weeks by a small group of heavy users, then posted on the wall of the kitchen, as well as included in the businesses then developing library of SOP’s.  We also left a big framed photo of the fishbone on the wall in reception, as a reminder to all that improvement was everybody’s job, and that it could be fun, as well as useful.

And, far fewer problems with the coffee machine since.

 

Header photo courtesy Alwin kroon via Flikr