Blog

Best is the enemy of better

CI peopleI first heard this phrase while undergoing lean manufacturing training, half a lifetime ago.  I've always found it a useful way of reminding myself that even the best companies, operations or processes will have room for improvement if you look at them properly.

I'd always thought it came from one of the founding fathers of lean; Kiichiro Toyoda or Taiichi Ohno... but no, when you look closer it is a variant of something said by Voltaire "The best is the enemy of the good" ("Le mieux est l'ennemi du bien").

I've also seen it embelished (By Milliken Research if memory serves) to "Good is the enemy of best and the best is the enemy of better"...  I kind of like this one most.

Many companies and industries have forgotten this aphorism.  Hubris created an internal myth of invincability.  In the 50s and 60s it was the UK Motorcycle industry, in the 70s and 80s the car industry losing out to better quality, cheaper foreign imports.  In the 90s the behemoths in the IT industry, DEC, Honeywell and many more, gave way to the 'Open Systems' revolution and the upstart PC vendors.  Even IBM, who pioneered the PC pulled out of the market due to better, cheaper more agile competitors.  In all of these cases, the 'Best' companies succumbed to game-changing indusry shifts and companies more willing to adapt and thrive in the new world. 

More recently the retail giant Tesco has been put under massive pressure from the low-cost players Aldi, Lidl and others.  Hopefully their reaction will redress the imbalance.

When you are good it is easy to become complacent assuming success will continue. But when you are good, there are others out there trying to be better than you. Unless you are constantly improving you run the risk of losing your competitive advantage.

So when a company says it is 'the best', or the 'leading player' or 'too big to fail', its an early indicator that it is in trouble.  A corporate mindset that does not embrace continual improvement in EVERY area of their business and does not embrace new technology, markets or threats is likely heading the way of the dodo.  'Maybe not today, but soon and for the rest of their life.'

I've also seen a reflection of this in companies looking to improve their business.  Those that are driving towards being the best often can become myopic in their ambition, seeking ever more perfect solutions or 'magic bullets' to their problems and missing important steps on the journey.  If you won't settle for anything but the 'best', you are condemned to stay where you are, or even settle for worse. The obstacles to getting to the 'best' are often insurmountable, while improvement short of perfection can often be obtained.

So what should you do about it?

  1. Grab every chance of improvement, don't wait for that holy moment when perfection is at hand, because it probably 'ain't gonna happen'.
  2. Where you can, 'Just DO IT'...  the good old 'suggestion boxes' worked in the 50s and still work now if you can harness your employees knowledge
  3. It's usually best to adopt a structure for tackling such things in a systematic way... my default mode is lean thinking, but there are many other tools such as Six Sigma, which you can apply
  4. Last but not least, make sure your staff are ALL trained in the relevant approaches and how your company improves itself.  It is the employees that will make the difference, as a manager, give them the wherewithal, sponsor the improvements and reward success

There are only 3 key questions you need to answer when looking at operational mprovement:

Am I doing the right 'stuff'

What is waste in the system, can I get rid of pointless steps? (Consider the 7 Wastes of Lean Thinking)

Am I doing the 'Stuff' right

Can we simplify what we are doing?  If you do the same thing over and over, then find a way of automating it with templates, foolproofing, AUTOMATION. (Consider the 5 S approach within Lean)

Am I managing the 'Stuff' properly

I wish I had a pound for every conversation I've had about over-engineering the data collection and management approach.  I've seen hundreds of thousands of pounds spent on reporting solutions when the source data is suspect at best.  You can check out one of my other blogs her on this matter:  Here

As a first principle only add complexity to your reporting and management if you are going to make some kind of decision based on that data.  The 'just in case' mentality will kill your simplicity here.

Finally, as my introductory paragraphs tell us, there needs to be flexibility in the system. Things will not always go as planned and the system must be flexible enough that it can be modified easily.

Take some time out to consider how your company adapts and improves, consider how these tools could help. You never know, 'this could be the start of a beautiful friendship'.

Its Been a While!

First an appology. 

Its some  months since our last post...  not because we don't love posting this stuff, but because we've been busy!

Its been a frantic period...  weve completed two major package selection projects in both defence and education sectors and are heavily into implementation.

If you are interested in how we go about a selection and implementation project, then you can see the approach in one of our previous blogs here:  https://www.idmb-advisory.co.uk/index.php/news-and-opinion/9-implementation

blue track

For the selection process, specifically, it is important to avoid tick-boxes, wish-lists and personal agendas when defining your business requirements.  Don’t get hypnotised by ‘features’ – the many bells and whistles available in modern systems, most of which you will use; rarely or never.  The tick-box approach invariably leads to over-engineered solutions which virtually guarantee a real struggle to make the system fit your business.  Despite the internal noise and posturing, experience suggests that most businesses have a core which is absolutely common with everyone else’s.  The trick is to focus on the handful of things which are truly unique and provide the process differentiation for your business.  This ‘back to basics’ agenda should be the thread by which you navigate through the whole of the implementation cycle. 

So, what are the questions you really need to answer?

  • Which business processes are fundamental to driving my competitive position?
  • Which package will give me a real edge in these areas?
  • Is the package competent in supporting the other, less core, aspects of my business?

We've used this mantra successfully in dozens of similar projects.

Looking at the current implementations, we are now at the 'What do we want to report?" stage, prior to setting up the core data and framework.  Right at the core of this process is one  of our other blogs; https://www.idmb-advisory.co.uk/index.php/news-and-opinion/25-the-heisenberg-uncertainty-principle-applies-to-business-systems-projects-too...  and addressaing - "What we want to report against; versus how easy will it be to fill in (or default) the relevant fields.

Office Supercharger Developments

Pretty soon, we will be asking for you builds and suggestions for our Office Supercharger products, so get your thinking caps on.  Come autumn we will be entering a new development cycle and we want your views, opinions  and wishlists of things you would want in our office superchargers.  If you want to get started, then you can log your builds here

Oh, and by the way, have a great summer.

Adaptiveness, the continuing battleground in supply chain management

blue squigglesToday's supply chain is complicated, driven by the need for speed at low-cost, across multiple layers, involving many parties and partners. Add to this, thousands of products, dozens of outlets, hundreds of suppliers and a plethora of both internal and external manufacturing capabilities. Season this, with a fine sprinkling of increasing market volatility, more frequent promotions, faster new product introduction and it is not surprising that this heady brew sometimes drives the supply chain and manufacturing leadership reaching for the ‘morning after’ cure.

Indeed, over the last ten years you've probably invested millions in your supply chain. Your logistics and supply chain controllers have attended just about every supply chain conference and seminar. You've talked to every consultant around and know all the buzzwords, having implemented at least half of them.

BUT STILL THIS IS NOT ENOUGH.

Sadly, there is no magic bullet, no single leap you can make to get you to the ‘promised land’ of decreased inventory with improved availability. Supply chains are not the neat linear processes that a pipeline implies. They are more like overlapping and tangled, strands of rope. With customers pulling on one end and suppliers the other. Meanwhile, distributors and manufacturers are trying to create enough slack to untangle the knots that cause the difficulties of one supply chain to impact on another.

Thankfully, the new realism caused by the collapse of the dot.com bubble has created an environment where sceptical customers are demanding practical, simple and fast solutions. Vendors have responded with simplified offers using pre-configured software and templates. Consultants are delivering services that simplify processes and untangle the knots. Modern solutions use technology only as a means to deal with unavoidable complexity and to facilitate rapid transfer of information and assist decision-making.

So, what does the future hold?

In the increasingly networked supply chain that needs to be flexible and adaptable in volatile markets, which can't afford to discard legacy systems every five minutes, a rigorously thought out battle plan is essential. This includes the ability to plug and play new functionality, systems and processes as well as a strategy for continually improving the flexibility and responsiveness of the whole organisation.

Finally, having the right planning process at the heart of this adaptive supply chain is the key to ensuring success. The planning function acts like a conductor keeping the constituents of the supply chain orchestra in harmony. This can only be done with modern technology, good visibility and a deep commitment to managing (and rewarding) end to end performance, rather than functional excellence.

I Can't Keep It Simple Stupid


1262841
Throughout the years I’ve been engaged in operational excellence projects, one challenge has been a constant.  How do I reconcile my lean execution system with my computer support system?  Like oil and water, they struggle to mix.  

Here are some ideas that might help.

Lean zealots will insist you should do away with systems... They are an admission of failure.  In many ways, this is very true, but misses a fundamental truism.   Not all things can be made simple.  Cross-border, cross organization and cross language communications and structures; complex product options exacerbated by lumpy demand; the need for ever shortening response times; all add to a level of ‘irreducible complexity’    

Though I would even challenge the root-cause of these complexities, before I accepted them as being irreducible, (for instance lumpy demand is often self-inflicted via. promotions, month-end pushes and sales KPIs), my experience is that while you can minimize and militate against them, there always remains a core which needs support.

To get the best from improvements in this environment, demands a strange hybrid of systems savvy, lean thinking.   For a major electronics OEM, the compromise involved segmenting some of their ‘Runner’ products (highly predictable/stable demand) as a group managed outside the main MRP system using a kanban pull system.  Demand for lower level componentry and raw materials (which was common to other segments) is driven by a forecast based on the throughput rate of the lean pull system as well as dependant demand coming through MRP from other segments.   To handle the execution meant that common components were issued as line-side or pull stock to the lean segment (unplanned issue in ’MRP speak’) and through conventional MRP kit issues for the rest.   For some products, we also used a 2 bin replenishment process (both physically and within MRP’s ordering method) 
This might sound a little complex, but effectively you are taking as much as you can outside the system and then managing the rest with systems.  Aligning system parameters (MRP ordering method) to their (near) equivalent physical/lean (2bin/kanban) processes is possible and is greatly simplified in contemporary MRP systems with recent embellishments  such as non-MRP stocks, line-side stocks and support to pull systems.


The chemists among you will know that to make oil and water mix, you simply need to add soap.

In our case the soap is simply the following 3 simple rules; use lean techniques to simplify as far as is humanly possible; use systems to deal with the irreducible complexity;  and most importantly of all, apply lean thinking to the way you configure those systems to, "keep them simple stupid”.

The Heisenberg Uncertainty Principle Applies to Business Systems Projects Too!

1280241 85345163
There has rarely been a better time for using IT systems for business management and measurement. Systems are sophisticated and flexible and modern hardware can eat through large data sets. However, having been a ‘victim’ of well intentioned but ultimately futile attempts with technology there are a number of key observations which need to be considered to improve any systems project.
The most important consideration is the premise of the Heisenberg Uncertainty Principle. In quantum mechanics, the Heisenberg Uncertainty Principle (HUP) states a fundamental limit on the accuracy with which certain pairs of physical properties of a particle, such as position and momentum, can be simultaneously known. In other words, the more precisely one property is measured, the less precisely the other can be controlled, determined, or known.

It is identical with systems projects... the more precise you make the data collection (characterised by the various codes and hierarchies you deploy); the less chance the end user has of using the correct code. This therefore undermines the very precision you are trying to drive. If everyone books to a handful of codes, you can be pretty sure the figures are right. If there are hundreds, the total will be right, but the underlying breakdown will be largely fictional due to the inherent difficulty an individual has in picking the correct code.

Consequently when you are looking at this crucially important and topical subject you should think about the following;
Remember why you are doing this project and focus on the ‘critical few’ metrics that will make a genuine difference to your business;
Keep the number of codes that users have to navigate to an absolute minimum. Accept the loss of discrimination for the increase in precision;
Make the key measures visible... use classic lean management systems, short interval controls and other visible management techniques so that the output becomes central to operational improvements;
For the limited number of codes you do use, look at ways of ‘error proofing’ data entry through both systems (Validation rules) and user (Crib sheets) approaches;
Start simple... most over-engineered systems are spawned by people ‘theorising’ at what is needed. You should design the end-state, but get a simple practical solution working first; then look at how to make it better. At some point you will discover where the boundary is between more detail and less precision.
The HUP is fundamental to the invention and performance of so many modern inventions from the phone to the computer, from GPS to laser printing. Perhaps its application in business systems deployment can be equally profound.

Ian Batey

Author

Ian Batey has spent over 40 years in various line roles in manufacturing, IT and management consulting.  He has advised at both management and board level  across the globe and been responsible for dozens of successful operational improvement and IT implementations.

View my profile on LinkedIn

Blog RSS

Subscribe to our mailing list

View previous campaigns.