Employees who perform the work see workarounds, handoff delays and abnormal conditions that procedure authors may overlook. Convert this expertise into verifiable control improvements.
Participation improves control design because the people doing the work understand real constraints. The benefit is not an abstract engagement score: It is a procedure, tool or decision path that survives normal pressure and abnormal cases.
Published context: ISO: ISO 10018:2020, Guidance for people engagement.

Workers reveal the real process interface
People performing a task see unavailable scanners, awkward handoffs, near misses and customer exceptions that flowcharts omit. Invite them before controls are designed so solutions target actual work. Participation should not be reduced to signing a consultation sheet after the decision is made.
Follow one normal and one unusual transaction with operators and ask where the proposed control could fail under peak conditions.
Design participation around real decision rights
Set out which issues employees can decide, which require technical approval and how feedback will influence the final design. Without a visible response, repeated surveys become a source of cynicism. Include night shift, temporary and remote workers rather than hearing only office staff.
Evidence check. Provide a feedback register with owner, decision, reasons and communicated outcome. Test whether contributors recognize the action taken.
Use co design to improve usability
Prototype the instruction, screen or checklist at the actual workstation. Check reachability, equipment, sequence, required data and whether the user can perform the task while wearing appropriate PPE. Avoid adding a form step that produces the same information twice.
Observe whether the prototype works during changeover or rush periods. Distinguish a genuine control weakness from cosmetic preference.
Invite challenge on exception handling
The strongest design test asks what happens when an input is missing, a customer is urgent or an authorization cannot be reached. Employees often know the unofficial workaround; this information is vital for engineering a safer alternative. Do not punish candid discovery of weaknesses.
Evidence check. Record abnormal scenarios and the proposed escalation route. Verify that a named person has authority to resolve them.

Balance participation with specialist obligations
Employee proposals should be assessed against customer commitments, legal obligations and technical safeguards. Participation does not transfer accountability for statutory controls to a workshop vote. Explain why a suggestion is accepted, modified or declined.
Preserve decision rationale and involve specialists where safety, environmental or highly regulated operations are affected.
Frontline co design acceptance test
Co design begins before the proposed control is fixed. Observe actual work and ask employees to locate the points where equipment, sequence, staffing or information breaks the idealized flow. Invite members of different shifts and employment categories, because an instruction that works in a daytime pilot may fail at night or during maintenance. Make the purpose and non negotiable safety or customer criteria explicit so participants can challenge the method without thinking the organization has abandoned the desired outcome.
A feedback register should show each issue, who considered it, the decision and why it was accepted, modified or rejected. Employees need not get every requested change, but they deserve a reasoned response. When a suggestion affects a critical safeguard, seek competent technical and legal review. If the control is tested on the production floor, record the participants, sample conditions, deviations and acceptance criteria. Revisit whether the redesigned task still works with protective equipment, shared terminals and peak throughput.
The most useful participation often concerns exception cases. Ask workers what they do when a scanner fails, a label cannot be read, a supplier substitutes material or an approval is unavailable. These accounts can expose previously invisible dependencies. Do not assume an observed workaround is acceptable; use it to design an authorized alternative with adequate safeguards. An improvement workshop should therefore produce an operating decision, a controlled change and a plan to test effectiveness. Counting suggestions alone tells little about the quality of control design.
After rollout, compare observed execution with the pilot and monitor for new unintended effects. Workers should be able to report repeated delay, duplicate entry or a safety problem through a trusted mechanism. A supervisor must take ownership of the follow up rather than redirect every concern to a distant ISO coordinator. Where the data support it, share how frontline input improved the actual method; where the pilot failed, explain what is being reconsidered. Participation becomes a durable quality principle when it changes decisions and creates reliable practical controls.
A practical acceptance exercise should focus on frontline feedback obtained, prototype tested in context and decision rights understood. Involve employees early, give them a visible route to challenge unsafe or impractical controls and verify the redesigned task under real conditions. The responsible reviewer should also ask which failure or contrary sample would overturn the initial conclusion. Where the available population is small or unusual, explain the limits of inference. Documented trial observations across shifts, incorporated employee feedback, approved acceptance criteria and sustained exception performance.
Participation must also be reviewed for representation. If only the most confident employee attends the redesign session, important constraints affecting temporary workers, night shifts or workers using assistive technology may be missed. Seek representative examples and provide private routes for raising sensitive concerns. Compare the final design against task time, reachability of equipment, data burden and response to abnormal cases. Incorporate suggestions when they strengthen a required outcome and explain decisions when they cannot be accepted. A sustained feedback channel gives managers an early warning mechanism as new products, contractors and operating conditions alter the control environment.
The time saved by an intuitive control should not be mistaken for a reduced level of assurance. If employees propose a simpler sequence that preserves identification, verification and evidence, it may be the stronger design because it is more likely to be followed consistently. The process owner should evaluate the proposed method against applicable criteria and the possible consequence of error. Pilot it under real conditions and record why it was accepted. An improved task should have an unambiguous success condition and a clear treatment for abnormal results.
Employee participation can also strengthen internal audit sampling. Frontline personnel know which conditions challenge a control: Night shifts, urgent orders, supplier substitutions and equipment resets. These insights can guide auditors toward representative risk scenarios without allowing participants to select only favorable records. When findings are returned to the team, explain which suggestions led to change and which required further technical analysis. This completes a learning cycle in which operational evidence, management decisions and worker experience continually improve one another.
Management may also track how quickly employee proposals move from observation to a tested decision. A raw suggestion count can be manipulated and encourages low value submissions. Instead, sample several consequential proposals and check the clarity of the issue, technical evaluation, decision rationale and resulting control. Good participation has an observable effect even when an idea is rejected: The worker learns the reason and can raise further evidence. The resulting trust helps expose weaknesses before customers or auditors discover them.
| Evaluation lens | Topic specific focus | Evidence to request |
|---|---|---|
| Condition to observe | Frontline feedback obtained | Direct observation or approved task record |
| Capability signal | Prototype tested in context | Demonstration, interview and sample comparison |
| Follow up outcome | Decision rights understood | Trend, error or exception decision evidence |
| Governance check | Feedback loop visibly closed | Named owner, escalation and effectiveness review |
Measure adoption through observed work
After approving the design, sample actual tasks across shifts and experience levels. Review exception quality, rework and complaints without claiming a perfect improvement from one favorable week. Give users a way to report unintended effects after rollout.
Evidence check. Compare observed behavior with the pilot acceptance criteria and change the instruction if the control proves too difficult to sustain.
Make improvement visible to contributors
Close the feedback loop by showing what changed because employees participated. Recognition should reward useful identification of risks, not simply agreement with management. Revisit the design after tooling, personnel or customer requirements change.
An effective participation culture is demonstrated when frontline evidence changes a documented management decision and the new control remains usable.
Management decision and practical next step
Involve employees early, give them a visible route to challenge unsafe or impractical controls and verify the redesigned task under real conditions.
Acceptance evidence: Documented trial observations across shifts, incorporated employee feedback, approved acceptance criteria and sustained exception performance.