A studio changes its workshop check-in procedure. For years, staff printed an attendance sheet and brought it to the door. From Monday, they check names against a list on a shared tablet. Someone asks an AI assistant to rewrite the instructions. The result is clear. Yet on the first busy morning, a colleague reaches for the printer. She knows about the new process. The old one is simply the answer that comes to mind when she hears ‘check-in’.
The temptation is to write a longer announcement. A better starting point is to look at where people encounter the change. If the same folder, checklist and opening line still point towards the old routine, the new instruction has to compete with those cues. A short notice, placed where someone makes the decision, can make the difference between having read the update and knowing what to do next.
What a change of context can do
In a 2002 study of directed forgetting, psychologists Lili Sahakyan and Colleen Kelley had participants study two lists of words. In some conditions, people were told to forget the first list before studying the second. In others, an intervening task was used to change what they were thinking about between lists. In their experiments, the context change produced patterns similar to the instruction to forget: poorer recall of the first list and better recall of the second under the comparison conditions.
The researchers also found that prompting people to think back to the initial study setting helped recover some of the first list in certain groups. That matters for interpreting the result. The earlier information had become harder to bring to mind under particular conditions; the study did not show that it had been erased. The authors presented context change as an explanation for their findings. They were testing recall of words, not training people to use new software or testing AI-generated instructions.
The studio can take a design question from that work without treating the laboratory result as a workplace guarantee: when a familiar prompt has two possible answers, what tells a person which answer belongs here? In this example, the phrase ‘workshop check-in’ names both routines. A cue that identifies the date, the device and the first action gives the person at the door a better way to tell them apart.
Put a cue at the point of action
Start by walking through the task as someone would do it on a busy morning. Which message do they open? Where do they stand? What do they reach for? A revised attachment at the bottom of last month’s email may be accurate and still hard to find. In the studio, a short card beside the tablet could read: ‘For workshops from Monday: open today’s attendance list on this tablet.’ It marks the boundary and tells people how to start.
Use one cue the team can recognise without relying on colour, memory or familiarity with the file system. Put the same wording on the shared checklist and in the brief that goes out before the session. Ask the assistant to help shorten the wording, but give it the effective date and scope yourself. Shortening ‘from Monday for workshops in the main studio’ to ‘for all sessions’ would create a fresh mistake, especially if another venue still needs the paper sheet.
Decide what should happen to the old instructions
Moving an old guide out of the everyday workflow does not mean destroying it. The studio might still need it to understand last month’s attendance records, or as the basis for a documented fallback when the tablet is unavailable. Archive the previous guide with its effective dates and mark the current version where staff normally look. If part of the old routine is still valid, explain exactly when it applies instead of telling everyone to forget it.
If an AI assistant is involved, check what material you give it for the next task. For a new staff checklist, use the current guide and supply any fallback rule explicitly. For a question about an earlier workshop, use the policy in effect on that date. Putting both versions in an input can be useful for a comparison, provided they are labelled and the question says which to apply. An instruction to ignore old guidance does not itself remove files or establish what an assistant can retrieve. The related MaryChuks article on keeping decisions clear across chats explains how to preserve this distinction in a project handover.
See what people do when the old answer would have worked
- Try the ordinary case. Give a colleague a realistic arrival scenario and ask what they would do first, with the new cue in its actual location.
- Try a boundary case. Ask what happens at a venue that still uses paper, or if the tablet is unavailable. A clear update should help people apply the exception correctly.
- Watch where they look. If they open the archived guide first, change the route to the current one before rewriting another announcement.
- Check again later. After several real sessions, ask which step still causes uncertainty. Keep the cue until the team can find and apply the new procedure reliably.
An AI assistant can help explain what changed. The people doing the work still need a way to recognise when the change applies. The test of a revised instruction is whether it gives them a clear first move at the moment the old routine would otherwise take over.
Source
- Sahakyan and Kelley, A contextual change account of the directed forgetting effect, Journal of Experimental Psychology: Learning, Memory, and Cognition (2002).