Poor check-in results: what should you do?

First read the exact wording of the questions. A value refers to that statement and the period considered, rather than automatically to all collaboration. Then check whether participation or team composition changed and whether a comparison with earlier results makes sense.

Also look at the work context. Were there unusual tasks, missing information or changes in responsibilities? These observations can support interpretation. They should not already be presented as a final explanation. An assumption remains an assumption until further information supports it.

Choose only results that may be shared under the agreed rules. Comments in particular can make people or events recognisable. The article on anonymity in employee surveys explains why the absence of a name field is not enough.

Start with the shared purpose: you want to understand what makes work harder and which change might help. Then describe the observation without judging respondents. For example: 'Feedback on the clarity of our priorities is more critical than in the previous period.'

Add what remains unclear: 'This does not yet tell us which situations contribute most.' This wording creates room for interpretation. It requires neither agreement with a predetermined cause nor a defence of the critical assessment.

Avoid opening with 'I cannot understand this result' or 'It is not that bad.' Even if your own experience differs, let the feedback stand initially. You can add your perspective later without making it the standard for whether other perceptions are acceptable.

Ask about situations and processes. 'Where does prioritisation become difficult?' is more specific than 'Why is the mood poor?' Equally helpful is: 'When does it already work well, and what is different there?' This considers existing possibilities as well as obstacles.

Ask for examples without requiring identifying details. A description of the process is often enough. There is no need to establish publicly who gave which answer or who might have written a comment. Make this boundary explicit.

Record observations separately from explanations. 'New tasks arrive through different channels' describes a process. 'Nobody cares about our planning' is an interpretation. Both may be voiced, but the distinction helps identify a specific point to address.

When feedback concerns leadership, the person involved should not automatically facilitate and judge every statement. Consider whether another suitable person should support the discussion. People need to be able to describe their views without fearing an immediate round of demands to justify them.

A helpful response might be: 'I can see that changes I make to priorities are difficult for you to follow. I want to understand where that happens most.' This acknowledges the feedback without treating every interpretation as proven.

Specific personal allegations or sensitive individual cases need an appropriate separate route for resolution. An open team meeting is not suitable for every situation. Record how the issue will be taken forward rather than exploring details in front of the whole group.

Agree to discuss working conditions that can be changed and specific situations. Interrupt claims about character or motives when they replace clarification. Ask instead which observable behaviour or process is meant and which change would help.

If several topics arise at once, first collect them visibly. You do not have to address everything immediately. Then choose a point where the need for action and the ability to influence it meet. Keep other topics documented and make clear how they will be handled.

Different views do not have to be reconciled immediately either. A team can experience the same process differently. Check whether different roles or situations explain that. The goal is a workable agreement rather than a forced shared rating of every experience.

Hypothetical example: The team describes unclear priorities because several sources assign additional tasks. Instead of resolving to 'communicate better', it agrees that changes in task order will go through one clearly designated contact. Every new priority makes visible which existing task will be deferred.

The measure therefore names a specific change in the process. Also record who coordinates implementation and when it starts. A general intention without responsibility is hard to review later. A short written agreement with the measure, responsibility and review date is enough for this step.

State the expectation too: What should become easier or clearer after the change? This might be a more understandable order or fewer conflicting assignments. That expectation is initially a hypothesis. It will later be checked against feedback and suitable observations of work.

Say openly when the team cannot make a decision itself. A structural problem should not be obscured by an additional team routine. Instead, document which decision is needed and who is responsible for it.

Agree who will pass on the need for action and when feedback will follow. The next update may be that a decision is still pending. What matters is that the issue does not disappear into a collection without an identifiable way forward.

Do not promise a solution you cannot decide on. You can commit to passing on the situation clearly, making its status transparent and examining possible steps within your influence. This keeps opportunities for action distinct from limitations.

At the next agreed meeting, first check whether the measure was implemented. Only then does it make sense to ask whether the desired development is visible. A good idea that was not used in practice first needs clarification of the implementation barriers.

Then consider recurring feedback alongside the work context. Improvement can be a useful indication, but does not prove the cause on its own. Changes in workload, staffing or other measures may also matter. Measuring AI adoption in a team also shows how to interpret feedback and observations together.

Record a decision: retain, adapt, end or continue observing with a specific open question. A new review date helps prevent the agreement from being lost in daily work. Not every measure has to succeed for something to be learned from its use.

Avoid treating results as an assessment of individual performance. Team feedback describes experienced conditions and does not answer questions about the value of individual employees. A critical comment is not automatically representative of everyone involved either.

Do not turn the discussion into a contest over the correct perception. Different experiences can coexist. The relevant question is which specific change to try under these conditions or which further information to obtain.

Finally, avoid ending without next steps. An understanding conversation can matter, but does not replace a decision about what follows. Document measures, responsibilities and open questions so the team can return to them later. Guidance on confidentiality and sample questions supports preparation for the next check.

EngageBeat makes recurring feedback visible so you can use it to choose measures and follow them up. How it works explains the framework. The demo shows sample data; decisions about your next steps remain yours.

Further reading: analyse results systematically. The team feedback session guide shows how to agree a specific change afterwards.