Engaging with a change on its actual merits instead of on how it feels to be changed.
Most workplace change isn't chosen by the people it happens to — a new process, a reorganization, a tool everyone now has to use. Adapting well means separating three things that arrive together and feel like one: whether the change is a good idea, what it costs you personally, and how badly it was introduced. Those can have different answers. A sound change communicated terribly is still sound; a change that costs you real expertise you spent years building is a genuine loss even if it's right for the organization. People who handle change well aren't the ones who feel nothing about it. They're the ones who can name the loss and still evaluate the thing.
Compares every new system against the old one, as remembered, which is not quite the old one as it was. The previous tool was fast and simple and everyone knew it — the three-week onboarding, the quarterly outages and the spreadsheet that existed to work around it having faded from the record. Holds the replacement to a standard that the incumbent never actually met, and finds it wanting, correctly, against a system that did not exist.
Announces the change with genuine enthusiasm and expects it returned by Thursday. Treats any expression of loss as resistance to be managed — a communication problem, a mindset issue, something for the change champions to address. Has not considered that a person whose hard-won expertise just became irrelevant is not resisting anything; they are correctly noticing a cost, and being told it isn't one is what converts them into an actual opponent.
Adopts the new process fully and visibly, attends the training, and continues running the old one privately in parallel, because the old one works. Updates both. The organization believes migration is complete, the reporting is drawn from a system that only half-reflects reality, and the real state of things lives in a spreadsheet on one laptop belonging to someone who is shortly going on leave.
Has been through six of these and knows how it goes: wait, say little, and it will be reversed or forgotten within a year. Is right often enough for the strategy to feel validated, and declines to engage with the two changes in ten that were real and where early input would have shaped something. Has converted a reasonable empirical observation into a policy of never participating, and then observes, accurately, that nobody consults them.
A new tool replaces one you're expert in, and your expertise no longer counts for much. What would you do — argue the new tool is worse, or name the actual loss to yourself and separately assess whether the change is right?
You're rolling out a process change and the team is unenthusiastic. What would you do — work on the communication, or ask what it costs them specifically and find out whether they know something you don't?
Your team is quietly keeping the old spreadsheet alongside the new system. What would you do — insist they stop, or find out which things the new system genuinely can't do yet?