7of 8
Retention: What brings early users back?
Initial interest doesn’t prove that a product earns repeat use. Define when customers would genuinely need it again, track meaningful returns and account for reminders or founder assistance.
By the EWOR Team2 min read
Someone might try a solution out of curiosity, to help you or to meet a one-off need. To understand whether they will return, look at the next genuine opportunity to use it. Initial interest and sustained engagement require different evidence.
Define what return looks like
Start with the recurring customer need, not an arbitrary retention interval. A weekly planning tool and a service used when moving office should not be judged by the same return schedule. Some solutions are valuable precisely because the problem they solve rarely recurs.
For a hypothetical weekly planning service, meaningful return might mean creating and using a second plan at the next planning opportunity. Opening a reminder is a different behaviour. Define the action you want to observe and the observation window before the pilot begins.
Be clear about what the pilot delivers, too. If participants cannot complete a useful first task, a return-use test may reveal more about a broken initial experience than ongoing demand. Keep that failure visible rather than excluding those participants from the results.
Keep the starting group visible
Track who started the pilot, who completed the first use and who returned. New sign-ups cannot make up for missing return users in a retention claim.
Record whether each participant had a genuine opportunity to use the solution again. If some did not, report both the full starting group and the relevant subgroup, explaining the distinction. Do not redefine eligibility after seeing who returned.
Distinguish voluntary return from attendance at a scheduled research appointment. Record any reminders, incentives or founder assistance. These may be legitimate parts of a service, but they affect what the observed behaviour can tell you about sustained interest.
Track only what you need to answer the question
Explain how the pilot works, including any human delivery behind the interface, which events you will record and how long the data will be retained. Obtain informed consent for participation and tracking, and make withdrawal straightforward.
Collect only what you need to understand return use. A participant identifier, a relevant usage event and a timestamp may be enough. Recording unrelated activity or private content does not make the experiment stronger. A follow-up conversation with consent can help explain why someone did not return without making surveillance the default.
If the pilot involves payment, state the delivery, cancellation and refund terms clearly, and honour them. A first purchase is not the same as repeat use.
Interpret return use in context
Early repeat use is encouraging, but a small, recruited pilot with personal support is different from ordinary use of an automated product. Keep those conditions attached to the results rather than presenting them as proof of lasting retention.
If participants do not return, investigate whether the need recurred, the first experience delivered value and the next use was accessible. Then decide whether a specific change warrants another test.
The key question is whether the solution earns another use under the conditions tested. Initial enthusiasm alone cannot answer it.





No comments yet.
Be the first to comment on this signal.