Velocity is rate of change with direction — how fast you're moving and where. In physics it's displacement per unit time (vector); in product and orgs it's output per unit time in the direction that matters: features shipped, learning cycles, decisions made. Speed alone isn't enough; a team can be busy in the wrong direction. Velocity combines pace and alignment. High velocity in the right direction compounds: you learn faster, you capture opportunity before others, and you build momentum. Low velocity or velocity in the wrong direction wastes time and lets the market or competitors move first.
Physics gives the clean definition: velocity = displacement / time. Speed is magnitude; velocity adds direction. In strategy, the analogue is throughput in the direction of the goal. Sprint velocity in agile is a proxy: story points per sprint. The limit on velocity is usually not raw effort but bottlenecks — dependencies, approval, context-switching — or misalignment so that motion doesn't translate into forward progress. Increasing velocity means removing friction, parallelising work, and ensuring that "fast" is fast toward the target.
The strategic use: measure velocity in the dimension that matters (revenue, learning, quality-adjusted output). Optimise for that. Remove bottlenecks and reduce cycle time. Distinguish velocity from activity — more meetings and more tasks can be low velocity if they don't move the needle. The mistake is equating busyness with velocity. The second mistake is optimising for local velocity (one team) at the expense of end-to-end velocity (outcome to customer or market).
Section 2
How to See It
Velocity shows up as cycle time, time to market, decisions per week, or learning loops per month. Look for "how long from idea to shipped?" and "how many iterations did we get?" When teams complain about slowness, they're usually describing low velocity — something is capping the rate of useful output.
Business
You're seeing Velocity when a company measures time from concept to revenue or from bug report to fix. The metric is output per unit time in the direction that matters. High-velocity companies ship often, learn fast, and adjust. Low-velocity companies have long release cycles and slow feedback. The difference is often process (approvals, dependencies) and alignment (everyone pulling the same way).
Technology
You're seeing Velocity when eng measures deployment frequency, lead time (commit to deploy), or sprint velocity. The goal is not just "we're coding" but "we're delivering value at a rate." CI/CD and small batches are velocity enablers; long-lived branches and big releases are velocity killers. Direction matters: velocity toward the right product beats velocity toward the wrong one.
Investing
You're seeing Velocity when you assess how fast a company can iterate — on product, on GTM, on strategy. Startups that can run many small experiments per quarter have high learning velocity. Those stuck in long planning cycles or slow release processes have low velocity. The best founders create organisations that maintain or increase velocity as they scale.
Markets
You're seeing Velocity when time-to-market determines who wins. First mover, fast follower, or fast learner — the player that can move from insight to action fastest often captures the opportunity. Market velocity (rate of change in the environment) also matters: in fast-moving markets, organisational velocity must match or exceed it.
Section 3
How to Use It
Decision filter
"Measure velocity in the dimension that matters: output per week/month toward the goal. Is the bottleneck capacity, process, or alignment? Remove the bottleneck. Ensure 'fast' is fast in the right direction — not just activity."
As a founder
Optimise for end-to-end velocity: idea to customer value. That usually means small batches, short cycles, and fewer approval layers. Measure deployment frequency, time to decision, and learning cycles. The mistake is adding process that slows velocity without improving quality. The second mistake is measuring activity (hours, tasks) instead of velocity (value per unit time). When velocity drops as you scale, find the bottleneck — often it's coordination or decision rights.
As an investor
Assess whether the company can sustain or increase velocity as it grows. High early velocity that collapses at 50 or 200 people is common; the ones that scale velocity have built systems (delegation, autonomy, clear goals) that don't cap throughput. Ask: how many iterations per quarter? How long from decision to outcome?
As a decision-maker
Use velocity to prioritise. When something is slow, diagnose: is it capacity (need more people or tools), process (approvals, dependencies), or alignment (moving in wrong direction)? Fix the bottleneck. Protect velocity in the core loop — the thing that directly drives the goal — even if it means saying no to side work.
Common misapplication: Confusing velocity with speed in the wrong direction. A team can ship fast into a dead end. Velocity is rate of progress toward the goal. Align direction first; then maximise rate.
Second misapplication: Sacrificing quality for velocity. Short-term velocity that creates tech debt or customer harm reduces long-term velocity. Sustainable velocity balances pace with quality and learning. Sometimes slowing down one cycle improves the next.
Hastings built Netflix for speed of iteration: A/B tests, rapid content and product decisions, "context not control." The company's velocity in trying ideas and killing what doesn't work is a competitive advantage. Velocity is maintained by high talent density and loose process — fewer layers, more ownership.
Musk pushes for maximum iteration velocity: "move fast," rapid prototyping, test to failure. SpaceX runs many test cycles; Tesla iterates on production and product quickly. The bottleneck is often production or supply chain; velocity is measured in "how many iterations per year" and "time to next test."
Section 6
Visual Explanation
Velocity — Rate of useful output in the direction of the goal. Bottlenecks cap it; alignment and small batches increase it.
Section 7
Connected Models
Velocity ties to momentum, iteration, and the speed of learning and execution. These models either define it or help increase it.
Reinforces
[Momentum](/mental-models/momentum)
Momentum is mass times velocity. In organisations, momentum is velocity sustained — the flywheel effect. High velocity builds momentum; momentum makes the next unit of velocity easier. The two reinforce: velocity creates momentum; momentum protects velocity.
Reinforces
Iteration Velocity
Iteration velocity is the rate of cycles (build, measure, learn). It's velocity in the dimension of learning. High iteration velocity means more experiments per quarter, faster product-market fit, and faster adaptation.
Reinforces
Time Value of Shipping
Shipping earlier has value: learning, revenue, competitive position. Velocity is the rate at which you capture that value. The faster you ship, the higher the time value you capture. The two are directly linked.
Leads-to
[Feedback](/mental-models/feedback) Loops
Faster velocity shortens feedback loops: you ship, you learn, you adjust. Tight feedback loops improve the next cycle. Velocity and feedback loops are mutually reinforcing — velocity enables fast feedback; fast feedback improves velocity by reducing rework and misdirection.
Section 8
One Key Quote
"In order to win, we should operate at a faster tempo than our adversaries. … We should operate inside their time scale. So we are inside their OODA loop."
— John Boyd, OODA Loop
Boyd's insight: velocity through the observe-orient-decide-act cycle determines who wins. Operating "inside their loop" means your velocity is higher — you act before they've finished orienting. Velocity is the competitive variable.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Measure velocity, not activity. Hours worked and tasks completed are poor proxies. Output per unit time toward the goal — deployments, decisions, learning cycles — is velocity. Define the goal, then measure rate of progress.
Find and fix the bottleneck. Velocity is capped by the slowest step. Often it's approval, dependency, or coordination. Remove or parallelise the bottleneck. Don't add capacity elsewhere until the bottleneck is addressed.
Direction matters. Velocity in the wrong direction is waste. Align the team on the goal; then maximise rate. If velocity is high but outcomes are wrong, fix direction first. Velocity without alignment is chaos.
Small batches increase velocity. Large batches (big releases, big projects) create long wait times and late feedback. Small batches reduce cycle time and rework. They feel slower per item but usually increase end-to-end velocity.
Protect the core loop. The loop that directly drives the goal (e.g. ship → learn → iterate) should have the highest velocity. Say no to work that doesn't feed that loop or that slows it down. Velocity in the core loop compounds.
Section 10
Test Yourself
Is this mental model at work here?
Scenario 1
A team ships 50 story points per sprint but product metrics don't improve. Another team ships 20 points and metrics move.
Scenario 2
Releases take 6 weeks because of approval and QA gates. The team wants to ship every 2 weeks.
Scenario 3
A startup runs 3 experiments per week on pricing and positioning. A competitor runs 1 per quarter.
Scenario 4
A company celebrates 'everyone is so busy.' Roadmap slips; few features ship.
Section 11
Top Resources
Summary: Velocity is rate of useful output in the direction of the goal. Measure it, find the bottleneck, and protect the core loop. Don't confuse activity with velocity or speed in the wrong direction with progress.
Boyd's loop: observe, orient, decide, act. Velocity through the loop — tempo — determines competitive advantage. The source of "get inside their loop."
Build-measure-learn as the core loop. Velocity of that loop (how fast you cycle) is the key to finding product-market fit. Small batches and rapid experimentation.
DevOps and delivery performance. Deployment frequency, lead time, and time to restore as velocity metrics. Data on what increases velocity in software.
Shipping earlier has value. Velocity is the rate at which you capture that value. The faster you ship the right thing, the more value you capture.
Leads-to
[OODA Loop](/mental-models/ooda-loop)
OODA (observe, orient, decide, act) is the decision-action cycle. Velocity through the loop — how fast you complete a cycle — determines who wins in competitive and uncertain environments. High velocity is fast OODA.
Tension
Speed
Speed is raw rate; velocity is rate with direction. Pursuing speed without alignment can mean fast in the wrong direction. The tension: maximise speed in the direction that matters; don't confuse activity with velocity.
