<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1907245749562386&amp;ev=PageView&amp;noscript=1">
Event_bg

The Leonardo Blog

All Posts

Continuous Improvement and Discontinuous Innovation - We Need Both

Improving non-existent processes - QuoteThere is often a tension between process improvement and innovation. Improvement is seen to be just fiddling around at the edges, rather than making the massive gains offered by radical transformation. Continuous process improvement is important, and we also need discontinuous innovation. However, process improvement needs a performance boost; as well as counteracting weaknesses and threats, it needs to focus on opportunities and strengths. We need to work beyond the tangible current state to discover and improve non-existent processes.

Imagine this. Monday morning 9:05, and we are at a government agency starting an in-house five-day training course on process analysis and improvement. My 25 students are all eager to get going, and their CEO is there to kick us off with some well-chosen words of encouragement (I know she had good words, because I wrote them for her). Going completely off script, she starts out by saying, “I’m not interested in improvement—I want innovation!” Interesting way to start a week all about improvement!

I knew what the CEO meant. She’d had too many experiences where process-improvement exercises had delivered lots of recommendations, but very little change. She wanted stuff to happen; she wanted the performance of the organization to be demonstrably and significantly improved. Her targets weren’t aspirational—they were real, practical, and urgent. Just as Edison did not invent the light bulb by improving the candle, she could see that incremental change was unlikely to be enough to meet her objectives. She was understandably concerned that her well-meaning analysts were about to fiddle about at the edges, while ancient, deeply-flawed processes burned up her budget, public goodwill—and, perhaps, her next employment contract.

Our CEO wanted us to be improving processes that didn’t yet exist. That’s a challenge both impossible and necessary. Although it is important to pursue continuous improvement, there is a limit to the benefits to be gained by incremental improvement; from time to time, we need to make a significant leap to a whole new performance level.

There are many ways to categorize innovation: lifecycle, industry, impact, scope, product, process, source, internal vs external, and marketing methods. This discussion focuses on process innovation, which heavily influences all innovation, since my definition of a process includes all the activities required to transform inputs into outputs, and all the elements required for management and execution of the process.

There are two key differences between process improvement and innovation. They are both about change and, inevitably, that is about changing processes. The first difference is a matter of degree: how much change is involved? An innovation will result in a new process that is radically different to the one it replaces. A more modest process improvement leaves us with a process that is recognizably the same, although improved in some way.


The second difference comes from the drivers of the ideas for change. There are two broad categories, with some overlap.

Innovation will generally be idea driven, while process improvement will be performance driven. Process improvement will be based on a problem looking for a solution (e.g. we need to take two weeks out of the supply chain execution time). Innovation will likely come from a solution looking for a problem (e.g. how could we use RFID technology to improve our supply chain?).

We need both: continuous improvement and discontinuous innovation.

Big problems and big opportunities require big change. Opportunities and problems are also changing; largely, but not only, because of digitization, they are morphing into something qualitative and quantitatively different: check-in becomes check-through; a shopping list becomes a shipping list; and a regular check-up changes to continual assessment.

The process of process improvement needs a lot of work. It is too often restricted to resolving operational problems defined by performance data and failure reports. Current and urgent defects must be fixed expeditiously, but that should not limit the scope for improvement.

If the airport check-in counter queues are too long, many things might be analyzed: physical queuing arrangements; the number of check-in staff available, and their level of efficiency; common problems that slow the process; business rules regarding status and upgrades; possible IT changes, etc. Perhaps, though, you could challenge the need for check-in counters, or even the need to check in. What if a simple fingerprint scan was enough to check in? Or, perhaps, the detection of a passenger’s smartphone on arrival at the terminal checks them in automatically. What queue problem?

Process improvement is about SWOT: strengths need to be protected and amplified, weaknesses need to be removed, opportunities needs to be seized, and threats need countermeasures. The problem is we almost always focus on the W, and perhaps the T—the negative perspectives. Innovation happens in the O, and perhaps the S.

In analyzing processes, we need to put much more emphasis on The Big O; this is where innovation happens. Of course, we need to improve the candle, and we also need to invent the incandescent light bulb—and then go on to invent the LED, then the LED smart light, and then… whatever comes next.

Process improvement suffers if we are just working with what we have now, what we can see and touch. To maximize the benefits, we need to also consider what is not there; those future processes that have the potential for radical improvement.


Incremental improvement of the current state is important and, if done properly, delivers significant benefit. Innovation leading to radical improvement comes when we explore non-existent processes.

New Call-to-action

Roger Tregear
Roger Tregear
Roger is a Consulting Associate with Leonardo. He delivers consulting and education assignments around the world. This work has involved many industry sectors, diverse cultures, and organization types. Roger briefs executives, coach managers, and support project teams to develop process-based management. Several thousand people have attended Roger's training courses and seminars in many countries - and Roger frequently presents at international business conferences. Roger has been writing a column on BPTrends called Practical Process for over 10 years. This led to the 2013 book of the same name. In 2011, he co-authored Establishing the Office of Business Process Management. He contributed a chapter in The International Handbook on Business Process Management (2010, 2015). With Paul Harmon in 2016, Roger co-edited Questioning BPM?, a book discussing key BPM questions. Roger's own book, Reimagining Management, was published in 2016.

Related Posts

Leonardo wins 2020 Red Hat ANZ Professional Services Partner of the Year

Red Hat announced Leonardo as their 'ANZ Professional Services Partner of the Year'. This is the third year in a row Leonardo has been recognised at these regional awards, and we're extremely honoured again for this acknowledgement. Well done to Team Leonardo for your superb work delivering great outcomes for clients - and to Red Hat Asia Pacific for their amazing partner growth and results over the past year.

Leonardo Invests in Apromore to advance AI-Driven, Open-Source Process Mining Technology

MELBOURNE, AUSTRALIA – 7 July 2020 – Leonardo today announced its investment in Apromore - a leading developer of open-source, AI-driven process mining technology. The investment forms part of a Series A round of funding totalling $A6.8 million, led by German business process management specialist GBTEC, and also included The University of Melbourne, which helped to incubate Apromore prior to spin off.

Leonardo wins 2019 Red Hat Hackathon - Customer Experience with OpenSource

      We're thrilled to share with you that Leonardo has won 2019 Red Hat Hackathon 'ReBoot Customer Experience with Open Source'. Early on Friday morning ( 5am AEDT 13th December 2019),  Leonardo awarded first place from a field that included 320 participants from across the globe.  The Hackathon's brief was to reinvent customer experience using Open Source. Providing an outstanding customer experience that customers actually love is especially challenging in more traditional industries like banking, insurance, telecommunication, public sector/government, healthcare, manufacturing, or transportation. These markets offer great opportunities for change and disruption as has been shown by many examples such as Uber disrupting transportation, Twilio disrupting telcos and Stripe or Transferwise disrupting banking.  We want you to be the next disrupter who creates a customer experience that users actually love.  An Open Source solution - ACE  Airline Customer Experience Our project is an application using a Red Hat Process Automation Manager process-as-microservice developed for "ACE Airlines", our fictional client (see video above for the demo). It communicates personalised, event-driven (gate change, delay, etc.) messages to passengers in the language of their choice, using their preferred communications type (SMS, push notification, email).