Latest News:

Making ‘go (normal)’ regarding the output easy to see.

February 8, 2024
I (Ben) have just started working with a new client. What we’re initially focusing on is making ‘go (normal)' regarding the output easy to see. Just as the example illustrates, when ‘go' is made easy to see …

I (Ben) have just started working with a new client. The site is about to undergo significant changes due to a large volume increase. The increase will utilise the same people, the same shifts and the same machines.

What we’re initially focusing on is making ‘go (normal)’ regarding the output easy to see. Just as the below example illustrates, when ‘go’ is made easy to see, ‘no go’ (everything else!) becomes very obvious …

Making ‘go (normal)' regarding the output easy to see. -

We can then efficiently problem solve the abnormal (‘no go’) and include methods such as visual management and root cause analysis.

If go is not easy to see, then we’ll most likely go around in circles. Why is this so?

A big part of gaining stability (thus less firefighting) and/or improving is relentless problem solving of ‘abnormal’. If abnormal is not easy to see, if it’s subjective (based on opinion), then you’ll spend a whole lot of time, effort and energy grappling with opinions and interpretations (of normal/ abnormal). This will bog you down. You’ll be going around in circles, but not improving.

Is making ‘go’ (normal) easy to see a skill? You bet it is. Can it be learned? Yes it can.

There is a great quote by Einstein.

Making ‘go (normal)' regarding the output easy to see. -

I’m looking forward to the ensuing conversations as we practise ‘Getting Started With Work Standards’ by making ‘go’ regarding the output easy to see. (By default, we will define ‘no go’!) I’ll provide an update in April 2024 with the learnings we’ve had.


If you’d like to read more about Getting Started With Work Standards read more here, or watch a brief video clip.