I have been part of a lot of digital transformation projects, the ones that soared and the ones that quietly died. As the year closes and I look back at the failures, they share a root cause that has almost nothing to do with technology. The software worked. The people did not adopt it. That is the whole story, repeated in different costumes.

This is the case for treating digital transformation people first. The tool you choose matters far less than whether the humans around it are convinced, supported, and led. I have watched a mediocre system succeed because the team believed in it, and a beautiful, expensive system rot on a server because nobody could be bothered to change how they worked.

If you are planning a transformation for next year, the most useful thing I can give you is not a technology recommendation. It is a map of the three human roles that quietly decide whether your project lives or dies.

The Failures All Rhyme

Let me be concrete about what failure actually looks like, because it is rarely dramatic.

  • The new CRM that everyone logged into for two weeks, then abandoned for the old spreadsheet, because the spreadsheet was faster for the thing they actually did every day.
  • The inventory system that was technically live but ran alongside a shadow paper ledger, because the warehouse team never trusted the numbers and kept their real records by hand.
  • The reporting dashboard nobody opened, because the one person who understood it left, and no one else had been brought along.

In every one of these, the technology was fine. What failed was human: a team that was never convinced, a middle manager who never enforced the change, a power user who was never won over. The project did not fail in the code. It failed in the org chart. This is the same truth I explored from a different angle in Technology Is a People Problem Wearing a Software Mask, and a year of hindsight has only made me more sure of it.

The Three Roles That Decide Everything

Every transformation lives or dies on three people. Name them before you start, and if any one is missing or unconvinced, fix that before you write a single line of code.

1. The Sponsoring Owner

This is the person with authority who wants the change and is willing to spend real capital, political and financial, to make it happen. Not a signature on a budget, presence. The owner who says "we are doing this" in a meeting and then never mentions it again has sponsored nothing. Teams read what leaders pay attention to, not what they announce once.

The test for a real sponsor: are they willing to be inconvenienced by their own project? Will they use the new system themselves, ask about it weekly, and back the manager when someone pushes back? If the owner treats transformation as something that happens to other people, the whole thing is already on borrowed time.

2. The Middle Manager

This is the most underestimated role and the most common point of failure. The middle manager is where a decision from above becomes a daily reality, or does not. They set the tone for their team, they decide whether the new way is enforced or quietly optional, and they are the ones who absorb the complaints in week two.

Here is what gets missed: middle managers often have the most to lose. The new system might expose their numbers, change their routine, or reduce the informal power that came from being the person who knew things. If you have not made the change good for the manager, or at least not threatening, they will not fight for it. They do not have to sabotage it. They just have to shrug, and the team follows.

3. The Skeptical Power User

Every team has one: the person who knows the current process better than anyone, who has seen tools come and go, and who is loudly unimpressed by your project. New leaders often treat this person as an obstacle to route around. That is a mistake. This is the person you must win first.

Why? Because the team trusts them more than they trust you. The skeptical power user is the real influencer on the floor. Win them, genuinely, by taking their objections seriously and solving the problems they raise, and they become your most credible advocate. Fail to win them, and every doubt they voice in the break room outweighs every slide in your kickoff deck. The order matters: win the skeptic early, and the rest of the team comes along far more easily.

What This Changes About How You Plan

If digital transformation is a people project, then your plan should look different from the typical technology plan.

  1. Budget for change, not just for software. Training, hand-holding, the productivity dip while people learn. This is not overhead, it is the actual work.
  2. Name the three roles explicitly. Who is the sponsor, who are the managers, who are the skeptics. If you cannot name them, you are not ready.
  3. Sequence the humans before the features. Win the skeptic, equip the manager, secure the sponsor's visible attention, then roll out. A rushed launch to an unconvinced team is money set on fire.
  4. Measure adoption, not just delivery. "The system is live" is meaningless. "80 percent of the team uses it daily and the shadow spreadsheet is gone" is the number that matters.

A grounded technology strategy builds these human realities in from the start rather than bolting them on when adoption stalls. That is a large part of Why Your Business Needs a Technology Strategy, Not Just a Website.

The Takeaway

After every project I have watched succeed or fail, the pattern is the same. Put digital transformation people first, because the tools almost never fail on their own. Unconvinced teams and absent owners fail them.

Before you choose a platform for next year, choose your sponsor, equip your middle manager, and win your skeptic. Do the human work first and mediocre software will succeed. Skip it and the most beautiful system money can buy will quietly die on a server. If you want a partner who plans for the people and not just the code, that is the work I do with partners.