Archive for March, 2010
Bridge Those Silos with Incentive Alignment and KPIs
Posted by Ashish Bhagwat in BPM, Business, Leadership, Management, Technology on March 31, 2010
Silos within the organizations boil down to plain WIIFM (What’s In It For Me?), the way organizations measure performance and the type of behaviors they encourage. There’s a relationship among KPIs, Objectives, Expectations, Inspection, and Incentives. We can bridge the silos by understanding this, and effectively using the technology and tools available to us once we know what needs to be done.
Social is a Phenomenon, not another Discipline/Practice!
Posted by Ashish Bhagwat in BPM, Business, Technology on March 25, 2010
Yesterday in Forrester #crmjam on Twitter, Social (networking, not cause!) aspects got a lot of attention. One of the converging points, as per Theo, is around social BPM and social CRM. This is correct, however, IMO, Social is a Phenomenon and not a discipline. What should remain – when we are done with this phenomenon – is the set of disciplines that are better placed to collaborate and synergize toward customer centricity.
On BPM, Incremental Improvement and Innovation
Posted by Ashish Bhagwat in BPM, Business, Innovation, Leadership, Management, Technology on March 21, 2010
If Incremental Improvement is so much loved by business stakeholders, it’s not because BPM cannot do otherwise, they just like it that way! As for Innovation in BPM, We are at a point of time which is most conducive in recent few years for big leap innovations in BPM – as discipline & as technology.
How important is it to qualify an opportunity or solution as BPM?
Posted by Ashish Bhagwat in BPM, Business, Management, Technology on March 20, 2010
I have seen many a successful BPM solution that has been more so in hindsight. And a lot of hyped up solutions/initiatives that started off as BPM solutions ended up as duds. What’s important is to remain true to the BPM drivers and objectives. And that is, to make an impact on customer experience and measurable parameters that really matter. If you do that, you will end up doing what’s best for the objective, call it BPM then if you wish! Pre-qualification of a problem (as a BPM candidate) or solution (as BPM implementation) isn’t as important as it seems.
BPM Ecosystem – Blurring Boundaries or Systematic Convergence?
Posted by Ashish Bhagwat in Architecture, BPM, Business, Cloud Computing, Leadership, Management, Technology on March 16, 2010
In the initial years of BPM, we thought we had few problems that would slowly disappear with maturity in the discipline / technology. Come 2010, and we are dealing with more variants of similar problems. Depending on where you look from and where your stakes lie, this could be a case of blurring boundaries or of significant convergence in BPM ecosystem as illustrated here. Can we all “converge” and leverage on our best opportunity in recent times to really take BPM to where it belongs?
Unified Communication will play an important role in BPM (why ignore it?)
Posted by Ashish Bhagwat in Architecture, BPM, Business, Management, Technology on March 10, 2010
Most of the current focus of Social BPM is around Web 2.0 and social networking. It’s amusing that Unified Communication (UC) has been overlooked. Social media do their bit in terms of bringing people together on some of these media. But, a whole lot of duplication of collaboration effort can be reduced drastically by leveraging UC. I’m convinced UC will play an important role in BPM, but should it remain a subconscious effort?
Dynamic Process Capabilities are powerful, but use with caution
Posted by Ashish Bhagwat in BPM, Business, Management, Technology on March 8, 2010
To have capability to define and execute dynamic processes on the fly is really powerful, and we see a lot of progress in this area. However, we need to be cautious when using such capability. Such dynamic processes are difficult to manage, the metadata is inconsistent, one finds it very difficult to benchmark the processes and define KPIs. And process adherence becomes a huge challenge. With some caution, we could prevent this right & powerful solution from being applied to wrong problems… Read more.
