Usage Frequency Ratio

An active user count only describes size. A hundred and twenty thousand people used the product this month tells you the scale and nothing else — whether those people came every day or stopped by once all month hides behind the same figure. The two situations are nothing alike as products, and they both get written down as 120,000.

The gap showed itself at Pagedeck during a quarter when Ravi spent heavily on advertising. Monthly active users went from 8,400 to 12,000 while paid conversions and revenue barely moved. Grace asked why a 40 percent increase in people changed nothing, and answering that meant looking at what the new arrivals did once they were inside. A monthly count alone offered no way to look.

A proper way to measure frequency already existed: group everyone who arrived in the same period and follow that group over the following weeks. It takes weeks before it answers anything, and it takes an analyst. The usage frequency ratio is the quick instrument that sits in that gap. Divide three numbers already on the dashboard by each other and the answer is available the same day.

Divide daily, weekly and monthly active users — all counted under the same definition — by each other. Three pairings are useful, and each answers a different question.

1. Daily over monthly. The share of a month's users who showed up on a given day. Twelve thousand daily against 120,000 monthly is 10 percent. Multiply that by 30 and you get the average number of days per month one person shows up: 10 percent works out to three days. This is the one that reads attachment as a single number, it gets used more than the other two, and it also goes by the name stickiness.
2. Daily over weekly. The share of a week's users present on a given day; multiply by seven for days per week. For a product used at work, weekends fall out of the window, so this pairing gives the more honest figure.
3. Weekly over monthly. How many people stop by only once in the month. Above half means almost nobody is an occasional visitor. Below a quarter means most of the audience arrives once a month and leaves.

One condition has to hold before any of the three mean anything: all the inputs must be measured with the same ruler. If daily active users (DAU) and monthly active users (MAU) disagree about what counts as active, which midnight ends the day, or whether employee accounts are stripped out, the quotient carries no information. Count document opens daily and every login monthly, and the ratio comes out low for reasons that have nothing to do with the product.

A good level follows from how often the product is meant to be used. A product with a reason to be opened daily and one with a reason to be opened monthly were never in the same range to begin with. Messaging apps clear 50 percent; a payroll tool at 5 percent is behaving normally. Reading an industry average of 20 percent and declaring your own 11 percent a failure is the most common mistake made with this metric.

So the reference points come from inside: last quarter's value, the value before and after you changed something, and how often the product was designed to be used in the first place. That third one is a judgment rather than a number. A collaborative document tool should be opened on every working day, so the weekly pairing ought to land somewhere in the forties — well below that means a reason to open it hasn't shown up weekly yet.

When the value moves, always check which side of the fraction moved. A ratio rises along two different paths. The same people come more often, or the occasional visitors leave entirely and shrink the denominator. The second path is a product getting worse while its metric improves, so a ratio watched by itself invites applause at exactly the wrong moment. Keeping the absolute weekly active users (WAU) next to it separates the two cases.

"Monthly is up 40 percent and the usage frequency ratio dropped from 11 percent to 8."

The people we brought in came through the door and never settled.

"We can move this ratio with notifications, but I'd rather we didn't."

The easy way to move the number is bad for the product.

"Our daily and monthly definitions don't match. Let's fix the definitions before dividing them."

Two values measured with different rulers can't be divided into anything trustworthy.

Pagedeck brings this ratio out only at quarterly reviews. After a quarter where Ravi pushed acquisition, it's the first thing Mia checks: did the ratio hold up against the extra volume. In the quarter when monthly went from 8,400 to 12,000 while the ratio fell from 11 percent to 8 percent, the conclusion was that people arriving from ads never found something to do inside the product, and the next quarter's plan moved from acquisition toward the first-week experience.

One number didn't make that decision. It pointed at where to look, and what was actually wrong came from separately picking apart what new accounts did in their first week.

Taking 10 percent to mean each user spends three days a month in the product is the first misreading. The multiplication is clean, so it reads naturally. But an average conceals the distribution behind it. The same 10 percent could be everyone showing up three days, or a tenth of the audience showing up daily while the other 90 percent stops by once. The two call for completely different work — nudging everyone up a little versus giving 90 percent of people a reason to come back a second time. Plan from the average alone and you end up doing neither.

Treating the ratio itself as the goal is the other frequent move, and it happens because raising it is easy. Send three notifications a day and next month's ratio will certainly climb, along with the number of people who turn notifications off — and people rarely turn them back on by themselves. That state, where notifications come often enough that recipients skip them or disable them outright, is called notification fatigue. The ratio is an instrument, not a thing to lift; what deserves lifting is the reason people have to come back each week.