# Embracing Change at Work When You Didn't Choose It Canonical URL: https://headwayskills.com/knowledge/professional-behaviors/embracing-change/ Markdown URL: https://headwayskills.com/knowledge/professional-behaviors/embracing-change.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving professional behaviors at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Embracing change at work isn't about feeling positive about it. Eight practical steps for handling a reorg, a new system, or a change you never got a vote on. ## Key facts - Title: Embracing Change at Work When You Didn't Choose It - Category: Professional Behaviors - Primary skill: Professional Behaviors - Related skills: Building Resilience, Building Confidence - Primary keyword: embracing change - Source page: https://headwayskills.com/knowledge/professional-behaviors/embracing-change/ ## What this page covers - Embracing change at work isn't about feeling positive about it. Eight practical steps for handling a reorg, a new system, or a change you never got a vote on. - Practical guidance for embracing change - How this topic connects to Professional Behaviors ## Detailed explanation Something at work has changed and you didn't get a vote on it — a reorganization, a new system, [a manager you didn't choose](/knowledge/working-with-your-manager/how-to-work-with-a-new-manager/), or a job that quietly turned into a different job. Embracing change at work is not about feeling positive about it. It is a sequence: find out what is actually changing, let yourself react, ask why the decision was made, separate what you control from what you don't, and then change how you work — deliberately, and in that order. The reason it feels harder than that sounds has less to do with your attitude than you probably assume. ## Why embracing change is harder than it looks According to Prosci, which studies organizational change, the most commonly cited reason employees resist is not stubbornness but a lack of awareness of why the change is happening — the organization failed to explain the business reasoning behind it. What feels like a character flaw is often an information gap, and information gaps have an obvious fix. The second finding is less comfortable and more validating. In Prosci's research, 41% of employees name mistrust in their organization as the primary driver of their resistance, usually tied to worries about job security. That number matters because it means a large share of resistance is not irrational. Sometimes people resist change because they have watched previous changes go badly. Any honest treatment of this topic has to allow that your objection might be correct. Then there is the immediate reaction, the one that arrives before you have thought about anything. Prosci attributes it to the brain's error-detection circuitry — the anterior cingulate cortex, which registers departures from the status quo — and notes that when that circuit fires, what it produces is anxiety and fear. The first feeling is not a judgment about the change; it is a detection signal, and it fires for everyone. Finally, being told why is not the same as having had a say: Prosci and the Employers Council both identify exclusion from the decision as its own driver of resistance, with people who weren't consulted reporting they feel unheard, threatened, or blindsided. If you are angrier than the change seems to warrant, you may be reacting to the process rather than the outcome. ## How to embrace change at work, step by step BDO describes the employee experience of change as a transition rather than an event: a sense of loss first, then a stretch of confusion, then acceptance and engagement. Endings, a middle, and new beginnings. It is the same basic shape as Kurt Lewin's much older unfreeze-change-refreeze model, and it explains why "just get on board" doesn't work. There is a middle you have to go through. The steps below follow that shape from the inside. ### 1. Find out what is actually changing Establish the facts first: what has actually been decided, what is still being worked out, and what is someone's guess being repeated in the kitchen. Announcements are usually vaguer than the version circulating an hour later, and most people spend the first days reacting to a composite of the two. Write down what you know for certain. Everything that follows depends on it, because you cannot usefully react to a change you have half-invented. ### 2. Let the first reaction be a reaction You are allowed to not like it. This is the endings part of the transition, and something is genuinely ending — a routine that worked, a team you liked, a piece of the job you were good at. Naming what you are losing is not self-indulgence; it is what stops the loss from leaking out sideways two weeks later in a meeting. Do it privately, or with someone outside the situation. The goal is to have the reaction somewhere it costs you nothing. ### 3. Ask why the decision was made Given that missing reasoning is the single most cited driver of resistance, this is the highest-value move available to you. Go to your manager and ask what problem the change is meant to solve, what the alternatives were, and what it means specifically for your work. Ask it as a question, not as a challenge. You may get an answer that changes your view, or one that confirms your concerns and tells you something real about the organization. Both beat not knowing. ### 4. Split the change into what you control and what you don't Most of an organizational change sits permanently outside your control. The decision, the timeline, the budget, other people's reactions — none of that moves because you disagree with it, and spending energy there is what turns change into exhaustion. So draw the line explicitly. On one side, the parts that are decided. On the other, what you choose to learn, what you say and to whom, and what you ask for while things are still fluid. That second list is usually longer than it feels on day one, and written down, the dread tends to shrink into a handful of ordinary decisions. ### 5. Test the story you are telling yourself Somewhere between the announcement and the reality, you built an account of what this means. They've already decided everything. This will make my job worse. They're managing me out. Some of it is likely accurate; some is your error-detection circuit [filling gaps with worst cases](/knowledge/resilience/automatic-negative-thoughts/). Take the conclusions you are most convinced by and ask what evidence you actually have for each — and what you would tell a colleague who described the same situation. For the fear that survives that, do the useful version of worrying: picture the worst realistic outcome, work out what you would do if it happened, and note what you can do this week. A fear you have a plan for stops running in the background. ### 6. Decide how you will talk about the change in front of other people This step has the longest reputational tail. There is a real difference between disagreeing and complaining. Disagreeing means saying, once and clearly, in the room where it might matter, what your concern is and why. Complaining means saying it repeatedly, in corridors and group chats, to people who cannot act on it. The first is a contribution; the second reads as negativity, and it sticks to you long after the change has stopped being controversial. So decide in advance [where your objection gets raised](/knowledge/professional-behaviors/how-to-speak-up/) and where it does not — then follow the new way of working while you still disagree with it. That combination is normal professional conduct, not capitulation. The awkward part is that you cannot see how this reads from inside your own head, least of all in a stressed week; if that blind spot is worth closing, [how you come across](https://assessment.headwayskills.com/) is something you can get a straight read on. ### 7. Do one thing the new way Waiting until you feel ready is the most common way people stall here. Belief that you can work the new way is not something you think your way into; it arrives after you have done it once. Pick [the smallest real action](/knowledge/confidence/confidence-competence-loop/) inside the new arrangement — one task in the new system, one conversation with the new team — and do that. Then a second one. The confused middle shortens through repetition, not resolution. Expect to be slower and worse for a while; that is what learning looks like from the inside. ### 8. Set a review date and be honest at it Pick a date one to three months out and put it in your calendar now, while you still remember what you objected to. On that date, ask plainly: does the objection still stand, or has it faded now the thing is familiar? Both answers are useful. If the discomfort has gone, you have learned something about your own reactions that makes the next change easier. If the concern survives real exposure, it was probably legitimate rather than a threat response — and you can now raise it with evidence, which is a far stronger position than day one. In the meantime, BDO notes that people do not move through these phases at the same speed. Colleagues reaching acceptance while you are still in the confusion is a difference in pace, not a verdict on you. ## The skills that make change easier to sit with Read back over those eight steps and notice what they consist of. Almost none of it is about change specifically. It is asking a manager a direct question, choosing where to voice disagreement, checking your own conclusions, taking a first uncomfortable action. Those are ordinary work skills, and they are why some people move through a reorganization without much damage while others spend six months miserable in the same one. **Professional Behaviors** covers the conduct half of this, and it names being open to change as one of its basic behaviors — alongside showing respect, showing humility, and expressing appreciation. Just as directly, it names the opposite as a behavior to avoid: excessive complaining and criticism. That is the practical content of step 6. Embracing change, in this sense, is not a feeling you have to produce; it is what you do with the new policy and the new system while your opinion catches up. **Building Resilience** is what steps 4, 5 and 8 draw on. It works through what you can actually control, through catching the automatic thoughts a change sets off and checking them for the usual errors — mind reading other people's motives, all-or-nothing readings of your future — and through using people you trust rather than carrying it alone. Not toughness. Accuracy, mostly, about a situation that invites you to be inaccurate. **Building Confidence** is what step 7 runs on. It is built by doing rather than by deciding to feel differently, which is why the first small action in the new arrangement matters more than any amount of preparation. Part of it is accepting the discomfort instead of fighting it — being willing to be visibly not-yet-good at something in front of people who watched you be competent at the old thing. None of that is temperament, and none of it is fixed. Being open to change is a behavior the framework counts among twelve that anyone can build with practice, and the free Work Skills Test reads across all twelve at once — so if this change has exposed a gap, you can find out [which skill to build first](https://assessment.headwayskills.com/) rather than guessing. ## What this looks like a year from now Some of the eight steps above probably describe things you already do. If you have ever gone quiet, worked out what was actually bothering you, and then raised it once in the right room, that is most of the sequence already. The gaps are the changeable part. Handling change well is not a temperament you were issued at birth; it is a set of behaviors, and the people who look unbothered by reorganizations almost always learned them somewhere. You can do that without becoming a different person — what counts is what you do in the first two weeks, not who you are. It also compounds, because the more responsibility you take on, the more changes arrive that you did not choose. And you have already done the part most people skip, by going looking for how to handle this while it is still happening. ## Find out where you stand You know the sequence. The one thing left is an honest read on the skills it runs on. The **free** Work Skills Test is a short self-assessment of all twelve work skills — including the professional conduct, the resilience and the confidence this particular change is testing. It shows you where you currently stand on each and which of them will make the biggest practical difference to you right now. **[Take the test](https://assessment.headwayskills.com/)** *Free, and it takes about 7 minutes.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Embracing change at work isn't about feeling positive about it. Eight practical steps for handling a reorg, a new system, or a change you never got a vote on. ### Which Headway skill does this connect to? This guide connects primarily to Professional Behaviors. It also relates to Building Resilience, Building Confidence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/resilience.md - https://headwayskills.com/knowledge/confidence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/professional-behaviors/embracing-change/ Preferred summary: "Embracing change at work isn't about feeling positive about it. Eight practical steps for handling a reorg, a new system, or a change you never got a vote on." ## Change log - 2026-07-07: Content collection version published.