Every year, my birthday is a milestone I use to reflect. It’s a marker to actually stop and ask what the last year added up to, not in revenue or projects finished, but in what I learned from being in the room with so many leaders and watching them do the hardest parts of the job up close.
This year the lesson was hard to miss, because the same thing kept happening in different buildings, with different teams, for different technology.
Every conversation that started as a technology conversation turned out to be a people conversation at the root.
The pattern behind why technology rollouts failed
An organization would bring us in because something wasn’t working. Sometimes it was framed as a technology problem, a new tool that wasn’t clicking or adoption that had stalled. Sometimes it was framed as an unknown problem causing turnover or a team that had gone quiet.
We’ve conducted many needs assessments and when we got past the surface, most recommendations come back to people. A manager who couldn’t explain the change, so the team filled the silence with their own worst guesses. A group of people who had decided this was one more thing being done to them rather than with them. Trust that had thinned somewhere a year earlier and never got repaired, so every new ask landed on empty.
When a new tool was in the picture, it usually wasn’t the problem. It was the thing that made the existing culture gaps impossible to ignore.Why the tool takes the blame
New technology is easy to point at. It has a name, a price tag, a launch date and use can usually be measured concretely. When it doesn’t deliver, it’s the obvious suspect.
But technology doesn’t create trust problems. It exposes them. Drop a new system into a team that already communicates well and trusts its manager, and the bumps can get worked out fast. Drop the exact same system into a team that’s been talked at instead of talked to, and it stalls. Same software, completely different outcome, and the variable was never the tool.
That’s the part leaders miss when a rollout goes sideways. They go looking for a better platform or more training. The fix they actually needed was a conversation they’d been avoiding.
What the leaders who adopted technology change did differently
I watched leaders, in English and in French, learn this the hard way and then learn it well. The ones who came through weren’t the ones with the best software or the biggest budget. They were the ones willing to do the slow, human work the technology couldn’t do for them.
They sat down with people, one at a time, and named what was actually changing, including the parts that were uncomfortable. They didn’t oversell or pretend a hard change was a gift. They said what was true, answered the real questions, and supported their teams while people worked through it. They led through the discomfort instead of automating around it.
It took longer than sending an all-staff email. It worked, which the all-staff email never does by itself.
The machines got better and the people got more important
Here’s the through-line of my whole year. Technology keeps promising to do the hard part, and it keeps handing the hard part right back: the judgment call, the honest conversation, the decision to show up when a change is landing badly and a team needs to hear from a human being instead of a help-desk ticket.
This year of my work the machines got very good and the people got more important, not less. I don’t find that ironic or surprising. I’ve leveraged people power my whole career and it’s the whole reason People-Powered Solutions exists.
The better the tools get, the more valuable the human skills become: the manager who can read a room, the leader who can deliver hard news without breaking trust, the person who notices a quiet employee checking out and does something before they’re gone. No system does that without humans, and it never will.
How to tell whether your rollout is really a people problem
Here’s something you can use the next time a change stalls, before you spend another dollar on the tool. Sit down and answer these honestly, based on how things actually are rather than how you hope they are.
- Can every person affected explain, in their own words, why this change is happening? Not repeat the announcement, explain it. If they can’t, the reason never really landed, and no amount of training fixes a why that didn’t take.
- Did the people who use the system have any real say in how it rolled out, or did it arrive finished? People protect what they help shape and resist what gets handed to them done.
- When something goes wrong with the new tool, do people tell you quickly, or do you find out weeks later? That answer is a reading on trust, not technology.
- Was there already a change your team felt burned by before this one? Old wounds don’t stay in the past. They ride along into every new rollout until someone names them.
- Are your front-line managers equipped to answer the hard questions, or are they passing them up the chain and guessing in the meantime? The middle is where adoption is won or lost, and it’s the layer most often left to fend for itself.
- If you answered honestly and most of those landed badly, that isn’t a failure. It’s a diagnosis. And a people problem is far more fixable than a tool you’ve already sunk a budget into.
Where to start
To lead people through technology change, you can begin with just a few moves, done in order and done for real.
- Start with the why, in plain language, including the parts that are hard. Tell people what’s changing, what will be uncomfortable, and what isn’t changing at all. Certainty about the boundaries lowers fear faster than any reassurance.
- Give people real decisions and empowerment in the rollout. Not a survey with feedback that goes nowhere, but a genuine choice about timing, sequence, or how the thing gets used day to day. Ownership is the antidote to resistance, and it costs you nothing.
- Equip your managers before you equip your staff. The people in the middle carry this change every day, and if they can’t answer the obvious questions, the whole thing wobbles.
- Then watch for quiet, not just complaints. A team that’s stopped pushing back hasn’t agreed with you. More often it’s checked out. Silence is the signal most leaders miss.
None of that requires new software. All of it requires a leader willing to do the human part on purpose.
If this sounds like your organization
If the last year taught your organization the same thing, you’re not behind.
Work through the questions above and the real problem usually turns up in plain sight. Fixing it is harder than buying a shiny new software, and a great deal more worth it. It’s also most of what we do at People-Powered Solutions.
So if you run the assessment and don’t like what you find, you don’t have to sort it out alone. Send us a message to tell us what you’re up against and we’ll map out what would actually move your team forward.
The organizations that come through change well aren’t the ones with the best software. They’re the ones whose leaders decided to do the human part on purpose. You can be one of them.
