How to prioritize design work when everything feels urgent

When everything feels urgent, it’s hard to identify what truly matters.

Design teams often face competing requests from product, engineering, sales, leadership, and customers, all backed by convincing reasons for immediate attention. But when everything is treated as a priority, nothing truly is. The result is simply a queue of competing demands.

Good prioritization helps teams decide what matters now, what can wait, and why.

Return to first principles

Before ranking requests, take a step back from the backlog and return to first principles.

First-principles thinking means reducing a situation to its fundamental truths rather than accepting existing assumptions or proposed solutions at face value. In product work, that means asking:

• What outcome are we trying to create?

• What problem is preventing that outcome?

• Who is experiencing the problem?

• What evidence do we have?

• What happens if we do nothing?

• Which constraints are real, and which are assumptions?

This approach is valuable because most design requests arrive as solutions: redesign this screen, add this feature, update this component, or support this sales opportunity.

However, the proposed solution may not address the underlying problem.

If users don’t understand a product’s value, simply redesigning the dashboard may not help. The right response might be to improve onboarding, reposition the product, or engage with users before designing anything.

Instead of asking which request should come first, ask: Which problem, if solved, would create the most meaningful progress toward our goal?

Urgency and importance are different

Urgency usually comes from time pressure. Importance comes from consequences.

A request might feel urgent because a stakeholder has a meeting on Friday. Meanwhile, persistent issues like onboarding friction may lack a deadline but impact customers daily.

The loudest request isn’t necessarily the most important one.

A useful way to test urgency is to consider the cost of delay:

• Is this blocking engineers or another team?

• Is it affecting a critical customer journey?

• Is it creating meaningful business or user risk?

• Will waiting make the problem more expensive to solve?

• Is the deadline real or merely preferred?

This helps distinguish work that truly needs immediate attention from tasks that have become urgent only because of internal pressure.

Prioritize the smallest effective response

Important work doesn’t always require a complete design project.

Sometimes the most effective response might be a working session, a rough flow, a design spike, a lightweight prototype, or a quick review of an engineer-led solution.

Instead of asking, “Should we do this project or not?” ask:

What is the smallest design intervention that enables the team to make the next decision?

A designer might unblock engineering in an afternoon without resolving every edge case. A rough prototype could expose a weak idea before the team spends a month building it. A few user conversations might reveal that a proposed feature isn’t necessary.

Prioritizing the response, not just the request, gives the team more options than simply “now” or “later.”

Make trade-offs visible

Prioritization shouldn’t happen privately inside the design team.

There should be a single, transparent view of what’s in progress, what’s next, what has been deferred, and why. When priorities change, the team should understand what shifted and what was displaced.

This changes the conversation from “When will design get to my request?” to “Is this more important than what we already agreed to do?”

Designers can help clarify effort, risk, and potential impact. But product leadership should ultimately own business priorities. Designers shouldn’t be left to quietly resolve stakeholder conflicts through the order in which they complete tasks.

A healthy prioritization process won’t make everyone happy. It will make the trade-offs clear.

When everything feels urgent, don’t ask the design team to move faster in ten directions. Return to first principles, identify the most consequential problem, and choose the smallest effective step toward solving it.