Application strategy: metrics and KPIs for small teams

A small team has a problem that no one mentions in metrics manuals: time. Every hour spent assembling the panel is an hour not spent building the product. And the panel does not deliver functionality.

The literature on product metrics almost always assumes a structure that the lean team does not have: someone dedicated to data, robust tools, time for analysis. When a team of three or four people tries to follow this manual, one of two things happens, either they drown in dashboards that no one looks at, or they give up measuring and go back to deciding in the dark.

The thesis of this text, for those who run an app with few people, is a defense of focus: the challenge of a small team is not to measure a lot, it is to choose the very few numbers that actually change decisions. Metrics that don't change what you're going to do the following week are a luxury that a lean team can't afford.

Why copying the dashboard from big companies breaks the small team

Large companies monitor dozens of indicators because they have people to do so and because each area takes care of a piece. A small team doesn't have this division. The same people who write code also look at metrics, talk to the user and decide on a direction.

Trying to replicate the dashboard of a large company, in this context, is self-sabotage. You spend scarce energy collecting and organizing numbers, and you have little left over for the only thing that matters: using those numbers to decide and act.

Worse: too many metrics generates paralysis. Faced with twenty indicators, no one knows which one to pull. The team is busy interpreting data instead of improving the product. For those who are small, simplicity is not laziness, it is a survival strategy.

The question before the metric: what would I do differently?

The best filter for a lean team is brutally practical. Before adopting any metric, ask: if this number goes up or down, will I do something different?

If the answer is no, the metric is not worth your time. It may be interesting, it may sound professional, but if it doesn't change the decision, it's dead weight on the panel. A good metric, for those with few people, is the one that triggers action.

This filter eliminates most vanity metrics out of the box. Total downloads rarely change what you do tomorrow. Retention of the last cohort, yes, it tells you whether you should correct the product before bringing in more people.

The minimal dashboard for a small team

A lean team can make good decisions with a handful of well-chosen indicators.

Retention of new users. The number that tells you whether it is worth bringing in more people. If those who enter don't stay, attracting more is a waste. This is almost always the most important indicator for a small team.

Activation. How many of those who arrive actually start using the product for real. If there are a lot of people coming in and stopping at the door, the problem is at the beginning of the experience, and this usually has a cheap and high-impact fix.

Main function usage. The frequency of the action that defines the value of the app. Looking at this weekly gives an honest pulse of health without requiring complex analysis.

Qualitative signals. For a small team, talking to users is cheaper and richer than putting together sophisticated analyses. What people complain about, what they praise, where they get stuck, this, coming straight from the source, is often worth more than a graph.

Four fronts. It's enough to decide well without drowning anyone.

The specific risks of measuring too little

Focus has a cost, and it's worth recognizing it. Looking at few metrics means, by definition, having blind spots. Something may be breaking in a dimension that you are not observing.

The defense against this is not to measure everything, it is to review from time to time whether the chosen metrics are still the right ones. As the product evolves, the number that matters most changes. The minimal panel needs to be revisited, not frozen.

There is also the risk of confusing simplicity with superficiality. Looking at average retention, and not behavior by cohort, can hide the fact that new users are worse off than old ones. A small team needs few metrics, but they need to be well chosen and well read. Simple is not the same as shallow.

The rhythm of looking matters more than the sophistication of the data

A small team gains less from in-depth analysis and more from regularity. Looking at the same four indicators every week, at the same time, creates something that no sophisticated dashboard delivers on its own: a sense of direction over time.

The advantage of regularity is that it reveals trends, and trends are what actually inform decisions. An isolated number says almost nothing. The same number observed for six weeks shows whether retention is improving, stable or bleeding, and that's what changes what the team does.

This ritual also solves a typical lean team problem: the metrics that no one looks at. It's easy to set up a panel and abandon it. A fixed, short moment during the week, dedicated to looking at the few numbers that matter and deciding on an action based on them, is worth more than any expensive tool consulted sporadically. Cheap consistency beats intermittent sophistication.

Simple tool beats powerful tool

A common temptation in small teams is to adopt a powerful analytics platform, thinking it will solve the data problem. The opposite almost always happens: the tool is so complex that no one configures it correctly, and it becomes just another half-baked thing.

For those with few people, the best tool is the one the team actually uses. A well-maintained spreadsheet, fed consistently, far outperforms a sophisticated platform forgotten in the first week. The discipline of looking is worth more than the power of the tool.

In the end, a small team's metrics strategy is a small team's strategy in general: do little, but do it well. Pick the few numbers that matter, look at them regularly and have the courage to act on what they say. Focus is not what remains when there is a lack of people, it is the advantage of those who are small and know it.

This simplicity is a phase, not a destination. As the team grows and gains capacity, it makes sense to expand what is measured. But the discipline learned while you're small, linking each metric to a decision, is what keeps the dashboard from bloating without purpose later on. Those who learn to measure with a focus on scarcity rarely fall into the trap of excess when the structure increases.

If you run an app with a lean team and feel like you're measuring too much or too little, it's worth talking about how to pare it down to the essentials. On the blog there are other texts about product management and focus that talk about this challenge.