Velocity Without Intent: The Strategy Bottleneck Nobody Talks About

Lenny Rachitsky has written extensively about product strategy, most notably in his Strategy Blocks framework. The framework is elegant: define your mission, set 3-5 strategic pillars, make explicit tradeoffs, and align the team. But the framework assumes something that most teams do not have: clarity on intent before they start executing.

The real bottleneck in product strategy is not execution speed. It is the gap between velocity and intent.

What Lenny Gets Right

Lenny’s approach emphasizes starting with a profound understanding of user needs. His framework at Ramp, documented in How Ramp Builds Product, shows a culture of rapid experimentation, tight feedback loops, and iterative development. The emphasis is on doing over planning, on momentum with meaning.

This works when you have clarity. When the strategic direction is set, velocity is a competitive advantage. Ramp moves fast because everyone knows where they are going.

But the framework breaks down when the intent is blurry. When teams are asked to execute on strategic pillars that were never rigorously defined. When “understanding the user” becomes a checkbox rather than a discipline.

The Bottleneck Is Not Execution

Most product strategy content focuses on how to move faster. Better roadmaps, faster sprints, clearer OKRs. This is velocity optimization. It assumes the intent is already clear.

But the bottleneck for most teams is not how fast they can ship. It is whether they are shipping the right thing. Velocity without intent is not efficiency. It is just motion.

Lenny writes about choosing metrics that actually indicate whether customer needs are being solved, like activation and retention, rather than vanity metrics. This is intent-first thinking. But most teams do not have the patience for it. They want to ship first and figure out the metrics later.

The bottleneck is cultural, not processual. Teams default to velocity because velocity feels productive. Intent feels like thinking, which feels like not working.

The Ramp Culture Problem

Ramp is often cited as a case study for high-velocity product development. Their approach to product strategy emphasizes flexibility, rapid iteration, and outcome-focused metrics. But Ramp also has something most companies do not: a clear business model, a defined market position, and a founder who sets the intent.

For companies without that clarity, importing Ramp’s velocity without importing their intent is a recipe for waste. The cultural DNA matters more than the process DNA. The inputs are not transferable. What works at Ramp requires prerequisites that most organizations do not have.

This is the hidden lesson. Lenny’s content is often consumed by teams who need the intent first, not the velocity. They copy the output without the input. They optimize for speed without defining the destination. The playbook works, but only if you have already solved the problem that the playbook assumes.

The Fix Starts With Intent

The discipline is simple but unpopular. Before you optimize for velocity, define your intent. Before you build, validate. Before you ship, align. The steps are straightforward. The resistance is cultural.

Lenny’s framework actually includes this. The Strategy Blocks approach involves making disciplined choices about where to deploy scarce resources. It involves explicitly stating areas that will NOT be a focus. This is intent-first planning.

Most teams skip this step because it feels slow. They want to start doing rather than planning. But the cost of doing the wrong thing faster is higher than the cost of planning longer.

The real bottleneck is not a lack of process. It is a lack of patience. Teams consume the playbook but skip the foundation. The strategy works for companies with clarity. It fails for companies that assume clarity is optional.

Sources:
– Strategy Blocks: An Operator’s Guide – Lenny’s Newsletter
– How Ramp Builds Product – Lenny’s Newsletter
– Getting Better at Product Strategy – Lenny’s Newsletter
– How We Build Product at Ramp
– Product Velocity – ProdPad