Most of the reporting on enterprise AI adoption frames the problem backwards. The dominant narrative is that organizations are struggling to adopt AI. The data says something di...

Most of the reporting on enterprise AI adoption frames the problem backwards. The dominant narrative is that organizations are struggling to adopt AI. The data says something different. Organizations have already adopted it. Leadership just was not invited to the adoption.

This is not a technology problem. It is a communication problem. And the structure of the communication failure is older than AI, older than enterprise software, and documented more rigorously in the relationship-science literature than in any MarTech report you will read this year.

The First Three Minutes

John Gottman's research team can predict the outcome of a couple's conversation with 96 percent accuracy based on the first three minutes.[^1] The finding is structural, not magical. The tone set in the opening moments reveals the pattern that will govern everything that follows. A softened start predicts resolution. A harsh start predicts escalation. The trajectory is fixed before most participants realize they are on it.

The same structure governs organizational communication. The first time your leadership team addressed AI, whatever was said, whoever said it, whatever tone was struck, determined the trajectory of every subsequent conversation about AI use in your organization.

If the message was skeptical, employees learned to hide. If the message was silent, employees learned that AI was not a topic for open discussion. If the message was enthusiastic but vague, employees learned that enthusiasm was the only acceptable response and that their actual questions had no sanctioned channel.

Gottman's related finding is that his Four Horsemen, which are criticism, contempt, defensiveness, and stonewalling, predict divorce with 94 percent accuracy.[^2] Stonewalling proves especially lethal. It is the shutdown pattern in which one partner withdraws entirely from an overwhelming exchange. Habitual stonewalling predicts dissolution within years. Not because the stonewaller is cruel, but because unresolved issues accumulate while both parties pretend the structure is still sound.[^3]

AI in the enterprise is not following the pattern of prior technology rollouts. That is why the stonewalling metaphor applies here and not to other technology adoption stories.

Why AI Breaks the Old Playbook

Every previous enterprise technology followed a one-direction model. IT evaluated. IT procured. IT deployed. Employees got trained. Employees used the thing at work. Nobody went home and used their personal SAP instance on the couch. Nobody had a richer relationship with Workday on their phone than their CFO had in the boardroom.

AI breaks that pattern in three specific ways.

First, employees already have a relationship with the technology before their employer shows up. They use it at home. They use it on their personal devices during work hours. They chose the vendor themselves.

Second, the tool requires zero organizational infrastructure to adopt. There is no procurement gate to pass, no security review to clear, no budget approval to secure. The friction to use a free-tier AI tool is lower than the friction to ask a manager whether using it is permitted.

Third, the output is indistinguishable from human work. Unlike a CRM entry or an ERP report, AI-generated prose can be pasted into any document, email, or presentation without a trace. This is what makes the shadow use possible. It is also what makes non-disclosure so temptingly easy.

These three differences mean the traditional technology-adoption playbook is structurally irrelevant. Procurement gate, security review, staged rollout, training schedule, all of it. The tool is already inside the building. The relationship has already formed. The only question is whether leadership knows, whether leadership has been invited into the conversation, and whether anyone is reviewing the prompts alongside the outputs so the organization can converge on what good actually looks like.

The Shadow Partner

Organizations have acquired what can only be described as a shadow partner. Not a sanctioned vendor. Not an approved tool. A direct relationship between individual employees and AI systems that leadership did not initiate, does not monitor, and in many cases has explicitly prohibited yet cannot terminate.

In couples therapy, a shadow partner is an emotional affair, hidden debt, or a secret behavior. It is devastating not because of the act itself but because of the secrecy it introduces into the primary relationship. The secrecy signals that something essential cannot be discussed. Once that signal is sent, the trajectory of every subsequent conversation changes.

Employees learn what topics are safe. Leaders learn to see what they want to see. The gap between what is happening and what is acknowledged widens until it becomes the defining feature of the relationship.

Jason Greer of Greer Consulting reframes the entire problem in a single observation. Shadow AI is not a technology problem. It is a trust problem. Employees are not turning to unapproved AI tools to be rebellious. They are turning to them to survive the pace of work.[^4]

That reframe matters because it changes what the fix has to be. When 78 percent of AI users are bringing their own tools to work, which is the headline figure from the Microsoft and LinkedIn 2024 Work Trend Index, the behavior is not deviance.[^5] It is adaptation under constraint. Employees are not rebelling against policy. They are compensating for the absence of one.

The fix cannot be a better policy document. It has to be a communication practice that names what is already happening and builds shared understanding from that starting point, not from the starting point leadership wishes it had.

The Anatomy of the Hidden Relationship

The numbers are no longer suggestive. They are conclusive.

The Microsoft and LinkedIn 2024 Work Trend Index, drawing from a massive sample of knowledge workers across industries, found that 75 percent now use generative AI in their work.[^6] Within that population, 78 percent bring their own AI tools to the workplace.[^5] The figure climbs to 80 percent at small and medium businesses where IT governance structures are typically thinnest.[^7]

A Gartner figure cited by workforce analytics firm Second Talent offers directional corroboration: 68 percent of employees use AI tools without IT approval.[^8] The Microsoft 78 percent figure is the headline. It comes from a primary source with transparent methodology. The Gartner number serves as cross-validation from an independent research track.

The inverse statistic is equally telling. Only 34 percent of AI tool usage flows through approved enterprise accounts.[^9] The remaining 66 percent runs through personal accounts, free tiers, and browser-based interfaces that leave no audit trail. Two out of every three AI interactions in the average organization are invisible to the people responsible for data security, compliance, quality assurance, and strategic planning.

This describes a relationship that has already formed without leadership's participation. The organization did not select the vendor. The organization did not negotiate the terms. The organization does not control the data pipeline. Yet the organization receives the output, in emails, in reports, in client deliverables, every single day.

The Survival Motive

Understanding why employees choose this path is essential to addressing it. The Microsoft and LinkedIn survey asked shadow AI users directly. Ninety-one percent said they need these tools to stay productive.[^10] Not to gain an edge. Not to experiment. To survive the pace of work as it currently exists.

That figure reframes the entire conversation about governance. You cannot meaningfully regulate a behavior that employees experience as a precondition for doing their job.

The EY 2025 Work Reimagined Survey adds texture. Among surveyed employees, 64 percent reported an increase in workload due to performance pressure.[^11] This is the paradox at the heart of current AI adoption. The tool marketed as a productivity enhancer has become a source of additional pressure. Meanwhile, 37 percent worry that overreliance on AI could erode the skills and expertise they spent years building.[^12]

Three statistics together create a composite portrait of the employee experience. Ninety-one percent need AI to survive. Sixty-four percent experience increased workload. Thirty-seven percent fear skill erosion. This portrait is neither triumphant nor resistant. It is exhausted. The tool that was supposed to reduce burden has increased it. The skills that defined professional competence feel threatened. The only relief available is a tool that must be used in secret.

The Chain of Hiding

Secrecy in organizations, like secrecy in couples, does not emerge from nowhere. It follows a causal chain, and the Microsoft and LinkedIn data reveals that chain with precision.

Fifty-three percent of AI users worry that using AI on important tasks makes them look replaceable.[^13] That fear produces the next link. Fifty-two percent are reluctant to admit using AI on their most important tasks.[^14] The hiding produces the final link. Leadership, seeing no disclosed use, assumes there is no problem.

The organization enters a feedback loop in which the absence of visible AI use is interpreted as evidence of compliance rather than evidence of concealment.

The most damning statistic in this chain is the 67 percent of employees who do not know whether their company even has an AI policy.[^15] Two-thirds of the workforce is operating without clarity on what the rules are. This is not a policy gap alone. It is a communication failure so profound that leadership has not managed to transmit the existence of rules, let alone their content.

When two-thirds of your workforce cannot tell you whether a policy exists, the problem is not the policy. The problem is the channel through which policies travel.

The Leadership Perception Gap

If the workforce is hiding its AI use, leadership is complicit in its own blindness.

A BCG survey published in the Harvard Business Review in November 2025, drawing from 1,400 U.S.-based employees across organizational levels, asked a simple question about enthusiasm for AI adoption. Among executives, 76 percent reported that their employees feel enthusiastic.[^16] Among individual contributors, the actual figure was 31 percent.[^17] Leadership misreads the emotional temperature of its own organization by a factor of 2.45.

This misperception ratio is the organizational equivalent of Gottman's stonewalling finding. One party has constructed a reality in which the problem does not exist. The 145-percentage-point gap between what executives believe their workforce feels and what the workforce actually feels is not a minor miscalculation. It is a structural disconnect that makes meaningful intervention impossible until it is named and addressed.

When leadership believes enthusiasm is the dominant sentiment, it will design initiatives that assume buy-in. Those initiatives will fail because the buy-in does not exist. The failure will reinforce leadership's sense that employees are resistant. The actual dynamic, which is that employees are cautious, unsupported, and communicating in a code leadership has not learned to read, will remain invisible.

The EY 2025 data adds a further dimension of missed opportunity. Eighty-eight percent of employees use AI at work, but primarily for basic tasks like search and summarization.[^18] Only 5 percent are maximizing AI to transform their work.[^19]

Beneath the hiding, there is massive untapped capability. The organization is paying for AI potential it cannot access because leadership has not created the conditions under which that potential can be expressed. Employees will not experiment with transformative AI use while they fear that basic AI use makes them look replaceable. The fear that produces concealment also produces underutilization.

The organization loses twice. Once in the productivity gains it forfeits. Once in the signal it sends that innovation is safest when it is invisible.

From Couples to Organizations

Gottman's stonewalling finding maps directly onto the leadership behavior pattern these data reveal. A leadership team that writes a blanket "no personal AI tools" policy and hopes the problem resolves itself is stonewalling. A leadership team that holds town halls celebrating AI transformation while 52 percent of its workforce hides their most important AI use is not merely out of touch. It is engaged in the organizational equivalent of a partner claiming "we have great communication" while the other partner is preparing to leave the conversation entirely.

Andrew Christensen and his colleagues have documented a complementary pattern across decades of couple research: the demand-withdraw cycle.[^20] One partner demands change. The other avoids the topic, distracts from the conversation, or ends it to maintain the status quo. This pattern is one of the most destructive forms of coercive communication behavior in couple conflict, documented across cultures, orientations, and age ranges.

The organizational mapping is precise. Leadership demands compliance with AI policies that do not reflect actual use. Employees withdraw into unapproved tools and silence. The demand does not produce the desired behavior. It produces better hiding.

Gottman's research on flooding adds a third dimension. Flooding is the physiological overwhelm that causes a partner to shut down during conflict. Both sides in the AI conversation are flooded. Leadership is flooded by the pace of AI development, the volume of vendor claims, the regulatory uncertainty, and the sense that any position taken today may be wrong tomorrow. Employees are flooded by productivity pressure, skill anxiety, and the cognitive load of using a powerful tool in secret.

Flooding on both sides produces shutdown on both sides. The conversation that would address the problem cannot occur because both parties are too overwhelmed to begin it.

The Operational Contract

Constance Noonan Hadley, organizational psychologist at Boston University Questrom School of Business, provides academic grounding for the renegotiation frame. Her argument is that companies must renegotiate the operational contract with their employees as AI puts more power into the hands of workers in terms of how the job gets done.[^21]

Hadley's framing matters because it comes from outside the relationship-therapy parallel. She is not applying Gottman to organizations. She is describing a structural shift in employment relations that happens to map precisely onto the renegotiation dynamic couples therapists facilitate.

The operational contract, meaning the set of mutual expectations about how work gets done, has already changed. Employees are already exercising more power over the how of work by selecting their own AI tools, defining their own workflows, and making their own judgments about quality and appropriateness. The only question is whether leadership participates in drafting the new terms or discovers them after they have been implemented by default.

This renegotiation is not optional. The contract has already been rewritten in practice. The question is whether it gets rewritten intentionally, with all parties at the table, or ex post facto, when a compliance incident or competitive pressure forces the conversation that should have happened months earlier.

What Power-User Organizations Do Differently

The Microsoft and LinkedIn data reveals a critical variable that separates organizations where AI use thrives from organizations where it hides.

The survey identified a population of power users. These are employees who use AI multiple times per week and have moved beyond basic search and summarization into more sophisticated applications. Power users are not concentrated in specific industries, company sizes, or demographic groups. They are concentrated in organizations with a specific communication infrastructure.

Power users are 61 percent more likely than non-power users to have heard from their CEO on the importance of using generative AI at work.[^22] They are 53 percent more likely to receive encouragement from leadership to experiment with AI tools.[^23] They are 35 percent more likely to receive tailored training that helps them apply AI to their specific job functions.[^24]

These three differentiators share a single characteristic. They are all communication behaviors. They do not require a specific vendor, a specific platform, or a specific budget line. They require leaders who talk about AI, who create permission to experiment, and who invest in skill-building rather than assuming employees will figure it out on their own.

The tool is not the variable. The conversation is.

Organizations that want more sophisticated AI use, meaning use that transforms work rather than merely accelerating it, should not start with a technology decision. They should start with a communication decision. The CEO needs to say something specific. Managers need to encourage something specific. Training needs to address something specific.

The Prompt-Review Protocol

The prompt-review habit is simple in concept and demanding in execution. When a piece of work is submitted, two things get discussed in the feedback loop. The final output, and the prompt that produced it.

The reviewer asks a single additional question. What prompt got you here?

The producer shares the prompt. The exact language, the context provided, the constraints specified, the iterations attempted. The conversation that follows is not an audit. It is a joint examination of how a particular piece of work was constructed, and whether the construction process can be improved.

This practice produces three effects over time.

First, it ends the hiding. Once prompt review is normalized as a standard part of quality assurance, there is no incentive to pretend the work was produced without AI assistance. The conversation shifts from "Did you use AI?" which carries judgment and risk, to "How did you use AI?" which carries curiosity and developmental intent. The 52 percent who currently hide their most important AI use no longer need to. The 53 percent who worry about looking replaceable discover that AI skill is valued, not punished.

Second, it builds a shared vocabulary of what good looks like. Organizations currently have no standard for AI-assisted work because they have no visibility into how that work is produced. Two employees can submit equally polished reports that were generated by radically different prompting strategies, one thoughtful and iterative, one lazy and single-shot, and the organization cannot distinguish between them. Prompt review makes the production process visible. Over time, teams develop norms. This kind of task requires this kind of prompt structure, this level of context, this verification step. The standard emerges from practice, not from policy.

Third, it teaches prompting by example rather than by lecture. The most effective way to improve prompting skill is not a training session. It is repeated exposure to the prompts that produce good results in your specific domain, on your specific tasks, with your specific quality standards. Junior team members learn by reviewing senior prompts. Senior team members learn by seeing approaches they would not have considered. The review creates a bidirectional learning loop that training cannot replicate.

Implementation

The prompt-review protocol does not require a steering committee, a budget request, or a vendor selection process. It requires one leader to ask one team one new question.

The implementation path is deliberately constrained.

Identify one team that already uses AI heavily. Do not start with a team that is AI-averse. Start with a team that is already producing AI-assisted work in quantity. They have the most to gain from making that work visible and the least to lose from ending the hiding. Marketing teams, research functions, and customer success operations are common starting points.

Select one recurring deliverable. Do not attempt to review every piece of work. Choose one deliverable that repeats weekly or biweekly, a report, a content piece, an analysis, and add the prompt-review question to its existing review cycle. The goal is to build a habit around a specific trigger, not to create a new process for everything.

For one week, add the question: what prompt got you here? One week is long enough to produce multiple examples and short enough to feel manageable. After one week, the team evaluates. Did we learn something? Did the conversation feel useful or surveillant? What would we adjust? The evaluation itself is a prompt-review conversation. A conversation about the conversation.

The tone of this practice is the difference between success and failure. If prompt review feels like an audit, employees will produce prompts designed to pass inspection rather than prompts designed to do good work. The frame must be developmental and curious. The leader who says "show me how you got here so we can all get better" creates a different dynamic than the leader who says "show me how you got here so I can check it."

Three Prerequisites

Three conditions must be true for prompt review to work.

Leadership must have said something. The prompt-review protocol cannot be the first time AI is discussed. If leadership has been silent on AI, the prompt review will feel like a trap. A sudden interest in a topic that was previously ignored. The CEO does not need to be an AI expert. The CEO does need to have said, explicitly, that AI use is expected, that learning in public is valued, and that the organization is figuring this out together. The power-user data is unambiguous on this point. Sixty-one percent more likely to have heard from the CEO is the top differentiator.

There must be no punishment for disclosure. The prompt-review protocol is not a mechanism for catching violators. If an employee has been using a personal AI account for six months in violation of an uncommunicated policy, the prompt review must be met with curiosity, not discipline. Any punitive response will instantly shut down every other disclosure in the organization. The 52 percent who hide their use are hiding for a reason. The organization must earn the right to see their work by demonstrating that visibility is safe.

The review must be bidirectional. Junior staff must review senior prompts, not only the reverse. This is not a hygiene check. It is a learning practice, and learning flows in both directions. Senior leaders who refuse to share their prompts, who exempt themselves from the transparency they demand of others, undermine the practice entirely. The leader who says "I know less than you do about this, but here is what I tried" models the vulnerability that makes the entire system work.

The Practice Begins

Return to the Gottman parallel. The intervention that saves a relationship is rarely a new purchase, a new rule, or a new environment. It is a new pattern of conversation. The couple that learns to discuss their process, meaning the meta-conversation about how they are talking and not just what they are talking about, breaks the cycle of demand and withdraw.

The organization that learns to review prompts, not just outputs, breaks the cycle of hiding and blindness.

The prompt-review habit does not require budget approval, vendor selection, or a steering committee. It requires one leader to ask one team one new question. What prompt got you here? That question, asked consistently and without judgment, opens a channel that has been closed. It names what is already happening. It creates the conditions under which shared understanding of good can emerge.

No external hire, no software purchase, and no committee charter can substitute for that single act of communication.

Opening the channel fixes the hiding. It does not fix the inconsistency. Two people can review each other's prompts every day and still produce wildly different outputs, because prompts are instructions, not systems. The conversation is necessary. The conversation is not sufficient.

What happens when the conversation needs to scale, when the organization needs consistency that individual prompts cannot provide, is the subject of part two.

Communication is not a one-time event. It is a practice that either deepens or decays.

[^1]: Gottman, J. M., and Levenson, R. W. (1992). Marital processes predictive of later dissolution.

[^2]: Gottman, J. M. (1999). The Marriage Clinic: A Scientifically-Based Marital Therapy.

[^3]: Gottman Institute research summaries on stonewalling and the Four Horsemen.

[^4]: Jason Greer, Greer Consulting, public commentary on shadow AI adoption.

[^5]: Microsoft and LinkedIn, 2024 Work Trend Index.

[^6]: Ibid.

[^7]: Ibid.

[^8]: Gartner research cited by Second Talent, 2024.

[^9]: Microsoft and LinkedIn, 2024 Work Trend Index.

[^10]: Ibid.

[^11]: EY 2025 Work Reimagined Survey.

[^12]: Ibid.

[^13]: Microsoft and LinkedIn, 2024 Work Trend Index.

[^14]: Ibid.

[^15]: Ibid.

[^16]: BCG survey published in Harvard Business Review, November 2025, n=1,400.

[^17]: Ibid.

[^18]: EY 2025 Work Reimagined Survey.

[^19]: Ibid.

[^20]: Christensen, A., Eldridge, K., Heavey, C. L., and Baucom, B. R., research on demand-withdraw communication patterns.

[^21]: Constance Noonan Hadley, Boston University Questrom School of Business, commentary on the operational contract.

[^22]: Microsoft and LinkedIn, 2024 Work Trend Index.

[^23]: Ibid.

[^24]: Ibid.