Continuous improvement
Impact effort matrix: choose an improvement
Use an impact effort matrix to compare improvement proposals. Keep evidence, uncertainty and mandatory requirements beside the estimated positions.
An impact effort matrix places proposed actions on two axes: expected effect and effort to implement. It helps a team compare options before committing to the next piece of improvement work.
The position is an estimate. A point in a favourable quadrant does not establish a measured return or approve the action.
ASQ's method starts with proposed solutions and assesses their effect and effort. Use the matrix after understanding the problem well enough to compare actions that could address it.
Keep the proposal and its evidence together
| Field | What the team should record |
|---|---|
| Proposed action | The specific change and process boundary |
| Expected effect | The outcome that should change and the evidence behind the estimate |
| Effort | People, time, dependencies and relevant cost |
| Uncertainty | What remains unknown and how it affects the position |
| Requirement | Safety, quality or other conditions the action must preserve |
| Next check | Evidence needed before proceeding |
Use comparable definitions across proposals. A cash-saving estimate, released staff capacity and a reduction in customer delay are different measures. Agree how they enter the comparison instead of treating each as the same kind of impact.
Read the example without treating it as a trial result
ASQ illustrates the method using a patient-record mix-up during hospital transfer. The proposed responses include identification policy, training and bar-code matching. The example uses the matrix to compare actions after the incident.
Its plot is a prioritisation judgment. It does not report a controlled evaluation showing how much each option reduced errors.
The same distinction matters in operations. The PDCA example shows why an expected benefit needs a trial with a prediction and conditions to protect.
Keep requirements from becoming optional scores
An obligation or required containment action cannot be deferred simply because a team assigns it high effort. Separate that work before ranking discretionary improvement trials.
For uncertain proposals, identify the smallest useful check that could change the estimate. Review the plot when the evidence changes rather than preserving a favourable position from the first workshop.
Use the matrix at the right scale
The automation scoring Note assesses process suitability and value before selecting technology. The portfolio explanation covers investment and shared capacity. An impact effort matrix for a local trial does not replace either decision.
Bring the next few bounded proposals with their evidence and requirements. Choose a next check the team can actually resource, record why it was selected and revisit the estimate after the result.