Technology Implementation Is an Operational Exercise. Adoption Is a Leadership Challenge.

Two questions get asked before almost every technology decision:

Can we do it? 

Should we do it, financially?

Far less time gets spent asking what it will actually feel like for the people living through it.

Building the rollout plan is operational work. Getting people through it is a leadership challenge, and the two are not the same.

Resistance Is Rarely About the Tool

When people push back on a new technology, the resistance is almost never about the technology itself.

It’s about what the change implies: 

• Will this replace part of my role. 
• Will the way I’ve always worked still count for something. 
• Is this the beginning of mattering less.

To the person asking those questions, the concern is real, even when the actual risk turns out to be smaller than it feels. 

Naming that directly, rather than assuming it resolves on its own, changes the conversation. It doesn’t make the feeling disappear. It makes it easier to work through.

Build the Human Case, Not Just the Business Case

Business cases are built around value and feasibility: will this create value, can we implement it. Those questions are necessary, and most organizations are good at asking them.

Fewer organizations build a parallel case for the human side of the same decision. We call that the Human Case: questions worth working through alongside the operational ones, before a technology change is approved, not after.

Work. People. Culture. Leadership.

Work

•  What will change?
• What new skills are needed?
• Where could friction emerge?

People

• What concerns will people have?
• Who feels most affected?
• What support is needed?

Culture

• What message does this send?
• Does this align with our values?
• How might trust be affected?

Leader Actions

• Have we explained why?
• Are managers prepared?
• Are we measuring adoption?

None of these questions are complicated on their own. What’s easy to miss is that no one is responsible for asking them unless a leader makes it someone’s job.

Communication Has to Go Both Ways

Many organizations treat communication about a change as a one-way announcement: here’s what’s happening, here’s the plan. That kind of communication informs. It doesn’t create room for people to process what they’re hearing.

The more effective approach goes both ways: small, informal opportunities for people to ask questions and describe how the change is landing for them, even when the underlying decision isn’t up for revision. Meeting people where they are starts with actually asking, not only telling.

Leaders Don’t Need to Have All the Answers

Many leaders operate on the assumption that their team needs them to project certainty. In a slower-moving environment, that instinct made sense.

It matters less today. Planning horizons that once stretched three to five years now typically run closer to six months to a year, because decisions are being made faster and with less information than before.

A leader who acknowledges what isn’t yet known, while staying clear about the direction and how the decision was made, builds a different kind of trust than a leader who projects certainty they don’t have. It’s the trust that comes from honesty, not the trust that comes from having every answer.

Some Resistance Is Worth a Second Look

Not all resistance to a change is the same, and it’s worth resisting the instinct to treat all of it as something to manage past.

Some resistance comes from fear, and that deserves a direct, human conversation. Some of it is pointing at something the rest of the organization moved past too quickly: a risk, a gap, a piece of institutional knowledge worth protecting. Telling the two apart is one more reason to build the Human Case before the decision is finalized, not after the resistance shows up.

The Human Side Hasn’t Changed

Technology will keep changing, and the pace of that change is unlikely to slow down. What has stayed remarkably consistent is what people need from their leaders during periods of change: honest communication, room to react, and leaders willing to say when they don’t have every answer yet.

Build the business case. Build the Human Case alongside it.

AJO helps organizations build these leadership capabilities through executive coaching, leadership development, team coaching, and organizational consulting, so leaders are ready for the human side of technology change, not just the operational side.