A steep downward-sloping curve of fading footprints, with a bright glowing marker placed early on the path where most footprints are still solid, versus a faint marker placed far down the path where almost no footprints remain Growth
AI-generated, Working Theory
Growth · ◉ Evergreen

How long until it's worth it?

by · ·4 min·Working Theory

Very few dashboards can tell you the number that sits between signups and month-one retention and quietly decides them both: how long it takes a new user to reach the moment the product is actually worth it.

Most growth dashboards can tell you how many people signed up and how many are still around a month later. Very few can tell you the number that sits between those two and quietly decides them both: how long it takes a new user to reach the moment the product is actually worth it. Not the moment they finish signup. Not the moment they tick your activation checkbox. The moment they get the thing they came for — the first real payoff — and feel it. Call it time-to-value, and treat it as a lever you drive down, not a stat you glance at.

The reason it’s a lever and not a vanity number is that attention leaks on a schedule. A new user arrives with a small, decaying budget of patience and intent, spent from the second they land. Every screen, every field, every “verify your email and come back” is a place where some fraction of them quietly leaves — and they leave before they ever felt why they came. If your first genuine payoff sits twelve minutes and nine steps down the path, you are collecting your survivors at the bottom of a long slide. If you can get them there in two minutes and two steps, you collect them near the top, while the budget’s still full. Same product, same payoff — a completely different number of people who ever experience it.

users still paying attention minutes since sign-up → value at 2 min value at 12 min move the payoff left, and more people are still there to feel it
Where you place the first payoff on the attention curve sets how many people ever reach it. Original diagram · Working Theory

Once you can see the number, the work almost names itself. Map the true critical path — the shortest honest line from “landed” to “first payoff” — and then fight everything that isn’t on it. The profile you can ask for later. The team invite that can wait. The settings tour that’s really for you, not them. Every step you defer off the critical path pulls the payoff left on the curve and hands you more survivors. This is the operational twin of an idea worth reading next to it — your activation metric might be a thermometer, not a lever — which warns you to pick a “value” event that actually causes retention rather than merely correlating with it. Time-to-value only pays off if the “value” you’re racing toward is the real one.

Which is the one caution that keeps this from turning into a stopwatch you optimize into the ground. The goal is time-to-value, not time-to-anything. Rush people past the setup that the payoff genuinely depends on and you’ll hit your two-minute target and lower your retention — you delivered them fast to a room with nothing in it. So compress ruthlessly, but only on the path to the payoff, and never through it. Instrument the median minutes-to-first-value. Watch it per cohort. Drive it down on purpose. The fastest-growing products aren’t the ones with the most features on the first screen; they’re the ones that get you to “oh, that’s why” before your patience runs out.

Sources

  • Time-to-value / speed-to-first-value as a growth lever
  • the distinction between activation events that correlate with retention and those that cause it

Liked this? Get the next one in Working Theory.

Going weekly in August (it's in beta now). One genuinely interesting read on building, the brain, and the science most people missed.

Subscribe →
Got a reaction, a counter-example, or something I missed? Reply by email — I read everything.
◉ join in

Where have you hit this — in a product you use, or one you're building?

Threads open here soon. For now, the conversation lives two clicks away — discuss on GitHub, or just reply by email. I read and answer everything.