The professional services engagement taught us something that has nothing to do with technology.
When we walked into the first team meeting, the energy was off. Polite, professional, but tense. These were smart people. They’d read the same headlines everyone else had. They knew what “we’re bringing in an AI consultancy” usually means for the people whose work is about to be automated.
The CEO was bought in. He could see the maths. But the team? The team was terrified.
We’ve seen this in every engagement since. The technology is never the hard part. The fear is. And ignoring it — treating it as a change management problem to be handled with a town hall and a FAQ document — doesn’t work. People aren’t worried about “change.” They’re worried about their mortgage.
What we did differently in that engagement — and what we’ve done in every one since — was simple: we told the truth on day one. Every person whose role would be affected was told they weren’t being replaced. They were being moved into growth-focused work. The automation was taking the worst parts of their jobs, not their jobs.
The target was to reallocate 3 people into pure growth roles. We hit 4.
But the number that matters more: the team that was nervous on day one became the loudest advocates by month six. Not because we convinced them. Because they could feel it in their daily work. Less time in spreadsheets. More time on the work they were actually hired to do.
We now treat this as a design constraint, not an afterthought. Before we touch a system, we answer: what happens to the people? If the answer is “they lose their job,” we need a different plan. Not because we’re sentimental — because it doesn’t work. Fearful teams resist automation. They find workarounds. They don’t adopt. They sabotage, not maliciously, but instinctively.
The best automation projects we’ve run are the ones where the team is genuinely excited about what they get to do instead. That’s the design problem worth solving — and it’s the one most AI consultancies skip entirely.