Stop measuring happiness. Start measuring team net value.

Most team surveys ask one question in many forms: are people happy here? Engagement, satisfaction, eNPS, weekly mood check-ins. The scores come back, the dashboard turns green or amber, and the leader is left with a number that says how people feel and nothing about what to do next.

We do not think happiness is unimportant. Gallup's meta-analysis of its Q12 engagement survey reports that business units in the top quartile of engagement are 23% more profitable than those in the bottom quartile, with markedly lower turnover. Engagement matters. The problem is that an engagement score is an outcome, not a lever. It tells you that something is working or not working, and leaves you to guess what.

Why happiness scores plateau

Run an engagement survey for three years and you will usually see the same curve. The first result is a shock, a few visible things get fixed, the score rises. Then it settles somewhere around "fairly positive" and stays there. Every survey after that produces the same meeting: the number is fine, a few comments are worrying, let us do a workshop.

There are three reasons for the plateau.

• A happy team and a productive team are not the same thing. A team can enjoy working together, feel appreciated and still miss every deadline, because nobody agreed what the goal was. The happiness score cannot see this.
• Averages hide the split. A 3.8 out of 5 can mean everyone chose 4, or that half the team chose 5 and the other half chose 2. The second team has a problem the first does not, and the average looks identical.
• The score has no owner. "Engagement" does not belong to anyone. Nobody can act on it directly, so it becomes something HR reports and managers acknowledge.

A P&L for the team

When we started building PEAKTEAMS we borrowed an idea from finance. A company does not run itself by asking whether customers are happy. It keeps a profit and loss statement and looks at what comes in, what goes out and what is left. We wanted the same instrument for a team's capacity to create value.

The research base is the input-process-output view of team effectiveness, which Ilgen, Hollenbeck, Johnson and Jundt refined in 2005 into a model of teams as systems that turn resources into results through how they work together. On top of that we add one line that most models leave out: friction, the energy a team loses to bureaucracy, politics and unproductive meetings.

Each team member answers the survey in about 12 minutes. Every KPI is scored from 1 to 5, and the four lines are combined into one number.

What Team Net Value is

Team Net Value is a score from 0 to 100. It is the value a team creates, the average of Input, Process and Output scaled to 0 to 100, minus a tax for friction. The tax is multiplicative rather than subtractive: friction can only consume value that exists. A team that creates very little cannot look average just because it has low friction, and a team with severe friction can lose almost everything it creates.

We read the score in five bands: 0 to 20 is critical, 20 to 40 poor, 40 to 60 average, 60 to 80 good and 80 to 100 excellent. The band tells you roughly where the team stands. The four lines tell you why.

From "are people happy" to "where is value lost"

This is the change in conversation. "Are people happy?" has one answer and no next step. "Where is value lost?" has four possible answers, and each one points somewhere specific.

• Input is low. The team is being asked to deliver without clarity, resources or a stable set-up. This is usually a management problem, not a team problem.
• Process is low. The team has what it needs but cannot work together well. Look at trust and safety, communication and conflict first.
• Output is low while Input and Process are fine. The team may be working on the wrong things, or its results are not reaching the stakeholders who matter.
• Friction is high. The team is creating value and losing it to meetings, politics and overhead. Cut, do not add.

We also do not trust the averages inside each line. For every KPI we look at score and agreement together. A high score with low agreement usually means the leader thinks things are fine while part of the team disagrees, and that pattern causes the worst surprises. And rather than hand a team twenty things to think about, the report names one high-leverage thing to fix first.

Happiness is a fine thing to want for the people you work with. It is just not a management instrument. Team Net Value is. More on the individual KPIs in our guide to team performance metrics.