Employees can use OpenAI’s ChatGPT, Anthropic’s Claude, Google’s Gemini, and AI embedded in SaaS products every day while their company still lacks a shared approach to AI. Leaders then face two different questions: where employees already use AI, and whether the organization has strategy, governance, training, and executive alignment around that use. Separating those questions makes the management problem clearer. Individual experimentation can develop before an organization decides what AI is for and where it belongs.

Individual AI use can precede organizational adoption

That gap matters when work moves between people. Employees can independently choose tools, devise prompts, review outputs, and decide when to disclose AI involvement. Once that work enters a shared workflow, those choices affect colleagues and customers. Organizational adoption therefore requires explicit decisions about acceptable uses, human review, disclosure, and the outcomes AI is expected to improve.

Independent choices can collide

The problem is shared judgment about when AI improves communication. Several people can optimize message production while making the conversation itself less useful. Training can establish expectations for when AI belongs in a workflow, where human judgment is required, and when colleagues or customers should know AI was involved. Without common expectations, teams may discover incompatible practices only when their work intersects.

Tool choice creates another coordination decision. Employees may encounter Google’s Gemini, Anthropic’s Claude, OpenAI’s ChatGPT, and AI instances embedded in SaaS products. A company can set criteria for choosing among available tools and define expectations for context, review, data handling, and disclosure. Governance then becomes an operating framework for decisions employees already make.

Okoone experts
LET'S TALK!

A project in mind?
Schedule a 30-minute meeting with us.

Senior experts helping you move faster across product, engineering, cloud & AI.

Please enter a valid business email address.

Scale increases the coordination burden

Marketing teams, executives, and other functions can require different AI practices because their work differs. Leadership still needs enough common ground to make expectations clear across the enterprise. More participants can mean more decisions about approvals, training, disclosure, and oversight. Those decisions become part of the operating model for AI use across functions.

Governance also has to address how employees frame requests to AI systems. A large language model, or LLM, generates responses from the context and instructions it receives. The wording of a prompt can embed an assumption before the model generates an answer. Training can teach employees to inspect those assumptions, provide relevant context, challenge weak outputs, and judge how much confidence a response deserves.

Disclosure creates a related management choice. Companies need to decide when AI-assisted work should disclose that involvement and what information the disclosure should contain. Different workflows can justify different requirements based on their audience and consequences. The management task is to make AI-assisted work transparent and reviewable where disclosure matters.

Strategy should precede tool choice

The practical starting point is the business problem. Leaders should define the intended outcome, relevant information, decision to be supported, constraints, and standard for a useful result. Those requirements provide criteria for choosing a tool and designing prompts. They also give reviewers a basis for deciding whether AI-generated output serves the task.

Starting with those requirements can reduce repeated changes to prompts, tools, and approaches after work begins. The same principle applies across an enterprise when employees begin generating output before defining the result they need. A strategic brief can move decisions about purpose, context, constraints, intended use, and review expectations earlier in the workflow. It also creates a shared reference point for evaluating the result.

That brief can expose assumptions before they shape AI output. A loaded prompt may direct attention toward a presumed weakness, incomplete context may exclude relevant considerations, and an unclear objective may cause employees to optimize an answer that serves the wrong goal. AI can influence judgment even when a person retains formal decision authority. Strategy defines what employees are asking the system to help them decide.

Governance can turn experiments into shared capability

A governance system gives employees common rules for recurring decisions. Depending on the organization’s needs, those rules can define approved uses, disclosure expectations, guardrails, training requirements, and executive responsibility for intended outcomes. Teams can adapt their practices within those boundaries. The aim is to make expectations clear before AI-assisted work crosses functions or reaches customers.

Shared training can establish a baseline for framing requests, supplying context, reviewing outputs, identifying potential bias, and escalating uncertain cases. Teams then have common methods for evaluating work even when their specific uses differ. Management also gains a basis for revising rules when recurring problems emerge. This helps turn individual learning into practices that can operate across teams.

Organizations can phase this work. Leaders can define an initial scope, set rules for it, assess how the process performs, and revise those rules before extending AI use to other workflows. This turns employee experience into evidence for later organizational decisions. Responsibility must also be explicit so unresolved questions have an owner.

Measure AI use and organizational readiness separately

Executives can assess two dimensions: where AI enters employees’ work and whether shared strategy, governance, and training keep pace. Widespread experimentation paired with weak shared practices creates a coordination problem. Limited experimentation creates a different management problem because leaders have less organizational experience from which to learn. Separating these dimensions prevents a single adoption label from hiding materially different conditions.

The practical diagnostic is the gap between employee behavior and organizational readiness. Leaders can examine where AI enters workflows, which decisions employees make independently, where work crosses team boundaries, and which recurring questions still lack clear owners or rules. Those observations provide a concrete basis for deciding where governance or training is needed. They also show whether the organization can support AI use deliberately as it spreads.

Key takeaways for decision-makers

  • Separate AI use from adoption: Employee experimentation can spread before the organization has shared strategy, governance, training, or executive alignment. Management can assess these dimensions separately to identify readiness gaps.
  • Set rules for shared workflows: Independent choices about tools, prompts, review, data handling, and disclosure become organizational concerns when AI-assisted work crosses teams or reaches customers. Governance owners can define common expectations before practices collide.
  • Build coordination as AI scales: Wider AI use increases decisions about approvals, training, oversight, prompt design, and disclosure. Functional leaders can adapt practices to their workflows while operating within enterprise-wide standards.
  • Define the business problem first: Business owners can specify the intended outcome, relevant information, constraints, and review criteria before selecting tools or writing prompts. A strategic brief gives teams a shared basis for evaluating AI output.
  • Turn experiments into shared capability: Governance owners can convert employee experience into repeatable practices through clear guardrails, training, accountability, and phased expansion. Recurring problems then become inputs for improving organizational standards.
  • Track organizational readiness alongside AI use: Executives can map where AI enters workflows against the strategy, governance, training, and ownership supporting that use. The resulting gaps show where management attention is needed as adoption spreads.

Alexander Procter

September 21, 2026

6 Min

Okoone experts
LET'S TALK!

A project in mind?
Schedule a 30-minute meeting with us.

Senior experts helping you move faster across product, engineering, cloud & AI.

Please enter a valid business email address.