Assessing Adoption and Objections with Evidence
In one sentence
Adoption is assessed not by speaking positively about the change but by correct and sustainable application at suitable opportunities.
By the end of this lesson
- Calculate 75% correct use from 18 correct records out of 24 applications.
- Compare the rates of supported and independent applications separately.
- Separate application opportunities, missing observations and incorrect-use records.
- Choose a suitable intervention without turning an objection into an evidence-free judgment of attitude.
- Refuse to declare lasting adoption on the basis of a one-time demonstration.
Why it matters
Everyone giving approval in the meeting where the change was introduced does not show that they use the new method at the workstation. Likewise, an operation done correctly at the first demonstration does not prove it will be done correctly once help is withdrawn. An adoption assessment rests on the moments when a real opportunity to use the new method arose. If a person's task did not come up that day, they are not counted as failing because they did not use it. If the task came up but the required tool was missing, this too is not interpreted directly as unwillingness. Alongside correct use, the observation must record the opportunity and the working condition. That way, instead of vague comments about attitude, one can see where the application took place, where it stalled and what support it needed. The target of the intervention is chosen accordingly.
The observation unit of the correct-use rate is the application. The same worker can make correct and incorrect applications at different times. For this reason one cannot move from the question of what percentage of applications are correct to the conclusion of what percentage of workers have adopted. The link to the person code, the shift and the support status must be examined separately. Intensive observation of a few people may not represent the whole team. If observation was made only on easy products or at hours when help was at hand, the rate may show ordinary conditions as better than they are. The observed scope is stated clearly; supported and independent applications are not mixed. Rather than making a rate look high, explaining correctly which condition that rate represents is more valuable for a workable change decision.
No automatic causal link is assumed between an objection and incorrect use. A worker who has voiced a concern about the change may still use the new method correctly. Another worker may have given a positive view but applied the critical sequence wrongly. A stated view and an observed behavior are two different types of information. When they are examined together, a learning gap, a physical barrier or an unsuitable solution can be investigated. Treating an objection as behavior to be punished can reduce the reporting of later difficulties and can spoil the measurement. Failed trials also stay in the record. An assessment that selects only successful examples cannot learn the limit of the method. The acceptance of the change should be tied not to the silence of workers but to evidence of safe and repeatable application.
Sustainable adoption is tested over time and under ordinary conditions. A one-time demonstration can be starting evidence; it is not the final decision. New observations are needed in periods when help has decreased, different shifts are working and product conditions have changed. This lesson assesses the application scope and the objection evidence together; the detail of skill verification for a single task belongs to M29, and the sustainment audit of a kaizen result was the subject of the earlier lesson. The basic question here is in which opportunities the new method is used correctly and which barrier limits it. The success criterion is defined in advance. If the result does not meet the target, the meaning of the numbers is not changed; a new trial is planned on support, resources or the method, and the uncertainty is kept visible.
When choosing an intervention, first decide which explanation is being tested. If use rises after a new explanation is given, it cannot immediately be said that the rise comes only from the explanation; tool access or the support condition may have changed in the same period. For this reason the task scope, the method version and the help level are kept in the comparison, or their differences are explained. If the team will decide between two workable options, it writes in advance the expected effect and the acceptance evidence of each option. That one option fails does not prove that workers do not want the change; it may show that the option did not meet the barrier concerned. This information is used in the next trial. Keeping positive and negative results together prevents the same ineffective intervention from being repeated again and again. If why the application stalls remains open, the decision can also remain conditional; there is no need to close the uncertainty with a single attitude label.
Formula
Correct-use rate (%) = Number of applications observed as correct ÷ Number of valid observed applications × 100
Independent correct use (%) = Number of correct unaided applications ÷ Number of unaided observed applications × 100
Observation coverage (%) = Number of valid observed opportunities ÷ Number of planned suitable opportunities × 100
Number of incorrect applications (applications) = Number of valid observed applications − Number of correct applications
Unlock the rest of this lesson with an Academy account
Create a free Academy account with your work email address; it can be used once it is approved.
- Step-by-step instructions
- Worked example with real numbers
- Where the method misleads
- Common mistakes