The Motivation Gap

I once watched a team of ten become a team of four in six months.

They were bright, capable people — developers, data engineers, quality engineers — building performance metrics across sites. The codebase was complex. The stakeholders were demanding. And every quarter, leadership would float a new initiative to "explore AI opportunities."

The team went through the motions. Attended the workshops. Reviewed the vendor decks. Built a prototype that nobody asked for.

Then they started leaving. One by one. Not because they couldn't do the work, but because they couldn't see the point of it anymore.

When the dust settled, the team was four people, a product owner, and me trying to keep the rituals alive. The AI exploration? A footnote in a steering committee deck. The metrics they were supposed to build? Still half-finished.

The Distraction That Looks Like Innovation

Here's what leadership saw: a team that was "resistant to change" and "not embracing AI."

Here's what I saw: a team that knew the difference between real work and theater. They had spent years maintaining a brittle system with no runway to modernize it. Then they were asked to "innovate" on top of a foundation they already knew was cracking.

The AI exploration wasn't a strategy. It was a distraction from the fact that nobody wanted to fund the hard, unglamorous work of fixing what was already there.

When you ask a burned-out team to get excited about a technology with no clear use case, you don't get innovation. You get resignation.

The Contrast

In the same organization, a different team was operating. Three people. One software engineer, one data engineer, one data scientist.

Their project was harder. Their data loads were slow. Their analysis pipeline was unreliable. Their AI layer was hallucinating. Every week brought a new technical hurdle that would have justified shelving the whole thing.

But they didn't slow down. They sped up.

They rewrote the data ingestion. They rebuilt the analysis method. They rearchitected the AI layer. And they did it at a velocity that made leadership nervous — because they weren't asking for permission, they were solving problems in real time.

The difference? Their work had a user.

When the analysis finally worked, people used it. When the AI stopped hallucinating, people trusted it. When the data loaded fast, people stopped exporting to Excel. The team could see the impact in Slack messages, in meeting invites, in the quiet shift from "this tool is mandatory" to "this tool is useful."

What Actually Drives Motivation

I've thought about this contrast a lot. Same company. Same budget constraints. Same corporate noise. Two completely different outcomes.

The ten-person team had resources, coverage, and executive visibility. The three-person team had none of that. What they had was relevance.

Relevance is what separates a team that's executing from a team that's enduring. It's not about the technology — it's about whether the person doing the work can draw a straight line between their effort and someone else's outcome.

The ten-person team couldn't. They were building metrics for a dashboard that might get reviewed in a monthly meeting. The three-person team could. They were building something that made someone's daily work easier.

The SMB Angle

Small and medium businesses don't have the luxury of keeping teams busy with exploratory work that never ships. Every person is close to the customer, the process, or the problem. There is no room for theater because there is no room for waste.

That proximity is your advantage. Not because your teams are inherently more motivated, but because they can see the impact. When a three-person team builds something that works, the whole company knows. When a ten-person team builds something that doesn't, they get reassigned to the next initiative.

If you're thinking about adopting AI in your business, the question isn't whether your team is "ready for AI." The question is whether you can give them a problem that matters enough to solve.

The Question to Ask This Week

Look at the work your team is doing right now. Not the roadmap. Not the backlog. The actual work happening today.

Can every person on that team name the specific person whose job gets easier because of what they're building?

If the answer is no, you don't have a motivation problem. You have a relevance problem. And no amount of AI strategy will fix it.