The Uncomfortable Questions · An AI FAQ for leaders
Question #17 · TalentWhat’s harder to replace in your organization: a skill AI can learn, or a relationship AI can’t?
The short answer
Most workforce plans count skills. Few count relationships.
The client who stays because of one person. The team that performs because of one manager. Those don’t show up in an automation business case, and they’re often the first casualties of one. Map them before you restructure.
Norm E. Murray
The psychology
Why it happens
Skills are listed in systems and priced in business cases. Relationships live between people, so the spreadsheet never sees them.
What gets measured gets kept
The McNamara fallacy is the habit of treating what can be counted as what matters, and ignoring the rest. Roles and hours fit neatly in a model. The trust that holds a client in place does not, so it drops out of the decision.
Trust does not transfer
Economists call these relationship-specific assets: value that exists only between two particular parties. A contract can be reassigned to a new account lead. The confidence the client placed in the old one cannot.
Organizations remember through people
Psychologists call it transactive memory: groups store knowledge in who knows what and who to call. Remove one well-connected person and you lose more than a role. You lose the route to everything they could reach.
Savings come first, damage comes later
Present bias makes us overweight what arrives now against what arrives later. The savings land this quarter. The client who drifts away or the team that stops performing shows up long after the case was approved.
Your move
What to do about it
- Map relationships before you redraw roles.For each function in scope, name the people clients ask for, the managers teams follow, and the people others go to when something breaks.
- Ask your top clients who they trust.Find out which names keep them with you. If the answer is one person, you have a concentration risk that no system of record will show you.
- Add a relationship line to every business case.Before approving an automation, require a plain answer: which relationships does this touch, and what happens to them?
- Protect the time relationships run on.Efficiency programs often cut the informal check-ins and hallway conversations first. Decide which ones stay, on purpose, before someone optimizes them away.
- Plan the handoff as a relationship, not a task.When someone must move on, introduce their successor early and in person. Transfer the trust while the person who holds it can still vouch for someone else.
Keep going
Related questions
Get a sharp take like this every morning
Norm’s Edge is a free daily briefing for leaders: one AI story, one decision, one minute.
Free. One email a day. Unsubscribe anytime with one click.
Prefer to read first? See Norm’s Edge