Monday, February 20, 2017

BPI Awaken Phase - Case for Change

BPI Awaken Phase - Case for Change

Case for Change.png   

Description

  • A highly-compelling justification (from the organisation's perspective) of why the organization must change. The Case for Change creates a common understanding among key decision-makers as to the broad challenges that need to be grasped and the importance for addressing them quickly.        
  • In awakening to the immediate/longer-term actions required to confront the new reality, one or more possible “levers for change” (factors over which management has direct influence) will emerge as critical to future business success:
    • Strategy/business positioning
    • Product/service offering
    • Business processes
    • Technological     leadership
    • People and social systems
    • Structure
    • Environment/regulations.

Value

  • Establishing a strong Case for Change fosters a deep understanding and ownership on the part of key     decision-makers of the problems at hand. It engages all senior executives, and ultimately all employees, in facing the challenges of the future. The leadership team’s “buy-in” to the Case for Change enables senior management to present a united, credible front to the organization.
  • Unless there is full management (and, ultimately, employee) support for the need     for change, the subsequent BPI exercise will have a weak foundation     and become easily derailed (or its implementation will become     unnecessarily drawn out).    

Approach

The Case for Change is the critical Awakening phase deliverable that provides the impetus for completing the activities of the Envision phase. (In many an organizations, it is necessary to begin work on the Internal Organizational Overview, Business Position and Holistic Business Model as tactics to help establish a compelling Case for Change.) A Case for Change is developed by describing the company’s current situation, and placing it in the context of the new business realities it now faces. This constructive confrontation of the current business “paradigm” with the emerging threats/opportunities for survival serves to “awaken” the leadership team and generate a climate of urgency. (Strategic Analysis Framework)
  1. Meet with Chief Executive Officer (or equivalent) and other senior executives to discuss business issues.
  2. Review existing analytical information on the company’s competitive position and key business problems.
    1. Identify sources of benchmark data that highlight the current and future business challenges. (Benchmarking)
    2. Map any historical trends on revenue, profitability, market share, morale, industrial controversies etc. (Company Baselining)
  3. Obtain agreement on who needs to be involved in the process.
  4. Design a workshop to facilitate the development, by the leadership team, of a compelling case for change.
  5. Pre-interview a representative sample (at least) of the leadership team.
  6. Conduct the workshop.
  7. Debrief the leadership team.
  8. Formalize the agreed-upon Case for Change and the process for communicating it more widely within the organization.

Guidelines

Problems/Solutions

  • The role of the Chief Executive Officer (or equivalent) is sometimes contentious. Advise that he/she adopt the role of “participating equal”. Coach him/her on how to handle likely conflicts that may emerge from the adoption of such a role.

Tactics/Helpful Hints

  • Identify ground rules that will facilitate candor, creativity and focus. Provide open access to all information gathered and analysed prior to the workshop.
  • Focus on external drivers and opportunities. Encourage “constructive dissent” about the meaning of the data and the relevance of drivers and opportunities.
  • Use a     technique such as Five Shared Basic Concepts to facilitate open discussion of the alternate views within the leadership team about the purpose and future of the organisation, and the degree of urgency for change.
  • Design a workshop format that allows for maximum involvement of participants. Keep lectures and formal presentations to a minimum.

Resources/Timing

  • Facilitators should adopt a non-expert role and should concentrate instead on group dynamics and     on encouraging openness between participants.
  • These     interviews and workshops are potentially sensitive and require careful positioning and experienced facilitation. The preparatory phases leading up to a workshop are critical. More than one workshop may also be required.
  • As the Case for Change is made known across all levels of the organizations, similar tactics will need to be adopted (at later stages of the BPI initiative) to bring other managers and employees on-side. These     efforts are identified as part of the Communications Plan.

Monday, February 13, 2017

BPI Storyline for a Vision-driven Scenario

BPI Storyline for a Vision-driven Scenario

Following on from previous BLOGS regarding the implementation of large scale Integrated Software Solutions I came across an old  Business Process Improvement (BPI) Methodology developed by KPMG some years ago that I believe is still relevant in days environment. The BPI methodology represents an approach to a large-scale, complex, holistic and dramatic Business Performance Improvement programme. This Vision-driven Scenario was selected because, as such, it calls for a large inventory of deliverables to be created during the course of the programme. The Vision-driven Scenario has the following assumptions.
  • No constraints have been established by Organisation senior management to limit the effort.
  • An external consultant has been asked to assist the Organisation from start to finish—Awaken through Implement.
  • Redesigned processes drive the software selection, development and implementation (and not vice-versa).
The scenario requires that all deliverables and techniques described in the Methodology are used to successfully complete the program.
The scenario comes best to life when the phase-level storylines are read, since this is where all the deliverables are described and related to each other. Below is a brief synopsis of the eight phases.

Awaken    

The purpose of the Awaken phase is to bring the leader(s) of an organization to the realization that some kind of significant change is required. A number of high-level activities are conducted at this early stage to sensitise the chief executive and senior management to the magnitude of the change exercise.
The Awaken phase ends when the chief executive (and management team) acknowledges that the organisation needs to change, recognises that change can bring significant benefits and has engaged a Consultant to initiate the required improvements.

Envision   

The purpose of the Envision phase is to develop a common context and understanding (between the chief executive, senior management and the consultant) of the organization, its current challenges and its future direction. As rudimentary as it may seem, unaligned perceptions and perspectives of senior managers and consultants will delay or derail the program. This phase enables the organisation to initiate the BPI efforts so that all project activities strive toward consistent objectives.
The Envision phase ends when multiple levels of the client organisation have an image of where the organisation wants to be and can consistently and uniformly articulate where the organisation is headed. At this point, both the organisation and consultant share a common understanding of the organisation’s structure and operations, the external context in which it operates and what the organisation wishes to become. This shared view provides a single focus for BPI activities outlined in the Mobilisation Plan. At this stage, the BPI program is publicly announced throughout the organisation, a Program Office is established and a core team of organisation and consultants are chartered to explore the (as yet unquantified) opportunities of the “future state”.

Focus

The purpose of the Focus phase is to identify the major opportunities for performance improvement that are associated with existing processes, technology and human resources. This identification comes not only from appropriate analysis of the existing environment, but also from a full understanding of the direction that the company is taking and the external environment (political, economic, social, etc.) in which it competes. The communication of these opportunities to the organisation serves to sensitise management to the scope/degree of changes being considered and allows for the prioritisation of the design activities that are to follow in subsequent phases.
Upon completion of the Focus Phase, senior management will have a clear strategy of where they are taking the company. Core team members will have a common understanding of the company’s current performance, associated opportunities and constraints to implementation, as well as the degree to which management is willing to support the solutions being contemplated. Affected employees will be fully aware of the BPI program—why it is necessary, what aspects of the company may be impacted, as well as whether they will personally play a direct or indirect role in the various phases of the program. Priority Opportunities are isolated and, for the first time, quantified (to a +/- 50 percent level of accuracy). This effort, when carefully managed, adequately resourced and remaining under full sponsorship of the chief executive can be accomplished in three to five weeks.

Design High Level

The objective of this phase is to develop a portrait of how the organization will conduct business in the future. Design teams are chartered to support the core team in creating this portrait. It includes a description of the Business Case for the new or redesigned work processes, as well as an overview of technology and human resource changes that the eventual implementation of the recommended “To-Be” processes will require. Sufficient detail is designed to enable a +/- 30 percent level of accuracy in expected benefits and cost.
By the end of the Design High Level phase, a complete business solution will have been designed, and a Business Case and the Migration Plan will have been agreed upon “in-principle” by senior management, and understood by all affected managers and staff. The Program Office serves as the focal point of all migration planning and Business Case activities, maintains communication channels and dispatches unresolved issues that have been identified for further analysis in subsequent phases. This multiple team organisation-consultant effort may require 8 to 16 weeks to complete, and is strongly dependent on the number and level of detail of migration scenarios contemplated.

Design Details

The objective of this phase is to design the details and understand the consequences to the organisation of implementing the preferred “To-Be” business solution. The BPI program becomes a composite of multiple, discrete projects for which parallel teams of technical specialists, aided by design team members, explore the interrelated impacts of conducting simultaneous changes to processes, human resources, technology, policies, and physical infrastructure. This planning facilitates the identification of real costs, benefits and migration activities that will maximize the probability of a successful implementation and demonstrable results for the company. All detail is designed to enable a +/-10 percent level of accuracy (i.e. a 90% level of confidence).
Upon completion of the Design Details phase, management will have given its unequivocal commitment (i.e. for sponsorship, dedicated resources and funding) to move forward with a set number of implementation sub-projects with a high level of certainty in cost and confidence in benefits. Key employees will have been assigned active roles to deliver project results on time and on budget. Individuals are considered accountable for the success of the project, and specific rewards and consequences are often implemented to motivate appropriate actions.
The start, end and duration of each subproject is governed by the Migration Plan. Each sub-project has its own timeline dictated by the complexity and required activities of its scope. The Program Office manages the integration, communication and coordination of these efforts, which for large-scale projects, can easily represent 50 discrete projects and 600 dedicated resources.

Build

The purpose of this phase is to construct and test all outputs of key components of the business solution. Subproject teams work in parallel to build an infrastructure capable of supporting the “To-Be” processes. Information technology systems are validated against initial requirements both from a technical and a user perspective. All necessary support documentation is drafted or assembled in anticipation of the “go-live” implementation date. Modifications/upgrades are made to physical facilities, and organizational programmes are put in place to help deal with a broad range of employee-oriented issues.
By the end of the Build phase, the organization will have been shown a compelling demonstration of a working prototype of the business solution and will be able to confidently confirm the attainable benefits. Senior management will have declared “We are ready to go live”. Detailed implementation activities of every subproject will be known, and senior management will clearly comprehend their role during the upcoming Implement phase.
The Program Office monitors progress, risks and the quality of the multiple development subprojects; coordinates the timing of implementation and organizational impacts; and establishes a mechanism for benefit-tracking.

Implement

The objective of the Implement phase is to set in motion across the company the full suite of process, technological and social changes that have been designed and built. Implementation begins when the targets of change begin experiencing the impacts and are expected to adopt the new state. A wide range of activities are carried out by implementation teams in this phase (e.g., equipment installation, employee training, issue documentation/resolution, and managing compliance to new processes and policies).
Upon completion of this phase, the planned business solutions will be operational across the organization and employees will have been fully trained. Staff will be configured under the revamped organizational structure and will respect the revised policies that govern their work duties. The employees will see and feel the benefits and senior management will declare that the expected results from the BPI program have indeed been achieved.
The Programme Office acts as a “War Room”, coordinating and controlling all implementation events. Daily progress is monitored against Implementation Plans. Benefit tracking and Performance Feedback are in place to measure the learning curve and performance improvements against established timelines of the Migration Plan.

Enhance

The goal of the Enhance phase is to put in place mechanisms to ensure that performance improvements resulting from the BPI program are sustained over time and ultimately lead to opportunities for additional performance gains. By training small teams responsible for identifying and initiating ongoing improvements, the company will initiate an effort to make continuous performance improvement an integral part of the organizational culture.
Although this phase is ongoing, demonstrable results will occur on a number of fronts, including the successful completion of continuous improvement projects, as well as consistently improving results in customer and employee satisfaction surveys. The Programme Office activities focus on client relationship management, identifying opportunities to further enhance the client’s business performance. Senior management will recognize that continuous performance improvement is an initiative that must be supported on an ongoing basis and will set the foundation for the “awakening” to the next BPI initiative.

Thursday, February 9, 2017

BPI Technique - Work Packages - WP

BPI Technique - Work Packages - WP

Description

  • Work Packages are detailed, project-work step descriptions for small, separable groupings of activities within the BPI program. They serve as “turn-key” terms of reference describing work that may be assigned to a project work-team. Work Packages are often used in place of Design Charters to specify activities of a sub-team undertaking the implementation of Quick Wins.

When to use

  • Work Packages can be created whenever a grouping of logical, interdependent work tasks is identified as “ready for assignment” to a work-team. The actual date of assignment to a team may not be immediate and will depend on the timing of other interdependent activities.

Approach

An ongoing “laundry list” of suggestions for potential Work Packages is compiled over the course of the program. The suggestions are reviewed at regular intervals and developed into detailed Work Packages, as appropriate:
  • On an on-going basis, obtain suggestions from project team members and technical specialists for separable groupings of change/ implementation activities,    
  • For each logical grouping of activities, develop a separate Work Package that outlines:
  • Objectives - specific goals.    
  • Outputs - expected results.
  • Dependencies - other Work Packages whose results are interdependent.
  • Work-steps - activities required to complete the Work Package.
  • Resource Requirements - the skills and estimated time requirement of resources.
  • Schedule - the estimated elapsed time-frame for completion of the Work Package.    
  • Implementation Issues - Potential hurdles or risks associated with completion of the Work Package.
  • Review the Work Package with appropriate decision-makers. Modify as required.
  • Include the Work Package in the appropriate section of the “Program Book” (i.e. as a supplement/ enhancement to a Mobilization Plan, Migration Plan or Implementation Plan).
  • Identify the Work Package manager who will be held accountable for its successful completion (or a future candidate if the Work Package is to be commissioned at a later date

Guidelines

Problems/Solutions   

  • Projects have a high risk of failure as they enter implementation. Reduce this risk by developing and allocating Work Packages as early as possible.

Tactics/Helpful Hints

  • Work Packages can be developed as soon as logical groupings of change activities are identified. They may be assigned immediately to an accountable work package manager, or retained in a database and then commissioned at some later date. By "stock-piling" Work     Packages on an on-going basis, the organization has them ready to draw down and commission without losing time.    
  • Create a single Work Package that governs the management/co-ordination of all other Work Packages (e.g. management all Quick Win implementation activities).
  • The development of Work Packages usually requires several iterations with team members and management to ensure completeness (i.e. to avoid gaps and duplicated tasks) and the proper timing of dependent activities. Accordingly, it is advantageous to assign the initial development of a Work Package to a single individual as soon as it is identified as a logical grouping of activities.    
  • Clients may insist that detailed Work Packages be developed prior to presentation of the Committed Project Results and Budgets in order to ensure that all anticipated costs have been included in the total implementation cost estimates.
  • Technology-related Work Packages often span a migration period of twelve months or longer. There are, however, significant changes that can proceed without major technology alteration; the benefits of these should be derived as soon as possible. Accordingly, non-technology dependent work packages should be commissioned early.      

Examples / Templates

Example #1 illustrates a ‘laundry list’ of potential sub-projects (from which work packages would be created) for a series of human resources-related processes (e.g., pay/benefits, staffing process, etc.).
Projects that must be completed to implement redesigned processes include:
  1. Develop generic job specifications
    1. With 1st page summary for posting purposes.
    2. Standard clauses for posting    
  2. Develop staffing toolkit
    1. Update/harmonize guidelines, document best practices, do's and don'ts - Develop checklist for process
    2. Provide format for documenting selection justifications
    3. Provide letter of offer templates
  3. Establish CV database
    1. Determine criteria for inclusion
    2. Set up mechanism to ensure scanning of all recall/priority candidates
  4. Develop classification toolkit
    1. Document classification guidelines, checklist for process
  5. Equip HR with an automated telephone answering service
    1. Determine appropriate information and messages to be communicated
  6. Develop comprehensive orientation package for new employees
    1. Harmonize benefits/orientation package between two company locations
  7. Develop salary administration toolkit
    1. Harmonize compensation guidelines and document
    2. Document checklist for process
    3. Provide template
  8. Develop termination toolkit
    1. Document guidelines, checklist for process
  9. Negotiate changes to collective agreements
    1. eliminate pay exceptions
    2. reduce differences in benefit coverage, coverage codes
    3. convince unions to handle the administration associated with ‘bumping’
  10. Negotiate changes with insurance carriers
  11. Communicate changes to employees, line managers and unions
  12. Train line managers in new process, new system, roles and responsibilities.
  13. Develop workforce adjustment strategy for HR-transactions staff
  14. Classify/staff positions within HR-transactions group
  15. Train HR staff
  16. Develop and implement support technology.
Example #2 outlines the migration Work Packages used in redesigning the ‘core process’ of a small agency (200 employees) that distributes funds for research grants: Making Grant Decisions and Delivering Payments. It includes a Gantt Chart highlighting all migration activities as well as two sample Work Packages.

Work Package 2:    

Redesign application forms & supporting information package

Objectives

To produce a simplified application form and information package that will minimize the amount of information required from the applicant, and the amount of time applied by both the applicant and Agency staff.

Deliverables

  • Mandatory core application information requirements, standard across all     programs.    
  • Mandatory program-specific application information requirements and support materials.
  • Applicant "self-test" checklist to support self-screening of eligibility.
  • Sample completed application form for clients to consult in completing their applications.
  • "Did you remember" checklist for applicants in reviewing their application for completeness.
  • Standard memorandum "to the applicant" describing the use of the "self-test" and the "did you remember" checklists, the policies regarding late submission of applications,     return of supplementary documentation, tapes, etc., the Agency’s services for providing assistance to applicants and the Agency’s mechanisms for responding to successful and unsuccessful applicants.
  • Question/answer sheets for common inquiries.

Dependencies

This work package can be initiated immediately. Completion will require full approval of new policies (Work Package #1).
The deliverables must be provided to managers of the technology work packages.

Major Work-steps

  1. Develop straw-man of minimum mandatory application information requirements, both standard and program-specific. Identify which information fields, if any, will not be directly accessible by computer for any staff member to change.
  2. Review straw-man with representatives of the Agency’s finance section and auditor.
  3. Review straw-man with representatives of each program.
  4. Revise and present to management for approval.
  5. Design one standard "fill in the blanks" form follow-up letter for notifying early applicants of incomplete information.
  6. Design self-test checklist to determine applicant eligibility, by program.
  7. Prepare sample completed application forms.
  8. Design "did you remember" checklist for applicant to review completeness of information.
  9. Prepare standard memorandum "to the applicant" on application policies and protocols for inclusion in all application information packages.
  10. Communicate revised application forms and information package to all staff.
  11. Communicate reasons for revised tools to clients, and request feedback.

Resources

  • Work package manager (WPM); approx. 0.5 days per week for 4 weeks.
  • Application Design and Analysis Team (ADAT); 2 people for approximately 3 days     per week over 4 weeks.
  • Program representatives
  • Finance section representatives
  • Representative(s) from auditor.

Schedule

  • Elapsed time: 4 weeks.

Implementation Issues

It is expected that there will be periodic revisions to the grant application forms and information package as programs and eligibility criteria change with the needs of the research community. The outputs of this work package, therefore, must be positioned to reflect the minimum mandatory information given today's programs. The gains derived from this work package are large. Work packages for redefining programs and eligibility criteria can run in parallel, but should not hold up completion of WP#2.

Re-education of clients will be critical to success in using the revised tools produced in this work package.