The Decision That Could Wait

Very few people decide they want to pay for a dozen streaming services. You subscribe to watch one show. A few months later another platform gets the exclusive rights to something you want to see. Someone recommends a documentary. A family member asks to share an account. None of those decisions feel unreasonable. Eventually you look at your credit card statement and realize you’re paying for services you barely remember subscribing to. The difficult part isn’t deciding whether you wanted them in the first place. It’s deciding whether you still do.

Product portfolios evolve much the same way.

Launching a product is almost always a decision. It requires research, funding, planning, prioritization, staffing, and executive support. Organizations create entire governance processes to decide whether something deserves to exist. Ironically, far fewer organizations have an equally deliberate process for deciding whether it still should.

Organizations devote enormous attention to deciding whether to start something. Far less attention goes into deciding whether to continue it.

That asymmetry changes your portfolio in ways that are easy to miss. Entering the portfolio requires justification. Remaining in it often does not. Once a product exists, continuation quietly becomes the default. The question shifts from, “Can anyone make the case to keep it?” to, “Can anyone make the case to remove it?”

Those are fundamentally different standards. The first asks a product to continually earn its place in the portfolio. The second assumes it belongs there until someone proves otherwise. One actively tests yesterday’s assumptions. The other quietly carries them forward into another planning cycle.

This isn’t usually the result of poor leadership or bad governance. It’s often a consequence of how organizations respond to urgency. New opportunities demand immediate attention. Strategic customers need commitments. Competitive threats require responses. Acquisitions must be integrated. Planning cycles move on. The urgency to add something is almost always visible. The urgency to revisit yesterday’s assumptions rarely is. As a result, new work continually enters the portfolio while existing work quietly continues under assumptions that are never revisited.

Eventually, continuation stops feeling like a decision at all. It becomes part of the background. Budgets roll forward. Teams continue supporting products. Roadmaps absorb another year’s worth of enhancements. Nobody explicitly decides to keep the product. The assumptions that once justified it simply remain in place.

Organizations devote enormous attention to deciding whether to start something. Far less attention goes into deciding whether to continue it. Over time, portfolios don’t just reflect the decisions organizations make. They also reflect the decisions they quietly stop making.