Monday, September 30, 2013

Business Process Improvement Delivery Plan

It helps when implementing a BPM project to have a delivery framework; it accelerates the planning phase and serves as a checklist to make sure nothing is missing. I came the framework below whilst working for KPMG Consulting which I refer when working on BPM projects. It has eight distinct phases with deliverables defined in each phase. You will notice also the deliverables are colour coded to indicate responsibilities within the project team. The eight phases are depicted in the insert as a continuous cycle with the output of the Improve phase feeding the Stimulate phase.



There are essentially three major terms used when engaging on a Business Process Project and these are:
·         Deliverables - The diagram above lists the deliverables in each phase with falling four categories;
o   Process Management
o   Information Management
o   Change Management
o   Human Resources
·         Techniques – These are methods used to achieve the deliverables an example is the Business Entity Diagram and Value Chain, discussed in an earlier Blog, to define the Holistic Business Model
·         Achievements – This is the final goal or completion of the defined Milestones.

The Purpose of the Eight BPM Phases:

1.       1Arouse– Used to Kick Off the project and for the Management Team explain motivate the team by explaining the reason for investing in the project and their expectations .
2.       2.Envisage – Provides the means to develop a common content and understanding (between CEO, senior management and the consultant) of the organisation, its current challenges and its future direction.
3.       3. Focus - Identify the major opportunities for performance improvement that are associated with existing processes, technology and human resources.
4.       4. High Level Design - Develop a portrait of how the client organization will conduct business in the future
5.       5. Detail Design - Design the details and understand the consequences to the organisation of implementing the preferred “To-Be” business solution.
6.     6. Build - Construct and test all outputs of key components of the business solution.  To build an infrastructure capable of supporting the “To-Be”  processes
7.       7. Implement - Set in motion across the company the newly built processes, technological and social changes that have been designed and built.
8.       8. Improve - To establish mechanisms to ensure that performance improvements resulting from the BPM programme are sustained over time and ultimately lend to opportunities for additional performance gains.

I want to stress this is only a framework and although I use this as starting point depending on the organisation and the project scope I will vary the sequence and eliminate some deliverables.  I have attached a list of possible BPM deliverables as a reference.

Monday, September 23, 2013

Using Proven Sales Tools for Business Process Improvement

In many of the Business Process Projects I have been involved in, they have been focused on a specific area of the business. The reason is obvious, in that a potential problem has been identified, and hence the area of investigation is confined to that part of the business where the problem has surfaced.
I not sure how many Business Process analysts have been involved in Sales. But what I would like to do is share with a process that we used in Sales which is based on a premise that “pain flows through the entire organisation”. This consultative approach to selling was used to expand the number of contacts within a business that was directly or indirectly impacted by the issue raised by initial contact. It also provided a means of expanding the number of contacts within an organisation to justify the investment in your services. Likewise this can be used to expand the benefits gained from a business process improvement (business process re-engineering) project. The diagram links the impact of pain on the various organisations with in a company, providing a way of ensuring the process is improved from end to end.
There a few tools used to identify and analyse the impact of pain within an organisation:

1. Pain Chain Diagram

The Pain Chain Diagram provides a means of identifying the chain of events within an end to end process that impacts all who are involved in the process. It also highlights the impact on different business units within an organisation who are involved in a process that has problems.
The tools below are used to analyse the problems and recommend solutions that can be implemented with maximising the benefits to the organisation.






2. Vision Process Model

The matrix is used to structure the questions. Across the top are the question categories and down the side are controls used to ensure the questions are responded to in a structure manner
An important factor is in the way questions are asked. Firstly questions are open questions, providing a means for the responder to embellish on the pain. The new move into Control where we are trying to structure the responses and then Confirm our analysis.
We also direct the responder through a process of uncovering the pain, then exploring the impact of pain and present back a visualization of how we are going to help them resolve the problem.

3. Pain Sheet

The Pain sheet is used to record discussion with the responder.  It also provides a structured approach for identifying solutions to the cause of pain. 








4. Relationship between Vision Process Model and Pain Sheet

This diagram shows the relationship between Vision Process Model and the Pain sheet.
I have used this method many times to help structure workshops when developing the As-Is and identifying Quick Wins.









One of the hardest problems of implementing a Business Process Project is showing the benefits that can be gained from looking at end to end processes that flow across departments within an organisation. The Pain Chain approach I believe is an excellent way of communicating the impact of process breakdown on other parts of the organisation. It is a good way of documenting your findings and supporting the recommendations on improvements.