esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Make Commitment to Friends: Let People You Trust Hold a Goal With You

Learn how a design can turn a private goal into a promise to friends, how to build that flow, and how to keep it fair and safe.

In short

Make Commitment to Friends turns a private goal into a promise made to friends, so someone is waiting for the result and the goal is harder to drop.

9 min readFree

What you will learn

This lesson teaches one design technique: Make Commitment to Friends. A user makes a promise about a goal and names people who will know about it. Those people can follow progress, offer support, or check the result. The screen has three jobs. It helps the user pick a clear goal, choose who to tell, and see that the promise has been made.

By the end you will know why a promise to friends can add pull that a private plan lacks, how to build the flow step by step, and which risks to guard against, such as weak privacy, pressure and shame. A worked example uses two real goal tools so you can see the idea in use.

Key words

Commitment
A promise to do something later. In this lesson, the promise is a specific goal with a deadline.
Accountability
Being answerable to someone for what you said you would do.
Accountability partner
One person you report to on a set schedule about a goal.
Referee
A person who checks a user's progress reports and confirms they are true. The word is used by stickK.
Supporter
A person who follows a goal and cheers it on, but does not have to check the results.
Pre-commitment device
A tool that makes you decide now what you will do later, so your future self has less room to change course.
Consent
A clear yes from a person before their name, email or data is used.

Tip

This lesson is about the social promise only. Money at stake, comparing yourself with others, and reminders each have their own lesson in this course.

Why does a promise to friends work?

Many goals fail in the gap between meaning to do something and doing it. A private plan has no one waiting for the result, so it is easy to drop. A promise made to another person changes that. Once another person knows the goal, a missed goal has a social cost, since that person may bring it up later.

  • A social cost

    Missing a goal can feel like letting a friend down, not just skipping a task. That feeling is the main pull of this technique.

  • A regular rhythm

    A promise works best when it comes with a set time to report back. A friend who asks every Friday creates a steady check.

  • A visible promise

    A clear confirmation screen makes the promise feel real to the user, and gives the friend something concrete to hold them to.

Researchers have tested this idea.

Designers do not need to create this feeling from nothing. They need to make the promise clear and the reporting easy.

Tip

When you quote a number, trace it to a named study. Many numbers spread online with no source. Use a figure only if you can find the original.

Where does the research have limits?

The research is not one-sided. So an audience is not a magic fix. The helper has to be the right kind of helper.

Some popular claims go too far.

Tip

A friend who accepts every excuse gives comfort but not real accountability. Design for a partner who notices when a goal is missed, and who is kind about it.

How do you design the flow in four parts?

A good flow has four parts. Each part answers a question the user will ask on the screen. Keep the steps short, and let the user go back at any point.

  1. 1

    Set a clear goal

    A friend should be able to answer yes or no about the goal. Replace 'exercise more' with 'run three times this week', and show a field for the deadline.

  2. 2

    Choose who hears about it

    Offer clear options: pick people from contacts, pick a group, or name one accountability partner. On stickK, a supporter is someone who follows along, can see progress, and can leave comments in the goal's journal. Say what each person will see before the user confirms.

  3. 3

    Confirm the promise

    A stickK-style contract records the goal in writing, fixes a deadline, and can add extra incentives. On your screen, show the goal, the deadline and the names of the people who know, in one summary card.

  4. 4

    Offer optional check-ins

    Let the user pick how often friends hear: daily, weekly, or only at the end. Reports can be filed daily, weekly, or at the end of the commitment. Keep the check-in simple, such as a yes or no and an optional note.

Tip

Make the friend step optional. A user who wants a private goal should still be able to finish setup, and should not feel judged for choosing privacy.

Worked example: a running goal with a friend watching

This example follows how two real goal tools handle a goal such as running three times a week. Screen names come from their help pages and may change, so use this as a pattern, not a copy. The money side of these tools is left out on purpose.

  1. 1

    Write the goal

    The user first names the goal, then describes the actions that will get them there. For running, the goal is three runs a week, and the action is a planned run on each day.

  2. 2

    Name a friend during setup

    On stickK, a referee can be added during creation through an Invite a Referee step, or later from the details page.

  3. 3

    The friend is notified

    After each report, the referee gets an email asking them to confirm the report is accurate. The friend learns about the goal without the user having to send a message.

  4. 4

    The friend can check the claim

    A referee may accept the user's word, or ask for proof that the commitment was kept. This gives the friend a real role, not just a view.

  5. 5

    The friend can follow progress

    A supporter can see progress and post comments, so the friend can cheer or ask questions over time. This makes encouragement part of the same screen.

  6. 6

    Quitting is visible

    Because the friend already knows the goal, dropping it now has a social cost, which is the point of the design.

The money side is a separate idea. stickK can also send a pledged amount to a friend, a charity, or an organization the user opposes if the goal fails. Those stakes use loss to motivate, so they belong to their own lesson. Keep the friend step on its own when you copy this pattern.

Tip

Ask yourself what the friend sees on day one. If the answer is 'nothing until something goes wrong', the friend step is not doing its job.

Risks and ethics: protect people while you ask for commitment

A friend in the loop can help a user, but it can also hurt them. Designers need to protect three things: the user's privacy, the friend's choice, and the user's dignity when they fall short.

  • Privacy and consent

    Never add a friend without asking them first. Show the user exactly what the friend will see, such as progress only or the full history.

  • Audience control

    Let the user choose who hears, and let them change that list later. Never share a goal with a whole contact list by default.

  • Easy opt-out

    Friends should be able to leave, and users should be able to end, pause or change the arrangement without a penalty.

  • Shame-free failure

    A missed goal should lead to a plain next step, not a scolding message sent to everyone the user named.

Real products show both sides. Both rules protect the friend, and a good design should copy that care.

Some features push harder. That is pressure at the exact moment a person feels worst. Make sure any such rule is clear before the user commits, and never hide it.

Timing rules also carry trade-offs. The same rule can trap someone who truly needs to stop, so a designer should weigh that cost openly.

Tip

Test the failure screen. Read it as if a friend were looking over the user's shoulder. If the words feel harsh, soften them, and add a clear way to lower the goal, pause it, or remove a friend.

Check your understanding

Read each short scenario and decide which design fits the idea of a promise to friends. Think about who is told, who controls it, and what the user can change.

Quick check

A language-learning app wants users to practise every day. Which change best applies this lesson: (a) add a streak badge, (b) let the user pick a friend to receive their weekly goal and progress updates, or (c) send a push reminder at 8 pm? Explain your choice, and name one privacy control the screen should include.

Quick check

A walking app lets a user add a supporter for a goal of 10,000 steps a day. Which screen design best respects the friend and the user?

Key takeaways

Make Commitment to Friends works because a promise to another person adds a social cost that a private plan lacks. Build the flow in four parts: a clear goal, a simple choice of who to tell, a visible confirmation, and optional check-ins. Then protect the people involved. Ask for consent, let users choose and change their audience, make opting out easy, and never let a missed goal feel like a punishment. Treat the research with care, since some popular numbers have no source.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.