How to Build Employee Trust During Workplace Change

Workplace changes are communicated by me by providing information about the change and its reason as well as its expected impact on the work of employees. One option for communication that was helpful consisted in communicating the practical implication of the change and not just the reasons of the company, what will be the same, what will be different, and to whom employees can turn if they have any questions. The change seemed more predictable and easier to understand as people got a clear picture of their obligations.

In uncertainty, the human mind fills unknowns with fear. When people hear about a change, the first thing most of them wonder is what Monday morning will look like for them.

So I start with where we are right now and where we need to go, and I connect the change to our mission, vision, and values. If there are numbers behind the decision, I share them. Then I paint a picture of what things look like if we make the change, and what happens if we don't.

I say out loud that the change will be uncomfortable and implementation won't be perfect. I'm honest about what we still don't know, and I tell people when and how they'll hear from us next. Then I repeat the message on a steady cadence and through different channels, because most people need to see and hear it several times before it sinks in.

Feedback starts before the announcement, ideally while a major change is still being designed. Whenever possible, I want input from a variety of levels and viewpoints. I also make sure we have a way to gather unfiltered feedback from the employees most directly affected, so their concerns don't get softened on the way up through layers of management. They usually spot problems I can't see from my office, and when they've helped shape the change, they're more invested in making it work. Once we implement, we keep listening. That feedback shows us the hot spots and the wins, and it tells us where we can move faster or need to slow down.

The choice that has helped most is one very few leaders make. I tell my team what, based on everything I know, is not going to change. A few years ago I restructured our leadership team so fewer leaders reported directly to me. I met with each person one-on-one, then with the full team, and walked through why we were doing it and what would and wouldn't change. Our weekly leadership meeting stayed put. Having that steady ground let people map the new structure around things they already trusted, and the team has performed better and grown closer since.

After all of that, I give people time. It's natural to go into defensive mode or fear mode when something shifts. Their questions tell me what's really on their minds so I can address it directly.

I've used this approach to lead a lot of system-wide changes. In Before It Breaks, I write about Clarity and Consistency as two of the seven pillars of trust, and a major change tests both.

When we changed the scheduling algorithms, I ran live Q&A sessions where people could share real examples, like losing a preferred shift, and ask how they'd actually be affected. It made the changes feel concrete instead of abstract. In my experience, talking through specific scenarios beats sending a memo every time people are uncertain about workplace changes.

The communication choice that helped most at Pigment was telling people why before telling them what.

We had a workflow change last year that affected how the team tracked their work. My instinct was to announce the new process, explain the benefits, and move on. What I did instead was spend the first five minutes of the conversation on the problem we were solving. Not "here is the new system" but "here is what is not working and here is what you told us about it."

That sequence matters more than most leaders realize. When you start with the solution, people hear the disruption. When you start with the problem, people hear that you listened. Half the anxiety around workplace changes comes from employees wondering whether the decision was made in a vacuum without considering how their day actually works.

The other thing I learned is that the most useful communication is not the announcement. It is the follow-up two weeks later where you ask "what is not working about this change?" and then actually adjust. Most companies roll out a change, send the email, do one Q&A, and consider the communication done. The real engagement happens when people see that the change is a conversation, not a decree. They can handle disruption when they trust that their experience of it will be heard.

Leading with the underlying business logic is the only way to close the information gaps where employee anxiety thrives during a transition. When scaling global delivery teams, I've found that vague corporate announcements are the primary drivers of disengagement; people don't fear change so much as they fear the unknown impact on their individual productivity and security. To counter this, transparency needs to be granular. During a major operational restructuring, I moved away from generic Q&As and instead implemented role-specific impact sessions. We presented a side-by-side comparison of the current state versus the future state for each department, detailing exactly how workflows-like reporting lines or software delivery benchmarks-would shift. By mapping these daily impacts before speculation could take hold, we proved the decision was rooted in a deep understanding of their day-to-day reality. Treating employees as informed stakeholders rather than passive recipients prevents the productivity dip that usually occurs when a workforce spends its energy navigating rumors. Sustainable growth requires a team that trusts leadership values operational clarity as much as financial results.

The communication choice that worked was telling people what we knew and what we didn't know at the same time. Most leaders wait until they have the full picture before saying anything. By then the rumor has already filled the gap.

We had a structural change that affected a few roles. Before we had all the answers we told the team what was happening, why, and what was still being worked out. It felt uncomfortable to say "we don't know yet" but it was better than letting people wonder if we were hiding something. Engagement stayed intact. The people who left were the ones who had already been looking.

When we rolled out a new workflow at BuyBoxr, I asked the team what they couldn't lose in their daily routines first. We protected those pieces during the redesign. People resist change when they think it'll break what's already working for them. Ask what matters before you finalize anything. Most leaders skip that step and then wonder why everyone's pushing back.

When employees are concerned about daily impact, I start with a role-specific impact map rather than relying only on a general announcement, specifying what work changes, effective dates, tools, handoffs, where employees can raise role-specific concerns, and what remains unchanged. Managers should receive the same core facts and enough preparation to explain them consistently. Then give employees a defined way to respond, such as a brief feedback form organized by workflow, schedule, training and workload. That feedback should focus on process-level issues; individual employment matters should remain with the appropriate manager or HR contact. Review the input for recurring operational issues and address them in the next communication. This keeps the conversation focused on concrete work while giving employees a meaningful role in identifying implementation details that may need refinement. Repeat essential information across more than one channel so employees can absorb it and refer back to it.

One communication choice I've used is a before-and-after workflow demonstration built around fictional, non-patient scenarios. Instead of describing a new process in abstract terms, walk employees through a routine task from start to finish and show exactly where the new step occurs, who owns it and what the handoff looks like. Pause at each transition for questions, then revise the written workflow when a question exposes ambiguity. Patient information, PHI, or confidential employee details should not be used in the demonstration. The demonstration helps employees connect the decision to their actual work, while the revision shows that their participation has a practical purpose.

Employees rarely resist a change itself. They resist uncertainty about what it means for their own day. Announcements that explain strategy and skip the daily impact leave that question open, and rumor fills the space.

Start every change message with what will be different for the people hearing it. State what changes, what stays the same, and when each step happens. Say plainly what is still undecided and when an answer will come. Honesty about open questions builds more trust than a polished message with gaps.

The communication choice that matters most is letting direct managers carry the message. Brief them first, give them room to ask hard questions, and equip them to translate the change for their teams. Employees believe the person they work with every day. Follow up after launch, because the second conversation is where real concerns surface.

I start with what changes in someone's actual week, and only then explain why, because that's the question everyone is silently asking. In a small, family-owned company, the communication choice that matters most is telling people directly, in conversation, before anything goes out in writing, so nobody learns about a decision from an email or from a customer. I also leave room for questions right then, because the concerns people raise in the first ten minutes are the ones that would otherwise turn into rumors. People stay engaged when they feel told, not just informed.

When SemNexus restructured, I sent short weekly surveys asking what worried people and what they'd change. The trick was posting results where everyone could see them, then actually fixing things. When someone flagged confusing reporting lines, I sorted it out that week. People kept responding because their input turned into real changes instead of vanishing into a spreadsheet.

When I roll out new policies at my academy, I give instructors a Shift Checklist that spells out what to do before, during, and after each class. Staff always know the next step, even when things change. It works way better than just announcing updates because people can see exactly how their day-to-day shifts change instead of guessing.

Rolling out changes across franchises taught me something: test with small teams first. We let a few store managers try a new feature for a month, then had them tell the rest of the company what happened. Not a polished pitch, just their real experience. That did more than any memo. People saw someone like them making it work, and suddenly the change didn't feel so scary.

I ran the new diagnostic workflow live with technicians, answering questions on the spot. Seeing it happen on screen beat any slide deck. When people can't picture a change, they get nervous. But watching it step by step on actual equipment, they calm down and start asking smarter questions instead of just worrying. Show, don't tell.

Honestly, things worked best when I brought my team into the strategy, not just the outcome. When we shifted ad spend toward influencers, I walked them through why, then asked them to brainstorm client FAQs with me. People got curious instead of nervous. They owned it. Don't just hand down decisions. Show people where they fit.

When we upgraded our ecommerce platform at Luxury Flooring, we ran short role-specific webinars. Warehouse, customer service, and marketing each got their own session covering only what would change for them that week. People got less confused since they weren't wading through the whole project. A quick written recap after each session helped too. That combo kept everyone moving during the switch.

When we change processes at Searchical, communication matters most since we're remote. I ran a workshop showing our new keyword-gap method on live accounts, not slides. People asked questions, pushed back, and I followed up with an FAQ tackling the actual concerns they raised. That's how you get buy-in. Not by announcing changes, but by letting people see them work and voice their doubts.

When we shipped the big update at ShipTheDeal, I didn't lead with feature specs. I talked about how customers would checkout faster. Then I got Maria from support and Dev from engineering to explain what their days would look like after the change. People got it. They weren't just hearing orders from above. Skip the feature list. Talk about what actually changes for real people, and let your team tell the story themselves.

When we changed our process, I walked each crew through the new steps at our rehab sites instead of just emailing them. Then I'd ask which parts actually helped. Someone would usually point out it cut rework or made the site safer. Seeing it firsthand made the change stick better than any memo could.

When we rolled out our Knowledge Graph at SIGNLD, I asked a few frontline people to talk casually with their teams about what using it was really like. Just conversations, not presentations. People asked questions they'd never raise in a formal meeting. It worked because they heard from peers who'd been through it, not just leadership saying "do this." Let people see how change hits their actual work, not just the new steps.

On Acquire.com, I began making short Loom videos that described new workflows rather than trying to convey them via email or slide decks. I would open a real startup listing and mark what human judgment was still needed and why, giving the audience a clear idea of what had changed and what didn't. As a result, automating became less scary.

When you make a change, show people the real thing.

When employees are concerned about how a change will affect their daily work, I separate what has already been decided from what employees can still influence. This tells people where their input can directly shape implementation. I explain the reason for the decision, the practical effect on routines, and the timing, then ask employees to identify likely friction points in their own work. I also specify when leadership will review that feedback and how any adjustments will be communicated. If a concern cannot change the core decision, I say that plainly and address what flexibility remains. Candid communication does not mean having every detail finalized at the first discussion. It means being clear about what is known, what is still being worked through, and when employees can expect an answer.

One communication choice that helped was closing the feedback loop: after employee surveys and focus groups, we shared what we heard, what we were changing, and what would remain the same. Employee requests led us to shorten meeting times and add optional guided meditation sessions. The important part was showing what action followed. Gathering feedback without explaining what it changed can make participation feel disconnected from the outcome. When employees can see which suggestions were adopted and why other decisions stayed in place, they have a clearer view of their influence and a reason to stay engaged in future conversations.

Nobody reads the announcement. What you actually read is the first reply under it from someone you trust.

Our sales team spends the day matching founders with investors. Last year I moved them off their spreadsheets and onto a CRM, which meant changing the one screen they live in. I did not write a long note about why. I posted a 2-minute screen recording of my own pipeline in the new system, mistakes included, in the Discord channel where they already talk. The questions came in under the video where everyone could see the answers. A few reps still kept a spreadsheet on the side for a month. Next time I would ask 2 of them to record the video instead of me.

Before we roll out any change, we lead with the problem, not the announcement. What broke, what it's costing us, why the old way stopped working. People don't actually resist change, they resist not knowing the reason for it, and once they see the problem clearly, most of them are already halfway to accepting the fix before we've even proposed one.

We also name the hard parts out loud instead of glossing over them. When we changed our returns process, I told the team directly that the first month would be messy, that customers would get confused, and that we'd have to adjust things on the fly.

Nobody loves hearing that upfront, but they respect it. When the mess actually showed up, nobody panicked, because it had already been called. The change wasn't a surprise, and neither were the bumps along the way.

Then we put the new process on one page and walk every person through it individually, not in a group meeting, but one-on-one at their station. It's slower that way and it also works better, because people ask the real questions when their manager isn't standing in front of a room watching them.

The biggest change I made at my telecom company was moving from contractors paid by the job to employees on a legal minimum base wage plus uncapped performance pay, and what made people understand it was a pay rule they could check for themselves. Many of our early contractors only cared about the money, not the quality, and poor cable jointing shows up later as a fault and a crew sent back to redo the job. A pay change worries people because it touches their income directly, so explaining the reasons was never going to be enough.

The communication choice that worked was letting the system do the explaining. Every job was captured in the field in our own software and reviewed by our office admin before it counted, so any technician could see how a week of good work turned into pay, and some of our people earned around $200,000 a year under it. I also held to a rule I still use: never ask employees to do anything you would not do yourself. My advice is to show people how a change will be measured in their own daily work, because that answers the worry a memo cannot.