---
title: "Strategy Debt"
description: "The accumulated cost of saying yes to one-off requests instead of following a coherent product vision."
category: "Frameworks & Strategy"
canonical: https://featureos.com/glossary/strategy-debt
markdown: https://featureos.com/glossary/strategy-debt.md
source: FeatureOS (https://featureos.com)
---

**Strategy debt** is the accumulated cost of repeatedly saying yes to requests that don't fit your product vision. Every one-off feature built for a loud customer, an eager sales rep, or a well-meaning stakeholder, adds to it.

Unlike technical debt, there's no code to point to. The codebase might look fine. But the product quietly becomes incoherent.

## How it compounds

At first, the one-offs feel like good business. You kept the customer. You closed the deal. Six months later, you have a product that tries to do everything for everyone and does nothing particularly well.

Your team doesn't know what to prioritize anymore because the strategy keeps bending around requests. Your [roadmap](/roadmaps) looks like a wish list. Every new feature has to coexist with all the mismatched ones that came before it.

## Why it's harder to see than technical debt

With technical debt, an engineer can usually point at the problem. With strategy debt, the dysfunction is spread across dozens of individual decisions that each seemed reasonable at the time. No single bad call, but the pattern of calls degrades the product.

The fix is getting clear on what you're building and for whom, then having the discipline to say no to things that don't fit. That's harder than it sounds when a customer is threatening to churn or sales is promising the moon.

---
Source: FeatureOS — https://featureos.com/glossary/strategy-debt
FeatureOS: product feedback, roadmaps & changelogs — https://featureos.com