How to run your first team survey in one week

A first team survey does not need a project plan, a steering committee or a quarter of lead time. It needs one week, a team lead who is willing to hear the answer, and 30 minutes at the end to talk about it. Here is the plan we recommend to leads running their first survey with PEAKTEAMS. The mechanics work with any decent tool.

Monday: announce it and explain anonymity

Tell the team in your regular meeting or in a short written note. Cover four things: why you are doing it, what you will do with the result, how long it takes, and how anonymity works. The last point decides whether the answers are honest.

• Results are shown only as team aggregates, and only once at least three people have responded. Below that, nothing is visible, not even to you.
• You will never see who gave which answer. Free-text comments appear word for word without names, so people should not include details that identify them.
• You will share the headline results with the whole team and pick one thing to work on together.
• It takes about 12 minutes and can be paused and resumed.

Tuesday to Thursday: invite and collect

Create the team in your account, add the team members and start the survey. Everyone receives an email with a personal link. The link is personal: it lets people pause and resume and makes sure each person answers once, so nobody should forward theirs.

Keep the window short. Three days is enough for a team that sits in one or two time zones. A window that stays open for two weeks does not raise the response rate, it lowers the urgency. If your team is spread across continents, add one day and move the debrief to the following Monday.

On Thursday, check how many responses are in. You need at least three for the report to unlock. For a team of eight, aim for six or more; the result becomes much more representative once most of the team is in. Send one reminder, to the whole team, not to the people you suspect have not answered. You cannot know who they are, and you should not try to.

Friday: read the report, pick one thing, debrief

Give yourself 30 undisturbed minutes with the report before anyone else sees it. Read it in this order.

1. Team Net Value. One number from 0 to 100, with the four lines behind it: Input, Process, Output and Friction. The band (critical, poor, average, good, excellent) tells you roughly where you stand. The lines tell you whether value is missing at the start, lost in how the team works, not reaching stakeholders, or being taxed away by friction.
2. The 18 KPIs. Each is scored 1 to 5, and each shows agreement next to the score. Look first at low scores with high agreement: those are the shared pain points, and the easiest to fix because nobody needs convincing. Then look at high scores with low agreement: those are the places where you and part of the team see different realities.
3. Team identity. One of 16 identities built from four dimensions. It is not a grade. It describes how your team prefers to work, which is useful context for every number above it.
4. One Big Thing. The report names a single high-leverage intervention. You do not have to agree with it, but you should be able to say why if you choose something else.

Then pick one thing. Not three, not a themed action plan. One change that the team can make before the next survey and that would move a specific KPI. Write it down in a sentence, with a name and a date.

The 30-minute debrief

Hold the debrief within a few days of reading the report, while the survey is still fresh. The agenda is short on purpose.

• Five minutes: thank people, repeat how many responded, remind them nothing is traceable.
• Ten minutes: show the Team Net Value, the four lines and the three or four KPIs that stood out. Do not walk through all 18.
• Ten minutes: ask what surprised people and listen. Where agreement was low, ask what the different experiences are, without asking who held which view.
• Five minutes: propose your one thing, adjust it if the team has a better one, confirm the owner and the date.

End by saying when the next survey will run. That sentence is what makes the first one credible.

After 8 to 12 weeks: run it again

The first survey is a baseline. The second one is where it starts to pay off, because now you can see whether the one thing you changed moved the KPI you expected it to move. Eight to twelve weeks is long enough to act and short enough that the context is still comparable. Keep the questions the same, keep the window short, keep the debrief at 30 minutes.

If you want a reusable structure for this, our team health check template covers the cadence and the debrief in more detail, and team survey questions explains what the 18 KPIs ask.