Prioritization

You have room for one meaningful project this month.

Sales wants a Salesforce integration.

Support wants bulk editing.

Data shows new-user activation fell from 68% to 51%.

What goes first?

Prioritization is not mainly about ranking ideas.

It is about deciding:

Where should we spend scarce time right now?

You need context before you can answer.

The Salesforce integration is blocking one large deal.

Bulk editing affects around 12% of weekly users.

The activation drop started immediately after last month’s onboarding redesign.

Now the options look different.

Impact

How much value is affected?

Severity

How painful is the problem?

Confidence

How strong is the evidence?

Urgency

What happens if we wait?

Effort

What will solving it consume?

You do not need a framework yet. You need good inputs.

The activation problem deserves immediate investigation because:

• it affects every new user
• you know when it started
• there is a plausible recent cause
• acquisition may now be leaking through onboarding

That does not automatically mean:

Rebuild onboarding.

The priority may be learning what broke.

Now imagine the Salesforce deal is worth 40% of annual revenue and closes Friday.

Your answer may change.

That is the point.

Priorities are not universal rankings.

They depend on context.

RICE and similar frameworks can organize thinking.

They cannot make the decision for you.

Weak inputs with decimal places are still weak inputs.

Do not ask:

Which feature wins?

Ask:

What matters most right now, and what evidence supports that?