Purpose
The goal!
To design a Should-Be Process that addresses the breakdowns and disconnects and takes advantage of opportunities identified earlier, leading to ongoing workflow improvement and/or a specific change.
Why do it?
It establishes a common set of expectations for the change and a context for agreement on the new Should-Be.
It is important to identify what the Should-Be Process looks like so that the organization can answer the question “Why should we invest time and effort in improvement or change?”
It motivates the team.
It provides information to share with other stakeholders.
What to do:
Educate the Design Team on the work that has been performed to date.
Create a Should-Be design that incorporates knowledge from the As-Is analysis using a collaborative and creative team approach.
Illustrate the process using cross-functional flowcharts when it helps with understanding.
Decision:
Have all Activities and Tasks been identified for the Should-Be Process?
Does the “Should-Be” process design and related assumptions meet the design criteria and address breakdowns and disconnects identified in “Analyze and Identify”?
Help: In many cases it is best to interview departments and create a draft of the process before conducting a group design session.
Label activities beginning with a verb. Try not to use the same verb twice. These words will eventually become the top navigation components of Smart Solutions.
If the existing process is close enough to the future state, make a copy of the As-Is Worksheet, save it as Should-Be and modify it to represent the improved process. A determining factor is the tally of the breakdown categories performed in the analyze activity. If the percentage of issues was low in the process area then, saving the As-Is as the Should-Be and tweaking the process may be less work.
If you are beginning with the Should-Be template perform a move and copy to the As-Is worksheet and move to the Should-Be.xls file.
Responsibility
Team Leader
Team Members
Team Facilitator
Before you begin
Process and Resource Owners agree to opportunities that surfaced during the Gate 3 presentation
Process and Resource Owners agree on future vision of the process and have affirmation from Process Council (if necessary)
Procedure
By completing these steps, a Should-Be process is established. Ensure the design team agrees that the design will accomplish process objectives
Step |
Action |
1 |
Prepare meeting agenda and frames including a draft of the Should-Be process in theShould-Be.xls. |
2 |
Review Team Charter, As-Is and Gate 3 Presentation with design team for understanding of assignment and improvement opportunities |
3 |
Review draft of high level Should-Be process with the team. |
4 |
Modify Should-Be process until agreement is reached at the activity level, remember to name the activity with a verb first.
Guideline: The process or sub-process should be able to be described in 5 to 9 activities. |
5 |
Determine the tasks for each activity. (5 to 9 per activity) Include decision points and branching so that a complete process is designed. Illustrate the process using cross-functional flowcharts when it helps with understanding. Compare with As-Isbreakdowns and disconnects and identified improvement opportunities to ensure the process has been significantly improved. If any “disconnects” are not addressed, the team needs to modify the “Should” process design or outline a procedure for addressing them in the future. |
6 |
Determine inputs and outputs at the activity level by reviewing the tasks based on the workflow. |
7 |
Document inputs coming from outside the process and outputs to other processes/activities on the Inter-Process Linkages page in the Should-Be.xls |
|
|