Projects/
Goal-setting proof of concept
Search projects, pages and writing
⌘K
Email address copied
Stealth startup
·
Education · Proof of concept · Mobile app
·
8 weeks
·
5 min read
Featured

Designing a Goal-Setting App Where Friends Keep You on Track

Achiever is a goal app built around people instead of reminders. A partner checks on you, a small crew sees your check-ins, and your progress reads at a glance. I designed it for a stealth startup, from the first conversations to a clickable iOS prototype, in eight weeks.

The goal was to define the product, test the core idea cheaply, and leave the team with a prototype they could put in front of investors and early users. I was the only designer, working directly with the founder.

My role
Lead Product Designer
Solo designer, working directly with the founder
Team
Solo designer, working directly with the founder
Duration
8 weeks
Product scale
iOS proof of concept
Outcome
Clickable iOS prototype in 8 weeks

Outcomes

What changed because of the work.

See all

What I designed

The things I designed and shipped on this project.

See all
  1. Market review, proto-personas and a journey map
  2. Design principles, core loops and navigation
  3. Low-fi wireframes and quick tests
  4. Onboarding that brings in a crew and a partner before the first goal
  5. A weekly home with check-ins, proof, pace and missed-week recovery
  6. Crew and two-way partner accountability with nudges
  7. Templates, milestones and stakes judged by your partner
  8. Progress, lessons in context, chats and a small design system

The brief

The problem, what I designed, and the result.

See all
01
The problem

People rarely fail at goals for lack of a plan. They drop off around week three, and reminders are easy to swipe away. The founder wanted a goal app where other people, not the app, keep you going.

02
What I did

A market review, informal conversations, proto-personas, a journey map, low-fi tests, a visual system and a clickable iOS prototype, as the only designer working directly with the founder.

03
The results

A clickable iOS prototype with 39 screens across seven flows, a small design system, handoff notes and a test plan. The founder took it into investor and early-user conversations.

How the work ran

With a founder making decisions quickly, I kept research light and close to the product and got something in front of people by week five.

  1. Research and analysis. A founder workshop, a review of stickK, Beeminder, Habitica, Focusmate and Strava, and informal conversations with people in the target group, which became three proto-personas and a journey map.
  2. Design and iteration. Information architecture and low-fi wireframes, then hi-fi screens and a small design system, with the product reworked around the partner and the crew after the early tests.
  3. Ship and test. Quick, informal sessions on the low-fi screens in week five, then a clickable iOS prototype of 39 screens with a test plan for the next phase. The hi-fi prototype hasn't been tested yet.
Goal-setting proof of concept

Most people know what to do. They just stop doing it.

People don't usually fail at goals because they lack a plan. They fail somewhere around week three, when the first excitement is gone and a busy week gets in the way. One miss turns into two, two turns into quiet, and the goal disappears without anyone noticing.

Most goal and habit apps answer that with more reminders. The thing is, reminders are easy to swipe away. A friend asking where you were this morning is not.

The brief: a friend at the door, not a notification

The founder came to me with an idea and a rough MVP direction: a goal app where other people, not the app, keep you going. Skipping a morning run is easy when your phone buzzes. It's a lot harder when a friend is standing at your door. The brief came down to four things:

  1. Support people, but use the group to hold each other accountable.
  2. Use game mechanics and behavioural psychology to keep people committed.
  3. Keep it easy, with guided flows instead of blank forms.
  4. Show timely, easy-to-read progress, so people always know where they stand.

The audience was mostly men, roughly 25 to 45, working on money, fitness, career or learning goals. Many had tried habit apps before and dropped them. What they were missing was someone who notices when they don't follow through. The "mostly men" focus came from the founder's target market. It shaped the tone, imagery and colour, and it's something to keep checking as the product grows.

Eight weeks, one designer

With a founder making decisions quickly, I kept research light and close to the product, and pushed to get something testable in front of people by week five.

  • Week 1, kick-off: founder workshop, goals, constraints and what success looks like for a proof of concept.
  • Week 2, discover: competitor and market review, and informal conversations with people in the target group.
  • Week 3, define: proto-personas, journey map, "how might we" questions and design principles.
  • Week 4, structure: information architecture and low-fi wireframes of the core screens.
  • Week 5, test early: quick, informal sessions on the low-fi screens, then rework the flow around what came up.
  • Weeks 6-7, design: hi-fi screens, design system, imagery and copy.
  • Week 8, prototype: clickable iOS prototype, handoff notes and a test plan for the next phase.

What other apps get right

I looked at the products people already use to stick to goals: stickK, Beeminder, Habitica, Focusmate and Strava. Each one gets part of the answer right. stickK shows that real stakes with a named judge work. Beeminder shows that visible pace beats a bare percentage. Habitica shows that letting your group down is a stronger motivator than losing points. Focusmate shows that a real person at a set time is hard to skip, and Strava shows that being seen by people you know keeps you showing up.

stickK

Commitment contracts with money on the line and a referee who confirms your progress. Money can go to a charity, or an "anti-charity" you dislike.

  • What I took: real stakes and a named judge work. stickK's co-founder has said users with money and a referee reach their goals far more often than those without (company-reported).
  • The gap: it feels like a legal contract, with little everyday support or community.

Beeminder

You track data against a "bright red line". Fall off it and you "derail", which charges your pledge, and the pledge goes up each time.

  • What I took: visible pace beats a bare percentage, and escalating stakes keep people honest.
  • The gap: it's built for data-minded self-trackers and is harsh for anyone who just had a bad week.

Habitica

Habits as a role-playing game. In a party quest, your missed dailies damage the whole party.

  • What I took: letting your group down is a strong motivator, stronger than points.
  • The gap: the fantasy theme puts off a lot of people, and the game can become the point.

Focusmate

Book a session and get paired live with another person who is also working on something.

  • What I took: a real person at a set time is hard to skip.
  • The gap: it's built for focus sessions, not long goals that run for months.

Strava

A social training log with clubs, group challenges and "kudos" on activities.

  • What I took: being seen by people you know keeps you showing up, and proof is built in.
  • The gap: it only covers fitness, and the social side can tip into comparison.

None of them combines everyday support, people you know, and real but small stakes in one place. That gap became the product: small stakes, settled by people you actually know, in an app that feels supportive rather than punishing. The placement below is my own judgement from reviewing each product, not a measured survey. On my read, stickK and Beeminder carry real stakes but you're mostly on your own. Habitica, Focusmate and Strava bring other people in, with Habitica's stakes the highest of the three. Typical habit trackers are solo and soft. Achiever sits at real but small stakes, with people you know.

What this meant for the product:

  • Stakes work best with a named person judging them. So every stake has a judge, usually your partner.
  • Letting your group down beats losing points. So the crew shares a streak that only grows if everyone checks in.
  • A person at a set time is hard to skip. So every check-in has a deadline and a witness.
  • Pace is easier to act on than a percentage. So progress always says if you're on track and what to do if you're not.
  • Harsh punishment makes people quit. So a missed week opens a recovery plan, not a penalty screen.

Sources: stickK (Wikipedia) · What is Beeminder · Beeminder: derailing · Habitica wiki: obstacles and party damage · Focusmate: purpose · Strava group challenges

What I heard

I had informal conversations with the founder and a handful of people from the target group, on top of the desk research. There was no survey and no formal interview study, so I treat these themes as strong hunches to test rather than proven facts. Five of them kept coming up, and they pointed the same way as the market research: the missing piece isn't knowledge or tracking, it's another person.

  1. They already know what to do. Nobody we spoke to lacked information. They knew how to save, train or study. The problem was keeping going after the first few weeks.
  2. Reminders get swiped away. App notifications blended into everything else on the phone. A message from a friend did not.
  3. One miss turns into quitting. After a bad week, people felt embarrassed and went quiet instead of getting back on track. Shame did more damage than the miss itself.
  4. Big goals feel too far away. Saving 45,000 or running a half marathon felt abstract. Small, dated steps felt doable.
  5. A friend helps, but it fades. Several people had tried a gym buddy or a savings pact. It worked until one of them stopped asking.

Those themes became five "how might we" questions:

  • How might we make someone you know notice when you skip, without it feeling like surveillance?
  • How might we turn a big goal into steps small enough to start this week?
  • How might we help people come back after a miss instead of going quiet?
  • How might we keep accountability going both ways, so it doesn't fade?
  • How might we show progress so clearly that you know in a second if you're on track?

Three people the product had to work for

From the conversations I built three proto-personas. They're working hypotheses, not validated segments, and the names and quotes are illustrative.

Tomas, 34: the restarter

"I know exactly what I need to do. I just never get past week three."

  • Wants: to save 45,000 for a pickup to start his own construction business, and someone to keep him honest without lecturing him.
  • Gets stuck on: ignoring app reminders, and going quiet after a missed week out of embarrassment.
  • In Achiever: weekly check-ins with a witness, a stake on each milestone, and a recovery plan when he misses.

Mike, 31: the steady one

"I don't mind being the guy who checks in. It keeps me going too."

  • Wants: to run a half marathon in April, and to help friends stick to their goals.
  • Gets stuck on: losing interest when his training buddy drops off, and having no easy way to check on others.
  • In Achiever: Tomas's partner. He gets pinged when Tomas goes quiet and has his own runs checked in return.

Daniel, 41: the lone starter

"None of my friends are into this stuff. I'd do it with strangers if it didn't feel weird."

  • Wants: to get back into the gym after years off, and a group that takes it seriously.
  • Gets stuck on: having nobody in his life to bring along, and worrying about being judged by fitter people.
  • In Achiever: joins a crew matched by goal area, starts without a partner and finds one inside the crew.

Week three is where goals die

I mapped Tomas's goal over a typical first month, comparing motivation on your own with motivation that has a partner and a crew. The dip around week three is where most goals die, so that's where the product does most of its work: a partner who gets pinged when a check-in isn't logged, and a "don't miss two" recovery plan after the first miss. The journey is illustrative, based on the themes from the conversations, not measured data.

  1. Sets a goal. Excited, plans big. In Achiever: a template, milestones and a partner before the goal exists.
  2. Weeks 1-2. Motivated, ticking things off. In Achiever: a weekly check-in with proof, posted to the crew.
  3. Week 3. A busy week, and motivation dips. On your own, this is where it slips. In Achiever: the partner gets pinged if the check-in isn't logged by the deadline.
  4. Misses once. Embarrassed and tempted to go quiet. In Achiever: "Don't miss two", so adjust the week, tell the crew and watch a two-minute lesson.
  5. Two weeks later. On your own, the goal is usually gone and forgotten. With a partner and crew: back on track, the crew streak intact and the next milestone in sight.

Six rules and the mechanics behind them

I used six rules to settle design decisions:

  • People before notifications. Every reminder names a person. "Mike gets pinged at 20:30" lands harder than "Don't forget to log".
  • Two-way by default. You check on your partner and he checks on you. Being responsible for someone else's streak is a reason to keep your own.
  • Small stakes, settled often. A stake on each milestone, judged by your partner, beats one big bet a year away.
  • One set of numbers. Saved amount, percent, milestones and pace always agree, on every screen.
  • Help at the moment it's needed. Lessons appear after a miss or before a stake, not only in a library.
  • Direct, not preachy. Short, honest copy that treats people like adults. "You said 7:00. Shoes on."

The game-like parts are deliberately few, and each one is tied to a person rather than to points. Every check-in has a time and a witness ("Due Fri 20:00. Mike gets pinged at 20:30"), every stake has a judge, and the crew shares a streak that only grows if everyone checks in. The behavioural ideas behind them, and where each shows up:

  • Social accountability (Home, Crew): your blank slot next to four "Done" marks does more than a push notification.
  • Commitment device (creating a goal): a stake on each milestone, with a named judge and a plain-words consequence.
  • Loss aversion (stake nudge): the stake is framed as something you could lose, kept small enough to say yes to.
  • Implementation intention (Home): every check-in has a time and a witness.
  • Forgiving streaks (missed week): a weekly streak with "Can't this week" and a recovery plan, built around never missing twice.
  • Group goal (Crew): a crew streak that only grows if everyone checks in, plus a weekly crew challenge.
  • Proof (proof check-in): a bank screenshot or photo with each check-in, so "trust me" becomes something people can see.
  • Visible progress (Home, goal): pace instead of a bare percentage, like "On track, 625 $ by Fri" or "behind by X".

Four loops, four tabs

Before drawing screens I mapped the four loops the app has to support. Everything in the navigation exists to keep those loops short.

  • First run: Welcome, goal area (multi-select), experience, backup style, find your crew and invite a partner, then Home.
  • Weekly loop: Home (this week), Done it (with proof), posted to the crew, milestone hit (badge), next milestone (pace updates).
  • Miss and recover: Can't this week, adjust the week, tell the crew, a "never miss twice" lesson, back on track.
  • Partner loop: Mike is quiet at 7:00, you get an alert at 7:31, you nudge or call, Mike logs his run, and the crew count updates.

There are four tabs, and people are in two of them:

  • Home: this week's check-in, goal with pace, crew status.
  • Crew: who's in today, crew streak, challenge, feed and your partner.
  • Learn: lessons, also linked from the moments they help.
  • Chats: crew chat pinned, partner tagged, one tap to call.

Goal creation sits behind "New goal" on Home, because people do it rarely and the weekly loop matters more.

Low-fi first, then quick tests

I sketched the core screens in grey boxes first and put them in front of a few people from the target group in quick, informal sessions. Nothing formal and no numbers, but it was enough to move the product in the right direction before any visual design.

Week 4 low-fi wireframes

Five things changed because of those sessions:

  1. Home led with content. People kept asking what they were supposed to do today, so Home now opens on this week's check-in, then progress with pace, then the crew. Lessons moved to their own tab and to the moments they help.
  2. The partner sat at the bottom. "Find partner" felt optional and most people never got to it, so finding a crew and inviting a partner moved into onboarding, before the first goal exists.
  3. A blank form stalled people. Goals now start from templates other people finished, then break into milestones with dates, tasks and a stake.
  4. Matches felt random. A grid of strangers gave nobody a reason to pick anyone. Crews are now matched by goal area, and partners come from your contacts or from inside your crew.
  5. Chat was just chat. Crew chat is now pinned, the partner is tagged, and alerts offer "Log it" or "Call Mike" directly.

Calm and confident, not playful

Most of the screen is neutral, the heavy moments are graphite, and violet only marks what you can tap, in a 70/20/10 split. Lime, sky, yellow and lilac appear only on categories, and the palette stays calm and grown-up to suit the audience. A condensed headline face from the Uniform family fits long goal names on one line and feels sporty without shouting. Photos are candid shots of real people with one shared grade, so the set feels like one shoot.

Visual system: colour split, typography, components and imagery

Onboarding: your people before your goal

People sign up full of energy and set goals alone. By the time they need support, there's nobody around to give it. So finding a crew is part of onboarding, before any goal exists. Three light questions set your goal area, experience and how much backup you want. Then you join a crew matched to your goal area and invite one partner, with a line that makes clear it goes both ways. "Skip for now" stays visible, so nobody feels trapped.

Onboarding: welcome, goal area, backup style and find your crew

Home: what's due, and am I on track?

People open the app needing to know one thing fast. Home has a fixed order: what's due, then progress with pace, then the crew. Each check-in shows its deadline and its witness. "Done it" asks for proof, like a bank screenshot, and posts it to the crew, which turns "trust me" into something people can see. When a check-in closes a milestone, you get a short celebration and a badge.

This week, proof check-in, milestone hit and the updated home

"Can't this week" opens a recovery plan, not a failure state. It asks what got in the way, offers three ways to adjust the week and lets the crew know you're regrouping. A two-minute lesson called "Never miss twice" opens right from that screen, and reminders always name the person who's waiting.

Missed week check-in and the Never miss twice lesson

Crew and partner: accountability both ways

Accountability fades when it only runs one way, or when the person checking in doesn't know what they're meant to do. The crew tab shows who's in today, a crew streak that only grows if everyone checks in, and a weekly challenge. The partner view spells out the rules of the pair: who checks whom, when, and what's at stake. Nudges are short and pre-written, with an optional call if he doesn't reply, and a lock-screen alert tells you when your partner goes quiet.

Crew, partner view, nudge and partner alert

Creating a goal with something on the line

Big goals feel far away, and a blank form is hard to fill in. Templates show how many people used a plan and how many finished it. Then three steps turn the goal into milestones with dates and tasks, and the partner gets pinged if one isn't logged.

Templates, goal details and milestones

A single bet a year out is too distant to change what you do this week. So each milestone gets a small stake, judged by your partner. "Loser buys dinner" or a charity donation keeps him on your side, and the last step is posting the goal to your crew.

Stake nudge, add a stake, overview and goal set

Progress you can trust

A percentage on its own doesn't tell you if you're doing well, and mixed signals make people stop trusting the numbers. So there's one progress model everywhere: 4,375 of 45,000 $, 10%, 0 of 5 milestones, and they always agree. Progress shows pace instead of a bare percentage: on track, or behind and by how much. The current milestone is graphite and the done ones go neutral, so only one thing stands out.

Goal timeline, milestone hit, goal after a win and deadline reminder

Lessons and chat at the right moment

Advice in a library rarely gets read when it would help, so lessons show up right after a miss or before a stake, and each one shows how many people in your crew watched it. The best accountability happens in real conversation, so the crew chat is pinned on top, your partner is one tap from a call, and alerts offer "Log it" or "Call Mike" instead of just "Open app". The app's job is to get two people talking, then step out of the way.

Learn, watch, lesson and article
Chats, chat with partner, add connection and Friday check

The result

In eight weeks the founder got a clickable iOS prototype covering onboarding, the weekly loop, crew and partner, goal creation, progress, learning and chat: 39 screens across seven flows. It came with a small design system, the proto-personas, journey map and market review, handoff notes and a test plan for the next phase. The founder took the prototype into investor and early-user conversations.

The hi-fi prototype hasn't been tested yet. These are the tasks I'd run in five or six moderated sessions:

  1. Join a crew and invite a partner during onboarding, without help.
  2. Log this week's check-in with proof.
  3. Answer "Are you on track for the truck?" from Home, and time it.
  4. Notice your partner hasn't logged his run and nudge him.
  5. Skip a week and get back on track.

There are open questions too. Bank screenshots need account numbers hidden automatically. A partner can only nudge so often before it turns into nagging. Real-money stakes raise legal and payment questions per country. Crews of strangers have to feel safe, or the idea fails for people like Daniel. And leaning male in the imagery fits the main audience, but it shouldn't push anyone else away.

What I took from it: the product isn't the tracker, it's the people around it. Early on it was tempting to make Achiever smarter, with better reminders, nicer charts and more content. The quick tests pulled me the other way. People didn't need the app to know more, they needed someone to notice. Once the partner and the crew became the centre of the design, most other decisions followed.

What the team said

See all
No items found.

More case studies

All 13 projects

Book a 20-minute intro call

Slots show in your own time zone.

Open to work

Let’s see if it’s a fit.

Twenty minutes is usually enough: the project or role, the product, and how your team works.