What word or phrase does every IT Leader hate to hear? What's the coolest thing that's ever been done with our Middleware products? IT Uncensored is a showcase of thought leadership about all aspects of IBM Middleware from your perspective. These experts get real about middleware—and themselves.
Lean and BPM: Two peas in a pod?
SUNIL AGGARWAL 270005B41K firstname.lastname@example.org | | Tags:  bpm business_process_manageme... lean
3 Comments | 3,075 Visits
Recently I have seen a resurgence of customers adopting lean techniques in their projects. In general, these have been very successful due to speed of delivery, quality of deliverables and output, and the ability to drive fundamental change to the business process being implemented. The result is significant and can offer quantitative cost reduction.
However, lean practitioners tend to do their utmost to avoid any involvement of IT in their delivery schedules, mainly due to the fear that changes cannot be achieved within the timelines. My belief is that the disciplines of business process management (BPM) and lean should be complementary. Lean allows customers to define and deliver process change by uncovering waste. BPM also delivers these results by validating that the implementation of the process is actually working in the best way. It does this by the looking at the actual implementation details—the quantitative data associated with the implementation. Critically, this usually comes from using the business activity monitoring (BAM) part of any BPM solution. This can highlight bottlenecks as well as suboptimal patterns.
So the question is, which one should be done first?
BPM should be seen as a set of tools to help a lean engagement. The lean method is sound and provides a solid mechanism to drive efficiency. However, I think there are two major downsides to relying on lean alone.
First, the lean process provides no real understanding of which process to start off with among the myriad business units of an organization and the prioritization of these. Decisions are typically made based on the “who shouts loudest” method.
Second, by not looking at the systems layer in detail, major efficiency drivers can be missed. BPM helps with both of these. BPM allows lean to both prioritize the order of processes and give the practitioner real operational metrics of detailed process information—some of which is hidden as “black box IT stuff.”
So, the answer is simply to do both. First, implement BPM in order to gain insight into the environment and help to prioritize efficiencies. Use lean techniques to change the processes and gain value, and then use BPM to implement some of the level 2 IT changes.
Have you been using lean techniques? How do you think lean works in concert with BPM? Please share your thoughts here or on Twitter.