|
|
|
|
|
Books and
more at:
USA:
 UK:
Canada:
|
|
|
|
Tools for the Follow-up stage
The Quality Toolbook
> Tool Finder > Starting from the project framework > Tools
for the Review stage
Identify |
Define | Problem |
Cause | Solution |
Implement | Review |
Follow-up
<-- Previous |
Next -->
This section identifies tools which may be used in the
Review stage of the
project framework for the following
activities:
If the implementation was successful:
- Standardizing the solution, writing it up as a normal operating procedure and spreading it to other areas.
- Looping back to previous stages for further improvements.
If the implementation was unsuccessful:
- Addressing the cause of the lack of success, to prevent it recurring.
- Looping back to previous stages to correct and repeat actions.
If the project is being closed down:
- Writing up the project as a 'success story'.
- Presenting results to managers and other groups.
- Using the lessons learned to improve the improvement process itself.
- Celebrating the success.
- Planning for future projects.
If the implementation was successful:
- Standardizing the solution, writing it up as a normal operating procedure and spreading it to other areas.
Document the changed process with
IDEF0,
Flowchart,
Flow Process Chart,
String Diagram or
Relations Diagram.
Use outputs from other tools to help demonstrate benefits of change.
Implement ongoing monitoring measurements with a
Control Chart or
Line Graph.
- Looping back to previous stages for further improvements.
Use a
Decision Tree or
Force-Field Diagram to help identify the best course of action to take.
If the implementation was unsuccessful:
- Addressing the cause of the lack of success, to prevent it recurring.
Use new measurements from tools to ensure correct causes are identified.
- Looping back to previous stages to correct and repeat actions.
Review use of tools and change as appropriate.
If the project is being closed down:
- Writing up the project as a 'success story'.
Use the output of the tools as actually used in the project, rather than creating them specifically for the write-up (this makes the report much more credible).
- Presenting results to managers and other groups.
As with the write-up, use the graphical output from tools that was actually
used.
Select a few key ones to illustrate specific points, rather than trying to
show every graph and list that was used.
- Using the lessons learned to improve the improvement process itself.
Use the
Pareto Chart,
Prioritization Matrix or
Voting to help select the most important changes to make.
- Celebrating the success.
Post large versions of key tool outputs on the walls.
Combine celebration with presentation of results to other people.
- Planning for future projects.
Measure processes as in the Identify phase.
Use the
Gantt Chart to plan broad timescales for actions.
<-- Previous |
Next -->
| |
|
|
