Velocity is a term borrowed from physics that has found two distinct homes in the startup ecosystem. In physics, it is defined as the rate of change of position of an object with respect to a frame of reference. It is a vector quantity, meaning it requires both magnitude and direction.
In a business context, founders typically encounter this term in two specific departments: product development and sales.
At its core, velocity is a metric used to measure throughput. It answers how much value your organization is capable of capturing or creating within a set period.
Velocity in Agile Development
#For software startups, velocity is most often associated with Agile or Scrum methodologies. Here, it refers to the amount of work a development team can complete during a single sprint.
Work is usually measured in story points rather than hours. Story points represent the complexity of a task. If a team completes ten user stories worth a total of 30 points in a two-week sprint, their velocity is 30.
This metric serves a specific purpose. It helps with estimation.
If you know your team has an average velocity of 30, and your product backlog has 300 points of work remaining, you can reasonably predict that you need ten more sprints to finish.
It is important to note that velocity is not a performance target. It is a calibration tool. A higher velocity does not always mean a better team. It might just mean they are estimating points differently.
Velocity in Sales
#Sales Velocity measures how quickly leads move through your pipeline and generate revenue. It is arguably one of the most critical metrics for forecasting cash flow.
The formula usually looks like this:
(Number of Opportunities x Average Deal Value x Win Rate) / Length of Sales Cycle
The result tells you how much revenue you can expect to bring in per day.
If you have many opportunities and a high win rate, but your sales cycle takes a year, your velocity is low. This highlights a cash flow risk that a founder must address.
Speed vs. Velocity
#Founders often confuse speed with velocity. This is a dangerous mistake.
Speed is simply how fast you are moving. You can move very fast in circles. You can build features rapidly that no one wants. You can make a high volume of sales calls to the wrong demographic.
Velocity requires direction. It implies you are moving toward a specific goal, such as product-market fit or a closed deal.
In a startup, high speed with the wrong direction results in wasted capital. High velocity means you are efficiently closing the gap between where you are and where you need to be.
Using Velocity for Decisions
#You should use velocity to identify bottlenecks and capacity limits.
In development, track velocity over three to four sprints. If the number fluctuates wildly, your process is unstable. You cannot predict a launch date until that number stabilizes.
In sales, use velocity to determine which lever to pull. If you need more revenue, the math will tell you if you should focus on increasing the number of leads or decreasing the time it takes to close them.
We must ask ourselves if our metrics encourage the right behavior. If we obsess over increasing development velocity, does the team start inflating point estimates? If we push for sales velocity, do reps annoy prospects by rushing them?
Velocity is data. It allows you to make decisions based on historical reality rather than optimistic guesses.