Velocity Gap
The gap between where the operational bottleneck has moved (clarity, ambition and distribution) and where organizational habits remain stuck (protecting execution capacity).
AI Strategy Glossary
Definitions of the terms Edward Chenard uses in his frameworks and guides: the Velocity Gap, the 8 Friction Defaults, the B1/B2/B3 portfolio, the Profit Center levels and more. Every entry links to the free article where it is explained in full and to the guide that turns it into a plan.
Velocity Gap · Friction Defaults · Permission Loop · Polish Paralysis · Meeting Dependency · Structured Waiting · Planning Inversion · Deck Over Demo · Consensus Lock · Readiness Hoarding · B1 (Break Even) · B2 (Break Through) · B3 (Break Away) · Profit Center Framework · Agent Yield Framework (AI Agent P&L) · So What Framework · Phronetic AI Framework · Strategic Architect · Semantic Mirror
Core ideas
Friction Defaults
Risk-management rituals that made sense when execution was expensive. They have calcified into organizational reflexes that persist despite the inversion of costs. The Velocity Gap Framework names eight of them.
The eight: Permission Loop, Polish Paralysis, Meeting Dependency, Structured Waiting, Planning Inversion, Deck Over Demo, Consensus Lock, Readiness Hoarding.
The 8 Friction Defaults
Permission Loop
The Slack conversation to get approval now takes longer than building the prototype. The email thread to confirm direction takes longer than trying both directions.
- Old logic
- Check before you do. Get buy-in before spending precious resources.
- New reality
- The Slack conversation to get approval now takes longer than building the prototype. The email thread to confirm direction takes longer than trying both directions.
- The fix
- Default to doing. Build rough versions first. Ask forgiveness, not permission. Leaders must cast wider vision so teams can ship autonomously within guardrails.
Polish Paralysis
People spend 80% of time on the last 20% of quality while the marginal value of polish drops. Polish becomes procrastination, a way to avoid getting ideas into contact with reality.
- Old logic
- You get one shot, so make it count. Don't waste execution on half-baked ideas.
- New reality
- People spend 80% of time on the last 20% of quality while the marginal value of polish drops. Polish becomes procrastination, a way to avoid getting ideas into contact with reality.
- The fix
- Ship ugly. The rough version that exists beats the polished version that doesn't.
Meeting Dependency
An hour of six people's time is 6 hours of work, often enough to just build the thing. Meetings about what to build often don't resolve what to build; they surface opinions and create delays.
- Old logic
- Get alignment before action. Get everyone in the room so we don't waste expensive execution time.
- New reality
- An hour of six people's time is 6 hours of work, often enough to just build the thing. Meetings about what to build often don't resolve what to build; they surface opinions and create delays.
- The fix
- Replace meetings with product demos. "What if I built the rough version and showed people instead?"
Structured Waiting
Waiting an hour in 2026 costs a prototype. You're outsourcing momentum to other people's calendars. Most of what you're waiting for doesn't need to be waited for.
- Old logic
- Coordination matters. Wait for feedback. Respect the process.
- New reality
- Waiting an hour in 2026 costs a prototype. You're outsourcing momentum to other people's calendars. Most of what you're waiting for doesn't need to be waited for.
- The fix
- Stop waiting. Do the next thing while waiting for feedback on the first. Assume the answer is yes. Make provisional decisions and keep moving.
Planning Inversion
This has literally inverted. Prediction is now expensive (and usually wrong); doing is cheap (and provides accurate data).
- Old logic
- Measure twice, cut once. Planning is cheap; execution is expensive.
- New reality
- This has literally inverted. Prediction is now expensive (and usually wrong); doing is cheap (and provides accurate data).
- The fix
- Cut planning by 90%. Let reality inform the plan through aggressive prototyping. If you haven't built something in two weeks, you're overplanning.
Deck Over Demo
A working prototype is more persuasive than a static presentation.
- Old logic
- Build consensus through presentations. Create "walking around decks" to get stakeholder buy-in.
- New reality
- A working prototype is more persuasive than a static presentation.
- The fix
- Build the demo, not the deck. Show working software. Why envision when you can demonstrate?
Consensus Lock
Consensus is a "priceless" drag on velocity, and it often isn't real anyway. People agree in meetings then undermine decisions later.
- Old logic
- Get everybody aligned before action. Distribute accountability through agreement.
- New reality
- Consensus is a "priceless" drag on velocity, and it often isn't real anyway. People agree in meetings then undermine decisions later.
- The fix
- Let results create alignment. "I tried X and here's what happened" is more persuasive than "Let's agree to try X." Run experiments first, align on data.
Readiness Hoarding
Sitting on drafts until "ready" means getting feedback too late to change direction. Finding out you're wrong in one week beats finding out in one month.
- Old logic
- Don't show work until it's complete. Half-finished work wastes other people's time.
- New reality
- Sitting on drafts until "ready" means getting feedback too late to change direction. Finding out you're wrong in one week beats finding out in one month.
- The fix
- Practice "ego death." Show raw, unfinished work. The discomfort of early feedback is far cheaper than the cost of late pivots.
Portfolio and maturity models
B1 (Break Even)
Table-stakes AI projects needed to stay competitive. If you do not do these, you fall behind.
B2 (Break Through)
Competitive-edge projects aimed at a 2-3x improvement on key metrics.
B3 (Break Away)
Industry-defining moves with 10x potential and an acceptable failure rate.
Profit Center Framework
A 4-level maturity model for data teams: Level 1 Descriptive Reporting, Level 2 Diagnostic Insights, Level 3 Prescriptive Recommendations, Level 4 Direct Revenue Generation. Teams at Level 4 generate revenue instead of being viewed as overhead.
Guide frameworks and related ideas
Agent Yield Framework (AI Agent P&L)
Replaces headcount-replacement math with a full agent P&L: revenue lines, five cost layers, and pilot-to-production decision gates.
So What Framework
Takes analytical work from data dump to strategic recommendation, with scripts for each level of maturity.
Phronetic AI Framework
Explains why answer-machine AI gets abandoned and how to redesign systems so expert users adopt them.
Strategic Architect
A 19-chapter operating guide for finance-led AI, including regulatory exposure and a 100-day roadmap.
Semantic Mirror
Why 85% of AI projects fail for the same reasons Big Data projects failed, summarized by the 10-20-70 principle.
Not sure where to start? Find the right guide for your situation or take the free Velocity Gap Diagnostic. Related: the full framework map · What Is the Velocity Gap?.