The briefing went well. Everyone in the room understood. The people using the revised instruction tonight were not in the room.
ORR IMS is an evolving learning example, currently connecting five starter kits. It is not a complete implementation of the four standards in its intended scope.
It is a small implementation problem with consequences for how we judge readiness. An activity can be completed exactly as planned while the plan excludes an affected group.
For an ISO enthusiast, this is worth examining from the receiving person’s perspective. How does a change reach someone who works different hours, covers another role or accesses information through a different route?
The output here is an affected-user coverage map. It connects each group to the changed task, communication route, practice, access and time they need. An attendance list alone cannot show that coverage.
Look beyond the people at the meeting
Consider a fictional retailer changing its returns process. Weekday staff attend the launch briefing; weekend staff and temporary cover are absent. All three groups may face the next customer return, but only one appears in the attendance record.
Writing “store team informed” would hide that gap. The useful planning question is how each affected group will learn the changed task before it needs to perform it.
When mapping affected users in your own system, consider who performs the task, supervises it, authorises a decision or supplies an input. Include relevant shifts, relief arrangements and external interfaces.
Be careful with broad group labels. “Operations informed” can conceal differences between people who routinely receive formal updates and those who receive instructions through another supervisor.
Ask what each person needs to do
A change announcement explains that something is different. People may also need to know what they are expected to do differently and when.
For a supervisor, that might mean performing a revision check before a defined event. For an operator, it might mean identifying the applicable instruction and knowing where uncertainty should be raised. For a relief supervisor, it may include understanding which changes and unresolved matters are being handed over.
These needs can require different communication methods. The person who approves the document may not be best placed to judge how a new user will interpret it.
Ask affected people to describe the changed task in their own words. Where appropriate, observe them working through an authorised practice or learning scenario. Match the method to the activity and the evidence needed.
Do not turn a signature into a claim that every required capability has been demonstrated.
Make time part of the design
In the retailer exercise, a weekend colleague needs paid work time to examine the change and practise a fictional return. If the only briefing occurs during the weekday shift, the plan has not yet provided that opportunity.
This detail matters because implementation consumes real capacity. Somebody must prepare, attend, ask questions, practise where needed and follow up.
If the plan assumes that all of this happens invisibly between normal tasks, find out whether that assumption is credible. Which work competes with the briefing? Who covers the task while the affected person participates? What happens when a customer deadline changes?
The answer may require a leadership decision. Record the tradeoff rather than allowing the implementation team to carry an unspoken expectation that everyone will somehow absorb the extra work.
Follow access all the way to the user
The approved instruction may be available in a system that some users cannot reach at the time of need. A password, device, connection or permission can become part of the implementation problem.
These are conditions to examine in the retailer exercise, not claims about a real employer.
Add access conditions to the coverage map: available device, login, location and support route. A temporary colleague may need a different arrangement from the person who authored the change. Record the access check required for each group rather than assuming one demonstration covers everyone.
A daytime demonstration from the author’s computer cannot establish that another shift has the same access. Define the population you need to cover and record which conditions were actually examined.
That makes the limits of the readiness conclusion visible.
Design relief handovers deliberately
Now extend the retailer exercise: a relief supervisor takes over after the initial rollout. The coverage map needs a way to include that person and any changes introduced since the original briefing.
This is an important learning point: a successful initial rollout does not settle every future coverage question.
A relief handover needs to transfer the relevant responsibilities and current state. What changes are pending? Which checks are due? Which issues remain unresolved? What authority accompanies the role, and when should the substitute escalate?
The outgoing and incoming people should be able to describe the same transferred work. Where their accounts differ, investigate the gap.
The aim is to make the handover dependable enough that the substitute can act without relying on a conversation they never heard.
Learn from a new user’s confusion
The ORR IMS acceptance protocol proposes observing a novice using the instructions and recording confusion, assistance needed and errors. That is a useful way to test whether the explanation carries enough context.
Use a safe fictional exercise with clearly defined boundaries. Observe before helping, then discuss where the person hesitated. A question that seems obvious to the author may be precisely the information missing from the document.
Do not manufacture participant feedback or describe a planned trial as completed. Record the actual person, task, conditions and observation where such a trial is authorised and performed.
After changing the instructions, revisit the affected step. A revised sentence is an intervention; its usefulness still needs examination.
Make an affected-user coverage map
A fictional retailer changes its returns process. Weekend staff and temporary cover use the process but miss the weekday briefing. The coverage question concerns who needs information, practice, access and time, rather than who attended the meeting.
List affected groups, the task each must perform, its communication route, available practice and evidence needed for readiness. Include one person outside the usual planning meeting.
Start with the document-control worksheet. Who is easiest to miss when a change is introduced? Leave a comment below; a question or fictional example is enough. If you want to propose a document change, the contribution guide explains the optional GitHub route.
Use fictional examples only. Do not share employer or client records, personal information or copied standards text.
Images are AI-generated illustrations, not photographs or evidence of actual implementation.
Part 8 of 12 in Making IMS Work with ORR IMS. Explore the series.
Leave a Reply