Proximate Objectives are goals that are close enough to be achievable -- objectives where you can reasonably assess whether they are feasible and can envision a path to accomplishing them. The concept comes from Richard Rumelt's *Good Strategy Bad Strategy*, where he contrasts proximate objectives with the vague, distant aspirations that often masquerade as strategy.
## The Problem with Distant Objectives
Many strategic objectives are so far removed from current capabilities and conditions that they are essentially wishes:
- "Become the market leader in five years"
- "Double revenue"
- "Transform the industry"
These may be legitimate aspirations, but they are not actionable. They don't tell anyone what to do next, and they don't create the conditions for progress. A leader who sets distant objectives without proximate ones is like a general who says "win the war" without specifying which hill to take first.
## What Makes an Objective Proximate
A proximate objective has these qualities:
1. **Feasibility is assessable**: You can realistically evaluate whether it can be achieved
2. **The path is imaginable**: People can envision concrete steps toward it
3. **It resolves ambiguity**: It tells people what to focus on and what to ignore
4. **It creates momentum**: Achieving it generates confidence, resources, and position for the next objective
5. **It absorbs complexity**: The leader takes on the burden of judgment, giving the team a clear target rather than passing along the full ambiguity of the situation
## Rumelt's Key Insight
Setting a proximate objective is an act of leadership, not a lowering of ambition. The leader's job is to absorb the uncertainty and complexity of the situation and translate it into an objective that is achievable given current knowledge and capabilities. This requires judgment about what is feasible, courage to commit to a specific direction, and willingness to be wrong.
As Rumelt writes: "One of a leader's most powerful tools is the ability to create a proximate objective -- one that is close enough at hand to be feasible. A good proximate objective resolves ambiguity and concentrates effort."
## The Kennedy Example
Rumelt uses Kennedy's 1961 moon landing objective as a canonical example. "Landing a man on the Moon and returning him safely to Earth by the end of the decade" was proximate because:
- Experts judged it feasible (barely) with concentrated effort
- It was specific enough to organize around
- It resolved ambiguity about what the space program should prioritize
- It created a chain of achievable sub-objectives (Mercury, Gemini, Apollo)
By contrast, "win the space race" would have been a vague aspiration, not a proximate objective.
## Proximate Objectives in Practice
- **Startups**: Instead of "build a billion-dollar company," focus on "achieve product-market fit with our beachhead segment"
- **Product development**: Instead of "build the best product in the category," focus on "reduce onboarding time to under 5 minutes"
- **Personal goals**: Instead of "become an expert in machine learning," focus on "complete one end-to-end ML project and deploy it"
- **Turnarounds**: Instead of "return to profitability," focus on "identify and cut the three largest cost centers that don't serve our core customers"
## Cascading Proximate Objectives
Proximate objectives naturally cascade. Achieving one proximate objective changes the landscape, creating new information and new possibilities that inform the next objective. Strategy becomes iterative: diagnose, set a proximate objective, achieve it, reassess, and set the next one.
This approach is particularly powerful in uncertain environments where long-term planning is unreliable. Instead of a rigid five-year plan, you have a series of achievable steps, each informed by what you learned from the previous one.