Archive / Before you build another feature, see whether five people come back

Before you build another feature, see whether five people come back

Run a small repeat-use test before deciding what to build next.

For: Solo founders, Small business owners

Topics: Business development, Productivity

Start with one job your app helps people do. Give five people who actually have that problem a chance to use it again on their own schedule. Five is a workable research batch, not a benchmark.

1. Pick one job

Prompt

My app helps [specific user] do [recurring job]. Tell me who to recruit, what disqualifies someone, what they should try first, and when they would naturally need it again. Draft an invitation and observation sheet. Do not recruit or message anyone.

2. Watch the first try

Prompt

Turn this core task [task] into a neutral usability script. Include consent, a success signal I can observe, and three follow-up questions. Use fictional data where possible. Separate what people did from what they said.

3. Decide what to change

Prompt

Summarize these de-identified notes [notes]. Count who completed the task, who had another chance to use it, and who returned without a reminder. Separate people who never had another chance from those who chose not to return. Suggest one change, one check, and what we still cannot conclude.

Try it on one example

For a weekly planning app, a seven-day return window may make sense. For a quarterly task, a week of silence tells you less. Write down what counts as a return before running the test.

Inspired by u/SetBest7071’s founder field notes: https://www.reddit.com/r/sideprojects/comments/1xr4j8c/made_3_apps_this_year_and_made_0_from_any_of_them/

Use it for: Run a small repeat-use test before deciding what to build next.

Back to the archive