One strategy I've used to lead workplace change while keeping the human experience at the forefront is open dialogue followed by gradual implementation. When I transitioned Ozzie Mowing and Gardening from a mostly solo operation to a small team, I knew the shift could be overwhelming if not handled thoughtfully. So instead of forcing processes or standards right away, I brought the team into the conversation. I shared my vision for where we were going and asked for their feedback on how we could get there together. We talked through job roles, customer expectations, and even how each team member liked to work. With over 15 years in the field and formal horticulture training behind me, I knew the practical needs of the business, but I also knew that ignoring the human element would only cause resistance. People are more likely to embrace change when they feel heard and valued. One example was introducing new ecofriendly gardening practices. I had been researching better organic methods and knew we needed to make the shift. But I didn't just throw new tools and products at the team. I spent time educating them on the why behind the change, backed by real examples from projects I'd worked on. I demonstrated the results firsthand and involved them in trials with select clients. Because of my background in both theory and practice, I could explain the horticultural science clearly while showing how it made their day to day easier and more rewarding. That combination built trust, and within a few months, the new methods became part of our DNA.
When we transitioned from siloed teams to cross-functional squads, I knew the structure would only work if the change felt empowering, not imposed. So before we made a single change, we ran "reverse town halls" where leadership didn't speak—we just listened. Designers, marketers, and developers shared what frustrated them day-to-day, and we used that as our blueprint. The strategy wasn't just to restructure—it was to co-design the change with the people affected. Each squad got to name their team and define their own rituals, like Friday demos or learning lunches. By keeping the focus on ownership rather than compliance, adoption came naturally. We saw better communication, faster decisions, and more pride in the work. The human experience didn't get in the way of change—it made the change stick.
One strategy that's worked well for us is leading change through micro-conversations before macro-decisions. Instead of rolling out a big shift all at once, we start by having small, honest discussions with the people most affected — not just managers, but frontline employees too. For example, when we transitioned to a hybrid work model, we didn't just send out a new policy. We hosted listening sessions, gathered feedback on challenges and preferences, and tested a few pilot schedules. That gave us real insight into what people needed, not just what leadership assumed would work. By including people early and often, we built trust and reduced resistance. The change still happened, but it felt collaborative, not top-down. That approach reminded us that change doesn't have to sacrifice empathy, in fact, empathy is what makes it stick.
Transparent communication paired with incremental implementation keeps people engaged during organizational transitions—exactly what we practice at ERI Grants when helping organizations implement grant-funded programs. Change feels overwhelming when people don't understand the 'why' behind new processes, so we start with stakeholder listening sessions to address concerns before rolling out new systems. For example, when a school district received a $4.8 million technology grant, we facilitated staff input sessions that shaped the implementation timeline, reducing resistance and increasing buy-in. The key is treating change as a collaborative process rather than a top-down mandate. With 24 years of experience, ERI Grants has secured over $650 million in funding with an 80 percent success rate by prioritizing human-centered approaches. That's how successful grant funding is achieved.
Change only sticks when people feel seen in the process. At spectup, one shift we made was moving from a flat decision-making structure to a more streamlined leadership framework as we grew. I knew it would trigger mixed feelings—some would feel relieved, others might worry about losing autonomy. So instead of announcing the change top-down, I involved the team early, framing it as a shared design sprint. Everyone could challenge, shape, and even veto parts of the new setup. One team member pointed out a bottleneck I hadn't noticed, and that input shaped the final model more than any consultant report could have. I also set up weekly "coffee drop-ins" during the transition—no agenda, just space to talk. It kept the tone human and avoided the sense that change was being "managed." If there's one thing I've learned, it's that people don't resist change—they resist how it's done.
At Achilles Roofing, the biggest workplace change we ever made was shifting from day-rate pay to performance-based compensation. Not because we wanted to squeeze more out of the guys—but because I saw the hustle in some of them wasn't being rewarded, and the slackers were hiding in the crowd. Now, a change like that can shake a crew. Roofing is already hard. The last thing I wanted was to make it feel like we were dangling pay over their heads. So I did it the only way I know how—face-to-face, no bull. I gathered everyone, looked them in the eye, and told them exactly why I was doing it. I said, "If you're giving 100%, you'll finally see that in your check. If you're coasting, now's the time to step it up—or step out." Then I asked for feedback. Some were hesitant, sure. But I made it clear: this wasn't just about money—it was about fairness and respect. I also didn't flip the switch overnight. We tested it for 30 days on a few jobs, tracked hours, tracked output, and showed the crew exactly how the numbers played out. They saw that the guys who worked smart and hard got paid more. The ones dragging feet? Either they stepped up, or they didn't last. Simple as that. The result? Our jobs ran faster. Mistakes dropped. Crews got tighter. And morale actually went up—because the real workers felt seen and rewarded. The key? Don't force change—walk them through it. Lead with truth. Show them what's in it for them, not just what it does for the company. That's how you lead change and still keep your people with you.
Leading change as a co-founder for Legacy Online School involves balancing innovation with people. Active listening and transparent communication to the team is one of the best things that we've done. We always take everyone along when we're implementing new changes whether it's in terms of technology, curriculum modifications, or workflow optimization. Instead of just rolling out a new process or tool, we engage the team in the decision-making process first. That means getting input from every department, listening to their issues, and incorporating their ideas into the plan. It's not a top-down mandate; it's creating a shared vision that everyone can stand behind. This maintains the human element at the forefront as the alterations we implement are based on the people who'll be utilizing them. When employees are heard and involved, they're more productive, invested, and aligned with the organization's purpose. We've seen at Legacy how creating this kind of inclusive change not only produces improved results but also forges our culture and connection with each other. It might be tough, but if we consider that the people who make it occur are at the center of it, then we can lead change in our company without sacrificing the people who make that change happen.
One of the most effective strategies I've used to lead workplace change while keeping the human experience at the center is what I call "change in conversation, not just in policy." At Nerdigital, we've gone through our fair share of transitions—new tools, shifting client demands, evolving workflows—and I've seen firsthand how people resist change when they feel like it's happening to them rather than with them. When we implemented a major shift to hybrid work, I made it a point to hold small, informal listening sessions before we rolled anything out. No corporate surveys or top-down memos—just honest conversations where people could voice their fears, frustrations, and hopes. It wasn't about selling the change; it was about understanding how it landed on a human level. What came out of those conversations reshaped how we approached everything. We adjusted policies based on real-life needs—whether that was giving teams more autonomy over schedules or improving tech support for remote setups. But more importantly, people felt seen in the process. That trust made adoption smoother and created a sense of shared ownership. The lesson for me? Even in fast-paced environments, slowing down to connect with people before you introduce change isn't wasted time—it's the foundation that makes change sustainable.
One of my drivers once called me at 11 p.m. after dropping off a guest who had just come back from a family emergency. Instead of rushing home, he stood with the guest's elderly mother until she had entered her house. It was then I realized that our company culture had changed—forever. At Mexico-City-Private-Driver.com, in leading workplace change, we chose to prioritize humanity over systems and processes. We decided to redefine performance based on empathy rather than completed trips. In 2023, I brought in a very simple albeit revolutionary model: following every ride interaction, our drivers wrote anonymously to report moments of kindness or discomfort (theirs and their guests!) in two or three sentences. In this way, I could begin looking for emotional patterns that were becoming evident in our work. For instance, the emotional patterns I began to see when review after review indicated that a long waiting period outside of any embassy showed a rise in stress for both the driver and traveler. Therefore, to mitigate and deal with stress, we decided that our best plan was to agree to an extra break before our next ride, pack better snacks in the car, and include a "relief buddy?" system where one drivers waits until the 1st driver is finished with his first drop off. I did not report to my partners the rise in our NPS score from 72 to 93 and our driver retention which bounced from around 40%. The most important effect, drivers, guests, were always mentioning names, "Arturo made me feel safe" or "Lucia noticed I looked overwhelmed and did not talk until I said it was alright to talk." When human experience becomes our north star, every ride across chaotic Mexico City becomes a journey of care.
One strategy that's worked well is involving employees early in the change process—not just informing them, but genuinely listening. When implementing a shift in our corporate training delivery model at Edstellar, the first step wasn't tech or policy—it was holding listening sessions across departments. People shared concerns, ideas, and what they needed to feel supported. That input directly shaped how the transition was rolled out, from the pace of change to the kind of training offered. It wasn't just about buy-in; it was about trust. When people feel heard and see their feedback reflected in the change, resistance drops and engagement rises.
One strategy that's proven highly effective is involving employees early in the change process through co-creation workshops. Instead of top-down decisions, the goal is to give people a voice in shaping how change is implemented—whether it's a new workflow, tech adoption, or restructuring. In one case, when transitioning to a new digital operations platform, teams were invited to share what tools helped or hindered their work. Their input directly influenced the rollout plan, training priorities, and even the interface customizations. This not only built trust but also turned potential resistance into advocacy. When people feel seen and heard, change becomes something they help lead—not something that just happens to them.
One strategy that's made a real difference is involving employees early in the change process—not just informing them once decisions are made, but actively listening to their input during the planning phase. When introducing new learning technologies at Invensis Learning, feedback was gathered from trainers, support teams, and even learners themselves before implementation. This not only surfaced pain points we hadn't considered but also created a sense of shared ownership. Change felt like something with them, not to them. By pairing transparency with empathy, the transition became smoother, adoption rates were higher, and trust across teams actually deepened instead of being strained.
One effective strategy for leading change while keeping the human experience at the forefront is how you run improvement projects. The project team needs to be the people who do the work in the area you seek to improve. There might be outside experts from engineering, information systems, or other areas. But these outside experts are not running the project. They are there to support the project. Almost all improvement programs have a systematic process for documenting the current state and crafting a better future state. For Lean Transformation, the world's #1 improvement program, a Value Stream Mapping project requires the team to create current and future state maps. The very process of creating a current state map by the people who do the work, brings out the need for change for everyone to see. The team sees the workplace change as something they want to do as it covers their human experiences from doing the job. The step to create a future state map requires people to take the time to research best practices and emerging trends. Designing a future state as an empowered team, with knowledge of the possibilities, means the buy-in for change is almost automatic. The changes will be designed with real people in mind and people hungry for the new and better way. Almost everything you read, watch, or listen to about change management comes when "someone else" designs a new way of doing things and then has to "sell" the change to the people who do the work. When it comes to most process improvement activities, you do not need the "someone else" and thus you do not need to "sell" the change. I know this won't work on everything. But you can significantly reduce the issues with workplace change and significantly increase the human experience by using the appoach I have outline above.