couldhaves

Couldhaves is a term used in project management, product development, and decision analysis to describe options, features, or outcomes that were not implemented but could have been. The idea encompasses both planning considerations—future possibilities that might be pursued if circumstances allow—and retrospective counterfactuals, evaluating what might have happened under different choices.

In backlog prioritization, could-haves are typically regarded as lower priority than must-haves or should-haves. They represent desirable but nonessential items that may be deferred, removed, or reconsidered if resources permit. Teams may maintain a separate could-have backlog or a loosely defined category within existing roadmaps to capture these ideas for potential future reconsideration.

In retrospective and postmortem discussions, couldhaves function as counterfactuals used to understand opportunity costs and to inform future planning. For example, a team might note that a could-have feature could have improved user engagement, or that a different architectural choice could have reduced maintenance effort. The aim is to identify learning rather than assign blame.

Criticisms of couldhaves include the risk of speculative planning or scope creep if such items receive disproportionate attention. Effective use requires clear documentation of the rationale, data supporting the assessment, and a deliberate process for prioritization. By separating proven issues, ongoing work, and possible enhancements, teams can leverage couldhaves for learning without destabilizing current plans.

See also: must-have, nice-to-have, MoSCoW method, counterfactual, backlog.