Jelena Racković · · 2 min read · Product & discovery
Revenue is too late: measuring what the team can actually move
Revenue matters. Nobody in a business can afford to forget it. But as a measure of what a product or design team is doing well, it is almost useless. It arrives late, it is shaped by a hundred things outside the team’s control and it tells you that something went wrong long after you could have fixed it.
A number nobody can move
When a team is judged on revenue alone, two things happen. First, it loses any sense of cause and effect, because revenue rises and falls with sales cycles, pricing, the market and the season. Second, it starts to feel helpless, or worse, it starts chasing short-term tricks that move the number this quarter and damage the product in the next.
Find the behaviour behind the revenue
The better question is which user behaviour drives revenue, and how the team can influence it. In a B2B platform, it might be how many clients complete onboarding in the first week. In a media product, how many readers come back three times in a month. In an internal tool, how quickly a request moves from submission to approval. These behaviours respond to design and product decisions within days or weeks, not quarters.
Measure what you can move
Once the behaviour is clear, the team can set goals it can actually influence, see the effect of its work quickly and learn from it. Revenue still sits at the top as the ultimate outcome. But the daily focus moves to the lever the team holds, and the conversation shifts from blame to improvement.
Closer to the work
Measuring this way also makes the work more meaningful. Designers see that a clearer flow brings more completed sign-ups, developers see that a faster page keeps more readers and managers see where to invest. Revenue follows, as it should, but it follows from things the team understands and controls.
Is your design system starting to fade?
I’d like to hear about it →