Are employees adopting the change or just performing agreement?

Check what employees do in normal work when leaders are absent. Compare actual choices with the purpose of the change, then investigate constraints before interpreting non-use as defiance.

Change adoption is the sustained use of a new practice in actual work rather than a temporary display of agreement with its sponsor. This article uses the term as an applied working label. Its research reference is Weiner’s 2009 theory of organizational readiness, especially shared commitment to a specific change and belief in the ability to implement it. The proposed method below is advisory guidance rather than a tested psychological scale.

Recognize the decision behind the pressure

Composite recognition scene: At home you see an enthusiastic update about a new process. A customer issue forwarded privately shows that the team returned to the old method as soon as the launch meeting ended. This is an invented illustration of a leadership pattern, not a client story or evidence about a particular person. Use the scene to identify the work choice that needs attention, without drawing conclusions about anyone’s psychological condition.

Look at the work behavior required by the change and the conditions needed to perform it. Attendance at training or a verbal endorsement may establish that someone received an instruction. It does not show that the new process can be used reliably. Ask for a concrete example of the work before judging either commitment or resistance from appearances alone.

Compliance follows an instruction under the conditions observed. Adoption means the practice becomes usable in the work; public agreement alone establishes neither. Ask someone to work through the changed task with the resources currently available. If the process fails at a handoff, investigate that handoff. A signed training record may confirm attendance, but the work example reveals what must be clarified or supplied before routine use is possible.

What the research supports

Weiner’s organizational-readiness theory treats commitment to a change and confidence in the ability to carry it out as distinct elements. That distinction helps when preparing a message. Employees may understand why management wants a change while still needing answers about workload, authority, or resources. Repeating the rationale does not itself resolve those questions.

Edmondson’s 1999 team psychological-safety construct concerns shared expectations about interpersonal risk. For an ordinary-work adoption check, ask whether employees can disclose that they still use a workaround. Explain how the account will be used and handle performance concerns through the appropriate process. A demonstration given under executive observation may omit precisely the problem the check needs to uncover. Invite a concrete account without promising immunity from every consequence.

Colquitt’s 2001 work distinguishes outcomes, decision procedures, interpersonal treatment, and explanations as dimensions of organizational justice. During an adoption check, ask whether employees received consistent instructions and a fair route to report exceptions. A completed training session does not answer a concern that one team must follow a rule another team can bypass. Investigate that procedure before treating non-use as a communication failure.

This adoption check uses industrial/organizational psychology to examine the work behind an apparent change in behavior. The cited studies do not validate the proposed check as a measure of adoption. Compare a routine task with the intended practice and record the conditions under which it succeeds or fails. Revise the workflow or its support when warranted, rather than counting agreement with the sponsor as evidence of ordinary use.

The ordinary-work adoption check

Choose one changed workflow for the five-step review. Define the task, expected result, available support, and evidence that would show routine use. Separate a capability gap from a choice to disregard an authorized instruction. Tell employees how observations will be used, and avoid creating an undisclosed attitude test from a practical check of their work process.

1. Define the intended practice

State the work behavior and benefit the change is meant to produce.

Describe the specific practice the change is intended to introduce. Name the work situation, the required action, and the intended use of its output. Avoid defining adoption as support for the executive sponsor. Ask what an employee should do differently during an ordinary customer request, exception, or handoff before deciding how implementation will be reviewed.

2. Choose normal work examples

Inspect permitted records and handoffs without covert monitoring or surprise personal scoring.

Choose permitted work examples with the responsible team and explain the review purpose. Include ordinary demands rather than only a prepared demonstration. Do not create covert observation or surprise individual scoring. Ask employees to walk through the practice and show where it fits, where it conflicts with another instruction, and what happens when an exception occurs.

3. Compare use with stated agreement

Identify where the practice appears only during formal reviews.

Compare the work examples with the process presented at launch. Identify which elements are used routinely and which appear only when management requests a status report. Keep the observation separate from an explanation of intent. A return to an older method may reflect missing capability, an unresolved dependency, disagreement, or another issue that needs a direct conversation.

4. Ask about constraints

Examine missing resources, conflicting incentives, or a poor fit with actual tasks.

Ask what prevents the intended practice from working in the selected task. Review access, time, tools, training, and conflicting rewards with the relevant owners. Separate a request for help from a challenge to the mandate. Do not repeat the rationale for the change as the sole response to an employee who has identified a specific implementation obstacle.

5. Repair and review

Adapt the implementation and inspect another ordinary work example before declaring adoption.

Approve a targeted repair and inspect another normal example afterward. If the practice does not fit the work, bring that finding to the change owner instead of quietly requiring an unusable sequence. Define which parts remain mandatory and which can be revised. Keep implementation learning separate from decisions about an individual’s performance or conduct.

Language to use during ordinary-work adoption check

Use the proposed wording with people performing the changed task and managers able to address its constraints. Replace placeholders with the actual workflow and support available. Obtain specialist review for consequential changes to work obligations. State what evidence you are seeking and invite correction when the planned process differs from how the task must be performed.

The intended practice is [specific action] during [work situation]. In this example, [observed use] occurred. Please walk us through the reason and any instruction or resource conflict. We will take [repair] to [owner] and review another example after it is resolved. This conversation should not assume a motive from one instance of non-use.

Use this instruction to clarify the next action: compare use with stated agreement. Say what that means in the actual situation rather than reciting the method’s name. Invite correction of facts, and distinguish a request for correction from a demand for agreement.

When a manager reports full adoption, ask for a routine work example and the criteria used. Avoid a debate about enthusiasm. If the example shows a missing step, ask why it was missing and what happened to the task. Correct the implementation claim without concluding that everyone has rejected the change or that all prior training was ineffective.

Work through a hypothetical ordinary-work adoption check

In the hypothetical continuation, a new approval process is demonstrated successfully at the launch meeting. The next unusual customer request follows the old route because the new approver cannot access the relevant record. Record the access gap and identify a temporary authorized route. The observation concerns implementation conditions, not evidence of disloyalty to the sponsor.

Suppose access is repaired but a team still omits the new step. Ask them to demonstrate the task again and explain their choice. There may now be a different issue, including an instruction from another manager. Do not assume the first repair has resolved every reason the practice was absent, or interpret a second question as deliberate obstruction.

Later, the practice works under normal demand but breaks during an urgent exception. Review that exception with the change owner. Clarify the approved contingency and rehearse it with affected teams. Adoption should not mean concealing cases where the new arrangement needs adaptation in order to preserve a favorable implementation report.

The record for ordinary-work adoption check

Keep the task definition, observed use, work obstacle, agreed response, and review condition in the record. Distinguish a reported barrier from a verified finding. Avoid labeling people as change supporters or opponents. Update the process guidance when a legitimate obstacle is resolved so employees receive the corrected instruction instead of being assessed against an obsolete version of the workflow.

Record the intended practice, selected work example, observed use, employee explanation, and authorized repair. Avoid converting a local review into an undisclosed ranking of commitment. Keep changes to the practice visible so future reviews use the current requirement. Explain what information is being inspected and handle individual concerns through their appropriate processes.

Use this completion check before closing the discussion:

What practice should appear in ordinary work?
Which permitted example shows its use or absence?
What explanation does the team give?
Does a capability or instruction conflict need repair?
Has the repaired practice been checked in another relevant example?

This review examines whether a practice is usable and used. It does not infer employees’ private motives or validate a universal numerical adoption score.

Review ordinary-work adoption check in practice

At the next decision milestone or promised update, examine this specific signal: whether the new practice remains useful in ordinary work without continual sponsor intervention. Compare the result with the original working note and inspect at least one completed action. Avoid reporting improved confidence or a calmer meeting as proof that the operating problem is resolved.

Review a later task under normal operating conditions and an authorized exception where appropriate. Check whether the repaired dependency stayed available and whether managers apply the same instruction. Report remaining limitations alongside progress. Avoid treating a positive launch survey or an executive presentation as the final evidence of sustained use.

Do not use covert surveillance to test adoption. Have privacy and employment advisers review any monitoring or employee-data collection.

For related preparation, use How to explain company change so people know what to do, How to choose change champions employees already trust, Should you announce company change live, by email, or both?, How to make a culture change show up in everyday decisions. Choose the guide that addresses the next concrete decision, and keep responsibility with the person authorized to make it.