A service organisation replaces its case-management system. Staff complete the training and pass a short assessment. A month later, some teams still use spreadsheets to track cases, others duplicate information in both systems, and managers disagree about which record is authoritative.
The problem is sometimes described as a failure to rewire established habits. That phrase may acknowledge that learning takes effort, but it does not explain the situation. Staff may lack practice, the new system may omit a necessary function, or the organisation may still require reports that depend on the old spreadsheet.
Neural plasticity provides a biological basis for continued learning. It does not turn an organisation into a brain or establish a complete theory of change management. To support adaptation, the useful questions concern what people need to learn, whether the process enables them to use it, and how the organisation will detect and correct failures under actual working conditions.
Keep the Biological Evidence at the Right Level
Adult brains can change with experience, but evidence about a particular learning task does not specify how long a business transformation should take. A training study measures defined participants, activities, and outcomes. A restructuring also changes authority, workload, relationships, tools, and incentives.
The adult-plasticity article examines evidence for learning beyond childhood and the limitations of fixed age cutoffs. That evidence gives no basis for assuming that older employees are necessarily the people who will struggle with a new process. Experience may help with understanding the work while creating expectations the new tool does not meet.
Avoid explaining adoption directly through dopamine, myelin, or neurogenesis without relevant evidence. An employee returning to a spreadsheet does not reveal the condition of a particular circuit. Their explanation and the sequence of work may provide more useful information: the new application cannot generate the report their manager still requests.
This does not make neuroscience irrelevant. It sets a limit on the inference. A biological account of learning and an operational account of an organisation answer different questions, and a good change programme needs evidence at the level where decisions are being made.
Define the New Practice Through a Complete Case
For the case-management system, specify what successful work looks like from receipt to closure. Identify who records the case, where it is assigned, what information is required, how exceptions are handled, and which record determines status.
Compare that sequence with the old one. Some steps may be unchanged, some may move between roles, and others may be new. Staff need to understand those differences, especially where an action that once worked now produces the wrong result.
A useful training case includes the judgement the person must exercise. Entering a straightforward example can teach navigation while leaving the difficult decision untouched. Include missing information, a reassignment, or a case that cannot be closed through the usual route.
Check whether the procedure is coherent before asking people to practise it. If two teams have incompatible instructions, more repetition can reinforce the conflict. If a required approval has no authorised owner, the barrier is a missing organisational decision.
Give affected staff a role in examining the sequence. They may identify exceptions absent from the project design or explain why an apparently redundant spreadsheet remains necessary. Their feedback should be tested against the intended outcome, rather than treated automatically as resistance or accepted without investigation.
Build Practice Beyond the Initial Demonstration
Watching an instructor complete a case is different from doing it independently. Both can contribute to learning, but they provide different evidence. A completion certificate establishes attendance or performance on the assessed task, not reliable use across the full range of work.
Include opportunities to attempt representative cases, receive usable feedback, and return to the procedure later. Roediger and Karpicke’s retrieval-practice experiments found benefits for delayed retention of studied material. Those experiments do not establish the outcome of a software rollout, but they support examining retention beyond immediate familiarity.
Spacing is another design consideration. Cepeda and colleagues investigated how study intervals affected later retention. Their findings do not supply a universal retraining schedule for employees. They provide a reason to plan opportunities for return and review instead of concentrating every learning activity into one launch session.
For the case-management team, an initial session could establish the basic route, followed by supported use on live work and later practice with important exceptions. The appropriate sequence should reflect case frequency, risk, staffing, and evidence of competence.
Job aids can remain available. A person does not need to memorise every infrequent procedure to perform it reliably. A clear, maintained guide may be the correct control for a rare exception, particularly where recall errors would have substantial consequences.
Make the Working Environment Support What Was Taught
Learning a new procedure does not ensure that the workplace makes it practical. A staff member may understand the new system but lack the necessary access, face a backlog that leaves no time for checking, or receive conflicting requests from different managers.
Allocate learning and support effort explicitly. If people must maintain the existing service while becoming familiar with a new tool, identify the additional capacity, reduced scope, or revised expectations required. Avoid silently assuming that training has no effect on available working time.
Protect appropriate opportunities to practise and investigate errors. The concentration article considers how task clarity, interruptions, and communication agreements affect this work. A team may need a support rota or a scheduled period for resolving difficult cases rather than an instruction to focus harder.
Recovery also matters. Controlled research on chronic sleep restriction found accumulating performance deficits. That supports taking workload and rest seriously, without claiming that one poor night erases all new learning or prevents every kind of adaptation.
The organisation can review its schedules and staffing without attempting to monitor employees’ biology. The relevant operational question is whether the plan repeatedly depends on overtime, unmanaged pressure, or unsupported workarounds. Those are conditions that managers can investigate and change.
Align Authority, Incentives, and Tools
If managers continue to request the old spreadsheet, employees have a reason to maintain it. Announcing that the new system is authoritative will not resolve the conflict unless reporting, approvals, and downstream dependencies change with it.
List the decisions and artefacts that depend on the old process. For each one, identify the replacement, owner, transition arrangement, and condition for retirement. Some parallel running may be necessary while results are reconciled. Indefinite duplication should have a visible justification and cost.
Measures need the same examination. A target based only on case throughput may discourage careful use during an early learning period. A measure of new-system logins can show activity without establishing that records are accurate or cases are being resolved correctly.
Make it safe and useful to report defects. Staff need to know where to raise a missing function, conflicting instruction, or potentially harmful error. The response should distinguish a knowledge gap from a design problem and route it to someone able to correct it.
This is where organisational adaptability becomes concrete. A team can notice a mismatch, establish what is happening, and change a rule, tool, or allocation. No claim about rewiring the collective brain is needed to explain that capability.
Test Transfer and Investigate Reversion
Assess performance where the procedure is actually used, after an appropriate delay and across representative cases. Check whether staff can complete the task with the intended support, recognise exceptions, and obtain help when needed.
Transfer is a question to test. A classroom demonstration and a busy service queue differ in interruptions, case variety, available information, and consequences. Practice in one setting may help without preparing the person for every demand of another. Simulation can still be useful when it reproduces important decisions and is followed by supported application.
When someone returns to an old method, reconstruct the case. What triggered the switch? Did they forget a step, distrust a result, lack access, face an unresolved exception, or follow a manager’s instruction? These explanations call for different responses.
An additional lesson may help a knowledge gap. It will not repair a missing integration or contradictory authority. Conversely, fixing a tool will not necessarily address a misunderstanding that persists after the defect is removed. Keep the diagnosis specific.
Evaluate Adoption Through Reliable Work
For the case-management change, track record accuracy, duplicate entry, unresolved exceptions, successful handoffs, service delays, and the effort required to obtain support. Use training and usage measures as context rather than treating them as the whole outcome.
Review difficult cases with the people doing the work. A pattern of workarounds can reveal a common problem worth addressing centrally. A small number of unusual cases may instead need a clear exception route. Avoid forcing all variation into either noncompliance or system failure.
The transition should have a decision process for expanding, slowing, or narrowing the rollout. Establish what evidence supports each choice and who can make it. Staff should not have to infer whether a known problem is acceptable because the project continues unchanged.
People can learn new procedures while retaining extensive knowledge of the old ones. The organisation’s responsibility is to provide a workable process, meaningful practice, usable feedback, and the resources to apply what is learned. Success becomes visible when cases move reliably through the new arrangement and the remaining difficulties produce specific corrections rather than speculative explanations about employees’ brains.
