Why workplace intelligence needs to earn trust before it earns authority
AI-generated insights about people carry higher stakes than AI-generated insights about almost anything else. The design of these systems has to reflect that.
The promise of AI in people operations is powerful: systems that can surface who is ready for promotion, flag employees who are disengaging before they hand in their notice, identify the hidden experts in your organisation, and map succession risk before it becomes a succession crisis.
These are genuinely valuable capabilities. They are also capabilities that, if deployed carelessly, can produce outcomes far worse than the manual processes they were designed to replace.
The reason is not that the technology is wrong. It is that trust in AI-generated insights about people is not the same as trust in AI-generated insights about weather forecasts or product recommendations.
People are not data points. And the stakes of getting it wrong are not symmetric.
The asymmetry of people decisions
When a recommendation system suggests the wrong film, the cost is 90 minutes and mild disappointment. When a workplace intelligence system surfaces an inaccurate flight risk assessment that causes a manager to treat a valued employee differently, the cost is a relationship, potentially a career, and the trust of everyone who finds out it happened.
This asymmetry shapes everything about how workplace intelligence should be designed.
An AI system that is right 80% of the time is useful for product recommendations. An AI system that is right 80% of the time is dangerous for promotion decisions -- because the 20% it gets wrong represents real people, in real jobs, with real consequences.
This is not an argument against workplace intelligence. It is an argument for a specific approach to it.
What makes an insight trustworthy
An insight about a person inside an organisation is trustworthy if it meets three conditions.
First, it is traceable. The user can follow the chain from the conclusion back to the evidence that produced it. Not "the system thinks Sarah is ready for a senior role" but "the system has 84% confidence Sarah is ready for a senior role, based on 12 recognitions from respected colleagues, 3 projects she led, 2 mentoring relationships she initiated and a certification she completed four months ago."
The conclusion is the same. The traceability is different. Traceability allows the human to evaluate whether the evidence is sound -- and to override the conclusion if they know something the system doesn't.
Second, it is honest about confidence. No system that makes inferences about people from incomplete data should present those inferences as certainties. The appropriate framing is probabilistic: this evidence suggests this conclusion with this level of confidence.
This is not hedging. It is accuracy. A system that presents uncertain conclusions as certain conclusions will eventually be wrong in ways that damage trust irreparably. A system that presents uncertain conclusions as uncertain, with evidence, will build trust gradually as its estimates prove reliable.
Third, it is transparent to the subject. The person the insight is about should be able to see that it exists, understand what it says, and access the evidence it is based on. Not because transparency is a legal requirement -- though in some jurisdictions it is -- but because a system that makes inferences about people that those people can never see is a system that people will rightly distrust and resist.
The three levels of inference
Not all insights about people carry the same risk. A useful framework distinguishes three levels.
Level one is observable fact. Sarah is in the product team. She has completed her GDPR certification. She has received 12 recognitions in the past six months. These are facts derived directly from events that occurred. Their accuracy can be verified by anyone with access to the source data. Surfacing them requires standard user permissions.
Level two is derived insight. Sarah has a collaboration score of 78 -- higher than average for her team. Her influence appears to extend significantly beyond her immediate team based on the cross-team distribution of her recognition network. These are inferences drawn from level one facts. They require the system to make a judgement about what the facts mean. Surfacing them requires manager or HR access, and they should always display the evidence that produced them.
Level three is predictive inference. Sarah shows signals consistent with readiness for a senior role. An employee in her department shows patterns that historically correlate with disengagement. These are the most powerful and the most dangerous insights. They require the highest access permissions, audit logging, explicit evidence disclosure, and a clear statement that the insight is probabilistic and human judgement is required to act on it.
Trust is built incrementally
A workplace intelligence system that launches with level three capabilities -- predicting flight risk, readiness, burnout -- before it has established trust in its level one and level two outputs will fail. Not because the technology is wrong, but because the trust infrastructure doesn't exist yet.
Trust in intelligence systems is built the same way trust in anything is built: through demonstrated reliability, over time, with honesty about limitations.
The right sequence is: prove the observable facts are accurate, prove the derived insights are reliable, establish the transparency mechanisms that let people see and dispute what the system knows about them, and only then earn the right to surface predictive inferences.
The companies that deploy workplace intelligence successfully will be those that treat trust as the product -- not the safety disclaimer at the end of a product launch.
Intelligence that earns its authority
The goal of workplace intelligence is not to replace the judgement of People Teams and managers. It is to give them better information to exercise their judgement with.
A system that says "promote Sarah" replaces judgement. A system that says "here is what we know about Sarah's readiness, here is our confidence level, here is the evidence, and here is what we don't know" informs judgement.
The first system might be right more often in aggregate. The second system produces better outcomes, because the human in the loop can catch the cases where the system is wrong -- and the system improves faster because those corrections are visible.
Workplace intelligence needs to earn trust before it earns authority. The companies that understand this will build systems that last.
The difference between recording work and understanding it.
Every company has systems that record work. Very few have systems that understand it. This distinction matters more than most people realise.
📄 People OpsYour HR team is spending 20% of their time on document requests. Here's the proof.
Employment confirmation letters. Salary confirmations. Visa support letters. These requests arrive every week, at every company, and almost all of them are still handled manually.
🔗 People OpsWhy five HR tools is worse than one
The standard advice is to buy the best tool for each problem. In practice, this produces a specific kind of problem that compounds over time.