We can use the definition of 'effectiveness' from 9000:2015 as a guide:
3.7.11 effectiveness
extent to which planned activities are realized and planned results are achieved
Breaking this down, we have these elements:
- extent that planned activities are realized
- extent that planned results are achieved
- (implied) 'extent' indicates a dataset that is a defensible sample size across applicable activities and time
So, for example, if we are correcting a process deficiency in process X123 by adding a checklist form F-0123 that must be signed and saved, then our effectiveness check might be:
- extent that planned activities are realized:
- checklist form F-0123 exists and is available to applicable workers
- checklist form F-0123 is being filled out correctly
- checklist form F-0123 is being filled out on every work order
- checklist form F-0123 is being saved in the right location
- extent that planned results are achieved (remember, we did this because of a process deficiency)
- process demonstrates improvement of x% from the deficiency (or elimination of the deficiency)
- extent:
- across this process, for at least 15 work orders (or for minimum of 1 months, etc.).
More colloquially, we would probably phrase this as something like:
- Effectiveness: Monitor for a minimum of 25 work orders as of 6/10/2022 that form F-0123 is being correctly filled out, signed, and saved as planned on every work order in process X123, and that rejection rates from process X123 are below 1.5% for a minimum of 3 months beginning with July 2022.
In this example, the extent values (number of work orders and timeframe) need to be defensible that they represent a reasonable sampling to demonstrate consistent realization and results.
What is not an explicitly stated part of effectiveness is
side effects. For example, if our form achieves the intended results, but its a 30-page checklist that takes 2 hours to fill out, causing worker unhappiness and missed work order deadlines, those are undesirable side effects. Side effects could be positive or negative (e.g., an improved process might make workers happier as a side effect), but in either case are missing from effectiveness. One could argue that 'planned results' should encompass the risk of side effects, so that changes our effectiveness statement to:
- Effectiveness: Monitor for a minimum of 25 work orders as of 6/10/2022 that form F-0123 is being correctly filled out, signed, and saved as planned on every work order in process X123, and that rejection rates from process X123 are below 1.5% for a minimum of 3 months beginning with July 2022, and there is no negative impact on process X123 on-time performance and no notable worker complaints relative to these changes.
Obviously, one can go down a rabbit-hole when trying to cover side effects, and usually I do not mention them in my effectiveness statements, as "it is just understood" that we don't want negative side effects, but I thought I'd mention it here.