John Cutler · 9 min read · Product Strategy
TBM 436: Tension-Based Prioritization (A Non-Framework)
Read the original on cutlefish.substack.com →
The post argues that teams can prioritize more effectively by focusing on the day-to-day tensions that shape decisions rather than following a formal prioritization framework. By tracing recurring arguments, failed convictions, and momentum, teams surface the real commitments needed to move work forward. It also offers a simple, actionable exercise to surface these tensions and shift emphasis from judgment to enacted prioritization.
Key Takeaways
- Prioritization-as-enacted matters more than prioritization judgment; execution determines outcomes.
- Surface recurring tensions to identify where conviction or momentum is lacking.
- Avoid endless frameworks and spreadsheets; focus on the real dynamics of the portfolio.
- Use simple team exercises to surface tensions and guide hard, enacted decisions.
Excerpt
I’ve come to believe that teams can prioritize much more effectively by focusing less on the specific things they’re prioritizing (which will naturally be important, and will naturally get attention) and more on the tensions they’re observing and acting out day after day. The tensions point the way to the real decisions. Most of what we call prioritization is forging agreeable narratives. It resolves very little and produces very little real commitment. But if you pay attention to where the same arguments/tensions keep surfacing, where conviction keeps failing, where momentum keeps winning despite everyone’s better judgment...that’s where you actually need…