Definition: The Velocity Gap is the distance between where the bottleneck in AI-era work has moved (clarity, ambition and distribution) and where organizations still guard it (execution capacity). Edward Chenard's Velocity Gap Framework names eight Friction Defaults, legacy habits that keep that distance open.
The definition
The Velocity Gap is the gap between where the operational bottleneck has moved, to clarity, ambition and distribution, and where organizational habits remain stuck, protecting execution capacity.
When building something was slow and expensive, it made sense to check before acting, plan carefully and align everyone first. Those habits protected scarce execution time. As AI makes building cheaper, the scarce things become knowing what to build, wanting to build something bigger, and getting it in front of people. The habits stay; the reason for them does not. That distance is the Velocity Gap.
The 8 Friction Defaults
The framework calls the habits Friction Defaults: risk-management rituals that calcified into reflexes. Each now costs more than the execution it was designed to protect.
- Permission Loop: Getting approval takes longer than building the prototype.
- Polish Paralysis: Polishing replaces getting ideas into contact with reality.
- Meeting Dependency: Meetings about what to build surface opinions instead of resolving the question.
- Structured Waiting: Momentum is outsourced to other people's calendars.
- Planning Inversion: Planning is treated as cheap and execution as expensive, when doing is now often the cheaper way to learn.
- Deck Over Demo: Static presentations are used where a working prototype would persuade more.
- Consensus Lock: Alignment is sought before action, and often is not real anyway.
- Readiness Hoarding: Work stays hidden until it is "ready", so feedback arrives too late to change direction.
Each default has its old logic, new reality and a fix in the glossary and in the full article.
How to measure it
Score your organization from 1 (rarely present) to 5 (deeply embedded) on each default. Add the eight scores.
| Total | Reading |
|---|---|
| 8 to 16 | AI-native ready. Focus on the new bottlenecks: clarity, ambition and distribution. |
| 17 to 28 | Moderate friction. Target the top two or three defaults for immediate intervention. |
| 29 to 40 | Severe Velocity Gap. Organizational change is needed before AI initiatives can succeed. |
The free Velocity Gap Diagnostic walks through the scoring, and the checklist turns each default into a question.
What it is not: other uses of "velocity gap"
The phrase is used elsewhere, which causes confusion. In February 2026, after Cognizant's Q4 2025 earnings call, its CEO Ravi Kumar described an "AI velocity gap" as the disconnect between money spent on AI infrastructure and the business value it produces. That is a statement about outcomes: value lagging spend.
The Velocity Gap Framework is about organizational habits that slow work down. One way to connect the two is interpretation, not a claim by either source: if value lags spend, the habits that slow redesign and learning are one candidate cause worth testing. Both can be true at once.
Where to go next
- Read the full argument: The Velocity Gap Framework (free).
- Check where you stand: the free diagnostic.
- Get the 90-day plan: The Velocity Gap Framework guide ($29), with role-specific action plans and worksheets.
- Not sure which guide you need: find the right one.
Frequently asked questions
What is the Velocity Gap?
The gap between where the operational bottleneck has moved, to clarity, ambition and distribution, and where organizational habits remain stuck, protecting execution capacity.
What are the 8 Friction Defaults?
Permission Loop, Polish Paralysis, Meeting Dependency, Structured Waiting, Planning Inversion, Deck Over Demo, Consensus Lock and Readiness Hoarding. Each is a risk-management ritual that made sense when execution was expensive.
Is this the same as Cognizant's "AI velocity gap"?
No. Cognizant's CEO used the phrase in February 2026 for the disconnect between AI infrastructure spending and business value. The Velocity Gap Framework by Edward Chenard is about organizational habits that slow work.
How do I measure my Velocity Gap?
Score your organization from 1 (rarely present) to 5 (deeply embedded) on each of the eight Friction Defaults. A total of 8 to 16 is AI-native ready, 17 to 28 is moderate friction, and 29 to 40 is a severe Velocity Gap.