Team feedback session: How do you make it work?

First, narrow down the subject. ‘How are things going here?’ can work as an open starting point but easily leads to many different topics. A narrower question is often more useful for a decision: ‘What is currently making our handovers difficult?’ Or: ‘How are we experiencing the new process for clarifying priorities?’

Also say what you can decide in this session. If the team is allowed to change a process, that scope should be clear. If someone else needs to approve it, name that beforehand. A session that promises participation but offers no visible influence creates unnecessary disappointment.

Decide whether you want to collect experiences, examine causes or choose a specific action. These steps can occur in one session, but should not constantly switch back and forth. Otherwise, the first experience described is immediately overlaid with proposed solutions before other perspectives become visible.

Choose a suitable time and announce the topic and purpose. If written feedback or survey results are available, check beforehand which can be shown within the agreed framework. Comments containing identifying details should not appear on a slide without careful consideration.

Prepare a manageable presentation: the relevant finding, known limitations and the question for the group. Do not show every available number just because it exists. To choose, ask which information actually changes the decision at hand.

Choose a facilitator and someone to record decisions. In a small team, this can be the same person as long as they carry out the roles consciously. In conflicts involving the team's own manager, a different facilitator may make sense. A feedback session is not a protected setting simply because it is called one.

The following process is an original practical suggestion for a short session. The time allocation is guidance, not a professional standard. Adapt it to the team size and topic.

For a short session, you could reserve half the meeting for understanding and the remaining time for selection and agreement, for example. This division is deliberately flexible. If an issue needs more clarification, a clearly agreed follow-up meeting is more useful than a quick superficial solution.

The DGUV culture dialogues also show a structured approach through specific everyday situations and initial ideas for solutions. They additionally provide materials for use in the workplace.

Ask about situations and consequences before asking for solutions. Useful opening questions include: ‘When did our coordination last work well?’ and ‘Where was work left undone because information was missing?’ Combining helpful and obstructive experiences prevents the session from becoming only a collection of complaints.

Then explore further: ‘What was different in that situation?’ ‘Which decision was missing?’ ‘What could we influence ourselves?’ Questions like these help identify a specific starting point. They are original facilitation suggestions, not diagnostic instruments.

Different questions help at the end: ‘Which change will we actually try?’ ‘Who will take the next step?’ ‘How will we tell whether the experiment was helpful?’ A question such as ‘Does everyone agree?’ is not enough if what is to be agreed has remained unclear.

First give people time to think individually before the discussion begins. A set speaking order can prevent the first contributions from immediately setting the whole frame. At the same time, no one should be pushed into personal disclosure.

Explain what kind of contribution is expected: an observed work situation, a follow-up question or a note about a limitation. That is more specific than asking people to be ‘honest and open’. Offer another suitable channel for personal concerns.

Pay attention to how the group responds to criticism. If every response is immediately qualified or played down, even formal speaking rules will do little. The facilitator can first summarise: ‘I want to make sure we have understood the experience before putting it in context.’ This does not mean automatically agreeing with the interpretation; it creates a basis for examining it.

Interrupt sweeping labels and return to the specific situation. ‘You never inform us’ becomes a question about which information was missing at which handover. Avoid deciding the conflict through a public vote about people.

If an incident needs confidential or formal handling, say so and agree on the responsible channel. The group does not have to solve every problem together. An unprotected discussion can create additional risks, particularly where there is a power imbalance.

A feedback session can also end without an immediate solution being agreed. It then needs a clear follow-up task: What information is missing, who will clarify it and when will a decision be made? Openness helps here; a vague ‘We will keep working on it’ does not replace responsibility.

Record a change in a way that can be checked in everyday work. ‘Communicate better’ remains too general. In a fictional team, an agreement might be: ‘Before the handover, the responsible person states the open point, next step and contact person.’ You can later observe whether the experiment took place.

Also record why you chose this change. This helps prevent a discussion a few weeks later that is only about compliance with a rule whose purpose has been forgotten. If the rule is implemented but the original obstacle remains, you must be able to rethink the solution.

Start the next review with the previous agreement. What was implemented? What was helpful? What side effects were there? Only then collect new topics. This keeps the session connected to actual changes instead of starting from scratch every week.

Brief written feedback can make issues visible before the group meets. It does not, however, automatically reflect everyone's full perspective. Consider obstacles to participation, clear questions and the limits of confidentiality.

The in-person session helps with interpretation and decisions. Written check-ins can then show how the relevant situation continues to be experienced. The two serve different purposes. The article Analysing an employee survey describes the transition from figures to a finding you can address.

You can start with a clear question and a firm review even without a tool. What matters is that feedback can have consequences for how work is organised. Only once that process is useful is it worth asking about suitable technical support.

EngageBeat provides brief recurring feedback and visible trends. You can use it to identify topics for change and keep observing suitable actions. A look inside the feedback tool shows the process; introductory guides are available for team leaders. A trial starts with 28 free days and moves to your chosen subscription unless you cancel in time.