by Meliorar

The Feature
Pressure Test.

Before you build it, pressure-test it.

Describe the feature you're considering in one or two sentences.

This anchors the entire session to something specific — not a hypothetical.

Dimension 01Signal origin

Where did this feature come from?

Pick all that apply.

Users asked for it directly, multiple timesOne high-value client requested itThe team identified it internallyA competitor shipped something similarIt came from a stakeholder or leadership decisionWe're not entirely sure — it's been on the list for a while

Which of these best describes the evidence behind it?

We have session recordings, interviews, or tickets that point to thisWe have anecdotal feedback from a few usersWe have a strong internal hypothesis but limited external validationWe haven't validated it yet — we're confident from experience

Dimension 02Problem definition

Describe the specific friction your user experiences that this feature solves.

The most revealing field in the tool. Vague answers here are the biggest signal.

How does your user currently work around this problem?

They use another tool or productThey do it manuallyThey don't — they just live without itWe don't know how they handle it today

Dimension 03Strategic cost

What is this feature competing with on your current roadmap?

Forces you to name the trade-off explicitly.

Which metric does this feature move, and in what timeframe?

Activation — users reaching the core value fasterRetention — users staying longer or returning moreExpansion — existing users upgrading or using moreAcquisition — attracting new usersWe expect it to move multiple metricsWe haven't mapped it to a specific metric yet

Who on your team has challenged this decision?

It's been through a formal review processA few people raised questions but we moved forwardIt hasn't been formally challenged yetWe're using this tool as the first challenge

Takes about 10 seconds.

Meliorar — Experience strategic partner

Substack·Website·Instagram

Edit with