Everyone is faster. Who is keeping the team aligned?
I ask founders a simple question when I first meet them: what are your tasks today?
Two years ago, the answer was a list of tickets. Now, at companies somewhere past Series A, I often hear: "I've got this Claude thread, and this Claude thread, and this Claude thread." Some teams have drifted away from Linear and email. Everyone has locked in on their own agents. Output is up. A company brain has to keep the rest of the team in view.
Then I ask how they know two people aren't doing the same thing. Nobody has an answer. We see the cost in sales-to-delivery handoffs at consultancies.
That is the alignment problem I see in 2026. Every person is moving faster, while the company struggles to keep up with itself.
Alignment was already expensive
Coordination cost a lot before anyone had an AI assistant. In 2012, McKinsey estimated that interaction workers spent almost 20% of the week finding internal information or tracking down colleagues. Asana's 2023 survey of 9,615 knowledge workers put "work about work" at 58% of their time.
Atlassian's State of Teams 2025, based on 12,000 knowledge workers and 200 Fortune 1000 executives, found that one in two workers said teams had worked on the same things without knowing it. Only 7% of executives felt confident they knew how every team's work supported company goals.
Microsoft adds the texture. Its 2025 Work Trend Index found about half of employees and leaders described work as chaotic and fragmented. Among the top 20% of users by incoming ping volume, the average gap between interruptions during core working hours was two minutes.
These studies use different definitions and populations. They describe a familiar cost: when knowledge lives in separate heads, inboxes and threads, finding out becomes a job of its own.
Then everyone got faster
The individual gains from AI are real. The organisation doesn't collect those gains by default.
Faros AI analysed telemetry from more than 10,000 developers across 1,255 teams. In higher-adoption periods, developers completed 21% more tasks and merged 98% more pull requests. Review time per pull request rose 91%. At company level, Faros reported no significant correlation between AI adoption and improvement.
Google's DORA 2025 research, drawing on almost 5,000 technology professionals, found a positive relationship between AI adoption and delivery throughput, alongside a negative relationship with delivery stability. Its argument is that AI amplifies the systems around it.
These are observational findings about software teams. They echo what I hear in funds, consultancies and scale-ups: people can get far enough alone that they skip the alignment conversation.
One person described the change well. Previously, everyone would bullet-point a solution together before starting. Now you build it, and discover later that a colleague built something next to it.
AI adds more places for context to drift
Silos now sit inside silos
Each person has several threads, and every thread carries its own context. You can end up with five single sources of truth: two in one person's threads, one elsewhere, two more over here. Each makes sense on its own terms. None is guaranteed to reflect the others.
More participants create more possible connections
Brooks's communication-path model gives a group of n participants n(n − 1) / 2 possible pairwise connections. Ten people have 45. Add ten agents and the fully connected model has 190. Real teams do not maintain every connection, but the arithmetic shows how fast coordination can expand.
Microsoft now proposes a human-agent ratio as a management metric. In its 2025 survey, 46% of leaders said their organisations were already using agents to fully automate workflows or processes.
Agents have started asking each other
Nicolas Bustamante described his agent messaging a colleague on Teams, and the colleague's agent answering from its own context. The exchange makes the coordination question more urgent: where is the shared record, and what may each agent disclose?
What misalignment looks like up close
These examples come from client and prospect calls over the past year. The organisations are anonymised.
Two documents, one methodology
A private equity fund and our team were defining a scoring methodology. A spreadsheet and a written document were both meant to be authoritative. Someone noticed they disagreed. The answer was "this one is more up to date": an uncomfortable sentence about a methodology that ranks investments.
The deep dive nobody knew about
The same fund's origination team flags a company in the CRM when research starts, so colleagues do not duplicate it. The flag exists because the duplication had happened before. Manual tagging was the defence.
Everyone grinding the same data room
An investor at a venture fund told me she had no idea what colleagues were researching. Everyone ran their own process. When a hot deal arrived, the team analysed the same data room in parallel and the firm paid for the same answer several times.
Three versions of the scope
In delivery projects, the statement of work can say one thing, the sales conversation another, and the engineers build to a third. An alignment call follows when someone notices. A shared record can expose the disagreement earlier.
The company that went back to tickets
A fast-growing AI startup we are onboarding told us alignment had become a theme at its current size. Its response was more discipline with the ticket tracker: a return to a practice the team had been leaving behind.
The org chart and the working map
When we map collaboration from permitted meetings, chat and email, the picture often differs from the org chart. People expected to work together may seldom talk. The gap is hard to discuss until somebody draws it.
Two threads, one shared record
What's the latest on the Acme deal?
Analyst A
Phase one: full scope.
Earlier scope documentAnalyst B
Phase one: reduced scope.
Approved 4 Oct · Deal desk noteEmail, chat, documents and CRM queried one at a time.
Same question. Different versions.
Missing information and different judgement need different fixes
Sometimes two people disagree because they have seen different things. One read the update. One heard the client call. The disagreement can disappear once both see the evidence.
Sometimes they have seen the same evidence and weigh it in different ways. That is healthy judgement, and it is where a team earns its pay.
In my experience, the information gap is more common, and it crowds out the useful disagreement. Meetings go on establishing facts before anyone can debate a decision.
The aim is a record that keeps itself current, so the meeting can debate what the evidence means instead of spending the hour establishing it.
A company brain helps close the information gap. The judgement stays with the team.
Give the work a shared memory
A company brain holds what the team knows from the places work happens: chat, meetings, email, documents, tickets and the CRM. People and their agents can ask it anything they are allowed to see, from one place.
Start each thread from current company context
Every agent starts from the same company record instead of each rebuilding it from scratch. Where two people have the same access, their answers draw on the same evidence. Where access differs, the answers differ too.
Write completed work back
When an analyst finishes research, the findings go back into the brain with their supporting evidence and access rules. The next authorised person picks up the analysis instead of repeating it. One fund we work with applies its investment thesis across its universe this way, updating it as people learn something proprietary. The alignment improvement mattered more than the speed improvement, which I did not predict.
Keep dates and sources attached
Your team can see when a fact changed in its source, and where it came from. Conflicting versions show up side by side. A date alone does not decide which document is authoritative, but it gives the team evidence to resolve the disagreement.
Give the same thing one identity
The same company, person or project shows up as one record, even when each system names it differently. People discussing "the Acme deal" work from the same picture.
Tell people before they collide
A daily or weekly brief can put the deal desk's latest position in front of the account lead before the client call. The brain tells people about relevant changes as well as answering questions.
Make the collaboration map visible
Within the information a reader is allowed to inspect, a collaboration map can reveal working relationships the org chart misses. It gives leaders a starting point for a conversation about handovers.
Keep private context private
Alignment does not require a company-wide view of everyone's inbox. Each person sees only what the source systems already let them see. Private personal context stays separate from shared company knowledge. Read how the brain knows who is asking.
What a brain cannot settle
It records what was written and said in the systems it reads. Knowledge that never left someone's head stays there. Transcripts and chat capture some of it, but never all of it.
Capture also changes behaviour. Someone joining a company where calls were recorded and shared described the consequence: sensitive conversations moved somewhere that was not tracked. Permissions reduce that pressure because private conversations can stay private. The tension still deserves attention when designing a rollout.
And if two partners read the same evidence and disagree, the brain can help them reach the evidence faster. It cannot make their decision for them.
Start where duplicated work costs most
For a fund, that may be deal research. For a software company, it may be the handover between sales, product and engineering.
Connect the channels where decisions happen. One recent pilot began with team chat, the meeting assistant, the wiki and the issue tracker. Those four covered much of the decision trail.
Start a daily or weekly brief early. Then measure how often people begin the same work, how long it takes to establish which version is current, and how many meetings exist to assemble facts.
If the brain is useful, those costs should fall. The meetings worth keeping are the ones where people make decisions from shared evidence.
With 60x, your first company brain use case is live in two weeks, with scope and access agreed before we start. Choose 60x Cloud with EU or US residency, or Your Cloud inside your own Azure, AWS or GCP cloud environment. See the installation plan. Book a demo.
Sources
- McKinsey Global Institute, The social economy, July 2012.
- Asana, Anatomy of Work Global Index 2023, March 2023.
- Atlassian, The State of Teams 2025.
- Microsoft, 2025 Work Trend Index: The year the Frontier Firm is born, April 2025. See its methodology for the interruption measure.
- Faros AI, The AI Productivity Paradox Report 2025. Analysis reflects data as of June 2025.
- Google Cloud, Announcing the 2025 DORA Report, September 2025.
- Frederick P. Brooks Jr., The Mythical Man-Month, 1975. Pairwise-path calculations are illustrative.
- Nicolas Bustamante, post on X, September 2026.
Client and prospect examples are anonymised. They describe our experience, rather than controlled research.