How to tell whether team building worked (and what to measure to get next year's budget)

The question always comes from the same direction: someone in finance wants to know what last year's event returned, and HR has to answer with something better than "people enjoyed it".

Start with the uncomfortable part: nobody can seriously demonstrate that a day of team building raised productivity. There are too many variables in between, and any supplier promising a percentage improvement is selling you an invented number. What does exist is a set of reasonable indicators, and they are perfectly enough to support a budget decision.

Before measuring: define what it was for

This is the step almost everyone skips, and without it there is nothing to measure. An event organised because "we should do something" has no possible result, because it had no objective.

Objectives that can be evaluated afterwards:

• Integrating two departments that work together and do not know each other.
• Welcoming a large intake of new people after a hiring period.
• Rebuilding the bond of a team that has become mostly remote.
• Rewarding a concrete result.
• Closing a hard year, which is a legitimate objective even if it sounds soft.

Writing it in one line before quoting changes the whole event, and it also defines what to ask afterwards.

What you measure on the day

• Actual attendance, not invitations. How many came out of how many were invited. If the objective was integration and a third of the team is missing, the result is already constrained, however well the day went.
• Participation in the activity. How many did the main activity and how many watched. If a substantial share watched, the day was badly designed for that group.

The 48-hour survey, deliberately short

Sent two or three days later, never a week after. Three questions are enough, and the third is the one that really pays:

1. From 0 to 10, would you recommend this day to a colleague?
2. How many people did you talk to that you do not normally see at work? None, one or two, three or more.
3. What would you change for next time?

The second question is the most useful of the three and almost nobody asks it. If the objective was integration, it is literally the measurement of the objective. And if the majority answer is "none", you already know the next event needs deliberately built subgroups, which we cover in team building for large groups.

The third is not measured, it is read. And it supports next year's budget request far better than any average.

What you look at after three months

This is where a day that worked separates from a day that was merely nice:

• Cross-department contact. Soft but visible: managers know whether people from two teams started writing to each other directly instead of escalating through their bosses. Asking that in a managers' meeting is worth more than a survey.
• The engagement pulse. If the company already measures engagement quarterly, compare the item on relationships between teams before and after. If it does not, this is a good moment to start: a single quarterly question already builds a series.
• Voluntary turnover for the period. Not attributable to the event, and still the figure that carries most weight in a conversation with finance, because it is the only one already denominated in money.

What not to promise

• A percentage improvement in productivity.
• A drop in turnover attributed to the day.
• An improvement in engagement caused by the event, when engagement is moved by ten other things.

Promising those is what makes the next budget request get read with suspicion. It is far stronger to say: this was the objective, this was attendance, people talked to people they do not normally see, and this is what they asked for next time.

How to build the one-page report

What works in a budget meeting:

1. The objective, in one line, the one written before the event.
2. Attendance, as a number and a percentage.
3. The results of the three questions, with the new-conversations figure highlighted.
4. Two or three verbatim quotes from the open question, unretouched.
5. What will be done differently next year, which is what shows there was learning and not just spending.

One page. Longer than that and nobody reads it.

The mistake that precedes all of this

A team with a structural problem, such as contradictory objectives between departments or a manager who is not working out, does not improve with a day outdoors, and measuring it will look bad however you measure. Team building works on a team that is doing fine and wants to do better, or on one that is just forming. That is developed in team building activities and what each one is good for.

And if what you are building is the whole event, team building in Chile covers the options within two hours of Santiago, and what a team building day costs explains how to compare two quotes without stopping at the final number.