Why Some Teams Win With AI and Most Don't

AI amplifies whatever foundation a team already has. The winners redesigned how they work. The losers bolted AI onto the old process. Here is what that means in practice.

Why Some Teams Win With AI and Most Don't

By now the numbers are familiar. MIT's Project NANDA found that about 95% of enterprise AI pilots produce no measurable impact on the bottom line. McKinsey found that only around 6% of companies are capturing real EBIT from AI. PwC's January 2026 CEO survey found 56% of chief executives had seen neither higher revenue nor lower cost from AI in the past year.

Everyone has the same models. So the interesting question is not why most fail. It is what the small group that succeeds is doing differently.

The research gives a consistent answer, and it is not the one most companies act on.

The winners redesigned the work. The losers added a tool.

McKinsey's 2025 State of AI is blunt about it. The single strongest predictor of whether a company captures value from AI is whether it redesigned its workflows around AI, rather than layering AI on top of how it already worked. The roughly 6% of firms it classifies as high performers are close to three times more likely to have redone their workflows than everyone else.

The MIT study reaches the same place from the failure side. It found most pilots fail not because the models are weak but because of "brittle workflows, lack of contextual learning, and misalignment with day-to-day operations." The tool was fine. The work around it was not.

A 2026 analysis of AI in team collaboration put the underlying rule in one sentence: AI amplifies whatever foundation is already there. Teams with clear processes and strong collaboration ship faster with fewer redos. Teams with weak foundations get more noise, more cleanup, and the same old delays, produced faster.

That is the whole finding. AI is a multiplier. It does not create a foundation. It scales the one you have, in whichever direction it already points.

Why "add a tool" keeps failing

Most companies bought AI to make an existing step faster. Draft the copy quicker, generate the images quicker, write the code quicker. The BU Questrom analysis of failed pilots notes that this rarely changes outcomes, because speed at one step does not help if the value never depended on the speed of that step.

Production was the step everyone sped up, and production was already the easy part. What determines whether the work is any good happens before and after it: deciding what is worth making, comparing the options, judging which one is right, and getting a team to agree and act. Those steps did not get faster. In many companies they got slower, because now there is more output piling up in front of them.

So the money went into the one part that was not the constraint, and the actual constraint, the thinking and deciding, was left sitting in the same scattered tools it was always in.

The foundation is the process, and most tools throw it away

If the foundation is what wins, it is worth asking where the foundation actually lives.

It is not in the finished deliverable. The deliverable is the output, and by the time you are looking at it the thinking is over. The foundation is the process that produced it: the rough idea, the research it ran into, the options that were considered, the reason one was chosen and the others were not, the feedback, the disagreement, the decision.

That process is exactly what most tools cannot hold. Chat is a line, so the reasoning scrolls away and dies in the thread. A document keeps the conclusion but not the path to it. A task board keeps what to do but not why. So the process evaporates, and all that survives is the result, which means the thing the research says wins, the foundation, is the thing companies are least equipped to keep.

There is a strategic cost to that. Mercer's 2026 work on AI notes that organizational capability develops "through practice rather than planning," by watching how work actually gets done and building on it. If the process disappears every time, the team never compounds. Each project starts from scratch. Nobody learns how the good work got made, because only the polished end of it was ever visible.

Where ALLO fits

This is the specific thing we built ALLO to do. It holds the process, not just the result.

A rough note sits on a canvas. Research gets pulled in next to it. Options are generated and laid side by side so a team can actually compare them instead of scrolling past them. Feedback attaches to the thing it is about. The decision stays next to the work that earned it. An idea starts small in one corner, grows as it collides with research and other people, and narrows toward something the team ships, and the whole path stays visible.

That is not a nicer whiteboard. It is the place where the foundation the research keeps pointing at, the process, the thinking, the reasoning behind a decision, has somewhere to live and compound instead of scrolling away. You keep making things in the tools you already use. What ALLO adds is the layer the winning teams have and the rest lose: a visible, shared record of how the work actually got thought through.

The evidence is consistent across MIT, McKinsey, and the rest. AI rewards teams that have a strong foundation and punishes teams that do not, because all it does is multiply what is there. The tool is now a commodity. The foundation is the whole game. The only question worth asking is whether your team has somewhere to build one.


FAQ

What separates teams that succeed with AI from teams that fail? Workflow redesign. McKinsey found the roughly 6% of companies capturing real value from AI are about three times more likely to have redesigned how they work around it, rather than bolting AI onto existing processes. AI amplifies the foundation a team already has.

Why do most AI pilots fail? MIT's Project NANDA found about 95% produce no measurable bottom-line impact, mostly due to brittle workflows and misalignment with daily operations rather than weak models. The tool was rarely the problem.

Why doesn't making production faster improve results? Because production was already the easy part. Value depends on deciding what to make, comparing options, and choosing well, and speeding up generation does not help those steps. It often overloads them.

What does it mean that AI is a multiplier? AI scales whatever foundation exists. Strong process and collaboration get amplified into faster, cleaner delivery; weak foundations get amplified into more noise and rework. It does not create a foundation on its own.

How does ALLO help teams win with AI? ALLO holds the process, not just the finished output. Ideas, research, options, feedback, and decisions live together on one canvas, so a team's reasoning stays visible and compounds over time, which is the foundation the research says separates winners from the rest.