Organisations in transformation often lose the basics: people can go for long periods without understanding how the scope of their role has changed (or is about to change). That ambiguity is often what unsettles a team, sometimes more than the change itself. An effective strategy during major organisational change, especially in larger corporations, is to establish a temporary, explicit operating model for roles and decisions within the specific function or project while the new one is being built The temporary model will give people something solid to stand on, particularly in a project environment where sequencing, ownership and escalation paths need to be unambiguous for work to progress. They will know who can decide, who will own which outcomes and where to escalate. It doesn't need to be perfect, but it needs to be functional enough for the work to keep moving. It will (a) prevent paralysis (b) stop issues from circling endlessly and (c) ensure the organisation doesn't lose weeks simply because no one is sure who can act. I've worked with multiple corporations during organisational change and I prioritise this approach because it stabilises the work immediately, even when the long-term structure is still unclear.
Change doesn't just disrupt systems—it stirs uncertainty, identity shifts, and unspoken fears. In periods of organizational change, teams aren't just adapting to new workflows; they're questioning their place in the future. That's why the most effective strategy for leading through change isn't just communication—it's meaning-making. People don't resist change because they're stubborn. They resist it when it feels arbitrary, sudden, or misaligned with their values. As a leader, your job is to help them see the "why" before the "what." One of the most effective strategies I've used is story framing. Instead of rolling out change as a mandate, I frame it as a chapter in a shared story. Every team, like every individual, wants to feel part of something evolving—not collapsing. I ask questions like: What problem are we solving now that we couldn't before? What values are we protecting, not abandoning? What roles are emerging that people can grow into? Then, I invite the team to co-author the next phase—through feedback sessions, small pilot groups, and visible wins. During a major product pivot in our second year, we had to shift nearly 40% of our roles and realign around a new market. Rather than launching it with a cold announcement, we created a "Transition Canvas"—a simple visual that mapped out what we were leaving behind, what we were stepping into, and how each team's strengths still mattered. We hosted live retrospectives, not just future plans. The result? Morale didn't dip. In fact, engagement scores rose during the transition. People didn't feel blindsided. They felt invited. Research from McKinsey shows that transformations with strong employee ownership are 79% more likely to succeed. But ownership can't be demanded—it must be earned through trust, context, and consistent storytelling. When people understand the meaning behind the change and feel they have a role in shaping it, they shift from passive receivers to active participants. In times of change, clarity is compassion. Leaders who make people feel seen, needed, and part of the future aren't just reducing resistance—they're building resilience. Because when your team believes in the story you're telling, they don't just follow you through change. They lead it with you.
Running Titan Technologies since 2008, I've led my team through everything from major security overhauls to pandemic-era remote work transitions. The one strategy that's consistently worked? **Train people before the change hits, not during it.** When we shifted clients to remote work setups, companies that waited until the crisis struggled hard. We'd already been training employees on VPNs, secure cloud storage, and endpoint protection months earlier. That meant when everything went sideways, their teams knew exactly what to do--no panic, no productivity crash. Here's what shocked us: businesses with pre-trained staff had 90% fewer security incidents during the transition compared to those scrambling to learn on the fly. That's the difference between smooth sailing and drowning in support tickets. My practical advice--start quarterly "what if" training sessions now, before you need them. Pick your next likely change (cloud migration, new software, whatever) and get your team comfortable with it while stakes are low. When the real change comes, you're not managing fear and confusion--you're just flipping a switch on skills they already have.
I've led my team through two massive pivots--first from sustainable transport to inclusive mobility, then rebuilding after the 2022 floods destroyed our shop. The strategy that actually worked wasn't about vision statements or roadmaps. It was **bringing the team face-to-face with the people the change would help**. When we shifted focus to adaptive bikes, I didn't explain the business case in a meeting. I invited our staff to join me at a seniors expo on Bribie Island and watch a 74-year-old woman cry after riding a trike for the first time in 15 years. My workshop manager Richard saw her hands shaking as she rang the bell, heard her say "I thought I'd never ride again," and suddenly the extra customization work made sense to him. After the floods, we were scattered across temporary locations and morale was crushed. I brought everyone to test ride our new Lightning model--the bike Richard designed for riders with dwarfism--before we shipped it to our first US customer. Seeing something we built from scratch being ordered internationally reminded the team why we existed. Within two weeks, people stopped asking "will we survive this?" and started asking "what else can we create?" Put your team in the room with the impact. Not quarterly--weekly. Our 70% female customer base, the "wobbly riders" who haven't been on a bike in decades, the parents ditching their second car--these aren't metrics on a spreadsheet. When your mechanic hears someone say your work changed their life, they'll follow you through anything.
I've led Foxxr through major pivots--moving headquarters from Santa Cruz to Florida, weathering multiple Google algorithm updates that destroyed clients' rankings overnight, and transitioning from traditional SEO to AI-driven strategies. The strategy that's kept my team intact through all of it? **Make the change feel like an upgrade, not a threat.** When Google's local algorithm updates started prioritizing different ranking factors in 2019-2020, some of our clients lost 60% of their leads in weeks. Instead of just telling my team "we need to change our approach," I showed them the actual client data. I walked them through why our old tactics weren't working anymore and--critically--gave them paid time to learn the new strategies before we rolled them out to clients. Here's what made the difference: I didn't ask anyone to change until they saw the results themselves. We ran split tests on our own site first. When our team watched our AI-optimized content outperform traditional SEO pages by 3x in lead generation, they became the ones pushing for faster adoption. My project managers started suggesting improvements I hadn't even considered. The contractor clients who've stuck with us for 10+ years? They've watched us evolve our entire service model multiple times. They stayed because we never changed *at* them--we brought them into the process, showed them the data, and let the results do the convincing. When people understand they're gaining something better, resistance disappears.
One of the most underrated yet wildly effective strategies during organizational change is ritualizing uncertainty. Most leaders try to contain uncertainty—calm the waters, over-reassure. But I've found the opposite works better: carve out regular space where uncertainty is named, normalized, and even invited. We ran something called "Open Loops Wednesdays." Every week, we'd meet for 30 minutes. No decisions. No fixes. Just a place for people to say what felt unresolved, what was confusing, what felt weird about the changes. No pressure to wrap it up in a bow. And something strange happened: morale improved. People stopped catastrophizing in silence. Teams started expecting ambiguity, instead of fearing it. The rhythm created a shared muscle: "We don't need everything figured out to move forward." The best part? It changed how we processed progress. We celebrated clarity—but we also learned to respect confusion as a signal, not a failure. I think that's what real leadership is during change—not pretending you have all the answers, but building a team that can thrive even when you don't.
I've led Make Fencing through some massive shifts--from solo operator to managing a growing team, and from small resi jobs to landing major commercial contracts. The one strategy that's actually worked? **Get absurdly specific about what success looks like at each stage, then let your team own their piece of it.** When we started taking on commercial work alongside our residential projects, I didn't just say "we're going bigger now." I sat down with Austin, Kallum, and the crew and mapped out exactly what a successful commercial install looked like versus our usual jobs--different timelines, different communication standards, different site protocols. Then I asked each person what they needed to nail their part. Austin needed different materials ordered earlier. Kallum needed clearer daily targets. That clarity meant when we delivered that boundary install ahead of schedule, it wasn't me dragging everyone along--they knew exactly what winning looked like and went after it. The key is making the change feel less like chaos and more like a clear mission with defined checkpoints. I learned this the hard way on that early job that threw us curveballs--we didn't have systems, so everything felt reactive. Now when things shift, everyone knows their role and the standard we're holding. People handle change fine when they know what good looks like and have the tools to get there.
I've scaled Blair & Norris from a one-truck operation to a multi-million-dollar company over 30 years, so I've lived through plenty of change--adding new service lines, upgrading technology, and growing the team from just me to multiple crews across Indianapolis. The most effective strategy? **Put your money where your mouth is first.** When we invested in hydrofracturing equipment (success rate jumps to 60-90% vs. traditional methods), I didn't ask the team to learn it--I got trained first, worked alongside them on the first jobs, and showed them I wasn't dumping change on them from behind a desk. When leadership gets their hands dirty during the transition, resistance drops fast because it's clear you're not asking them to do anything you wouldn't do. I also made sure financial investment showed we were serious. We upgraded our safety gear and tools *before* rolling out new protocols, not after. When guys see new equipment show up in their truck before you announce the policy change, they know it's real and you're backing them. Our A+ BBB rating didn't come from lip service--it came from proving through action that changes were about doing better work, not cutting corners. The turning point was always when the team could connect the dots themselves. After we added 24/7 live phone support, our crews started getting same-day callbacks from grateful customers instead of complaints about missed calls. They saw their work turning into raving testimonials without me having to sell them on "why this matters." Let the results do the convincing.
When I founded Metro Models in 2010, the fashion industry was making a rapid shift towards digital platforms. My team was nervous about the new technology. I found that I got the biggest bang for my buck with radical transparency. You can't cover up the messy bits of change. I was very clear with my staff as to why we needed to change our booking systems and how this would affect their day-to-day work. I shared the financial risks should we fail to adapt. Many leaders attempt to shelter their teams from hard truths. They think they are helping. They aren't. Secrecy just leads to gossip and fear. When I put everything on the table, the panic stopped. My team knew the stakes. They ceased thinking about the unknown, and they thought about the work. If you treat your employees as adults, they typically step up to the challenge. We made that transition successfully because everyone knew the reality of the situation.
I've led teams through change from both the football field and the aesthetic business side, and here's what I've learned works: **ground the change in something your team already believes in**. When we opened ProMD Health Bel Air, our staff was coming from different backgrounds--some medical, some aesthetics--so instead of forcing a new culture, we anchored everything to "Putting Patients First" and "One Team." Those weren't slogans; they were decision-making filters everyone could use daily. The specific tactic that moved the needle? We created an **open-door accountability system** where team members could flag process issues *and* propose solutions in real time. At Perry Hall, if a play isn't working, we adjust at halftime--not three weeks later. Same principle at the practice: when our Patient Care Coordinators noticed scheduling friction during our launch phase, we didn't wait for quarterly review. We fixed it that week because the team knew their input directly shaped outcomes. What made it stick was tying every change back to **visible patient outcomes**. Our AI Simulator tool was new tech for the team, but once they saw patients light up previewing their results, adoption was instant. People don't resist change when they can *see* it working for the people they're serving. That's true whether you're game-planning for Friday night or rolling out a new treatment protocol.
I've been operating gyms in Florida for 40 years now, and the biggest lesson I've learned about leading through change is this: **let your customers drive the change, not your own assumptions.** When we implemented member feedback systems like Medallia across Fitness CF locations, I didn't tell my staff what needed to change--I showed them what members were actually saying in real-time data. Here's what happened: We were planning to add more cardio equipment because *I thought* that's what people wanted. But the feedback showed members actually wanted more variety in group class times and better childcare hours. We pivoted immediately, adjusted our class schedule, and extended childcare availability. Member retention jumped because the changes came directly from their voices, not management's gut feeling. My team bought in instantly because they could see the member comments themselves--it wasn't me interpreting data behind closed doors. When your staff watches real people say "I need 6 AM yoga" or "childcare closes too early for my schedule," they don't resist the extra early shifts or coverage changes. They solve for actual humans they recognize, not abstract directives from above. The principle I've built both gyms around is simple: the customer is the boss. When change comes from listening to them rather than top-down mandates, your team stops seeing change as disruption and starts seeing it as service. That shift in mindset is everything.
The single most effective strategy I use is to co-design the new system with the people who will run it, then lock in weekly, hands-on sessions for the first two months. That early, steady rhythm builds trust, sets clear expectations, and turns change into a set of simple habits. It also surfaces real blockers fast, instead of letting them pile up and stall momentum. I saw this play out with a Series A logistics client where we built a founder-led content system using AI and automation. At first, adoption lagged because executives didn't consistently show up to train the workflows and give feedback. We shifted to making those sessions mandatory during onboarding and kept them on the calendar for the first 60 days. That created shared ownership, led to sharper inputs, and the results took care of themselves. The lesson is to design the system together, then protect the time to practice it until it sticks. Do that, and the team feels supported, not steamrolled, which is what carries you through change.
I run a care workforce where staff work alone in client's homes, making decisions that affect safety, funding, and legal compliance. The most effective strategy during major change is standardising judgment, not tasks. Here's a specific way I applied this. When NDIS funding rules shifted, it primarily impacted what frontline staff were allowed to do without risking unpaid work or compliance breaches. Overnight, activities that used to be routine became non-claimable unless they met tighter definitions. So if a support worker did the wrong thing at the wrong moment, they would trigger a non-claimable visit, a compliance breach, or a missed clinical escalation. So we set explicit field rules. One example: if a worker sees a sudden change in mobility or cognition, they stop discretionary tasks, record it the same day, and trigger an allied health review within 24 hours. If they don't, the consequence is clear: delayed care, potential harm to the client, and funding clawbacks on audit. In home and disability care, organisational change HAS to be methodical, it's based on that someone has to decide what to do next without guidance in a high-stakes situation. You do your part by removing guesswork from those decisions, because the cost of getting it wrong shows up in real homes, with real clients.
Don't launch change campaigns. Implement micro-commitments led by managers. Change initiatives stall in contact centre and regulated environments when they exist only in slide decks rather than in the actions and behaviours of team leaders and frontline staff. Change is executed daily by teams who respond to what their team leader demands, develops, and reinforces - not what the change management team communicates. Change endures when you empower frontline leaders to define it as part of the daily non-negotiables. We were experiencing dismal execution of a process change in one service organisation. Execution improved when we required team leaders to facilitate brief weekly meetings about topics related to the change and actual cases/call recordings. Take up began when team members understood how the change would affect their daily tasks, instead of just the policy. Spend the first couple of months documenting manager training, tracking coached employee development, and monitoring compliance to new process steps. The single biggest failure of leadership is announcing change to the masses and operationalizing it on the frontline in pencil rather than pen.
Make it a regular practice to retire and rebuild one core process each quarter. After a 40% performance drop, we shredded our playbooks and required every manager to rebuild a proven process from scratch. We paired veteran leaders with junior staff to surface blind spots and challenge habits. This approach gives teams permission to let go of what no longer works and quickly test better ways of operating. It builds adaptability into the culture, so people engage with change rather than resist it.
I lead through major change by building a single source of truth that everyone uses, with shared dashboards, clear procedures, and real-time data. It cuts noise, reduces handoffs, and keeps remote and field teams working from the same facts. When our office, field, and call groups struggled to stay aligned, we integrated ServiceTitan to connect them and set daily check-ins on Slack and Zoom. With identical job records and work orders visible to all, scheduling and updates stopped slipping through the cracks. We reinforced the shift with consistent training until the new routines became habit, which steadied performance during the transition.
Identify the people who handle change well, and use them as anchors during the transition. Start by meeting the people most affected. Listen carefully. You'll quickly spot who stays calm, constructive, and forward-looking. Keep those people close because they have the credibility to explain the upside to colleagues who are doubtful. They'll also flag issues early, while you still have time to fix them. Do this well, and the transition stays grounded in trust and day-to-day reality, not just leadership messaging.
The most effective strategy is to establish a clear direction early, craft a story, and help employees and clients see themselves in it. During significant change, uncertainty comes less from lack of information than from lack of orientation. Teams can tolerate ambiguity, experimentation, and even failure, but they struggle when they cannot tell the direction in which the company is moving. Many leaders complain that their teams "are stuck in the past," that they don't understand that "the world has changed." Sometimes it's true. More often, the leader has not explained which story will replace the old one. Declaring that "the old story is dead" does little for the organization if there's no clear direction to move toward. I advise leaders to be explicit about three things: what is changing, what is not changing, and what will be decided along the way. This converts diffuse uncertainty into navigable terrain. But direction alone isn't enough. People also need to understand what the change means for them: their role, their relevance, their future in the organization. A leader who provides strategic clarity but ignores the identity question will probably receive compliance but no engagement. Customers want to understand how they will be served. They both need to see a place for themselves in the story being written. Finally, executives have to make themselves explicitly accountable for the new story. This is the ultimate leadership test, and their people and customers will judge them by it. Hope this helps Federico Malatesta www.federicomalatesta.com
Make change feel safe by pairing full transparency with small, visible wins. Big reorganizations fail when people think change is something being done to them. The fastest way to keep morale and execution intact is to (1) tell the truth early and often, and (2) prove momentum with quick wins that reduce pain for the team. What it looks like in practice - Say what's changing, what's not, and what you still don't know. People can handle uncertainty; they don't handle surprises. - Create a "decision log" and publish it internally (one page): what we decided, why, what we rejected, when we'll revisit it. This stops rumor-driven second guessing. - Run the change as a sequence of 2-3 week "sprints," each ending in something the team can feel: fewer steps, fewer approvals, a faster handoff, a broken process fixed. - Make managers repeat the message in their own words. If the story isn't consistent at every layer, trust collapses. Why it works Transparency prevents the "leadership is hiding something" narrative, and quick wins prevent the "this is chaos forever" narrative. Together, they keep people engaged long enough for the new system to become normal. Kotter's 8-step model explicitly calls out building momentum through short-term wins and removing barriers as core steps in successful change. ADKAR is also helpful when you want to diagnose where individuals are stuck (awareness vs desire vs ability vs reinforcement).
The most effective strategy I use in times of major change is to operate with self-managed teams. When adults have clear policies, the autonomy to make decisions, and control over their schedules with the right scheduling support, they adapt faster and stay engaged. We reinforce that autonomy with real-time communication tools so our field teams can check in, share location, and get quick guidance without waiting on layers of approvals. I also build in one or two backup channels, because no tool is 100% reliable and staying connected is essential during change. This mix of trust, clarity, and reliable communication keeps momentum high and helps the team move through transition with confidence.