Leading Change with Operators: Participation, Teaching and Feedback
In one sentence
A worker's objection is information to be investigated; participation requires not only collecting views but also showing which decision those views changed.
By the end of this lesson
- Record feedback as an observable event, separate from a judgment about the person.
- Calculate the evidenced barrier rate over 24 records with the correct numerator and denominator.
- Choose different interventions for tool, explanation and shift-support needs.
- Keep participation, teaching and independent-application evidence apart.
Why it matters
A change that looks clear at the design desk may not be applicable at the workstation. The way material arrives, access to a tool or the shift handover differs from what the design assumed. When a worker points out this difference, if the first reaction is to label them as closed to change, information about the process is lost. The aim of participation is not for everyone to approve every proposal. The aim is to include the experience of those who do the work in the trial and in the decision. For this reason views are tied to concrete events: in which task, under which condition, what could not be done and what was the result? Instead of an interpretation of the person's intent, a testable explanation is sought. That way criticism becomes a starting point for developing a workable countermeasure.
The number of feedback records is not the same as the number of workers. The same person can report several difficulties in different tasks; the same event can also be described by several people. When the unit of record is not defined, rates lose their meaning. Counting repeated accounts of one event as separate barriers can distort priority. On the other hand, collapsing similar events that really happened in different shifts into a single record hides how widespread they are. What unit a record represents is stated at the start. In this lesson the basic unit is a feedback record about a unique application event. The person code, task, condition and evidence link are kept. The numerical summary helps decision-making without tearing what the worker said out of its context.
An evidenced barrier is a situation, supported by observation, that makes it harder or impossible to apply the new method under the defined conditions. The absence of a required tool and an explanation that is not understood do not call for the same intervention. In the first, resources and access are examined; in the second, the explanation and the way of learning. A concern that has not yet been verified is not regarded as wrong; it is kept as a record awaiting investigation. If there is a safety claim, there is no need to continue a dangerous job in order to collect evidence. The application is stopped at a safe limit and an authorized review is requested. The need for evidence does not mean forcing the worker to prove their complaint. Organizing the observation and the review is the responsibility of the change team; the worker's explanation is a valuable input to that review.
Teaching is not just giving a presentation either. The new work sequence, the critical quality condition and the situation that requires help must be understood. But this lesson does not design in detail how to teach a single task; that topic belongs to M29. Here the focus is on deriving the teaching need from feedback and providing the right time and support. An attendance signature does not prove that a person applies the method independently. Everyone staying silent at the end of a discussion is not consensus either. The change team must explain which proposal it accepted, which it put on hold and why, and when it will reassess. A suggestion-collecting arrangement with no return makes it harder for later views to be shared.
A participation arrangement that is easy to understand also makes visible why different workers look at the same subject differently. A job that is easy in one shift can become hard in another because no support person is available. Instead of choosing one of the two accounts as wrong, the conditions are compared. The person who gave the feedback is shown which part of the solution was changed and is given a chance to observe again. Even if the solution the worker proposed cannot be applied, the barrier they reported can be removed in another way. This distinction matters: rejecting a proposal is not ignoring the problem. For example, while the worker asks for the tool's location to be changed, the real difficulty may be that the tool does not return on time. Fixing sharing and handover, rather than changing the layout, may be what is needed. When options are tested together, the value of participation is not measured only by the number of accepted proposals. Which barrier was understood, which decision improved and how the workers' application conditions changed also go into the record. This approach prevents an up-front attitude divide between those who voice a view and those who do not.
Formula
Evidenced barrier rate (%) = Number of unique feedback records containing an evidenced barrier ÷ Number of unique feedback records reviewed × 100
Open barriers (records) = Number of verified barriers − Number of barriers verified as removed
Closure rate (%) = Number of barriers verified as removed ÷ Number of verified barriers × 100
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