Skip to main content

Choosing Your Next Milestone: One Target at a Time

Planning · 10 min read ·

How to pick a single, concrete milestone that moves your product to the next stage, with a test for good milestones and examples for each stage of growth.

Illustration: A cyan path across an isometric plain with a single flag marking the next milestone and small faint flags beyond it, minimal labels

A long journey feels manageable only when you can see the next landmark. Without one, effort spreads thin: a bit of design, a bit of marketing, a bit of code, a good deal of worry. With one, work narrows. You know what you are trying to achieve this month, and, which is just as useful, what you are choosing not to do.

This guide is about choosing that landmark well. It explains what a good milestone looks like, how to pick one for your current stage, how to set it up so that you learn from the result and what to do when you hit it or miss it.

What a milestone is

In project management, a milestone is a significant point or event in a project, marking progress or the completion of a phase. It is not a task. A task is work to be done. A milestone is a state of the world that you can check: it either has happened or has not.

For a young product, good milestones are about evidence, not activity. "Redesign the homepage" is a task. "Twenty people sign up from the new homepage in a week" is a milestone. The first tells you what to do. The second tells you whether it worked.

Why one at a time

The temptation is to chase several. Growth, revenue, a new feature, press, a new hire. Each seems important, and each would be nice.

The problem is learning. If you change five things at once and a number moves, you do not know which change did it. And effort is finite: a team that is working on everything is rarely finishing anything.

A single main milestone has three benefits. It focuses the team. It makes trade-offs easy: does this help us reach the milestone? And it gives you a clean result to learn from. Smaller supporting tasks are fine, as long as everyone knows which one is the main target.

What makes a good milestone

Use this test. A good milestone is:

  • Specific. It names a number, an event or a state. "More users" is not specific. "Fifty weekly active users" is.
  • Checkable. Anyone could look at the evidence and agree whether it has been met.
  • Meaningful. Reaching it would change what you do next, or prove something you need to know.
  • Within reach. Difficult but plausible in weeks, not years.
  • Dated. It has a rough time frame, so that you review it.
  • Owned. One person is responsible for tracking it.
  • Honest. It measures something real, not a number that can be inflated without helping.

If a candidate fails one of these, rewrite it. A good test is to imagine telling a friend: "We will have reached our milestone if ___." If you cannot finish the sentence, the milestone is not ready.

Choosing by stage

The right milestone depends on where you are. The guide to mapping growth stages sets out the stages; here are typical choices.

Idea. Talk to ten people in your target group and write down the problem in their words. Evidence: ten dated conversation notes and one clear problem sentence.

Prototype. Five people use a working version for its intended purpose without your help. Evidence: observed sessions or logs.

Launch. A hundred visitors arrive from outside your personal network, and a stated number try the product. Evidence: analytics showing sources and first use.

Early traction. A group of users who return weekly for a month. Evidence: a simple retention table.

Repeatable growth. One channel brings a predictable number of new users per week. Evidence: several weeks of consistent figures.

Notice that each milestone moves you from one question to the next. They are not arbitrary targets. They are answers.

Turning a milestone into a hypothesis

A hypothesis is a proposed explanation or prediction that can be tested. The lean approach to building products treats each step as an experiment: you form a hypothesis, build the least needed to test it, measure the result and learn.

Write your milestone as a hypothesis:

  • "If we simplify the first screen, then at least thirty per cent of new visitors will complete setup, measured over two weeks."
  • "If we offer a short onboarding message, more than half of new users will return in the following week."

This format forces you to name what you will do, what you expect and how you will know. It also makes failure useful: if the prediction is wrong, you have learned something specific.

Setting the size

Too big and the milestone feels unreachable and gets ignored. Too small and it does not move you. A useful rule of thumb is to choose something that you could reach in four to eight weeks if things went reasonably well, and could clearly miss if they did not.

If a milestone is large, break it into a short sequence: each step a checkable point on the way. Keep only the next one in focus. Plan the one after, loosely, but do not commit until you have learned from this one.

Writing it down

Keep your milestone on one card, visible to everyone who works on the product.

  • Name: a short phrase.
  • Evidence test: exactly what will show it has been met.
  • Date: when you will review.
  • Owner: who tracks it.
  • Supporting work: three or four tasks at most.
  • What we will not do: things you are deliberately postponing.

The last line is underrated. Saying no is easier when it is written down.

Tracking without obsession

Check the milestone on a regular schedule, weekly for most teams.

  1. Update the number or state of the evidence.
  2. Compare with the plan: ahead, on track or behind?
  3. Note what changed in the past week that might explain it.
  4. Decide one adjustment, or none.

Resist checking every hour. Daily figures bounce about, particularly with small numbers, and watching them can cause overreaction. A short weekly review is enough.

When you reach it

Reaching a milestone is a moment to pause, briefly.

  • Check the evidence honestly. Did you meet the test as written, or did you move the goalposts?
  • Record what you learned: what worked, what did not, what surprised you.
  • Say thank you to the people who helped.
  • Choose the next milestone, using the same test.
  • Share it, if you are comfortable. A short public note on progress builds credibility.

Do not celebrate by immediately adding three more targets. Take the time to understand how you got there, because that understanding is what you can repeat.

When you miss it

You will miss some. A miss is information, not a verdict.

  1. Look at the data. How far off were you? Was progress steady or sudden?
  2. Ask why. Was the milestone too ambitious, the approach wrong or the evidence unclear?
  3. Separate the problem from the plan. A missed milestone might reveal that the plan was wrong, or that the underlying assumption was.
  4. Decide: extend the date, shrink the target, change the approach or choose a different milestone.
  5. Write down the lesson, and what you will do differently.

Avoid two bad responses. One is to redefine the milestone so that you have technically met it. The other is to abandon it quietly and pick another, so no lesson is drawn.

Milestones that mislead

Some targets look good and teach you nothing.

  • Vanity numbers. Page views, followers and downloads, if unconnected to real use.
  • Activity targets. "Send fifty emails" measures effort, not outcome.
  • Others' benchmarks. A target borrowed from another company's story may not fit your product.
  • Cliffs. Milestones with no intermediate steps, which feel impossible until they are suddenly over.
  • Deadlines set for appearances, such as a date chosen to look good in a post.

Ask of each candidate: what would we do differently depending on the result? If the answer is nothing, pick another.

A worked example

A two-person team has a note-taking tool with some regular users and a slow trickle of sign-ups. They list five possible goals: add a mobile app, improve search, write more blog posts, apply to a directory and fix onboarding. All plausible. They place themselves at early traction and ask which one answers the question, "Do people come back?"

They look at their data: of the last hundred sign-ups, forty never created a second note. They choose a milestone: "At least fifty per cent of new sign-ups create three notes in their first week, measured over two weeks, from the current forty per cent." The owner is the designer. Supporting work: simplify the first screen, add a short prompt for the first note and send one welcome message.

They write down what they will not do: no mobile app, no blog posts, no new directory this month. After three weeks, forty-six per cent are creating three notes. They did not hit the target. They look closer and see that most of the lift came from the welcome message, and the first-screen change did little. They extend the target by two weeks, drop the unhelpful change and double down on messages. The next review shows fifty-three per cent. They record the lesson and pick the next milestone.

Questions makers ask

Can the milestone be financial? Yes, if it is concrete and meaningful, such as a first paying customer.

What about team milestones? The same rules apply. A hire, a process or a release can be a checkable marker.

How do I choose between two good options? Pick the one that answers the question you most need answered right now.

Should I tell my users? If it concerns them, yes. A simple, honest note about what you are working on builds trust.

Summary

A milestone is a specific, checkable marker of progress. Choose one at a time, matched to the stage you are in and written as a hypothesis you can test. Make it specific, measurable, meaningful, reachable, dated and owned, and write down what you are not doing. Review weekly, record what you learn when you reach it or miss it and avoid vanity numbers. A good milestone turns a vague wish to grow into the next clear step.

Questions and answers

What is a milestone?
A significant, checkable point in a project that marks progress, such as a first hundred active users or a working payment flow.
How many milestones should I pursue at once?
One main milestone at a time. Several at once dilute attention and make it hard to learn what caused a result.
How is a milestone different from a goal?
A goal is a wider direction. A milestone is a specific marker on the way, with an evidence test and a rough date.
What if I miss the date?
Look at why, adjust the plan and, if needed, choose a smaller milestone. A missed date is information.
Should milestones be public?
Sharing the next one can create useful accountability, as long as it is honest and you are willing to report the result.

Sources

Support