Velocity

Velocity

Core Concept

Speed is meaningless without direction - velocity combines rate of movement with vector alignment toward goals. Moving fast in the wrong direction is worse than moving slowly in the right one.

Trigger Conditions

• Team claiming "we're moving fast" but unclear if making progress toward goals
• Confusing activity (features shipped, meetings held) with progress (outcomes achieved)
• Optimizing for speed without validating strategic direction
• Evaluating performance using speed metrics alone (commits, hours, output volume)
• Choosing between multiple high-speed initiatives

Key Insight

Physics distinguishes speed (scalar: how fast) from velocity (vector: how fast + which direction). Business should too. 10x speed toward the wrong outcome = waste. 2x speed toward the right outcome = compounding value.

Execution Steps

1. Define the Target Vector

• What is the strategic destination? (revenue, market share, capability)
• Set a clear waypoint: "Achieve X by Y date"
• Ensure it's a position, not an activity: "30% market share" not "ship features"
• Vector clarity test: Can you draw an arrow from current to target state?

2. Measure Current Direction

• What are teams actually optimizing for? (often different from stated goals)
• Track angle between effort and target: 0° = aligned, 90° = perpendicular, 180° = opposite
• Calculate % of resources pointed at true target vs. tangential work
• Red flag: >30% of effort on work not directly advancing vector

3. Calculate Velocity (Speed × Direction)

• Speed: Output per unit time (features/week, revenue/quarter, users/month)
• Direction: Cosine of angle to target (1.0 = perfect, 0 = perpendicular, -1 = backward)
• Velocity = Speed × Direction cosine
• Example: 10 features/week at 60° angle = 10 × 0.5 = 5 effective velocity

4. Optimize for Velocity, Not Speed

• Can you reduce speed but improve direction? (often 2x better ROI)
• Cut initiatives misaligned with vector (even if fast-moving)
• Double down on aligned initiatives (even if slower)
• Pareto check: Do top 20% of initiatives drive 80% of vectored progress?

5. Track Velocity Over Time

• Plot: Distance to goal (decreasing) vs. Time
• If distance isn't shrinking despite activity, direction is off
• Recalibrate direction quarterly (markets shift, goals evolve)
• Leading indicator: Velocity trend line (improving/flat/declining)

Expected Outcomes

• Directional clarity: Everyone can point to the destination
• Ruthless prioritization: Easy to cut work not advancing the vector
• Compounding progress: Each sprint builds on previous toward same goal
• Early course-correction: Misalignment detected in weeks not months

Validation Checklist

• Defined clear target state (measurable destination, not activity)
• Calculated angle between current efforts and target (<30° ideal)
• Measured velocity (not just speed) for key initiatives
• Identified and cut >50% effort misaligned with vector
• Set up tracking: Distance to goal vs. Time chart

Common Pitfalls

• Confusing motion with progress: Busy ≠ effective
• Vanity velocity: Optimizing metrics that don't move the needle
• Direction drift: Target changes but teams keep old heading
• Speed worship: Celebrating "shipped 50 features!" when 45 were wrong direction
• Analysis paralysis: Endless planning of direction, never building speed

Success Indicators

• Distance to strategic goal shrinking each sprint/quarter
• Can articulate "why" for every major initiative (vector alignment)
• Low regret rate: <10% of shipped work deemed misaligned in retrospect
• Resource reallocation speed: Kill/pivot misaligned work within 2 weeks
• Team morale up: Clear direction reduces thrash and rework

Related Frameworks

• Eisenhower Matrix: Urgency (speed) vs. Importance (direction)
• First Principles: Define true destination before optimizing path
• North Star Metric: Single vector for alignment
• OKRs: Objectives (direction) + Key Results (velocity milestones)
• Goodhart's Law: Optimizing speed metrics distorts direction

Real-World Applications

• Product development: Ship fewer features in right direction vs. spray-and-pray
• Sales: Lead volume (speed) vs. ICP qualification (direction) toward closable deals
• Career: Taking any promotion (speed) vs. roles building toward 10-year vision (velocity)
• Startups: Blitzscaling (speed) only works if direction is validated (product-market fit)
• Content marketing: Publishing 10 posts/week (speed) vs. 2/week perfectly targeting ICP (velocity)

Source Attribution

• Physics: Newton's laws - velocity as vector (magnitude + direction)
• Andy Grove: "Focus is about saying no" - direction over activity
• Peter Thiel: "You can't make the wrong thing work" - direction first, speed second
• John Doerr: OKRs framework - objectives (direction) before key results (metrics)
• Jeff Bezos: "We are stubborn on vision but flexible on details" - hold vector, adjust speed

Scoring Rationale

Practitioner: 8/10 - Product/engineering leaders use implicitly, rarely formalized Clarity: 10/10 - Physics analogy is intuitive and universally understood Proven ROI: 9/10 - Misalignment is #1 cause of wasted effort in orgs Novelty: 7/10 - Physics is old, application to strategy/execution is underutilized Cross-domain: 10/10 - Product, career, sales, marketing, operations, life decisions

Total: 44/50