Zero to MVP — A Goal-Setting App Built on Behavioural Psychology

Why goal-setting apps are harder to design than they look

Most goal-setting apps fail for the same reasons people fail at goals: optimistic at the point of setting, no real support when motivation drops.

The project started with research — not with wireframes. This included reviewing literature on goal-setting theory, behavioural economics, psychology research on motivation and habit formation, and neuroscience work on reward systems and effort.

What the research showed:

• Specificity matters more than ambition. Vague goals (“get fitter”) fail almost universally. Specific implementation intentions (“I will run Tuesday and Thursday at 7am”) succeed at a much higher rate.
• Social accountability changes behaviour. Knowing someone else knows about your goal significantly increases follow-through.
• Small wins sustain motivation better than big milestones. The design had to create a sense of progress at frequent intervals, not only when major milestones were hit.
• Templates lower activation energy. Starting from a pre-built template reduces the cognitive effort of goal construction — one reason people procrastinate on goals they actually want to achieve.

These findings directly shaped the product features and how they were prioritised.

What was designed

Onboarding

A lightweight flow establishing the user’s primary goal area, their experience with goal-setting, and their preferred accountability style — enough to surface relevant templates and configure the initial experience without feeling like a survey.

Goal creation and configuration

The goal creation flow guided users through turning an ambition into an actionable goal through structured prompts. Users define goal type, set a specific metric or milestone, configure their schedule, and optionally add an accountability partner.

The design intentionally made goal creation slightly effortful — enough friction to create a sense of commitment, grounded in research on commitment devices: a small investment in setting up a goal increases follow-through.

Community goal templates

Templates cover common goal types structured around specificity principles. Each template shows the community context: how many people have used it, typical success rates, and anonymised notes from people who’ve completed it. This uses social proof as a motivational tool rather than just a discovery mechanism.

Progress tracking

Progress was designed around frequent small wins rather than big milestone celebrations. Daily check-ins are fast (one tap to log), the progress visualisation emphasises streaks and consistency rather than distance from the end goal. The first missed day triggers a recovery flow rather than a failure state — acknowledging the miss, prompting a quick reflection, and helping the user adjust their plan.

Notification design

A notification system was designed with:

• Reminders tied to the user’s configured schedule — at the right time to prompt action, not a generic default
• Encouragement at early stages, tapering as behaviour becomes habitual
• Re-engagement prompts after a missed check-in, designed as supportive rather than guilt-inducing
• Social notifications for accountability features — when a partner logs a win or checks in on the user

User testing with prototypes

Before finalising the design, user testing sessions were run with early prototypes — testing the goal creation flow and progress visualisation with users matching the primary personas, not internally.

Key findings:

• The goal creation flow needed one fewer step — users were losing momentum before finishing setup
• The progress visualisation initially emphasised the end goal too strongly, so the emphasis shifted to streak consistency instead
• Community templates were underutilised because users didn’t immediately understand what they were for, so explanatory copy was added to the browse screen

What the MVP proved

The design demonstrated that the core concept was coherent and usable. User testing validated the main flows and produced actionable improvements before development started.

After delivery, the client chose to pivot. The work served its intended purpose: a complete, tested design the team could take into development or investor conversations.