Define the Problem before Selecting a Solution
Problem framing defines who is affected and the gap between the current and intended situation. The framing shapes what evidence to collect and which solutions to compare.
Building a feature because usage is low assumes a cause. Record the observation separately from your explanation of it.
Specify Who Is Affected and When
For low signup volume, investigate reach, understanding of eligibility, and abandonment during entry. These problems require different changes.
GOV.UK discovery examines the problem before development. (GOV.UK: Discovery) Even an existing proposal needs a clear account of the problem it addresses.
Separate Observations from Possible Causes
Abandonment during entry is observable; too many fields is a possible explanation requiring investigation. Missing information or unclear instructions may also explain it.
Attach an evidence need to each assumption. Record the measurement period and conditions for later comparisons.
Compare Options against the Defined Gap
Compare instructions, intake conditions, and interface changes against likely causes and cost. Ease of implementation alone may leave the cause untouched.
Review the same situation after the change. Keep the public explanation aligned with the updated conditions.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To publish a website explaining the problem your service addresses, give SpreadSite a try!
Build a website with SpreadSite →