Why employees keep following old SOPs after procedures change

A changed SOP creates two procedures at once.

One procedure is written in the newly approved document. The other already exists in employee memory, repeated behavior, saved templates, software cues, job aids, and team expectations.

The second procedure often has more momentum.

That is why publishing an update, sending an email, or assigning the full course again may fail to change what people do. Effective retraining must identify what became obsolete, make the difference unmistakable, create practice with the new response, and remove the workplace conditions that keep triggering the old one.

Key takeaways

• Previously correct knowledge can become a source of error after a procedure changes.
• Old SOPs survive in people, tools, templates, social routines, and unofficial workarounds—not only in archived documents.
• Employees need to understand what changed, what stayed the same, and when the new rule applies.
• Repeating an entire course can bury the important change inside familiar content.
• Sustainable retraining combines targeted learning with updates to the work environment and later performance checks.

Previously correct knowledge can become negative transfer

Experience usually helps employees work faster. It creates patterns that reduce the need to think through every step from the beginning.

After a procedure changes, the same efficiency can become a problem.

A familiar cue may retrieve the old action before the employee consciously considers the update. The more often the previous process was practiced, the more available it may remain—especially under time pressure, distraction, or stress.

Research on prior knowledge shows that existing knowledge can support new learning when it is accurate and relevant, but it can also interfere when it conflicts with the new material. Source: Shing and Brod, “Effects of Prior Knowledge on Memory”.

Workplace researchers often discuss this challenge through the idea of organizational unlearning. A review of workplace unlearning research describes the need to discard obsolete knowledge and routines while acquiring new ones. Source: Kim and Park, “Unlearning in the Workplace”.

“Unlearning” should not be interpreted as deleting a memory on command. The practical goal is to make the new response more reliable than the old one in the situations that matter.

Old procedures survive in more places than memory

A source owner may replace the document and still leave the old system largely intact.

Look for the procedure in:

• printed job aids;
• screenshots and training decks;
• saved email templates;
• onboarding checklists;
• software defaults;
• form fields and approval routes;
• team chat messages;
• manager coaching;
• unofficial shortcuts;
• examples used in assessment;
• recordings of previous demonstrations;
• employees who train new hires informally.

Consider a hypothetical organization that changes the escalation path for client incidents.

The official SOP now requires notifying the on-call supervisor through a new system. The old course is replaced. But the shared checklist still names the previous manager, the software bookmark opens the old form, and experienced employees continue telling new hires to send a direct text.

The organization does not have one outdated artifact. It has an outdated network.

This is why source governance and learning governance must be connected. A source change should trigger a search for downstream dependencies, not only a new document version.

Explain the difference, not the whole document again

The most important retraining content is often the delta: the meaningful difference between the previous and current procedure.

Employees should be able to answer:

1. What changed?
2. What stayed the same?
3. Why was the change made?
4. Which roles and situations are affected?
5. When does the new process begin?
6. Which old action must stop?
7. What should replace it?
8. Where is the current source of truth?

This comparison reduces ambiguity.

A generic announcement such as “The incident-reporting SOP has been updated” requires employees to discover the operational difference themselves. Many will scan the document, recognize familiar sections, and miss the one condition that changes their behavior.

A better update is specific:

Previously, staff notified the office manager by direct message. Beginning September 1, staff must use the incident channel in the on-call system. The initial safety response and documentation deadline have not changed.

That statement does not replace the full source. It orients attention toward the change that must be learned.

Let employees reveal the old routine

Do not begin by telling employees the answer.

Begin with a realistic situation that activates the procedure they would naturally use.

For example:

It is 6:30 p.m. A client has an unwitnessed fall, reports no pain, and asks the caregiver not to contact anyone. What should happen next?

Ask the employee to choose an action and explain the reasoning.

The response can reveal whether the person is:

• following the new process;
• using the previous process;
• combining old and new steps;
• guessing from general experience;
• missing a prerequisite concept;
• relying on a local workaround.

This is more useful than asking whether the employee has read the update.

One response is still not enough to diagnose a stable belief. Use another scenario with different surface details to see whether the same reasoning appears again.

Practice the new response where the old one used to appear

Correction should occur in the situations that previously triggered the old action.

Use practice that includes:

• the same cue that started the old procedure;
• the decision point where old and new processes diverge;
• a comparison of the consequences;
• a chance to perform the new step;
• feedback tied to the current source;
• a different scenario requiring the same updated rule.

If the change affects a software workflow, reading about the workflow is not sufficient. The employee should use the new interface or a faithful simulation.

If the change affects judgment, a factual quiz is not sufficient. The learner should decide among realistic alternatives and explain which condition controls the choice.

If the change affects physical performance, observation may be necessary.

The instructional method should match the changed behavior.

Remove the cues that recreate the old behavior

Training cannot reliably overcome an environment that continues to point backward.

Update or retire:

• previous document versions;
• obsolete job aids;
• outdated screenshots;
• old forms and templates;
• bookmarks and links;
• automated reminders;
• examples in onboarding;
• manager talking points;
• assessment questions based on the old rule.

Also examine incentives and workflow constraints.

An employee may know the new process but return to the old one because the new system is slow, access is missing, supervisors respond inconsistently, or deadlines make the approved method impractical.

The CDC’s training-needs guidance recommends determining whether a performance gap is actually caused by a knowledge or skill need before choosing training as the solution. Source: CDC, “Assess Training Needs”.

When the environment rewards or requires the old behavior, more training is not the complete answer.

Use a targeted replacement cycle

A practical retraining sequence is:

1. Identify the obsolete action

Describe the exact behavior that should stop. Avoid broad statements such as “follow the revised SOP.”

2. Identify the triggering conditions

Determine when employees are most likely to retrieve the old process.

3. Compare old and new

Show the point of divergence and what remains unchanged.

4. Explain the governing reason

Connect the change to safety, quality, compliance, customer experience, or operational logic where the source supports that explanation.

5. Practice the replacement

Use a realistic task or decision, not only a document acknowledgment.

6. Update the environment

Remove obsolete cues and make the current process easier to find and execute.

7. Check later application

Use supervisor observation, workflow evidence, audit results, or a delayed scenario to verify that the new response persists.

This cycle treats the problem as behavior replacement rather than content distribution.

Connect source versions to learning dependencies

A learning system should preserve relationships among:

source version → requirement → concept → lesson → scenario → assessment → role → evidence

When a requirement changes, the organization can then ask:

• Which lessons teach the affected rule?
• Which questions still reward the old answer?
• Which roles perform the changed task?
• Which learners completed the previous version?
• Which job aids and templates depend on it?
• What historical evidence must be preserved?
• Does the change require communication, practice, reassessment, or all three?

This is a natural direction for LoreGraph’s approach to source-based workplace learning. The objective is not to regenerate every course whenever a document changes. It is to identify the affected knowledge and update the right downstream experiences.

Common mistakes

Sending only the revised document. Employees may not know where to focus.

Repeating the entire course. Familiar material can hide the changed rule and create unnecessary time cost.

Deleting the old file but leaving old cues. Templates, software, and coworker coaching may continue the routine.

Measuring acknowledgment. A signature proves receipt, not replacement of behavior.

Treating resistance as the only explanation. Reversion may result from memory, environment, unclear differences, or missing access.

Assuming one successful quiz is enough. The old response may return under pressure or after time has passed.

Next step

Choose one SOP that changed during the last year.

Write the previous action and the current action side by side. Then search for every place the previous action still appears: courses, job aids, templates, software, messages, assessments, and informal coaching.

Do not assign retraining yet.

First remove the contradictions. Then create one realistic scenario at the exact point where old and new behavior diverge.

That is the smallest useful unit of retraining.

Sources and further reading

• Kim and Park, “Unlearning in the Workplace: Antecedents and Outcomes”.
• Shing and Brod, “Effects of Prior Knowledge on Memory”.
• Carnegie Mellon Eberly Center, “Learning Principles”.
• CDC, “Assess Training Needs: Conducting Needs Analysis”.
• Park and Kim, “Exploring Linkages Between Unlearning and Human Resource Development”.