Effectiveness, not just amount, of spending

All you hear about currently is the Australian “health debate” a debate the pollies have decided to have as a political exercise, are discussions about who gets to spend the money i.e. exercise the power,  it has little to do with the health outcomes of Australians, that is just the excuse. 

Cynical perhaps, but if it were otherwise, you would be hearing real discussions  about the manner in which the billions were spent, not how just much, and by whom. We do need more to be spent, but more importantly in a society where health costs are increasing rapidly, and will continue to do so, we need debate, and importantly action, on the effectiveness  of the spending, and the means by which that effectiveness, measured by patient outcomes, can be improved.

Applying proven process improvement, Lean, and Six Sigma commercial disciplines to public spending should be a priority, but perhaps that would impinge on vested interests a bit much, so we leave it alone.

The parody via the “Lean” hyperlink above has a scary resonance, and  we leave discussion about the effectiveness of spending  alone, to the great cost of to our community over the medium & long term.

Knowledge is a pre-requisite, not a guarantor.

Deep knowledge is pretty common these days, the facilities to accrue it are readily and freely available, and it is no longer a key differentiator.

However, what is still not common is what has always separated the run of the mill to the standout, organisations with engaging leadership, motivated people, and good judgment.

Judgment comes from a combination of deep knowledge, varied experience, qualitative or spatial skills,  analytical skills,  and a preparedness to learn from experience. It is primarily a personal quality, but increasingly it is becoming a pre-requisite for an organisation to take on these human qualities via its articulation of purpose, values, and emergent strategy.

A businesses I had some contact with a while ago had deep knowledge, there were PhD’s galore, but the lack of judgment and wide experience had hamstrung their efforts in the face of a changing competitive environment. The changes necessary will be challenging and painful to the people, and their view of their roles, probably not all will make it despite their undoubted knowledge, as the business model must change, and with it the way they create and sustain value.

Knowledge is a pre-requisite for success, but is not a guarantor of success.  

Project collaboration paradox

Getting collaboration when you really need it, when the interaction can add value is usually at the beginning of a project. The closer you get to the completion of the project, the more the parameters tend to be set, it is the detail that changes, a much more mechanical process of executing what has been agreed through the early collaboration stages when things were more flexible and creative.

However, it is often towards the end of the project, particularly when the outlook is positive,  that it becomes easier to attract those who may have been useful at the beginning, but whose contribution later will only cause hesitation and changes that result in a slippage of delivery dates for the project.

Of course, the worst “collaboration” is when someone exercises institutional power after the point where it is useful.

Towards the end of a project, it is co-ordination and project management that is needed, not collaboration, which should have happened at the beginning. How often it gets all arse-about!

Forecasting and demand planning.

Developing a forecast of what you need to make to sell is a different proposition to doing a demand forecast, it is much more than a semantic difference.

A forecast is usually an extrapolation, sometimes very sophisticated, but an extrapolation nonetheless, of the past, and the only thing we know for sure, is that the future will be different.

A demand forecast looks at the drivers of demand, essentially looking backwards through the supply chain from the customer, and anticipating the level of demand by factoring in all the things that drive the customer to order a volume of product in any given period.

ERP systems are driven by forecasts, they are the core of any system, and the more accurately the forecast, the better the system works within the limitation of the rules written in. However, when the forecasts are informed by the drivers of demand, not just the inventory levels and automatic restocking rules in place, the value that can be delivered in vastly enhanced.

 

Lessons from NUMMI

Whilst we observe the rather sudden tarnishing of Toyota’s quality aura, it is easy to lose sight of the enormous value Toyota has given to our understanding of efficient and flexible manufacturing. The lessons are everywhere, there would not be a manufacturing operation anywhere in the dev eloped world that has not benefited from the expertise developed and shared by Toyota.

Our understanding of the TPS began when Toyota began manufacturing outside Japan, its first foray was a JV with General Motors in their Fremont California plant, in a JV called New United Motors Manufacturing Inc, or “NUMMI” as it is commonly called.

This JV is a milestone in our understanding of manufacturing, the link is to a Sloan Management Review article written by one of the modern gurus of lean manufacturing, john Shook,  who was a key employee in the development of NUMMI, and its subsequent success.

Anybody unfamiliar with the story should take 10 minutes and come up to speed, and this article is the quickest way.

 

To collaborate or not to collaborate

    It seems that everywhere there is a drive to collaborate, without any real regard to the challenges of collaboration, the behavioral and cultural changes necessary for success. Collaboration has become an end in itself, rather than a strategy that has the potential to deliver value to both parties under the appropriate circumstances.

    For a collaboration to be successful, there are two pre-conditions:

  1. There is a genuinely important shared goal, and the goal is powerful enough to drive resource allocation decisions in both collaborators
  2. The reward systems of both parties recognise the importance of achieving the goal.
  3. Without these two preconditions, there is little chance of the collaboration doing anything more than take some time, probably cover someone’s arse, and perhaps give the appearance of something useful  happening.