
The Service Companies didn't have a hiring problem. It needed tech built for growth and scale.
August 19, 2026

Workplace AI governance depends on psychological safety: the shared belief that people can take interpersonal risks without punishment or humiliation.
Amy Edmondson’s foundational research connected that safety with learning behavior. With AI, learning requires employees to admit uncertainty, report near misses, and reveal how they actually use the tools.
Consider an employee who uses a public AI tool to draft a sensitive performance message. The model invents a policy detail. She catches the error, rewrites the message, and tells no one. A colleague uploads internal information to speed up an analysis, then quietly deletes the chat.
No formal incident appears, so leaders conclude that adoption is progressing safely. In reality, fear and social judgment have removed the information leaders need to govern the technology.
Most organizations have an AI policy, a pilot program, or a list of approved tools. Those controls describe intended behavior. They rarely reveal actual behavior.
Microsoft’s global Work Trend Index found that 78% of AI users brought their own tools to work, while 52% were reluctant to admit using AI for important tasks. Leaders see licenses, training completion, and reported incidents. They miss personal accounts, copied data, improvised prompts, and errors corrected before anyone else notices.
A 2025 KPMG and University of Melbourne survey found that 57% of employees concealed their AI use, 66% relied on outputs without adequately evaluating accuracy, and 56% reported making mistakes because of AI.
Hidden AI use therefore creates an HR problem as much as a technology problem. It conceals skill gaps, workload pressure, policy confusion, and flawed workflows.
Employees often hide AI use for understandable reasons. Some fear that using it will make them look lazy, less skilled, or replaceable. Others fear discipline for crossing an unclear policy line. Many assume that leaders do not want to hear about small errors.
Research on employee silence shows that workers develop unwritten rules about when speaking up feels risky, even when their information could help the organization.
Power differences sharpen that calculation. Research by Elizabeth Morrison, Kelly See, and Caitlin Pan found that powerlessness increased silence, while perceived openness from the recipient reduced it.
Employees judge the safety of reporting AI problems from what happens to the first few people who speak. A defensive manager, public reprimand, or vague investigation can outweigh months of official messaging about transparency.
Social judgment adds another barrier. Slack’s Workforce Lab found that workers worried colleagues would view AI-assisted work as less authentic or judge them for using it.
Employees may share polished outputs while concealing prompts, failed attempts, and the degree of machine assistance. Teams then lose opportunities to compare methods, identify errors, and develop better norms.
A common leadership reaction involves tighter monitoring, broader prohibitions, and stronger threats. That approach may stop some unsafe behavior, but it can also teach employees to hide it more effectively.
Leaders need to distinguish intent. Deliberate misuse, fraud, retaliation, and repeated disregard for clear safeguards require accountability. Good-faith experimentation, confusion, and promptly reported mistakes require learning. Treating both categories identically destroys candor.
Effective AI governance requires continuous information from the people who use the systems. NIST’s Generative AI Profile frames risk management as an ongoing cycle of governance, mapping, measurement, and management. ISO/IEC 42001 similarly calls for continual improvement of an AI management system. Neither approach works when employees conceal real workflows.
Training matters as well. Article 4 of the EU’s AI Act requires providers and deployers to take measures to ensure sufficient AI literacy among staff.
Employees need more than a prohibited-use list. They need role-specific guidance on verification, privacy, bias, escalation, and the limits of automation.
HR should turn psychological safety into a practical operating system for AI use.
Start with near-miss reporting. OSHA recommends simple processes for reporting hazards, close calls, and incidents, including anonymous options, prompt responses, and protection from retaliation.
AI examples include an invented citation caught before publication, confidential information nearly entered into a public tool, or an automated recommendation rejected after human review.
Keep the reporting form short. Ask what task the employee attempted, which tool and information they used, what went wrong, whether the output reached anyone else, what prevented harm, and what would make safe behavior easier. Focus on the workflow rather than the employee’s character.
Classify reports by consequence and urgency. A low-impact near miss may require shared guidance. Confidential-data exposure may require immediate privacy and security review. An AI-influenced employment decision may require legal review and remediation.
The OECD’s proposed AI incident reporting framework offers a useful model for capturing context, harm, affected parties, and system characteristics.
Managers need a short response protocol because employees usually approach them first. Managers should thank the employee, stabilize immediate risk, gather facts without accusation, and explain what happens next.
After significant events, leaders should run a learning review that separates explanation from blame, following the logic of Google’s postmortem culture. The review should examine workload, incentives, tool access, policy clarity, training, and supervision while identifying reckless or intentional conduct when evidence supports it.
Involve employees in designing rules. International Labour Organization case studies show how responsible AI can benefit from worker participation. Employees know where approved tools fail, which deadlines encourage shortcuts, and which controls conflict with the job. Their participation exposes impractical rules before those rules produce more concealment.
Measure candor. Track reporting volume, disclosure speed, response time, recurrence, corrective-action completion, and near misses versus actual harm. OSHA’s leading indicators for reporting systems include near-miss reports, response times, and timely corrective actions. Early increases in AI reports may signal better visibility. A sudden absence of reports deserves scrutiny while AI use grows.
Pair those measures with pulse questions. Do employees know approved tools and data boundaries? Do they expect fair treatment after reporting a good-faith mistake? Have managers shared a near miss and the resulting improvement?
The strongest approach to AI adoption at work combines clear guardrails with candid experimentation. Employees need approved tools, realistic training, and safe channels for disclosing what went wrong. Leaders need to treat inconvenient reports as governance intelligence rather than reputational threats.
Weak psychological safety corrupts risk information, repeats failures, slows learning, and produces policies built around fiction. Leaders cannot manage workplace AI through silence. They need employees to reveal the messy reality of experimentation while there is still time to improve it.