Time to Wow

While signup counts were the result being reported, all the effort went into widening the door. Fewer fields, a bigger button, more advertising, and the number rose — and that number sat on the first line of the report.

The limit showed up when Mia put two tables side by side. Monthly signups had gone from 620 to 1,000, and people who created a first document had gone from 310 to 340. Three hundred and eighty more arrivals bought thirty more users. Session records showed that more than half of new accounts closed the tab without taking any action at all, and the median time those people stayed was four minutes.

Time to wow exists to measure those four minutes. Counting how long it takes an arriving user to reach something worth having, rather than how wide the door got, moves the work from the signup screen to the screen right behind it.

Take the gap between one user's signup timestamp and the timestamp of the first moment they hit value, then summarize those gaps as a median. Four steps.

1. Decide what counts as that moment. For a collaborative document tool, the candidate is the first time someone watches a colleague editing the same page. Pick it from data rather than intuition: split users who were still around two months later from users who left, and find the first-week action that separates the two groups most. If people who shared a document retained at 58 percent and people who didn't retained at 14 percent, sharing is the moment.
2. Fix the start point, normally the signup timestamp. Starting from the first visit mixes in people who came only to look, which makes the number swing.
3. Measure the gaps and take the median. Averages get dragged by the tail — one person who arrives three days later pushes a twenty-person average up by hours. A median ignores that person.
4. Count the people who never got there. Anyone who hasn't hit the moment within 24 hours has no value to record, so the reach rate goes alongside. If 420 of 1,000 signups reached it inside a day and the median for those 420 was six minutes forty seconds, this product has two numbers: 6:40 and 42 percent.

Both get written down because either one alone reads backwards. A two-minute median with a 12 percent reach rate does not mean the product is fast; it means a small group who were going to succeed anyway moved through quickly. The other 88 percent got nowhere and the number still looks good, which is how a metric meant to expose a problem ends up hiding one.

Splitting by arrival path matters too. Someone who found the product in search starts from a different line than someone who came through a team invite. The invited user is standing in front of a colleague's document the instant they click, which puts their median in the tens of seconds. Blend the two groups and any month where the invited share rises looks like a month where the product improved.

No threshold works across products. For a document tool or a notes app, where one person can produce a result in five minutes, five minutes is the bar. For a product that needs data connected and a dashboard assembled, two days is normal, and holding that product to five minutes only converts something meaningless into the wow moment.

So the comparison is against last month's number for the same product, not against another company's. Going from an 8:00 median at 38 percent reach to 6:40 at 42 percent means both numbers improved. Going to 6:00 at 31 percent means only the fast minority is left. Quarter-over-quarter cohorts read better than month-over-month here, because a single marketing campaign can change who arrives.

Shortening the number is usually less about removing steps than about doing the first one for the user: an example document instead of a blank page, a first paragraph already written, three commonly used templates offered up front. Where cutting fields in self-serve signup widens the door, this takes the first step on the user's behalf once they're through it. The two get worked on together, since a wide door in front of an empty room produces the exact pattern that made this metric necessary.

The stage where a new user first feels the value is itself called activation. Time to wow is that stage measured in minutes, so if the activation rate sits flat while this number drops, the first thing to check is whether the definition quietly moved to an easier action.

"Median is six forty at 42 percent reach. Both better than last month."

Reporting the time and the reach rate together.

"The number only looks good because invited users are mixed into it."

Failing to split by path inflated the figure.

"Let's move the wow moment from document created to document shared. That's where retention splits."

Re-picking the reference action from data.

Last quarter Noa reworked Pagedeck's first screen after signup. Instead of a blank document, a meeting-notes template opens with today's date already in the first line. The median fell from 9:10 to 5:20.

The reach rate, though, slipped from 39 percent to 37. What Mia pointed at was not a bad template. Offering only the meeting-notes one sped up the people who came to write meeting notes and made everyone else start by deleting a template. The next piece of work became showing three templates with a blank-document option beside them.

The most common misreading is that shorter is always better, which follows naturally from it being a measure of time. But the number counts only the people who arrived, so the harder a product is to reach value in, the better the surviving minority makes it look. Target the time without recording the reach rate and a team drifts toward redefining the wow moment as something easier. Move it from sharing a document to creating one, and from creating one to opening the app, and the median falls to tens of seconds while two-month retention does not budge.

The other one is that more guidance shortens it. Watching first-time users get lost makes adding explanation the obvious response. Adding steps to a post-signup tour usually lengthens the number instead. If a five-screen tour takes the median from six minutes to eleven with the reach rate unchanged, users spent those minutes reading rather than working. Designing onboarding, the process of helping a new user settle into a product, around distance to the first result rather than volume of explanation is what moves this number.