Activation is a question, not a metric

Ask five people on a team to define “activation” and you’ll get five different numbers, all defensible, none of them the reason anyone changed what they did this week. A single activation percentage rarely moves a decision. What moves a decision is a specific account, doing a specific thing, that someone has to respond to.

Activation as a behaviour, not a rate

A rate tells you 34% of trials activated last month. It doesn’t tell you which fourteen accounts crossed the line yesterday, or which one crossed it and then went quiet. Replace the rate with a named behaviour tied to an account: “invited a second teammate,” “connected a data source,” “completed the first weekly export.” Whatever it is, it should be something one person did, on one day, that you can point to.

Once activation is a behaviour, it stops being a slide and starts being a queue. Every account either did the thing this week or didn’t, and the didn’t list is where the meeting spends its time.

Turning it into a weekly question

The question we ask every week is not “what’s our activation rate.” It’s “which accounts crossed the activation line this week, and which ones were supposed to and didn’t.” That second half is the one that produces action. An account that missed its expected activation date is a person who needs a call, not a data point that needs a footnote.

• Which accounts crossed the activation behaviour in the last seven days?

• Which accounts were expected to cross it by now and haven’t?

• Of the accounts that crossed it last month, how many are still active?

The trap: optimising the definition instead of the outcome

Once a team has an activation number to report, someone eventually notices that the number can be improved by loosening the definition. Lower the bar from “completed setup” to “opened the app,” and the rate climbs without a single customer behaving differently. We’ve done this ourselves, twice, both times by accident and both times because the metric had started answering to a target rather than to a decision.

The fix isn’t a stricter definition. It’s tying the behaviour to a downstream outcome you check separately, like retention at ninety days. If tightening or loosening the activation definition doesn’t move that outcome, the definition was never the lever.

If you can improve the metric without a single customer doing anything different, you’re not measuring activation anymore. You’re measuring the definition.

What this looks like in a real review

In practice, this takes about six minutes of a weekly review, using Zevara to surface the accounts that crossed or missed the activation behaviour without anyone building a spreadsheet on Sunday night. The rest of the time goes to the accounts that missed it, one by one, with a name attached to each.

The same trap shows up in reverse. Teams sometimes tighten the definition to make a lagging number look intentional, calling a plateau “more selective activation” without changing what they measure downstream. The tell is the same either way: the metric moves and the outcome doesn’t.

Activation also behaves differently by account size. A five-person team crosses most behaviours within days; a two-hundred-person account can take six weeks to reach the same point through procurement and rollout, and treating both on the same weekly clock produces a false alarm on the larger account almost every time.

The fix there isn’t a different metric, it’s a different expected timeline per account size, checked against the same behaviour. Once we added that, the “missed activation” list stopped being dominated by accounts that were never actually behind. Write the adjustment down before you need it, not after the first false alarm makes everyone distrust the number.

None of this is unique to Zevara or to us. Any weekly review that reports a rate instead of a behaviour will eventually face the same choice between reporting honestly and reporting well.

This is why we resist giving activation a single company-wide owner. The product team defines the behaviour and keeps it consistent across the business, but the weekly check belongs to whoever owns the account relationship, because they are the one positioned to act on a miss the same day it appears rather than a week later in a retro. Splitting definition from ownership this way keeps the metric honest without making it any one person’s job to defend.

A rate is easy to report and easy to ignore. A named behaviour, checked against a specific list of accounts, is harder to report and much harder to ignore.