What’s the purpose of
a ‘management system’? What are its key elements? What are common failure
modes? How do you know if you have a
good one?
My job the past few decades has been to help our partners meet their business goals by developing strong people & management systems. My personal mission is to teach leaders Ambidexterity – the ability to both
a) Protect the core
with OpEx/Lean, and
2) Ignite new Growth
using the methods of Silicon Valley & Singapore.
Your management
system enables both and is analogous to the wire harnesses that enable high
performance airplanes & automobiles. I’ve written at length about the
questions above. In this piece I’d like to describe the tell-tale attribute of a
great management system.
Key Attributes of World Class Management Systems
World class management
systems make problems visible.
By ‘problem’ I mean
the difference between
·
What Should Be Happening, and
·
What is Actually Happening
Each of these must at
least define purpose, process & key metrics. By ‘visible’ I mean obvious to
all team members. ‘Everybody knows’, to paraphrase Leonard Cohen.
In practice this
means that problems are painfully clear at team boards at every level - from
the Senior Leader Obeya to front line team boards & huddle sessions. When I’m
asked by a Board or Senior Team to ‘assess our management system’, a key step is
to walk the value stream backwards, starting with the customer, and moving
upstream one step at a time. A parallel step
entails walking the customer journey backstream, starting with the top of the
proverbial funnel.
In my value stream
walks, I ask questions like:
·
Are problems visible (even to an outsider
like me)?
·
What do people talk about in their
huddles? Are problems understood & addressed in a clear & decisive way?
·
What’s the organization’s attitude to
problems? Are problems hidden, a sign of failure? Or are they, to quote W.
Edwards Deming, ‘the process speaking to us’?
·
Do teams have a standard approach to
problem solving?
·
How good is the data? Is it complete, end
to end, and of high quality?
·
Does the team develop ‘Your Own Data’
(YODA) as required? Or do they passively wait for corporate data?
Here are your key
checkpoints:
·
The visibility of problems, and
·
Quality of problem solving (the focus of
upcoming articles)
I vividly remember an
engagement with a large multinational consumer goods company. They were good, capable people and their company
had enjoyed strong growth for several years. They’d invested in teaching their team members root cause problem
solving. I spent a few weeks walking the most important value streams from the customer
all the way upstream. I attended team huddles and walked the shop floor.
I presented my findings
to the COO & senior management team:
·
Everything looks good on the surface – purpose strategies seem cogent, data seems to be flow, workplace
fundamentals look okay on the surface (e.g., 5S, standardized work, visual management), and
morale is fairly good.
·
But there's flashing RED light – team boards at all levels are always Green; the critical third wall of
the Obeya (Blockers) is usually empty.
‘But we’ve given everybody problem solving training,’ the team responded. ‘
There's flashing RED light,’ I repeated, and added the my old sensei' motto, ‘No problem, is a big problem.’
My report fell on
deaf ears.
Six months later
there were major outbreaks of food poisoning related to their products. Several
customers became ill, and the company’s brand suffered serious damage. A
number of senior leaders resigned.
The visibility of
problems and quality of problem solving are your early warning system, and a
key to de-risking your enterprise. You want to assess your management system? Start there.
Best wishes,
Pascal Dennis E: pascal.dennis@leansystems.org