Adoption Latency
The delay between an AI capability becoming available and a team actually incorporating it into working practice — a delay that scales with team size, because more people require more consensus before an unconventional or unproven tool is tried at all.
A small team can ship more with a new AI capability than a larger, better-resourced one, in the specific window right after that capability becomes available — before its use has been normalised, before best practice exists, before anyone else has proven it works for the specific problem at hand. The advantage is not raw output capacity. A larger team almost always has more of that. The advantage is speed to first attempt, and Adoption Latency is the name for what stands in the way of it: the delay between a capability becoming available and a team actually trying it in working practice.
The delay scales with team size, but not because larger teams lack talent or resources. It scales because more people require more consensus before an unconventional or unproven tool is tried at all. Two people can decide over lunch to try an unconventional approach with a tool that shipped last week. Twenty people need someone to champion the idea, a case for why it's worth the risk, and usually a fallback plan in case it doesn't work — and by the time all of that is assembled, the specific window in which trying it first mattered has often already closed.
Why this is not simply Coordination Tax under a different name. Coordination Tax measures the ongoing cost of keeping an existing structure functioning — the meetings, approvals, and status updates required to run as the team already operates. Adoption Latency measures something narrower: the delay before the team changes how it operates at all. A team with genuinely low Coordination Tax in its steady-state work can still have high Adoption Latency if trying something unconventional requires broad buy-in that routine operation does not. The two are correlated, because both scale with headcount, but they are not the same measurement, and a business can be efficient in its current operation while still being slow to try anything new.
**Why the window matters more than the eventual capability.** Every AI capability eventually becomes conventional. Best practices get written, case studies circulate, and the unconventional bet of one month becomes the standard approach of the next. Adoption Latency is not about who eventually adopts a capability — nearly everyone does, eventually. It is about who tries it first, while it is still unproven, while using it well is itself a competitive advantage rather than table stakes. A team's ability to occupy that window is determined less by its resources than by how many people have to agree before the attempt is made.
Adoption Latency is the structural precondition for the Latency Premium: the return captured specifically because a team's low Adoption Latency let it try an unconventional capability, and be right about it, before the window closed. Where Adoption Latency names the delay, the Latency Premium names what beating that delay is worth once the bet pays off — and the corresponding compensation mechanism, the Thesis Bonus, exists specifically because standard compensation structures are calibrated against team size and seniority, not against the low-consensus condition that Adoption Latency actually measures.
Application
Adoption Latency is tested by asking how long it takes an unconventional, unproven idea to move from being proposed to being actually tried — not by team size alone. A small team that still requires multiple rounds of justification before attempting something unconventional has high Adoption Latency despite its size. The genuine signal is whether the team can move from idea to attempt without needing to convince anyone who was not already going to be doing the work. A larger team attempting to compress its Adoption Latency needs to deliberately reduce how many people must agree before an unconventional attempt is made, typically by carving out a genuinely small, empowered sub-team with real latitude to try something without first securing broad organisational buy-in.
Context
Adoption Latency is distinct from Coordination Tax, which measures the standing cost of alignment a team already requires to keep functioning in its current state. Coordination Tax is a cost of steady state; Adoption Latency is a cost of change. A team can have relatively low Coordination Tax in its routine operations and still have high Adoption Latency if trying something genuinely new requires broad buy-in that routine operation does not. The two are correlated, because both scale with headcount, but they measure different things. Adoption Latency is also the structural precondition for the Latency Premium: a team's low Adoption Latency is what makes it possible to occupy the narrow window before an unconventional AI capability becomes an established best practice, and a Latency Premium is the return captured when that early bet is right.
This term is machine-readable
Any MCP-compatible AI assistant can retrieve the canonical definition of Adoption Latency at inference time — no training approximation.
First used: August 2026
Edition 1 · updated August 2026