A new team member starts Monday. No welcome. No introduction. No clarity on their role. Everyone just figures it out.
You'd never do that to a person. You're doing it to your robots.
We onboard humans. We install robots.
When a new person joins, we have a playbook. Welcome email. Team intro. A buddy. A few weeks to settle in.
When a robot joins, we send someone from IT.
And then we wonder why teams resist them.
Here's the irony: we ignore anthropomorphism in deployment — but it's exactly the thing that could make it work. When a robot resembles a human closely enough, people project onto it. They read intent into its movements. They feel uncomfortable when it's mistreated. Leaders who understand this can use it. A team that naturally relates to a robot is already halfway to trusting it. But only if the introduction is handled well.
The robot is legible — or it isn't
Research shows a critical difference between a robot being transparent (what it's doing) and explainable (why it's doing it). The why is what builds trust.
Think about a colleague who silently does tasks without explaining their reasoning. Competent, maybe. Trustworthy? Hard to say. Your team feels the same way about a robot they can't read.
When workers can't explain a robot's behaviour, they fill the gap with anxiety — quietly undermining deployments that looked fine on paper.
Your job isn't just to introduce the robot. It's to make it legible.
It's a diversity problem in disguise
Researchers have started applying D&I frameworks to human-robot teams. Robots represent an outgroup — triggering the same bias, resistance, and psychological distance that shows up in any team with a strong in-group.
The change management playbook you already have applies here more than you think.
Four things most organisations skip
Brief the team before the robot arrives. What's it here for? What changes? What doesn't? Workers who don't get answers invent their own — and the story they tell themselves is rarely flattering.
Define the role boundary. Working near a robot, with a robot, and alongside one feel completely different. Confusion here is where resentment starts.
Give it time. Trust doesn't form in week one. You wouldn't performance-manage a human in their first week.
Open a feedback channel. The people closest to the robot see things leaders and vendors don't. Let that knowledge surface.
Most organisations ask: is the robot working?
The better question: is the team working with it?
A robot that functions perfectly but that the team routes around is not a successful deployment. It's a trust failure dressed up as a technology win.
Your new colleague is already on its way. The question is whether you'll bother to introduce it properly.