Reading time: ~11 minutes. Last updated: June 2026.

Key takeaways

• 95% of enterprise generative-AI pilots deliver no measurable impact on the bottom line (MIT Project NANDA, The GenAI Divide: State of AI in Business 2025). McKinsey's State of AI 2025 confirms the picture: more than 80% of organizations see no material effect on EBIT.
• The reason rollouts fail is not the technology. MIT calls it a 'learning gap'; McKinsey puts it in one line: AI is 20% algorithms and 80% organizational rewiring.
• In healthcare the stakes go beyond ROI to patient safety and EU AI Act compliance, which treats most clinical AI systems as 'high-risk' and mandates human oversight.
• The key to the winning 5% is goal alignment across functions (R&D, IT, Regulatory, Medical Affairs, Quality) and psychological safety in teams — not another tool.
• One distinction reframes the whole topic: AI does not collaborate with people. Collaboration is a social process between humans. With an AI system you run an exchange and coordination. It sounds like a linguistic detail — it decides whether your transformation succeeds.

If you follow the headlines, you know the dissonance. On one side: AI designs drug candidates, reads X-rays, and writes clinical documentation. On the other: the hard data says almost no enterprise AI rollout produces a return.

That is not a paradox. It is a diagnosis. And the good news is that the problem blocking AI adoption in healthcare is solvable — because it is organizational, not technological. This article shows exactly where transformation breaks and what the organizations that succeed do differently.

What is AI adoption in healthcare, really?

AI adoption in healthcare is not buying a model. It is a durable change in processes, roles, and decision-making that lets AI tools genuinely move clinical, operational, and financial outcomes. That is the difference between 'we have a chatbot' and 'we cut the time from hypothesis to drug candidate.'

The clearest way to see it is at the level of value. There is individual AI — it saves a single person time (a faster email, a quicker article summary). And there is institutional AI — it redesigns the entire workflow so the organization scales revenue, quality, and speed. Most companies stop at the first level and then wonder why outcomes don't change. Because, as a core thesis of modern transformation puts it: productive people don't make a productive company — productive processes make a productive company.

Why do 95% of AI rollouts fail to move the needle?

Because companies 'swap the engine' but keep the old factory. They replace Excel with a chatbot for Excel, email with an email-drafting assistant — and expect a revolution. But a tool without a redesigned process is just a faster way of doing the same things.

The numbers are unambiguous and consistent across two independent studies:

• MIT Project NANDA (2025), The GenAI Divide: based on 300+ deployments, 52 interviews, and 153 executive surveys — only 5% of integrated AI pilots generate measurable value; the rest stall before they scale. The authors state plainly that the divide is driven not by model quality or regulation, but by approach.
• McKinsey, State of AI 2025 (November 2025): although roughly 80% of firms now use generative AI in at least one function, more than 80% see no material EBIT impact, and only about 39% attribute any earnings impact to AI (usually under 5%). The winning cohort is barely ~5–6% of organizations — and they consistently redesign their workflows.

This is not a data-science problem. It is an organizational one. And organizational problems are solved with people and processes — not another license.

AI doesn't collaborate. People do.

In marketing, 'human-AI collaboration' is a fashionable phrase. It sounds good, but it is imprecise — and that imprecision actively hurts rollouts. Collaboration is a social process. It happens between people, teams, and organizations. Its essence — as social psychologists Victor Wekselberg and Jacek Wasilewski show — is goal alignment across levels (individual, team, organization). It does not mean everyone holds one identical goal. It means individual, team, and organizational goals are consistent and non-conflicting.

So what do we actually do with AI? Two things that are easy to mistake for collaboration:

• Exchange (a transaction). You give the system context and a prompt; you get an output. Trust here rests on the expectation that the other party delivers what was agreed — not on shared goals. That is the definition of an exchange, not collaboration.
• Coordination. You decide who leads the task: whether a human leads the AI, a defined workflow leads, an agent plans the steps under supervision, or a swarm of specialized agents runs. This is a technical component of work — necessary, but not the essence of collaboration. A high standard of coordination does not imply a high standard of collaboration.

Why is this more than semantics? Because it shows up in results. A meta-analysis published in Nature Human Behaviour (Vaccaro et al., 2024) found that combinations of humans and AI generally did not beat the best of either alone — not the human alone, not the AI alone. You see augmentation of the human, but in most applications true 'synergy' is missing. In other words: dropping AI into a team does not create a magical, collaborating super-unit. What actually decides outcomes is the collaboration between the people who design, supervise, and interpret that system.

For healthcare, this isn't philosophy — it's a risk map. An algorithm may 'solve the problem correctly at the level of a cell but fail to solve it at the level of the whole biological system.' Clinical context, nuance, accountability for the patient, and trust are human competencies. AI amplifies them. It does not replace them.

Stop asking 'how should our people collaborate with AI.' Start asking 'how should our people collaborate with each other — in an environment where part of the work is exchange with AI and the coordination of agents?'

Five barriers that stall AI in healthcare

In a regulated sector, where an innovation must pass through R&D, IT, Regulatory, Quality, and Medical, these barriers are especially costly.

• Goal misalignment. Data Science is measured on model accuracy and speed, while Regulatory and Medical Affairs are measured on clinical risk and quality. The result: R&D deploys an algorithm that shortens molecule identification, and Regulatory rejects it for lack of transparency (the 'black box'). Without goal alignment across functions, the project dies at the proof-of-concept stage.
• Algorithm aversion vs. automation bias. Clinicians can be skeptical of AI recommendations — especially after one visible error (algorithm aversion). On the other side lurks automation bias: uncritical trust in the machine and the dismissal of one's own expertise. In medicine, both extremes can cost a patient's health.
• Lack of psychological safety. When people are afraid to admit they don't understand a tool, or that the system got something wrong, the organization loses its most valuable feedback and model errors stay hidden. Amy Edmondson of Harvard reminds us that interpersonal risk becomes business risk.
• Data — the foundation no one sees. No data, no AI — and data is today the most common and most underestimated cause of failure. Roughly 80% of data scientists' time goes not to models but to cleaning and integrating data, and about 60% of AI projects never reach production, mainly due to data quality, availability, and ownership. This too is a collaboration problem: between the people who enter data and the people who build models.
• AI doesn't reduce work — it intensifies it. An eight-month ethnographic study at a technology company (Harvard Business Review, Ranganathan and Ye, February 2026) found that workers voluntarily took on more tasks, worked faster, and worked longer, because AI made 'doing more' feel easy and rewarding. The short-term productivity surge turned into overload, cognitive fatigue, and burnout. In healthcare, where staff burnout is already a crisis, this barrier cannot be ignored. The remedy is not employee 'self-regulation' but a set of organizational norms for using AI — an 'AI practice.'

Four value levers for AI in healthcare

Every AI project should map to at least one of four levers. It's a simple filter that separates initiatives with real value from 'toys.'

• Revenue and innovation. Drug discovery and design, precision medicine, new service models. This is where AI-native CROs operate (Selvita with its CADD unit, Ardigen) alongside global pharma partnerships with AI-native firms.
• Cost. Automating knowledge work in the back office, handling tickets, extracting data from documents (OCR + LLM), classifying correspondence. Less routine, lower cost to serve.
• Risk and compliance. Compliance, quality, safety, monitoring of production processes, documenting decisions for regulatory audit. In the medical sector this lever often decides whether a model reaches the market at all.
• Speed. Shortening the decision cycle, time-to-market, and time-to-insight. GenAI for preparing documentation, synthesizing literature, and generating and evaluating hypotheses.

The EU AI Act and healthcare — what actually changed in 2026

If you're planning AI in medicine, regulation isn't an add-on — it's part of the design.

The EU AI Act (Regulation 2024/1689) has been in force since 1 August 2024 and applies in phases. Many medical AI systems qualify as 'high-risk,' which means hard requirements: risk management, data quality, documentation, transparency and — crucially — human oversight.

An important update worth knowing: under the Digital Omnibus on AI package, EU institutions reached a provisional political agreement in May 2026 to defer the deadlines for high-risk systems. For stand-alone systems under Annex III, obligations are set to apply from 2 December 2027 (instead of 2 August 2026), and for AI embedded in regulated products (including medical devices, Annex I) from 2 August 2028. Note: until the text is formally adopted and published in the Official Journal, the original deadlines technically still apply — so treat these dates as direction, not certainty.

What does this mean strategically? You got time — not an excuse. The human-oversight and decision-documentation requirements reward organizations that are already building collaboration processes among experts for reviewing AI outputs. That is exactly the same organizational capability that drives ROI. Compliance and effective adoption are, in practice, the same investment.

How to design AI adoption that delivers: 6 principles

These principles follow directly from what separates the winning 5% from everyone else.

• Narrow the scope. When in doubt, narrow. One concrete pain point, one process, a short cycle. Small scope wins, because it proves value quickly and can actually be redesigned.
• Redesign the process, not just the tool. The question is not 'which model do we use,' but 'what should the workflow look like after AI.' Skip this, and you're left with a faster email instead of scalable revenue.
• Start with data and data ownership. In 2026, an AI strategy without a data strategy doesn't exist. Decide who owns data quality and availability — at once a technical question and a question of collaboration across functions.
• Establish goal alignment across silos. Map the goals of R&D, IT, Regulatory, Medical, and Quality so they are consistent. That, not another status meeting, determines whether a project moves from pilot to production.
• Build the human into the loop (human-in-the-loop) and add observability. Autonomy without observability is a risk — in medicine, a double one. Mechanisms to raise concerns, to iteratively retrain models on expert feedback, and to transparently document decisions build trust and satisfy the oversight requirement.
• Create an 'AI practice' — norms, not self-regulation. Since AI intensifies work, set the rules: when to pause, how to sequence tasks, how to verify outputs. This protects the team from burnout and quality loss.

Each of these is fundamentally an organizational and human decision, not a technical one. That is why the leader's role shifts from 'maker' to 'manager-orchestrator': you no longer manage just people and processes, but people, agents, and automations — and the decision interval shrinks from hours to minutes.

Poland as a proving ground for AI in life sciences

This isn't a story of 'catching up.' Poland is the sixth-largest pharmaceutical market in Europe and the largest in Central and Eastern Europe, with strong institutional support and a maturing innovation ecosystem:

• The Medical Research Agency (ABM) runs a multi-year national plan to develop the biomedical sector, with a significant share of funds going to companies that use AI.
• The National Centre for Research and Development (NCBR) funds innovation and participates in European programs (including Horizon Europe).
• Local players are deploying AI in practice: Polpharma (digital twins in manufacturing), Adamed (machine learning in molecule design), Selvita and Ardigen (AI-driven drug discovery), Infermedica (medical triage used by, among others, PZU Zdrowie).

The gap? Polish organizations still lack the practices and tools to run complex projects at the intersection of biology, medicine, and data science — where generic tools (MS Teams, Jira) can't handle the specifics of a regulated industry. Whoever builds that organizational capability first will win in a market where technology isn't scarce — the ability to absorb it is.

FAQ: AI adoption in healthcare

Will AI replace doctors and scientists?

Not for the foreseeable future. The evidence (including the Nature Human Behaviour meta-analysis, 2024) shows AI works best as an amplifier of the human, not a replacement. Clinical context, accountability, and patient trust remain human domains.

Why didn't our AI pilot make it to production?

Most often for three reasons: no redesigned process, data problems (quality, availability, ownership), and goal misalignment across functions. These are organizational barriers, not technological ones — and they can be removed.

Is 'human-AI collaboration' a good term?

It's a convenient shorthand but imprecise. Collaboration is a social process between humans, grounded in goal alignment. With an AI system you run an exchange and coordination. That distinction helps you design roles correctly: AI is a tool, and it's the people around it who collaborate.

What does the EU AI Act mean for my medical project?

Most likely a 'high-risk' classification, with requirements for human oversight, risk management, and documentation. Deadlines for high-risk systems are being pushed (directionally to 2 December 2027 for Annex III and 2 August 2028 for medical devices), but preparation should be underway now.

Where exactly should we start?

With one narrow process tied to a clear value lever (revenue, cost, risk, or speed), with clean data, and with mapped, aligned goals across functions. Prove value in weeks, not quarters.

Will AI reduce my staff's workload?

Not necessarily — research shows that without deliberate norms, AI tends to intensify work. That's why you need an organizational 'AI practice': rules for verification, pauses, and task sequencing that guard against burnout.

Conclusion: it's time for architects, not tool fans

The era of 'lone geniuses' and isolated algorithms in healthcare is ending. Machines analyze billions of data points, but it is people who understand clinical complexity, create context, and build trust. The future of the sector lies not in blind faith in black boxes, but in the smart pairing of human expertise with compute — and in the collaboration between people that holds the whole thing together.

The question for leaders is no longer 'should we deploy AI.' It's: are you ready to become an architect of an organization where technology is a tool that amplifies teams — and where outcomes are decided by goal alignment and human trust?

Sources

• MIT Project NANDA (2025). The GenAI Divide: State of AI in Business 2025.
• McKinsey & Company (2025). The State of AI in 2025: Agents, innovation, and transformation.
• Ranganathan, A., Ye, X. M. (2026). AI Doesn't Reduce Work — It Intensifies It. Harvard Business Review, February 2026.
• Vaccaro, M., Almaatouq, A., Malone, T. (2024). When combinations of humans and AI are useful. Nature Human Behaviour.
• Wekselberg, V., Wasilewski, J. Cooperation, Collaboration, Coordination, Groupthink (on collaboration as a social process and the alignment of goals).
• Edmondson, A. C. — research on psychological safety (Harvard Business School).
• European Commission / Council of the EU / European Parliament (2024–2026). EU AI Act (Regulation 2024/1689) and the Digital Omnibus on AI — May 2026 provisional agreement to defer high-risk deadlines.
• PAIH / European Parliament Briefing (2025–2026) — the position of the Polish pharmaceutical market in Europe.

Read the full article on Collaboration.tech

What a system says doesn't tell you how it works. Your organization makes the exact same mistake when it confuses an impressive demo with readiness for AI transformation.

Key takeaways

• Output is not the mechanism. The fact that a result looks human doesn't mean it was produced the way a human would produce it — the core argument from Gary Marcus and co-authors in Nature (February 2026).
• Boards make the same mistake as AI enthusiasts, just in reverse: they look at an impressive pilot demo and infer readiness for the entire organization.
• The numbers are brutal: roughly 95% of generative-AI pilots produce no measurable return in P&L (MIT NANDA, 2025). Only 5–6% of companies actually capture value (BCG, McKinsey, 2025).
• AI transformation doesn't break on technology. It breaks on the layer a demo never shows: trust between people, the quality of information flow, and the alignment of goals across the organization.
• AI readiness can't be declared — it has to be measured. That's exactly what Collaboration.tech does.

A debate that looks academic — and costs millions

In late May 2026, two voices collided around a single question: do large language models actually understand?

On one side, Geoffrey Hinton — Nobel laureate in physics (2024) and one of the fathers of deep learning — has for some time suggested that today's AI models possess something like understanding, even inner states resembling those of humans.

On the other side, Pope Leo XIV took a very different position in his first encyclical, Magnifica Humanitas (released 25 May 2026). AI systems, the Pope writes, "may imitate… or even simulate… but they do not understand what they produce," because they lack the affective, relational, and spiritual perspective through which a human being grows in wisdom. Real understanding comes from experience, not from statistical adaptation to data.

AI critic Gary Marcus summed it up acidly but accurately in an essay whose very title reads: the Pope appears to understand AI better than Geoffrey Hinton does. The subtitle captures the whole idea: what a thing says doesn't tell you how it came to say it.

The dispute looks philosophical. It isn't. Beneath it sits a cognitive error that costs organizations real money every month — committed not against the model, but against themselves.

Output is not the mechanism — the heart of the argument

A language model produces fluent, human-sounding text because it was trained to predict the next word from vast datasets — not because it lived through something and understood it. Two systems with very similar outputs can arrive at them in radically different ways.

Marcus, together with Walter Quattrociocchi and Valerio Capraro, described this in Nature (the comment "Statistical approximation is not general intelligence," 17 February 2026) as a fundamental fault line in how we evaluate AI. The dominant assumption runs: "if a system statistically approximates human behavior, then it is close to a human." That assumption is false. Success in behavioral tests — including variants of the Turing test — is not evidence of general intelligence, nor of understanding.

This is a modern version of the Eliza illusion: back in 1966, the simple ELIZA program, which merely rephrased the user's sentences as questions, made people feel they were talking to someone who understood them. We see fluent behavior and project a depth that isn't there.

Your board makes the same mistake

Now let's move this from the model to the organization.

A company launches a pilot. An AI assistant writes great emails, summarizes reports, generates graphics, suggests the next step. The demo impresses the board. The conclusion lands: "It works. We're ready for AI transformation."

That is exactly the same mistake as Hinton's — just mirrored. Hinton looks at the model's impressive output and infers something about its interior. The board looks at the pilot's impressive output and infers something about the readiness of its own organization. In both cases they confuse the effect with the mechanism that produces it.

A successful demo says nothing about how it came to be:

• whether it worked thanks to organizational maturity, or in spite of its absence — because one enthusiast was patching everything by hand;
• whether it can be repeated at scale, or whether it will fall apart with the third team;
• whether the people who are meant to use it day to day trust one another enough to share data and work.

To borrow a manufacturing metaphor: most companies that "do something with AI" have swapped out the engine but never rebuilt the production line. A generic assistant handed to the whole company can deliver 80% adoption and 0% impact on transformation. People start writing faster emails — and that's it. Organizational productivity doesn't move.

What you really don't see in a demo

The data is clear. According to the MIT NANDA report from 2025 (a sample of about 300 deployments), roughly 95% of corporate generative-AI pilots produce no measurable return in the income statement (P&L). This is not an isolated reading — three independent 2025 studies paint the same picture: MIT NANDA 2025 (~300 deployments) found 95% of GenAI pilots with no measurable P&L return; BCG's Build for the Future 2025 (2,000 firms) identified just 5% as "future-built," deeply integrated with AI; McKinsey's State of AI (November 2025) found only 6% qualify as "high performers" generating more than 5% EBIT from AI.

Three samples, one result: only five to six percent of companies capture real value from AI.

The reason is mundane and uncomfortable. AI transformation doesn't break on technology. When AI leaders honestly assess the maturity of their own organizations, the weakest dimension turns out to be change management, with strategy and governance close behind. Technology, data, and talent are "okay-ish." The problem is that nobody designs the transformation — and so is everything happening underneath: trust between teams, the quality of information flow, willingness to share data, and the actual — not the declared — patterns of working together.

You don't see this in a demo. You don't see it with the naked eye at all.

And here we return to Pope Leo XIV's encyclical. His sentence — real understanding comes from experience, not from statistical approximation — describes organizations too. A company that buys AI tools without the collaboration infrastructure underneath isn't undergoing a transformation. It is approximating one. Simulating readiness. Imitating change. Just as the model imitates understanding.

First, a distinction: AI is a tool; collaboration is a process between people

In this whole discussion it's easy to fall for a mental shortcut that is itself a trap: "human–AI collaboration." It's a convenient metaphor, but a misleading one. Collaboration is a social process — it occurs only between people (teams, departments, organizations) and consists in generating alignment between goals across different levels.

AI does not collaborate. AI is a tool that people use. This distinction isn't pedantic — it has practical consequences. If the layer of collaboration between people is weak — team goals are misaligned, trust is low, information doesn't circulate — then no AI tool will fix it. Worse, the tool will only expose and accelerate the existing chaos.

That's why the real foundation of AI transformation is not the model itself. It's the alignment of goals and the quality of collaboration among the people who use that model. This is the layer that must be diagnosed before you start scaling the technology.

Postulating versus measuring

Most of the advisory market stops at the postulate: "you need to build an AI-ready culture," "you need trust and collaboration." True — and completely useless until it answers the question: ready to what degree, exactly where, and what do we do about it on Monday morning.

You can't manage what you haven't measured. And organizational readiness for AI can't be read off the enthusiasm in a workshop or a single successful pilot — just as a model's understanding can't be read off one polished answer. You have to look underneath, at the mechanism.

That is exactly what Collaboration.tech does. Instead of asking whether AI "works" in a demo, we measure what truly decides the success of a transformation: the real state of collaboration, trust, information flow, and goal alignment in the organization — the layer no demo will ever reveal. Diagnosis instead of declaration. Mechanism instead of effect.

The bottom line: ask the question the Pope would ask, not Hinton

Hinton looked at what the model says and filled in an interior. Let that be a warning, not a template.

Before your organization decides it's ready for AI because a demo impressed everyone, ask the question the Pope would ask, not Hinton:

Does what I'm seeing actually tell me how it works underneath?

If you're not sure — measure it. Because focus always beats dispersion, and diagnosis always beats declaration.

FAQ — common questions about AI transformation readiness

Why do most AI pilots fail to deliver value?

Because a successful demo says nothing about how it was produced or whether it can be repeated at scale. According to MIT NANDA (2025), about 95% of generative-AI pilots produce no measurable P&L return. The main cause isn't technology — it's weak change management and the absence of a collaboration infrastructure between people.

What is organizational AI readiness?

It's the degree to which an organization is actually able to turn AI tools into value. It comprises, among other things, alignment of goals between teams, trust, the quality of information flow, willingness to share data, and a designated transformation owner with a mandate from the board. Readiness can't be declared — it has to be measured.

Does a human "collaborate" with AI?

Not in the strict sense. Collaboration is a social process that takes place between people and rests on generating alignment of goals. AI is a tool that people use. If collaboration between people is weak, an AI tool won't replace it — at best it will expose and accelerate existing problems.

What did Pope Leo XIV say about artificial intelligence?

In the encyclical Magnifica Humanitas (25 May 2026), he wrote that AI systems "may imitate… or even simulate… but they do not understand what they produce," because they lack the affective, relational, and spiritual perspective. Real understanding comes from experience, not from statistical adaptation to data.

Where should a company start with AI transformation?

With a diagnosis of the layer a demo doesn't show: the alignment of goals, trust, and information flow between people. Only on that basis is it worth selecting and scaling specific AI use cases — focusing on the few most important ones rather than scattering effort across dozens of pilots.

Sources

• Gary Marcus, The Pope Appears to Understand AI Better Than Geoffrey Hinton Does — garymarcus.substack.com (May/June 2026).
• W. Quattrociocchi, V. Capraro, G. Marcus, Statistical approximation is not general intelligence, Nature 650(8102):792, 17 February 2026, DOI: 10.1038/d41586-026-00495-y.
• Pope Leo XIV, encyclical Magnifica Humanitas (released 25 May 2026) — Vatican News, TIME, NPR.
• MIT NANDA, 2025 report (sample of ≈300 deployments) — 95% of GenAI pilots with no measurable P&L return.
• BCG, Build for the Future, 2025 (2,000 firms); McKinsey, State of AI, November 2025.

Read the full article on Collaboration.tech

Cross-functional collaboration enhances innovation by combining the different knowledge, goals, and perspectives held across functions — product, engineering, marketing, operations, finance — into one aligned effort. When those functions align their goals (instead of chasing a single 'common' goal), span boundaries to exchange knowledge, and operate in psychological safety, they create the productive friction and recombination of ideas that innovation actually depends on. Artificial intelligence can amplify this work, but it does not replace it: collaboration is a social process between people, and AI is a tool inside it — not a member of the team.

That last point matters more than most articles admit, so this guide treats it head-on. Below, you will find what cross-functional collaboration really is, the four mechanisms through which it produces innovation, what blocks it, and where AI genuinely fits — backed by peer-reviewed research and 2025 industry data.

What is cross-functional collaboration (and why it is not 'coordination')?

Cross-functional collaboration is the social process through which people from different departments interact to align their individual, team, and organizational goals around the work they do together. The decisive ingredient is not how many meetings they hold or how neatly their hand-offs are scheduled. It is the relationship between goals at different levels — individual, team, department, and whole organization — and how consistent those goals are with one another (Wekselberg, Cooperative Theory of Groups).

This is where many organizations quietly fail. They mistake coordination for collaboration. Coordination is the technical synchronization of activity: who does what, in what order, by when. It is necessary, but it is not the essence of working together. A team can coordinate flawlessly and still innovate nothing, because their goals point in different directions. As the cooperative-theory research puts it, a very high standard of coordination does not signify a high standard of collaboration — it may just be a high standard of exchange.

So before you optimize tools and workflows, ask the more important question: do the functions actually share an understanding of what they are trying to achieve? Innovation lives in the answer.

A note on language: 'aligned goals,' not a 'common goal'

It is tempting to say that great teams rally behind a single 'common goal.' That framing is misleading. Functions do not — and should not — collapse their distinct objectives into one identical goal. Marketing optimizes for differentiation and customer value; operations optimizes for cost, reliability, and standardization. Those goals are different by design. Innovation comes from goal alignment — making those distinct goals compatible and consistent with a clear organizational direction — not from pretending everyone wants the same thing. Throughout this article, that is what 'alignment' means: compatible goals across levels, not a single shared target.

How does cross-functional collaboration enhance innovation? The four mechanisms

Cross-functional collaboration is not innovative by magic. It works through four well-evidenced mechanisms. Treat them as the levers you can actually pull.

1. Goal alignment turns diverse functions into one engine

Innovation requires many specialists to move in a compatible direction. When departmental goals drift out of sync with organizational goals, internal coherence drops — and so does effectiveness — even if every department hits its own targets perfectly. This is the textbook signature of a silo: each function succeeds locally while the organization underperforms globally.

The evidence is concrete. In a classic study of 36 professional firefighting teams, the more team members agreed on which goals mattered most, the more effective they were at the task in question (Wekselberg, Cooperative Theory of Groups). In a multinational cosmetics company, researchers measured goal congruence across four levels — international, national, department, and individual. Only where goals were consistent between the national company and departments, and between departments and employees, did financial performance improve. Higher goal congruence, better business results.

For innovation specifically, the implication is direct: align the goals first, and the cross-functional work that follows compounds instead of cancelling out.

2. Boundary spanning brings outside knowledge inside

New ideas rarely come from a team talking only to itself. They come from teams that reach across boundaries — pulling in market signals, technical know-how, and resources from elsewhere in (and outside) the organization. In a foundational study of new-product teams in high-technology companies, Ancona and Caldwell (1992) showed that teams which actively span boundaries — scanning the technical and market environment, coordinating horizontally with other groups, and shaping the views of senior leadership — secure more resources and achieve higher performance and innovation than inward-looking teams.

This effect scales. Research on multi-team systems finds that coordination between teams is as critical to overall performance as the work happening within any single team (Marks, DeChurch, Mathieu, Panzer, & Alonso, 2005). Cross-functional collaboration is, in essence, organized boundary spanning — and boundary spanning is how knowledge becomes recombined into something new.

3. Cognitive diversity creates the 'creative tension' innovation needs

Put product, engineering, and commercial people in a room and they will see the same problem differently. That is the point. Functionally diverse teams generate task conflict — disagreement about the work itself — and, handled well, that friction is a source of better solutions, not a defect (Weingart et al., 2010). When members appraise a problem from genuinely different vantage points, the differences in their judgments can generate creative tension that raises the innovativeness of the team's output.

The key qualifier is 'handled well.' Diversity of perspective only converts into innovation when the team can surface and work through disagreement productively — which is exactly what the next mechanism enables.

4. Psychological safety lets people take the risks that innovation requires

Innovation is, by definition, a sequence of attempts that might fail. People only attempt, challenge, and propose unconventional ideas when they believe it is safe to do so. Psychological safety — the shared belief that a team is safe for interpersonal risk-taking — predicts the learning behaviors that underpin innovation: asking questions, admitting mistakes, surfacing problems early, and experimenting (Edmondson, 1999). Without it, cross-functional groups default to polite silence, defensive turf-protection, and 'safe' ideas. With it, cognitive diversity actually gets voiced — and goal alignment gets honestly tested rather than performed.

What stops cross-functional collaboration from producing innovation?

If the mechanisms are clear, why is cross-functional innovation so hard? Five recurring barriers explain most failures:

• Silo mentality and goal misalignment. When departmental goals are out of sync with the organization's, collaboration between teams deteriorates even as collaboration within them stays high. Innovation that needs several functions then stalls at the seams.
• 'Not invented here' syndrome. Strong internal cohesion can backfire when a team rejects ideas, tools, or knowledge that originate elsewhere — a direct brake on the cross-pollination innovation depends on.
• Coordination mistaken for collaboration. Teams polish their hand-offs and dashboards, declare victory, and never align the underlying goals. Smooth logistics, zero recombination of ideas.
• Trying to build it from the bottom up in a hierarchy. In hierarchical organizations, strategy — and therefore the alignment of units' goals — has to be set from the top. When cross-functional collaboration is improvised purely from below, the goals of individual teams collide at higher levels and the effort dissolves into disorder. (In genuinely flat organizations, the invitation can originate from below.)
• Talk without action. Repeating the word 'collaboration' changes nothing. Collaboration is concrete: it shows up in what teams do, what they produce, and how they operate. Announcements that are not backed by changes to actual goals, tasks, and ways of working produce a declaration of change, not change.

Diagnose which of these is operating before you reach for a new tool. Most cross-functional innovation problems are problems of goals and structure, not of software.

Where does AI fit — and why AI is not a 'collaborator'?

Here is the distinction most 'AI teammate' marketing gets wrong. Collaboration is a social process that happens between people. It rests on aligning goals across human levels, building trust, and constructing a shared understanding of a situation. An AI system has none of those properties. Calling AI a 'collaborator' or 'teammate' is a category error. AI is a powerful tool that people use inside their collaboration — like a microscope, a spreadsheet, or a search engine, only far more capable.

This is not a semantic preference; the research backs it. In the largest meta-analysis to date — 106 experimental studies and 370 effect sizes — human–AI combinations on average performed significantly worse than the better of humans alone or AI alone. The combinations showed losses on decision-making tasks and meaningful gains on content-creation tasks, and they only beat the solo baselines when the human was already stronger than the AI at the task (Vaccaro, Almaatouq, & Malone, 2024, Nature Human Behaviour). In plain terms: bolting an AI onto a process does not automatically help, and many organizations overestimate how well their current setups work.

A second study underlines the need for judgment. When 758 Boston Consulting Group consultants used GPT-4 on tasks inside AI's capabilities, they completed 12.2% more tasks, worked 25.1% faster, and produced output rated about 40% higher in quality. But on a task deliberately chosen to fall outside those capabilities, AI-assisted consultants were roughly 19 percentage points less likely to reach a correct answer than colleagues working without it — the now-famous 'jagged technological frontier' (Dell'Acqua et al., 2023; published in Organization Science, 2026). The tool helps enormously in some places and quietly harms in others, and only human judgment — often cross-functional judgment — can tell the difference.

There is even an innovation-specific catch. Generative AI tends to lift any single person's output while narrowing the diversity of ideas across a group — outputs become more similar to one another (Doshi & Hauser, 2024). Diversity of perspective is precisely the raw material of innovation. So the more an organization leans on AI, the more it needs genuine cross-functional collaboration to keep its thinking varied.

The practical upshot for innovation is twofold:

• Frame AI as augmentation, not replacement. When AI is positioned as a tool that augments people, the response is higher engagement, more psychological safety, and more innovative behavior. When it is positioned as a replacement, the response is anxiety, resistance, and disengagement (Raisch & Krakowski, 2020). The framing you choose shapes the innovation you get.
• Use AI to remove the friction in collaboration, not to simulate the collaboration itself. AI is excellent at the things that slow cross-functional work down: searching scattered knowledge, drafting and summarizing, translating between a function's jargon and another's, surfacing patterns in data, and giving every function faster access to a shared base of information. That is real value — and it strengthens the human collaboration rather than pretending to be it.

What does this mean for AI adoption and organizational transformation?

If you take one strategic idea from this article, take this: cross-functional collaboration is the precondition for getting value from AI — not a nice-to-have alongside it.

The 2025 data makes the stakes vivid. In Boston Consulting Group's study of more than 1,250 companies, only 5% qualify as 'future-built' — firms that systematically build AI capabilities across functions and consistently generate real value. Another 35% are 'scalers,' and 60% are 'laggards' reporting minimal gains. The leaders are not winning on tools alone; nearly 90% of future-built companies expect most of their AI value to come from reshaping and reinventing business processes — inherently cross-functional work — and they favor a model of co-ownership between business departments and IT. The result is a widening gap: AI leaders are pulling ahead with roughly double the revenue growth and 40% greater cost savings than laggards (BCG, The Widening AI Value Gap, 2025).

This echoes decades of organizational research. Successful technology adoption requires a tight fit between business strategy, technology strategy, and organizational design (the Strategic Alignment Model; Henderson & Venkatraman, 1993). And the cultures that adopt digital and AI capabilities fastest are precisely those that value openness, an innovation orientation, and cross-functional collaboration (Hartl & Hess, 2017). AI transformation that lands as 'an IT project' fragments; AI transformation built on aligned, cross-functional human collaboration compounds.

Fix the human collaboration first, and AI becomes an accelerant. Skip it, and AI becomes an expensive way to make your silos faster.

How do you measure cross-functional collaboration and its impact on innovation?

You manage what you measure, so track both the inputs (the collaboration itself) and the outputs (the innovation it produces):

• Goal congruence: survey how consistently goals are understood across individual, team, department, and organizational levels. Misalignment here predicts downstream failure.
• Boundary-spanning activity: how often and how effectively teams reach across functions and outward to the market for knowledge and resources.
• Psychological safety: validated team-climate survey scores on whether people feel safe to question, challenge, and admit error.
• Innovation outputs: number of new initiatives shipped (including AI-driven ones), process improvements, time-to-market, and the variety — not just the volume — of ideas generated.

Read these together. High innovation output with low goal congruence is usually luck; high goal congruence and psychological safety with low output usually points to a missing capability or a structural barrier, not a people problem.

Key takeaways

• Cross-functional collaboration enhances innovation through four mechanisms: goal alignment, boundary spanning, cognitive diversity (creative tension), and psychological safety.
• Aligned goals, not a single 'common' goal. Functions keep distinct objectives; innovation comes from making them compatible and consistent — not identical.
• Collaboration is human; AI is a tool. There is no 'human–AI collaboration' in the literal sense — collaboration is a social process between people. AI augments that process.
• The research is sober about AI. On average, human–AI combinations underperform the best solo baseline (Vaccaro et al., 2024), AI helps inside its 'jagged frontier' and harms outside it (Dell'Acqua et al., 2023), and it narrows idea diversity (Doshi & Hauser, 2024) — which makes human cross-functional diversity more valuable, not less.
• Collaboration is the multiplier for AI value. Only 5% of firms are 'future-built,' and they win by reshaping cross-functional processes (BCG, 2025). Strong human collaboration is the foundation AI transformation is built on.

Sources

• Ancona, D. G., & Caldwell, D. F. (1992). Bridging the boundary: External activity and performance in organizational teams. Administrative Science Quarterly, 37(4), 634–665.
• BCG (Apotheker, J., et al.) (2025). Are You Generating Value from AI? The Widening AI Value Gap: Build for the Future 2025. Boston Consulting Group.
• Dell'Acqua, F., et al. (2023). Navigating the Jagged Technological Frontier. Harvard Business School Working Paper No. 24-013. (Published 2026, Organization Science, 37(2), 403–423.)
• Doshi, A. R., & Hauser, O. P. (2024). Generative AI enhances individual creativity but reduces the collective diversity of novel content.
• Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.
• Hartl, E., & Hess, T. (2017). The role of cultural values for digital transformation: Insights from a Delphi study. AMCIS.
• Henderson, J. C., & Venkatraman, N. (1993). Strategic alignment: Leveraging information technology for transforming organizations. IBM Systems Journal, 32(1).
• Marks, M. A., DeChurch, L. A., Mathieu, J. E., Panzer, F. J., & Alonso, A. (2005). Teamwork in multiteam systems. Journal of Applied Psychology.
• Raisch, S., & Krakowski, S. (2020). Artificial intelligence and management: The automation–augmentation paradox. Academy of Management Review.
• Vaccaro, M., Almaatouq, A., & Malone, T. (2024). When combinations of humans and AI are useful: A systematic review and meta-analysis. Nature Human Behaviour, 8(12), 2293–2303.
• Weingart, L. R., et al. (2010). Task conflict, problem-solving, and yielding in functionally diverse innovation teams. Negotiation and Conflict Management Research, 3.

Read the full article on Collaboration.tech

In 2025, MIT's Project NANDA published the most quoted statistic of the enterprise AI era. After studying 300 public deployments, interviewing 150 leaders, and surveying hundreds of employees, the researchers concluded that 95% of generative AI pilots deliver no measurable impact on the P&L. Only about 5% capture real value. Despite somewhere between $30 and $40 billion in enterprise spending, the overwhelming majority of organizations have nothing on the balance sheet to show for it.

The headline went viral as proof of an AI bubble. It's the opposite. Read past the number and MIT tells you exactly where the value went — and it isn't where almost everyone is looking.

MIT named the pattern the 'GenAI Divide': high adoption, low transformation. More than 80% of organizations have piloted tools like ChatGPT or Copilot; nearly 40% report deployment. And still, almost none of it reaches the income statement. It's the same signature we've tracked across this series — broad rollout, an average of two AI messages per employee per day, value trapped in a fraction of a percent of staff. 80% adoption. 0% transformation.

That gap is not a technology problem. It's the difference between collaboration and a very convincing imitation of it. This article is about telling the two apart — and it's the one the first three were building toward.

We began with the AI Adoption Paradox (92% investing more, 1% mature). We showed that psychological safety — not the model — decides whether people use AI honestly. We argued that trust calibration is the skill that lets them use it well. Each is a piece of one larger thing: how people work together when there's a machine in the room. Today we put that under the microscope.

First, what collaboration actually is

Here's where almost every 'AI collaboration' conversation goes wrong: nobody defines the word. We say 'collaboration' the way we say 'synergy' — a warm noise that means people doing something near each other. That vagueness is precisely what lets the imitation pass for the real thing.

The clearest definition comes from organizational psychologists Victor Wekselberg and Jacek Wasilewski, whose book Cooperation, collaboration, coordination, groupthink set out to end the muddle. Their conclusion is sharp: collaboration is a social process, based on the interaction of people, in which alignment is generated between individual goals and the goals of the team or organization. Doing a task together is not yet collaboration. Working in the same room is not collaboration. The essence is the relationship between goals — and whether people share an understanding of what's happening inside and outside the group.

From that definition they derive three conditions, and they're the bones of everything that follows:

• Aligned goals. Not one identical goal handed down, but compatibility between goals at every level — individual, team, organization — so they reinforce rather than collide.
• Compatible attitudes. People interpret the situation, the technology, and each other similarly enough to act coherently.
• Mutual knowledge. People know one another's competencies and limits well enough to divide work intelligently.

Hold onto this, because it's about to expose the most expensive misconception in enterprise AI.

There is no such thing as 'human–AI collaboration'

Read the definition again. Collaboration is a social process, and its engine is the alignment of goals. An AI model has no goals of its own to align. It has no stake in the outcome, no attitudes to make compatible, nothing to know about you in the way a teammate does. Strictly, then — and this matters more than it sounds — you do not collaborate with an AI. You operate it. You delegate to it. You divide labor with it. All useful; none of it collaboration in the sense that produces transformation.

This isn't pedantry. It's the whole misdiagnosis in one line. Organizations buy a tool, watch individuals get individually faster, see 'human–AI collaboration' on the dashboard, and conclude the transformation is underway. It isn't. The tool changed; the social process around it didn't. MIT found exactly this: generic tools excel for individuals precisely because they're flexible, but they stall in the enterprise because they don't adapt to how the organization actually works.

So where does collaboration live in an AI transformation? Between the people who have to rebuild the work around the machine. The hard part was never getting a human and a model to 'cooperate.' The hard part is getting the humans to align on new goals, form compatible attitudes toward the technology, and redistribute who does what now that a capable tool sits in the workflow. That is a social process. That is the 70%.

Where the value actually lives: the 10-20-70 rule

Boston Consulting Group put a number on it. Successful AI deployment breaks down as roughly 10% algorithms, 20% technology and data, and 70% people and processes.

Most organizations spend in almost the exact opposite proportion — pouring effort into the 10% (which model, which vendor, which benchmark) and treating the 70% as something HR will tidy up later. Then they land in MIT's 95%. The two findings are one truth told from both ends: BCG says 70% of the value comes from people and process; MIT shows what happens when you skip it. MIT even named the cause — the 'learning gap,' the failure to integrate AI into workflows, structures, and cultures. That gap is a collaboration gap. It's the 70%, unbuilt.

McKinsey's 2025 research closes the triangle from the leadership angle: the single strongest predictor of AI reaching the P&L is CEO-level ownership. Treat AI as a strategic shift and the organization moves; treat it as an IT upgrade and it stalls. As we put it in article #1 — AI adoption is a change project, not an IT project.

The trap: coordination dressed as collaboration

Wekselberg and Wasilewski are blunt about the most common counterfeit. Coordination is a technical component required in collaboration, but it is not its essence. A very high standard of coordination does not signify a high standard of collaboration — it can be nothing more than a high standard of exchange. People travelling on the same bus are exquisitely coordinated and not collaborating at all. Coordination only becomes collaboration when a shared goal appears.

This is the AI rollout in miniature. Everyone gets the tool. Everyone attends the training. Everyone is, technically, 'on the platform.' Clean, countable, and beside the point. The two-messages-a-day rollout is perfectly coordinated and entirely uncollaborative: the tool was distributed, but no goals were aligned, no attitudes reconciled, no work redivided. That precise gap — coordination that looks like momentum versus collaboration that creates value — is the machinery behind the GenAI Divide.

What gets mistaken for collaboration

The book lists four impostors, and each has a perfect AI-transformation twin:

• Good relations. A friendly team is not a collaborating team. The AI version: high engagement-survey scores, enthusiastic launch, and a flat P&L.
• Exchange. 'I'll do my bit, you do yours' is a deal, not collaboration. Most 'AI initiatives' are exchanges between a department and a vendor.
• Coordination. The big one — covered above.
• Influence. Getting people to use the tool is not the same as people collaborating to change the work.

If your AI program is really good relations, an exchange, or coordination wearing collaboration's name, the technology will work and the transformation won't come. Same as the 95%.

Seven tells that your collaboration is fake

The impostors above are the categories. Here are the day-to-day symptoms — drawn from research on how teams actually function — mapped onto AI:

• Top-down decisions. AI handed to IT or a 'central AI lab' that will handle it. Strategy decided for the users is coordination, not collaboration.
• Presence without engagement. On the platform, mentally checked out — the two-messages-a-day signature.
• Hidden agendas. When AI is quietly framed as a headcount story, people read the subtext and disengage.
• One-way communication. No real channel for 'the AI got this wrong,' so errors never travel up — and you tune the system on silence.
• Lopsided benefit. A handful of power users capture nearly all the value while everyone else stalls; the quiet resentment corrodes.
• Missing trust. Punished experiments stop happening — and without experimentation there's no learning curve, which is fatal for a probabilistic tool.
• Shadow AI. When advanced users have no sanctioned space, they build their own — unauthorized tools, personal accounts, off-the-books workflows. Worse: those people leave first.

Three or more? The bottleneck isn't your model. It's your collaboration architecture.

What you're building toward

The encouraging part: the opposite of imitation is designable, and we already have the blueprint — Wekselberg and Wasilewski's three conditions, translated into AI transformation:

Aligned goals. An AI strategy anchored to the business it serves, where each team's use of AI fits the outcomes the organization is actually pursuing — compatible across levels, not flattened into one slogan. MIT's 5% winners do exactly this: pick one real pain point, anchor to it, execute.

Compatible attitudes. Get the team to a shared, honest reading of what AI is and isn't good for. This is trust calibration from article #3, made collective — neither hype nor refusal, but a common stance the team can act on coherently.

Mutual knowledge — including the machine's. Know your people's competencies and the AI's: where it has the edge, where the human does, where each one's limit begins. That's how you divide work intelligently.

To which the data adds a fourth, practical anchor — shared accountability: an operational value metric tied to the transformation, so 'we feel more productive' becomes a number the team owns together. It was the absence of measurable impact that put 95% of pilots on the wrong side of the divide.

In a 10-20-70 world, these aren't soft extras. They are the 70%.

The test: collaboration or theater?

Run this on your own AI transformation this week. One honest point per 'yes':

• Do people share aligned goals for AI — beyond 'we should be using it'?
• Do people hold compatible, realistic attitudes toward what AI can and can't do?
• Is the human–AI division of labor explicitly defined — who does what, and why?
• Is communication two-way, with a real channel for reporting when the AI is wrong?
• Do people trust that experimenting and failing won't be held against them?
• Is there room to disagree about how AI should be used?
• Are wins and misses owned by the team, not pinned on individuals?
• Are AI's benefits distributed, or trapped in a few power users?
• Are people genuinely engaged — measured by changed work, not login counts?
• Were the people who use AI involved in deciding how it gets used?

8–10: You've built collaboration — protect it. 5–7: Solid, with real gaps. 3–4: Coordination wearing collaboration's clothes. 0–2: Collaboration in name only; the GenAI Divide already has you on the wrong side.

The questions that score worst are almost always the people questions — the 70%. That's not bad luck. That's the rule, confirming itself.

The opportunity hiding inside the warning

Read all of this not as a list of ways to fail but as the map the 5% already used. MIT's own data shows what they do differently, and none of it is magic: they buy and partner rather than build alone (vendor partnerships succeed roughly 67% of the time, internal builds about a third as often), they aim AI where the ROI actually is rather than where it's fashionable, and above all they close the learning gap — they rebuild the work, not just the tooling.

Our own market research points the same way: AI leaders run a tight handful of well-chosen use cases and earn around 2.1× the return of companies spreading effort across twice as many disconnected pilots. The difference isn't a smarter model. It's better collaboration among people, deliberately engineered.

That's the spine of this series. Psychological safety can be designed. Trust calibration is a competence, not a trait. And collaboration — the 70% — is a social process you can define, build, and measure. None of it happens by accident, and none of it happens by buying more tools.

The GenAI Divide isn't a verdict. It's an opening — for any organization willing to treat AI transformation as what it really is: not getting people to collaborate with machines, but getting people to collaborate with each other about how the work should change now that the machines are here.

Sources

• Wekselberg, V. & Wasilewski, J. (2023). Cooperation, collaboration, coordination, groupthink – what is it all about? (English ed.; orig. Mała książeczka o współpracy, Difin 2021).
• MIT Project NANDA. The GenAI Divide: State of AI in Business 2025.
• Boston Consulting Group. AI at Scale: the 10-20-70 approach.
• McKinsey & Company. The state of AI in 2025: Agents, innovation, and transformation (Nov 5, 2025).
• Internal market research, collaboration.tech / AI_MANAGERS (Poland, 2026).
• Edmondson, A. C. — foundational work on psychological safety.

Read the full article on Collaboration.tech

In our first article we described the AI Adoption Paradox: 92% of companies are increasing AI investment, yet only 1% call themselves 'mature.' In the second we showed that psychological safety is the hidden variable that decides whether people even try the tools.

But trying isn't the finish line. Once your team is using AI, a harder question appears — and it's the question that quietly determines your return on the entire investment: are they using it well?

Here's the uncomfortable answer from the research. The single largest meta-analysis on the subject found that, on average, human-AI teams perform worse than the better of the human or the AI working alone. Not better. Worse. The value doesn't usually leak because the model is weak. It leaks because people trust it wrong.

The skill that closes that gap has a name: trust calibration. This article is about what it is, why it's the bottleneck, and how to build it.

What trust calibration actually means

Most conversations about 'trust in AI' treat trust as a dial that should be turned up. Get people to trust the tools more, the thinking goes, and adoption follows. That framing is wrong, and it's expensive.

The goal is not more trust. The goal is calibrated trust — relying on AI when it is likely to be right, and overriding it when it is likely to be wrong. Researchers studying human interaction with automation have called this appropriate reliance for decades (Lee & See, 2004; Parasuraman & Riley, 1997). It is a match between how much you trust a system and how trustworthy that system actually is, for the specific task in front of you.

Two ways to get it wrong:

Under-reliance — rejecting good AI output. The team second-guesses, re-does, or ignores recommendations that were correct. Over-reliance — accepting bad AI output. The team defers to a confident-sounding answer that was wrong.

A well-calibrated team minimizes both. A miscalibrated team can be enthusiastic or skeptical and still destroy value — just in opposite directions. This is why 'is the team bought in?' is the wrong diagnostic. Buy-in without calibration is just faster mistakes.

Failure mode one: algorithm aversion

In a now-classic set of five studies, Dietvorst, Simmons and Massey (2015) gave people a forecasting task and let them choose between their own predictions and an algorithm's. The algorithm was measurably better. People still abandoned it — specifically after watching it make a mistake.

The sharp finding wasn't that people dislike algorithms. It's the asymmetry: people lose confidence in an algorithm far faster than in a human after seeing the same error. A human who slips up gets the benefit of the doubt. An algorithm that slips up gets fired.

This is algorithm aversion, and in an organization it looks completely reasonable from the inside. An analyst sees the AI get one forecast wrong, concludes 'it's not reliable,' and quietly goes back to the spreadsheet. No drama, no resistance — just a slow, invisible drift back to pre-AI ways of working, while the license fees keep auto-renewing. It is one of the most common reasons an AI rollout posts strong usage numbers in month one and flat ones by month six.

Failure mode two: over-reliance

The opposite error is just as costly and far less discussed, because it doesn't feel like a problem. It feels like productivity.

Logg, Minson and Moore (2019) ran six experiments and found the mirror image of aversion: algorithm appreciation. People often gave more weight to advice when they believed it came from an algorithm than when they believed it came from a person. So the picture isn't 'humans distrust AI.' The picture is messier — and more useful. Appreciation is strongest in domains people see as opaque or technical, and weakest in domains they see as needing human judgment, like character or ethics.

The danger surfaces when appreciation hardens into deference. A fluent, confident, well-formatted AI answer is extraordinarily persuasive — and modern generative tools produce wrong answers with exactly the same fluency and confidence as right ones. When a team stops checking because 'the AI is usually right,' it has stopped collaborating with the tool and started rubber-stamping it.

This shows up in the most counter-intuitive result in the field. Bansal and colleagues (2021) tested whether having the AI explain its reasoning would help human-AI teams. Intuitively, explanations should help people catch errors. They didn't. Explanations often increased people's tendency to go along with the AI — including when the AI was wrong. A persuasive rationale doesn't sharpen judgment by default. It can simply make a bad recommendation more convincing.

Over-reliance is harder to catch than aversion because the team looks fast, aligned, and confident. Right up until a wrong answer ships.

The evidence that should reframe your AI strategy

Put the two failure modes together and you get the central result every leader funding an AI transformation should know.

Vaccaro, Almaatouq and Malone (2024) published a preregistered meta-analysis in Nature Human Behaviour covering 106 experimental studies and 370 effect sizes. The headline finding:

On average, human-AI combinations performed significantly worse than the best of the human or the AI alone (Hedges' g = −0.23).

Read that carefully, because it is easy to misread. It does not mean AI is useless. The same analysis found human-AI teams did beat humans working alone (g = 0.64). The authors' precise term for this is augmentation without synergy: the combination helps the person, but the combination is still worse than just deploying whichever party — human or AI — was stronger for that task.

In plain terms: most organizations are leaving value on the table not because their people lack AI, and not because the AI is bad, but because the hand-off between the two is miscalibrated. The team overrides the AI when it should defer, and defers when it should override.

The meta-analysis also points straight at where to act. Performance losses clustered in decision-making tasks. Performance gains clustered in content-creation tasks. And the pattern of who-should-lead was clear: when the human was stronger than the AI, the combination produced gains; when the AI was stronger, the combination produced losses — because people kept inserting weaker judgment into a process the AI was handling better.

That is not an argument against human-AI collaboration. It is a precise specification of the engineering problem: calibration is the variable, and it is addressable.

Trust calibration is a capability, not a personality trait

Here is the genuinely good news, and the reason this is a growth story rather than a cautionary one.

Calibration is not a fixed trait that some employees have and others lack. It is a capability — and capabilities can be designed into workflows and built through practice. Three levers, drawn from the same research base:

1. Make the AI's reliability legible — per task, not in general

Aversion and over-reliance both thrive on vagueness. 'The AI is good' and 'the AI is bad' are both useless. Teams calibrate when they know where the tool is strong and where it is weak: which task types, which data conditions, which edge cases. Map your AI's competence to your actual workflow and make that map visible. Notably, Bansal's work suggests that simply showing the AI's confidence can support calibration better than elaborate explanations that mainly increase persuasion.

2. Give people authority to modify, not just accept or reject

A follow-up to the original algorithm-aversion work found something practical: people were far more willing to use an imperfect algorithm — and performed better — when they could adjust its output, even slightly. Binary 'accept the AI or don't' interfaces push teams toward one failure mode or the other. Workflows that let people keep agency and edit, override, or refine the AI's contribution produce more calibrated reliance and more durable adoption.

3. Train calibration with feedback, the way you'd train any judgment

People calibrate by seeing the consequences of their reliance decisions. When did deferring to the AI pay off? When did overriding it save you? Without that loop, the team learns from anecdotes — one vivid error becomes 'never trust it,' one lucky save becomes 'always trust it.' Build the loop deliberately: review where AI-assisted decisions landed, separate the AI's contribution from the human's, and treat miscalibration as a learning signal rather than a verdict on the tool.

None of these are technology problems. They are work-design and capability-building problems — which is exactly why they are solvable, and exactly why they are usually skipped.

How to know if your teams are calibrated

Calibration is measurable. A few signals worth instrumenting:

• Override accuracy. When people override the AI, are they usually right? When they accept it, was it usually correct? Low accuracy in either direction is miscalibration.
• The aversion fingerprint. Usage that spikes at launch and decays over the following months — especially after a visible AI error — is the signature of algorithm aversion, not normal 'novelty wearing off.'
• The over-reliance fingerprint. AI-assisted decisions that ship with near-zero edits, revisions, or recorded disagreement. Frictionless is not the same as good.
• Task-type fit. Are you pushing AI hardest into decision-heavy work, where the meta-analytic evidence shows losses cluster — instead of content-creation work, where gains cluster?

If you can't answer these, you are flying an AI transformation without instruments. Adoption dashboards count whether people use AI. Calibration is about how well — and that is the number tied to value.

The takeaway

The story of AI in organizations is often told as a contest: human versus machine, with one eventually winning. The evidence tells a quieter, more demanding story. The winner is neither the human nor the AI alone — it is the team that has learned to hand work back and forth at the right moments.

That skill is trust calibration. It sits directly downstream of psychological safety: a team has to feel safe enough to use AI honestly before it can learn to use it well. And it is the difference between 'augmentation without synergy' — the disappointing average — and genuine human-AI complementarity, where the team really does beat both of its parts.

The organizations pulling ahead aren't the ones with the most advanced models. Everyone has access to those. They are the ones treating calibration as a core capability — designed into workflows, measured like any other performance metric, and built through practice.

Sources

• Dietvorst, B. J., Simmons, J. P., & Massey, C. (2015). Algorithm aversion: People erroneously avoid algorithms after seeing them err. Journal of Experimental Psychology: General, 144(1), 114–126.
• Dietvorst, B. J., Simmons, J. P., & Massey, C. (2018). Overcoming algorithm aversion: People will use imperfect algorithms if they can (even slightly) modify them. Management Science, 64(3), 1155–1170.
• Logg, J. M., Minson, J. A., & Moore, D. A. (2019). Algorithm appreciation: People prefer algorithmic to human judgment. Organizational Behavior and Human Decision Processes, 151, 90–103.
• Vaccaro, M., Almaatouq, A., & Malone, T. (2024). When combinations of humans and AI are useful: A systematic review and meta-analysis. Nature Human Behaviour, 8, 2293–2303.
• Bansal, G., Wu, T., Zhou, J., Fok, R., Nushi, B., Kamar, E., Ribeiro, M. T., & Weld, D. (2021). Does the whole exceed its parts? The effect of AI explanations on complementary team performance. CHI '21.
• Lee, J. D., & See, K. A. (2004). Trust in automation: Designing for appropriate reliance. Human Factors, 46(1), 50–80.
• Parasuraman, R., & Riley, V. (1997). Humans and automation: Use, misuse, disuse, abuse. Human Factors, 39(2), 230–253.

Read the full article on Collaboration.tech

In our first article we described the AI Adoption Paradox: 92% of companies are increasing their AI investment, yet only 1% describe themselves as 'mature' in deployment. We argued that the gap between those two numbers is not technological — it's human. It lives in motivation, trust, competence, team design, and culture. The famous BCG 10-20-70 rule says it plainly: only 10% of the work of an AI transformation is about algorithms; 70% is about people and processes.

This article zooms all the way into that 70% — to the single most rigorously evidenced human variable in the entire picture. If you could measure and improve one thing to move your organization from the 99% toward the 1%, the research points clearly to one candidate: psychological safety.

What psychological safety actually is — and what it isn't

The term is over twenty-five years old. Amy Edmondson of Harvard Business School introduced it in a landmark 1999 study of 51 work teams in a manufacturing company, published in Administrative Science Quarterly. Her definition is precise and worth quoting exactly:

Psychological safety is a shared belief that the team is safe for interpersonal risk-taking — that you will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.

Read that twice, because almost every popular interpretation gets it wrong. Psychological safety is not about being nice. It is not comfort, harmony, or lowered standards. It is not the absence of pressure. It is the presence of a very specific freedom: the freedom to take an interpersonal risk — to ask the 'obvious' question, to admit 'I don't know how to do this,' to flag that something went wrong — without expecting it to cost you status, reputation, or career.

Google rediscovered this the hard way. Its two-year Project Aristotle study analyzed over 180 teams, expecting that the who of a team — individual talent, seniority, personality mix — would explain performance. It didn't. The strongest single predictor of team effectiveness turned out to be psychological safety. Academia had known this for thirteen years; Project Aristotle simply made the business world pay attention.

Why this matters more for AI than for almost anything else

The causal chain collaboration.tech works from looks like this: psychological safety → concrete behaviors (experimentation, error reporting, sharing discoveries across teams) → measurable adoption and learning → value creation. Without the first link, the rest of the chain never gets built — no matter how good the technology is.

The silent failure mode — shadow AI and the cost of low safety

When psychological safety is low, employees don't stop using AI — they hide it. They use personal accounts, paste sensitive data into consumer tools, and quietly compensate for an environment that punishes admission of uncertainty. This is shadow AI: invisible to leadership, ungoverned, unmeasurable, and impossible to learn from at the organizational level.

This is not a 'soft topic' sitting at the edge of the AI agenda. It is the agenda. AI is uniquely corrosive to psychological safety precisely because it makes the sentence 'I don't know how to do this' suddenly visible — and amplifies the quiet fear of becoming obsolete.

Three things most companies get wrong about psychological safety and AI

1. They treat it as sufficient. It isn't. Reich and colleagues found that psychological safety predicts whether employees start using AI — but not how often or how long they use it once they've started. It is the gate, not the engine. Sustained use is driven by workflow integration, perceived usefulness, and genuine task relevance. Build the gate, then build the road behind it.

2. They confuse safety with comfort. A psychologically safe team is not a conflict-free team. It is a team capable of productive discomfort — debating an AI's output, challenging an enthusiastic colleague, surfacing an uncomfortable doubt. Safety and high standards reinforce each other; they are not a trade-off.

3. They track the average instead of the distribution. The average attitude toward AI in a team tells you almost nothing. A team where everyone sits at 6/10 behaves completely differently from a team split between 10s and 2s. What matters is congruence — the spread, and which half of the team is enthusiastic and which is afraid. Bezrukova and colleagues make this concrete: when teams with a positive attitude toward AI were mandated to use it, their collaboration actually decreased.

How to measure it — diagnosis before intervention

Diagnosis points to intervention. The evidence base converges on a short list of things that genuinely move the needle. Leaders model fallibility first — when a leader says 'here's an AI mistake I made this week, and what I learned,' they give everyone permission to do the same. Reframe failure as 'intelligent failure' — Edmondson distinguishes blameworthy failure from the well-designed experiments at the edge of what's known, which is where almost all AI adoption lives. Frame AI as a learning challenge, not an evaluation — 'we're learning this together' builds safety; 'we're watching who adapts' manufactures shadow AI. Protect autonomy and basic psychological needs — Self-Determination Theory identifies autonomy, competence, and relatedness; blanket AI mandates damage all three, so give people genuine choice in how AI enters their workflow. And make space for the skeptics — the thoughtful skeptic with a real concern and no safe way to raise it is the person whose silence will cost you most.

The bottom line

Psychological safety is the gate to AI value. It is the highest-leverage part of BCG's 70% — and, unusually for a 'human' factor, it is concretely measurable, demonstrably improvable, and backed by one of the deepest evidence bases in organizational science. It does not guarantee a successful AI transformation. But its absence reliably guarantees a failed one — usually a quiet, expensive, shadow-AI kind of failure that never shows up cleanly in a quarterly review.

At collaboration.tech we treat AI transformation as a socio-technical problem: human-AI collaboration that becomes measurable team performance. If your organization is investing in AI but not yet winning with it, psychological safety is the first place we'd look — and the first thing we'd help you measure.

In the next article we'll move one link down the chain: trust calibration — why blind trust and reflexive distrust both wreck human-AI collaboration, and why 'appropriate reliance,' not enthusiasm, is the real goal.

Sources

• Edmondson, A. C. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly.
• Schepers, J., de Jong, A., Wetzels, M., & de Ruyter, K. (2008). Psychological safety and social support in groupware adoption. Computers & Education.
• Kim, S., Kim, J., & Lee, Y. (2025). The dark side of AI adoption: Organizational AI adoption and employee depression. Humanities and Social Sciences Communications.
• Tsagaroulis, R. (2025). AI adoption, psychological safety, and employee well-being. Loyola University.
• Bezrukova, K., Griffith, T. L., Spell, C., et al. (2023). Artificial Intelligence and Groups: Effects of Attitudes and Discretion on Collaboration. Group & Organization Management.
• Deci, E. L., & Ryan, R. M. (2000). Self-Determination Theory. American Psychologist.
• Google re:Work. Project Aristotle: Understanding team effectiveness (180+ teams, 2012–2014).
• Boston Consulting Group (2025). The Widening AI Value Gap: Build for the Future 2025.

Read the full article on Collaboration.tech

92% of companies plan to increase their AI investments over the next three years. Only 1% of leaders describe their organizations as 'mature' in their use of artificial intelligence. This isn't a statistical glitch or a survey error — it's the paradox that defines the current moment in business. And it reveals why the AI adoption problem isn't where most people are looking for it.

Welcome to the collaboration.tech blog. In this first post we show why AI transformation is, first and foremost, a psychological, organizational, and human challenge — and only after that a technological one. And why companies that understand this are already capturing twice the revenue growth of the rest of the market.

Three numbers that change how we think about AI

McKinsey's 'Superagency in the Workplace' report (January 2025) made the picture unambiguous: almost every company is investing in AI, and almost none is converting that investment into real value. In numbers:

• 92% of companies will increase their AI investment over the next three years
• 1% of organizations are 'mature' in AI deployment
• 47% of C-suite leaders believe their company is moving too slowly on AI

Boston Consulting Group, in its 'The Widening AI Value Gap' report (September 2025), adds an equally striking financial picture:

• 5% of companies are AI leaders ('future-built') — they systematically generate substantial value from AI
• 60% are laggards — minimal or zero financial returns despite their investment
• AI leaders expect twice the revenue increase and 40% greater cost reductions than laggards, in the areas where they apply AI

This is not a technology gap. It's an organizational one.

The 10-20-70 rule: where AI value actually comes from

BCG has articulated one of the most important principles of AI transformation today. It sounds simple — but its implications run deep:

10% of effort on algorithms. 20% on technology and data. 70% on people and processes.

Read that twice. Seventy percent. The bulk of the work in an AI transformation is work on humans — on motivation, trust, capability building, team design, decision-making structures, and organizational culture. Not on models, and not on cloud infrastructure.

Most companies do the exact opposite. 70% of their energy goes to technology, 20% to processes, and 10% — if anything — to people. That's the paradox. That's the 99% of organizations that can't convert investment into value.

The 'jagged frontier': when AI helps, and when it hurts

In 2023, Harvard Business School and BCG conducted one of the most rigorous studies to date on AI's impact on knowledge work. 758 BCG consultants (about 7% of the firm's global workforce) performed realistic tasks either with or without access to GPT-4.

For tasks inside the so-called 'frontier of AI capability' (Dell'Acqua et al., 2023), the results were striking:

• +12.2% more tasks completed
• +25.1% faster completion
• +40% higher quality

But there's a second finding that rarely gets discussed out loud. When the same consultants used AI on tasks outside that frontier — tasks AI isn't yet competent at — their performance was 19% worse than the group not using AI at all. Artificial intelligence didn't just fail to help. It actively hurt.

This 'jagged technological frontier' is one of the most important concepts for anyone deploying AI. Artificial intelligence isn't uniformly good or uniformly bad. It has patchy competence — and it demands judgment from humans about when to trust it and when to keep distance. That's a capability you can't buy with a license. You have to build it inside the organization.

Trust, psychological safety, and alienation

This is where it gets interesting — and where organizational psychology enters the picture in earnest.

Trust in AI erodes over time. Initial excitement about a tool gives way to disappointment as people discover its limitations (Schmutz et al., 2024). That's a natural psychological process — but for organizations it means the 'wow effect' of the first few weeks fades, and then the real work begins: calibrating expectations, designing processes, building respect both for what AI can do and for where it falls short.

What's more, research shows that adding AI to a team often reduces coordination, communication, and trust between people (Schmutz et al., 2024). Hybrid teams (Human-AI Teams, HATs) counterintuitively perform worse than teams without AI. Why? Because people don't know how to collaborate with an agent that has no intuition, doesn't remember yesterday's agreement, and doesn't feel the consequences of an error. This isn't a lack of training on the tool. It's a missing new mental model of collaboration.

Bezrukova et al. (2023) discovered an even more counterintuitive finding: when teams with a positive attitude toward AI were mandated to use it, their level of collaboration declined. When teams with negative attitudes received the same mandate, collaboration paradoxically rose. These are results you can't fix with better technology. They demand an understanding of psychology — autonomy, attitude congruence within a group, and power dynamics.

One small but important note: in measurements like these, the average attitude of a team tells you almost nothing. What matters is the distribution and the congruence. A team in which everyone sits at 6/10 behaves completely differently from a team in which half sit at 10 and half at 2 — even though the average is identical.

And this brings us back to psychological safety — the concept made famous by Amy Edmondson at Harvard Business School. Without it, employees won't experiment with AI. They won't speak up when AI is wrong. They'll hide their doubts. And the entire technology investment will turn out to be — a costly empty gesture. A Loyola University study (Tsagaroulis, 2025) found that poorly considered AI adoption undermines psychological safety, which in turn substantially increases the risk of depression among employees. This is not an add-on to a 'soft topics' agenda. This is the heart of the problem.

What actually separates leaders from laggards

Back to BCG: 'future-built' companies invest 120% more in AI transformation than the rest of the field. But the key difference isn't financial. The key difference is where they allocate their effort.

Leaders:

• anchor their AI strategy in the business vision — they don't buy AI for AI's sake; they embed it inside existing goals
• invest in people and processes versus technology at roughly 70:30 — the opposite of the rest of the market
• train more than half of their workforce in AI capabilities; laggards plan to train about one-fifth
• design new roles and career paths — instead of forcing AI into existing, unchanged positions
• actively manage trust and a culture of experimentation — because they know without it the whole investment collapses

In other words: AI leaders are companies that understand technology adoption is a change management project — not an IT project.

The limits of AI: what artificial intelligence won't do for you

Time for some honesty. AI handles business strategy well — data analysis, scenario modeling, generating decision options. Csaszar et al. (2024) showed that large language models can generate and evaluate strategies at a level comparable to human experts.

But AI won't write your mission. It won't generate a credible vision. And it certainly won't connect strategy with mission and vision in a way that's authentic and motivating to employees. This isn't a limitation of current models that will disappear with the next generation. It's a limitation in principle — because mission and vision are artifacts of human meaning, identity, and values. AI doesn't possess any of the three.

That's why real AI transformation in an organization isn't about replacing humans. It's about a deliberate division of roles between humans and AI — with full clarity about where each side has the advantage, and where its limits begin.

What 'psychologically informed' AI adoption looks like

At collaboration.tech we believe the gap between ambition and maturity — that famous gap between 92% and 1% — is currently the biggest market opportunity for companies willing to treat AI transformation as a sociotechnical problem. Concretely:

Measure the sources of trust problems with AI. Don't assume people will 'get used to it.' Diagnosis precedes intervention. You need to know what specifically in the employee's experience with AI is generating distrust — whether it's hallucinations, opacity, or a sense of lost control.

Separate social processes inside the team from transactions with AI. They aren't the same — even though they happen inside the same tools. Team cohesion has to be designed completely differently from collaboration with an AI agent.

Monitor and influence work motivation. Especially where 'algorithmic management' enters the picture. Research shows that intensive algorithmic management nearly doubles stress levels and increases psychosocial risks by 21% (Bowdler et al., 2026). That's not a price worth paying for efficiency.

Measure attitude congruence, not the average. Average team sentiment toward AI is misleading. The distribution — which half is enthusiastic and which half is afraid — determines actual dynamics.

Design capability development to prevent skill erosion. Over-reliance on AI leads to skill erosion, which Penttinen and Ruissalo (2025) demonstrated in an accounting firm: when the automation was removed, employees could no longer perform basic tasks. This isn't a doomsday scenario. It's a field study.

What you'll get by reading this blog

In upcoming posts on collaboration.tech we will:

• show concrete organizational-psychology tools that work in AI transformation
• analyze real-world company cases — both successes and painful failures
• explain the latest research at the intersection of AI, neuroscience, work psychology, and organizational design
• give you decision frameworks — no hype, no marketing, just an evidence-based approach

If your company sits somewhere between those 92% and 1% — investing, but not yet winning — you're in the right place.

In the next article we'll unpack psychological safety in the AI era — with concrete measurement and concrete interventions that work.

Sources

• McKinsey & Company (2025). Superagency in the Workplace: Empowering People to Unlock AI's Full Potential at Work.
• Boston Consulting Group (2025). The Widening AI Value Gap: Build for the Future 2025.
• Dell'Acqua, F., McFowland III, E., Mollick, E. R., et al. (2023). Navigating the Jagged Technological Frontier. HBS Working Paper 24-013.
• Schmutz, J. B., Outland, N., Kerstan, S., et al. (2024). AI-teaming: Redefining collaboration in the digital era. Current Opinion in Psychology.
• Bezrukova, K., Griffith, T. L., Spell, C., et al. (2023). Artificial Intelligence and Groups. Group & Organization Management.
• Csaszar, F. A., Ketkar, H., & Kim, H. (2024). Artificial Intelligence and Strategic Decision-Making. Strategy Science.
• Bowdler, M., et al. (2026). Algorithmic management and psychosocial risks at work. Scandinavian Journal of Work, Environment & Health.
• Penttinen, E., & Ruissalo, J. (2025). Skill erosion caused by AI. Aalto University.
• Asfahani, A. M. (2022). The Impact of Artificial Intelligence on Industrial-Organizational Psychology. The Journal of Behavioral Science, 17(3), 125–139.

Read the full article on Collaboration.tech

That gap has a name. Human-to-machine (H2M) collaboration — prompting, verifying, delegating to AI — is the visible layer. Human-to-human (H2H) collaboration — how distinct functional goals are aligned, how boundaries are spanned, how disagreement is made productive — is the scaffolding underneath. Skip H2H and AI just makes your silos faster.

Coordination is not collaboration

Most organisations confuse the two. Coordination is keeping parallel work from colliding. Collaboration is making distinct goals compatible across individual, team, department, and organisation — the textbook signature of teams that out-innovate. Without that alignment, every AI output gets re-litigated by hand, every handoff piles up at the same bottleneck, and the license fees keep auto-renewing.

The four mechanisms that actually move the needle

Our work — and the underlying research — converges on four mechanisms that turn diverse functions into one innovation engine. AI then amplifies the work; it does not replace it.

• Aligned goals across levels. Not 'common' goals — compatible distinct goals across individual, team, department, and organisation. This is where most AI rollouts quietly fail.
• Boundary spanning by design. Teams that scan markets, coordinate across functions, and engage leadership secure more resources and produce more innovation than inward-looking ones (Ancona & Caldwell; ~5.4× advantage).
• Cognitive diversity, productively used. Different functional lenses generate friction. Channelled well, that friction is the raw material of breakthroughs.
• Psychological safety. AI value leaks the moment people are afraid to flag a wrong output, a brittle workflow, or a bad assumption.

Why weak H2H breaks H2M

Dell'Acqua and colleagues (HBS / BCG) found consultants using GPT-4 on in-frontier tasks produced output ~40% higher in quality and worked 25% faster — but only when human judgment guided where AI should help. Hand the same tool to a team without aligned goals or safety to challenge outputs, and the lift disappears. The model isn't the variable. The H2H around it is.

Three diagnostic questions

• Can two team members from different functions independently rate the same AI output and agree within 10%? If not, you have an H2H quality-standard problem, not an H2M problem.
• When AI output is rejected, does the feedback flow back into the workflow — or die in someone's head? If it dies, you have an H2H learning-loop problem.
• Who decides when to escalate from AI to human? If the answer is 'it depends,' you have an H2H authority problem — and AI will only make it more expensive.

AI as tool, not teammate

AI removes friction in collaboration — search, drafting, translation between jargons, summarisation across silos. It does not align goals, build trust, or own a decision. People still do that work. Treating AI as a tool (not a teammate) is what lets the four mechanisms above compound instead of dilute.

Fix H2H first, then scale H2M

Every successful AI rollout we've shipped started with a short H2H reset: aligned goals across levels, explicit cross-functional handoffs, named owners for ambiguous calls, and enough safety to surface what isn't working. Then — and only then — does H2M scale cleanly. That is the order. Reverse it and you buy faster silos.

Read the full article on Collaboration.tech

The three layers of human-AI collaboration

We think about every engagement as three stacked layers: individual fluency (can each person prompt, verify, and escalate?), team coordination (where does AI sit in our handoffs?), and organizational governance (who owns risk, quality, and the feedback loop?). Skipping any layer creates the failure modes we keep seeing in the field.

Where to start: the 6-week pilot

• Week 1–2: Map the 3 highest-friction workflows. Don't pick the most exciting — pick the most painful.
• Week 3–4: Run a small pilot with 1 workflow and 4–6 people. Track cycle time, output quality, and adoption.
• Week 5–6: Decide. Kill it, scale it, or rebuild it. Document the operating-model change, not just the tool change.

The metrics that actually matter

Vanity metrics (logins, prompts sent) tell you nothing. Track three things: time-to-first-draft, rework rate, and the share of decisions where a human overrode the AI. The last one is your trust signal — if it's 100%, you don't have collaboration; if it's 0%, you don't have governance.

What to do this week

Pick one workflow. Write down the current cycle time. Run a 2-week pilot with one tool you already pay for. Measure again. That's the entire on-ramp — everything else compounds from there.

Read the full article on Collaboration.tech