Leading People Through the AI Shift: It’s Not a Technology Problem

"Leadership first, then AI" Brian Spisak, PhD

Most organizations are now asking the same question: How do we adopt AI? It’s the wrong first question. The better one is: How do we lead people who are worried about it?

A Technical Problem or an Adaptive One?

Ronald Heifetz of Harvard draws a useful line between technical problems and adaptive challenges. Technical problems have known solutions that an expert can implement. Adaptive challenges require people to change their habits, assumptions, and sometimes their sense of professional identity.

Rolling out an AI tool is technical. Helping a veteran analyst wonder whether her expertise still matters is adaptive. Many AI initiatives stall because leaders treat the second as if it were the first. They schedule training on the tool and skip the conversation about what it means.

Safety Comes Before Experimentation

Harvard’s Amy Edmondson has shown across decades of research that teams learn fastest when people feel safe to speak up, ask questions, and admit mistakes. She calls this psychological safety, and it matters more when everyone is learning something new.

If employees fear that admitting confusion or pointing out a flawed AI output will make them look replaceable, they’ll hide their struggles. Your organization will then be learning slowly, and you won’t know it.

Satya Nadella made a similar point in Hit Refresh. Drawing on Carol Dweck’s work on mindset, he pushed Microsoft’s culture from “know-it-all” toward “learn-it-all.” That shift matters when the tools change every few months.

Servant Leadership -- Applied

Ken Blanchard and others have long taught that servant leaders exist to develop and equip the people they lead. In an AI environment, that means several practical things:

•  Ask before you announce.   A department head might open a team meeting with three questions instead of a mandate: Where does your work feel repetitive? Where does it require judgment you would never hand off? What worries you about these tools? The answers usually reveal both the best pilot projects and the fears that would have sunk the rollout.

• Model your own learning. A CEO who says, “I asked the AI to draft this summary, and here’s where it got things wrong,” gives everyone permission to be a beginner. Leaders who pretend to be fluent teach their people to pretend as well.

• Redefine the human contribution. A nonprofit director might tell her staff, “If the tool drafts the grant report, your job becomes what it could never do: knowing our donors, sensing what’s unsaid, deciding what matters.” People stop asking “Will I be replaced?” and start asking “Where do I add the most value?”

Three Questions for Monday Morning

1.  Have I named what people are afraid of without dismissing it?

2. Do they feel safe telling me when the technology gets it wrong, or when they don’t understand it?

3.  Am I investing as much in developing people as I am in acquiring tools?

The organizations that thrive won’t necessarily have the best technology. They will be the ones whose leaders remembered that change is carried out by people, and that people follow leaders who listen first.

Jim Dittmar, PhD, President and CEO, 3Rivers Leadership Institute