Solutions / Test a feature

Before you build the feature, find out whether the belief behind it survives five interviews.

A feature is a belief about a problem. Write it down, interview the people who would use it about what they do today, and let the result open before the sprint starts.

Start freeBook a demo
Questions · Monday no-shows
Tell me about the last Monday you had a no-show.behaviouralQ1
What did you do in the hour after?behaviouralQ2
When was the last time a reminder went wrong?behaviouralQ3
Would you use an app for this?hypotheticalrewritten

What changes.

A belief per feature

"We believe clinic owners, who ring reminders by hand, lose an hour every Monday." Testable in a week.

No "would you use"

Narrera flags the hypothetical questions in your guide and rewrites them to ask about the past.

Results before the sprint

Five interviews, a target, a gate. The feature goes on the roadmap with the quotes attached.

Prioritise with evidence

Compare beliefs side by side.

Three candidate features, three projects, one portfolio view. The one with the most distinct people behind behavioural findings goes first.

  • Portfolio view ranks projects by evidence
  • Hypothetical findings listed, not counted
  • Read-only link for the engineering team
Projects
Monday no-shows5 interviews · target 5results open
Café rota by gut feel3 of 6 interviewsin progress
Late invoices0 of 5 interviewsquestions written
An example finding

A 2 is not demand.

Finding
MarcoOwner · Trattoria Vitale

I would probably pay for that, yeah.

3 · GeneralPain · VolunteeredSource 3, 00:08:12

Start with one belief.

Sign up, write the sentence, and Narrera writes your first ten questions. The notetaker joins your next call.

Start freeBook a demo