Time to Value: Measuring What Makes Users Stay
Most products lose people before those people ever feel the product work. This course teaches you to find that moment, measure how long it takes to reach it, and shorten it. It's written for product designers and product managers who want to read their own analytics instead of waiting for someone else to.
People throw four words around as if they mean the same thing: adoption, completion, retention, and time to value. They sit at different points in one user lifecycle, and the skill you're building here is knowing which one a given problem actually lives in. Confusing them is the most common mistake in product measurement.
You won't need to write code, but you will need to think clearly about what value means for your product, agree on how to count it, and read what the data tells you without lying to yourself. That last part is harder than it sounds.
What This Course Is, and What It Refuses to Do
Why it matters
Every product team eventually asks why people sign up and then disappear. The answer almost always lives in the stretch between signing up and feeling the product work. If you can measure it, you can shrink it, and shrinking it is one of the most valuable things a product team can do.
Concepts
Time to value is not a peer of adoption, completion, and retention, and this course is built around that distinction. It's one specific measurement that lives inside a single stage of the user lifecycle. The other three live in other stages. Treating all four as interchangeable is how teams end up measuring everything and improving nothing.
Instead of handing you four definitions, this course starts with the lifecycle, places each term where it belongs, then teaches you to measure and improve the one that matters most early: how long it takes a new user to reach value.
The honest frame. A metric is a flashlight, not a scoreboard. The number is only useful if it tells you where to point your next bit of work. If a metric goes up and you can't say why, you've learned nothing.
What you'll learn
The modules follow the same order you would run this work on a real product.
- Place the four terms in the lifecycle so you can name which stage any product problem belongs to.
- Define your value moment as one measurable event that two people would count the same way.
- Instrument the funnel with a handful of events and a tool pairing you can run yourself.
- Read the data as funnels, distributions, and cohort retention curves instead of one headline number.
- Shorten time to value with a written, testable change and a clear way to know if it worked.
The capstone ties it together. You run the full loop on one real product and leave with a one-page teardown a team could act on.
The Lifecycle, Not Four Words
Why it matters
If you can't say which stage a problem belongs to, you can't fix it. A retention problem and an activation problem look identical on a dashboard until you separate the stages. This module gives you the map everything else hangs on.
Concepts
A user moves through stages. The growth team at Reforge frames these as a chain you read backwards: start with retention as the goal, then work back through engagement to activation.
| Stage | The question it answers | Where our four terms live |
|---|---|---|
| Acquisition | Did they show up? | none of the four |
| Activation | Did they reach first value? | Time to value lives here. Completion lives here. |
| Adoption | Did they build it into a habit? | Adoption lives here. |
| Retention | Did they keep coming back? | Retention lives here. |
Activation is the moment a user completes the key action that delivers your product's core value. It's binary: they did it or they didn't. Sean Ellis, who coined the term growth hacking, describes the related aha moment as the point where the utility of the product clicks for the user and they understand why they need it.
Time to value puts a clock on it. Activation says whether they got there. Time to value says how long it took. A user who activates in five minutes and one who activates in five days are both activated, but they're not the same user, and the slow one is far more likely to leave before they ever arrive.
Completion usually means finishing a defined flow, like onboarding. Onboarding completion rate is a useful leading signal, but finishing onboarding isn't the same as reaching value. Plenty of users complete a setup wizard and still never feel the product work.
Adoption is sustained, repeated use, often of a specific feature. Optimizely draws a sharp line here that most teams miss: feature trial is one-time usage, feature adoption is repeated, sustained engagement. Opening a feature once isn't adopting it.
Retention is whether users keep coming back over time. Everything upstream feeds into it, and the business case for improving it is well documented. Fred Reichheld at Bain & Company found that increasing retention by as little as five percent can raise profits by twenty-five to ninety-five percent, depending on the industry (covered in HBR).
The trap. Teams jump straight to retention dashboards because that is where the business pain shows up. But by the time retention drops, the damage happened weeks earlier at activation. Retention is a lagging indicator. Time to value is a leading one.
Defining Your Value Moment and the Path to It
Why it matters
You can't measure time to value until you decide what value is. Most teams skip this and start tracking events before they agree on what success looks like. The data then becomes a debate over numbers instead of a source of insight.
Concepts
Your value moment is the first time a user does the core job your product exists for, not when they sign up or finish a tour. For a design tool it might be sharing a first prototype. For an analytics product it might be seeing a first real insight. For a messaging app it might be the first reply received.
The famous examples are useful and slightly misleading. Facebook found that users who reached seven friends in ten days were far more likely to stick. Slack pointed to around two thousand messages sent by a team. Twitter pointed to following thirty accounts. These became company-wide rallying cries.
Read this before you go hunting for your magic number. Mixpanel argues these numbers are an illusion. They are useful, but they are still an illusion. No single action perfectly predicts who stays. The value of a number like seven friends is that it focuses a whole company on one clear behavior, not that it is scientifically exact.
Define your value moment two ways and hold them loosely. First qualitatively: what is the experience that makes someone get it. Then check it against data: do users who take that action actually retain better than users who don't. Sean Ellis describes this as finding the action that maximizes the overlap between retained users and users who took it.
Then write the definition down as a measurable event. Vague: the user understands the value. Measurable: the user created a project, invited one teammate, and that teammate opened it, within the first seven days. The second version is something analytics can actually count.
Warm-up
- Take a problem your team is worried about right now and place it in exactly one lifecycle stage. If it seems to fit two, you have two problems.
- List the three actions your most loyal users took early that your churned users did not. These are your candidate value moments.
Activity: the TTV worksheet
This worksheet is the working document for the rest of the course. Fill it in for your own product and keep it next to you. Later modules sharpen it with real data.
| Step | What to do |
|---|---|
| 01 | Define the primary value moment. One measurable event with a time window. Avoid the word "understand." If an engineer and a non-product colleague picture different behaviors when they read it, rewrite it until they don't. If what you wrote is finishing a flow (completing onboarding, watching a walkthrough, reaching a screen), you have a completion metric. Rewrite it as the first time the user does the core job. |
| 02 | List every step it takes to get there. Start at sign-up and write down every screen, form field, and decision a new user passes through, in order. |
| 03 | Rate each step red, yellow, or green. Red: not necessary, so remove it. Yellow: necessary eventually, so defer it. Green: required to feel value. |
| 04 | Diagnose why people stall at each step. Friction: the step is tedious. Comprehension: they don't understand what to do. Trust: they don't believe the payoff is coming. |
| 05 | Capture empathy insights and top friction points. Write down what surprised you about the user's experience and which steps hurt the most. |
| 06 | Design the fastest path. Rebuild the flow on paper using only the greens. |
| 07 | Decide the first experiment. Pick the single change most likely to shorten time to value, and write down how you will know it worked. |
Steps six and seven are first drafts at this point. Module 04 gives you the data reads to check them, and Module 05 gives you the moves to act on them.
You've got it when…
You have a filled-in worksheet: a measurable value moment, a rated list of the steps to reach it, and one experiment you would run first.
Instrumenting the Funnel
Why it matters
A value moment you can't see in your tools is just an opinion. This module covers the small set of events worth tracking and the products that let a designer or PM answer their own questions without filing a ticket to the data team.
Concepts
You only need to track the steps between sign-up and your value moment, so you can see where people fall out. That's a funnel. Each step is an event with a clear name.
// The minimum funnel for a collaboration tool
account_created // acquisition
project_created // setup step
teammate_invited // setup step
first_invite_accepted // the value moment
returned_day_2 // early retention signalThe tools fall into a few groups. Most teams pick one analytics platform and add a qualitative tool. You don't need the rest.
Product analytics with strong funnels, cohorts, and retention curves. Self-service for PMs. Free starter tier.
Event analytics that competes directly with Amplitude. Funnels, retention, cohorts. Strong free tier.
Open-source analytics with funnels, session replay, and flags in one tool. Popular with engineering-led teams.
Adoption platforms. Track usage and ship in-app guidance without engineering. Good for onboarding work.
Lighter analytics built on event data, aimed at fast activation and retention reads for B2B.
Google Analytics 4. Free, common, weaker for product funnels than the event tools above. Fine to start.
Pair one quantitative tool with one qualitative one. Amplitude tells you that forty percent drop at the invite step. A session replay in Hotjar or FullStory shows you the confusing button that caused it. You need both halves.
Exercises
- Write the five-to-seven event names that make up your funnel from sign-up to value moment. Use consistent, past-tense naming.
- Check which of these events your product already tracks. Flag the gaps you would need engineering to add.
- Pick one analytics tool and one qualitative tool from the list and write one sentence on why that pair fits your product.
You've got it when…
You can name the exact events your product needs to track to see time to value, and which tool would show each one.
Reading the Analytics
Why it matters
A single average hides almost everything you need to know. The skill is reading the shape of your data. Once you have shipped and the events are flowing, this is what to look at.
Concepts
Start with the funnel. It shows how many users pass each step. The biggest single drop is your biggest opportunity. If forty percent of users create a project but only ten percent invite a teammate, your value moment has a wall in front of it at the invite step.
Then read time to value as a distribution. Userpilot's 2025 benchmark of 547 SaaS companies put median time to first value at roughly one and a half days, but an average can be dragged around by a few slow users. Look at the spread. If most users reach value in an hour and a long tail takes two weeks, the tail is your problem, and the average hides it.
Cohort retention is where it comes together. Group users by when they signed up, then track what fraction return over time. Productboard describes two ways to read the table. Read one cohort across time to see where it flattens, then read down a column to compare cohorts at the same age, which tells you if recent changes made things better or worse.
The shape of the retention curve tells you more than the headline rate. Amplitude and others describe three shapes:
The curve keeps falling and never flattens. Users aren't finding lasting value. This is a product-market fit warning.
Drops early, then levels off at a plateau. That plateau is your core of users who stayed. A sign of real fit.
Drops, flattens, then rises as lapsed users return. Rare and very strong. It hints at value that compounds over time.
The one comparison that proves time to value matters: split your retention by whether users hit your value moment. If activated users retain far better than non-activated ones, you have proof that reaching value drives staying. That difference is the argument for every onboarding fix you will ever propose.
On benchmarks. You will find numbers like a seventeen percent median activation rate or a twenty-four percent feature adoption rate. Treat them as directional. The right goal is your own curve getting better over time, not matching a stranger's average.
Exercises
- Build or open your sign-up to value-moment funnel and circle the single largest drop-off step.
- Plot time to value as a distribution. Note whether the average is being pulled by a slow tail.
- Pull a cohort retention chart and name which of the three curve shapes yours most resembles.
- Split retention by activated versus non-activated users and write down the size of the difference.
You've got it when…
You can look at a cohort retention chart and a funnel together and say where users are leaving and whether reaching value changes whether they stay.
Shortening Time to Value
Why it matters
Measurement is worthless if it doesn't change what you build. This module turns the read into a list of moves, the kind a product designer or PM can run without waiting on anyone.
Concepts
The whole job is to get more users to the value moment, faster. There are two ways: remove friction on the path, and pull the value earlier. Most teams only remove friction. Pulling value earlier is where designers earn their keep.
- Cut steps before value.
Every screen between sign-up and the value moment is a place to lose people. Remove fields, defer optional setup, allow social or single sign-on. Sean Ellis frames activation work as obsessively reducing friction in the first run. - Start users with something, not nothing.
Empty states kill momentum. Seed a sample project, prefill a template, or import existing data so the user sees value before they have done the work. - Guide to the one action that matters.
Use in-app prompts, checklists, and empty-state nudges that point at the value moment instead of a feature tour. Tools like Pendo and Appcues let you ship these without engineering. - Move value upstream.
Ask whether the user can feel the product work before finishing setup. If first value can happen on screen two instead of screen ten, time to value collapses. - Test one change at a time.
Pick the biggest funnel drop, ship one fix, and watch whether that cohort reaches value faster and retains better. Test one variable, then move to the next.
The discipline. Improving a number you don't understand is gambling. Before you ship a fix, write down the cause you believe is driving the drop, then check whether your change moved that specific step. If it moved and you can't explain why, don't celebrate yet.
Planning and assessing are two different modes. Before launch, you set the value moment and the funnel events and predict where friction will sit. After launch, you read the funnel and the curve to see where you were wrong, then work to close the distance. The loop runs every cycle.
Exercises
- Take your largest funnel drop and list three friction-removal changes and one move-value-earlier change.
- Write the hypothesis for your top change as: we believe X causes the drop, so we will do Y, and expect step Z to improve.
- Design an empty state for your product that shows value before the user has created anything.
- Define exactly which metric you will watch to know whether the change worked, and over what time window.
You've got it when…
You can take a funnel drop and produce a written, testable plan to shorten time to value with a clear way to tell if it worked.
Run the Full Loop on One Real Product
The brief
Project: A Time to Value Teardown
Pick one real product: yours, your client's, or one you use daily. Define its value moment, map the funnel that leads to it, decide which tools would measure it, read the data you have or can reasonably estimate, and produce a one-page plan to shorten time to value with a single testable change. The deliverable is a short written teardown anyone on a product team could act on.
The process:
- Place the product in the lifecycle and state which stage you are working in.
- Write the value moment as one measurable event with a time window.
- List the funnel events from sign-up to that moment.
- Choose one analytics tool and one qualitative tool, and say why.
- Read or estimate the funnel and name the largest drop-off.
- Identify your retention curve shape and the activated-versus-not gap.
- Write one hypothesis and one testable change to shorten time to value.
- State the exact metric and window you will use to judge success.
You have done the work when someone who has never seen the product can read your page and know where users are being lost, why you think so, and what to try first.
Reference: Vocabulary & Sources
Products mentioned
Quantitative analytics: Amplitude, Mixpanel, PostHog, June, and Google Analytics 4.
Adoption and in-app guidance: Pendo and Appcues.
Qualitative, session replay and heatmaps: Hotjar and FullStory.
Sources for deeper learning
Sean Ellis on growth hacking and the aha moment, in his own words, at learn.marsdd.com. He wrote the book Hacking Growth.
Mixpanel argues the famous magic numbers are a useful illusion, not science, at mixpanel.com.
A public summary of Reforge's retention and engagement framework, by Conor Dewey, at conordewey.com.
Amplitude on computing and reading retention curves at amplitude.com, and curve shapes plus cohorts at amplitude.com/explore.
Productboard on reading a cohort table both directions, and the activated-versus-non-activated comparison, at productboard.com.
Product School on time to value as a diagnostic at productschool.com.
Userpilot's 2025 benchmark of 547 SaaS companies, source of the roughly day-and-a-half median, at userpilot.com. Read benchmarks as directional.
Appcues on defining the activation event before measuring at appcues.com, and Optimizely on trial versus adoption at optimizely.com.
The Reichheld and Bain retention-to-profit finding, via Harvard Business Review at hbr.org and Bain at bain.com.