Illustrative scenario · Recovery-app onboarding

When onboarding asks for too much, too soon

A fictional wellbeing app asks a new member to complete a long profile before explaining what the service offers. The first decision is whether the person understands why those questions matter and feels able to defer them.

Illustrative scenario. The organisation, interface and research plan are fictional. This is an explanation of our approach, not a completed client study.

The question behind the interface

The opening sequence combines account creation, personal questions and reminder permission. A person cannot see which answers are necessary to begin. Asking for everything at once may create uncertainty about what is optional and who will see the information. This is a design hypothesis, not a finding from people using a real recovery service.

A proposed direction

Start with the first useful task, explain optional questions and offer a clear route to complete the profile later.

Illustrative interface · Proposed design · Recovery-app onboarding
Fictional example

Which questions help you start?

You can begin with a name and email. Add optional preferences when you are ready.

Continue with the basics →
  1. Create your account
  2. Choose one starting goal
  3. Add optional detail later

Static design example. The depicted action is not an interactive product control.

How we would investigate it

Use a safe fictional account and ask a relevant participant to begin without sharing private health information. Observe whether they can distinguish required and optional steps and explain what the app will do next.

Before recruiting, we would agree the decision the study must support, the people whose experience matters and a realistic task. The session plan would specify a safe starting state and avoid leading the participant towards the proposed solution. Relevant access needs, consent and handling of research material would be included in the scope.

The tradeoff to examine

Reducing the first step can postpone information the service genuinely needs. The product owner must identify the minimum necessary data before the interface labels a question optional. Reminder permission should be explained at the moment its value is apparent.

What would count as useful evidence?

Comprehension of optional fields, ability to proceed without unnecessary disclosure, and clarity about when deferred information will be requested.

Record the actions, misunderstandings and assistance required. Keep participant comments separate from interpretation and show important exceptions as well as patterns. A revised design would remain a proposal until it had been evaluated; task completion in a small qualitative study would not establish a population-wide conversion rate.

What this example leaves open

No participants were recruited for this scenario, and no improvement or commercial outcome has been measured. The screens explain an approach. In an actual engagement, the evidence could support a different recommendation, expose a constraint not visible here or show that another problem deserves priority.