Sites accumulate features because teams have more ideas than hours. The constraints are fixed: limited time, limited resources, and a finite amount of attention a visitor will spend on any interface. Most prioritization frameworks exist to manage that gap, but one question works well before any of them: what happens if we don't do this right now?

Why the evaluation frameworks come too late

Feature discussions tend to drop straight into detailed criteria:

  • KPIs/OKRs: what return will this feature produce?
  • Performance: will the new code help or hurt our metrics?
  • Accessibility: can all customers use the feature?
  • Maintenance: do we have resources to maintain the new component?
  • User experience: how will this affect visitors?

Each of these is a legitimate concern and sometimes a necessary conversation. Together they can also stall a decision. Asking the "what if we don't" question first establishes whether the work is necessary and where it ranks, before the deeper analysis begins.

A worked example: three modal improvements

Suppose three ideas for improving modals land on the table. The question sorts them quickly.

Lazy loading modal content

If we don't remove modal content from the initial page load, visitors download material they may never request, potentially blocking other critical content. This belongs in the priorities, with investigation to follow.

An animation on modal close

Without it, the close experience might feel jarring — or might not. It is unclear whether it changes conversion or drives readers away; probably not. This goes into the non-urgent, non-important column and gets revisited if bandwidth appears.

Missing aria-labels on close buttons and no keyboard focus retention in the modal

If we don't fix this now, the answer is simply to stop reading and go do it. Accessibility gaps of this kind aren't candidates for prioritization — they're immediate work.

Applying the question to what already ships

The same test works in reverse on existing code. Audit your site and ask what happens if you don't keep a given component: does that SVG animation really spark joy? (The source concedes that question is a trap — it does.)

Not a blanket "no"

This is not an argument for rejecting every incoming request. Without iteration and experimentation, sites go stale, slow, and outdated. The question is a communication tool — for the team or for your own internal debate — that surfaces the impact new code will have on a fast, accessible site.