Analysing team culture: how do you really work together?

Team culture includes shared expectations about how people work together, even when they are not written down. For example: Can a new colleague disagree with an experienced person? Who decides when two urgent tasks compete? Is support requested early, or only after something has gone wrong?

A mission statement can describe such expectations, but does not yet show what actually happens in daily work. Friendly interactions are also only one aspect. A team can like each other personally while still avoiding difficult questions. Conversely, lively disagreement can form part of constructive collaboration.

A simple distinction helps with analysis: What do we say about our collaboration? What do we do in specific situations? What consequences does that have for our shared work? Differences between these three levels are a starting point for questions, rather than proof of dishonesty.

Start with a recurring, relevant situation. 'Our culture needs to improve' leaves too many interpretations open. 'Important information is regularly missing at handovers' narrows the analysis and makes it clear who can describe the process.

Possible starting questions include:

• Why do difficulties become visible only shortly before a deadline?
• How is it that decisions receive agreement in a meeting and are questioned again afterwards?
• Why do we not help each other in time when workload peaks?
• What happens to a concern that challenges a planned approach?

Also record what already works well. If a handover between two shifts is reliable, it may offer clues for other handovers. An analysis focused only on deficiencies misses existing solutions and can easily confirm the manager's original assumption.

Choose ordinary work situations, rather than special workshops alone. Inform the team about the purpose and process. The analysis is not a reason for secret recordings or personal dossiers. Record the process and its effects without attributing fixed traits to individuals.

An observation might be: After the objection, the topic was changed immediately without clarifying whether the point was relevant. Claiming 'Nobody dares to say anything here' would already be a broad interpretation. Keeping these separate makes it easier to revise your explanation later.

Not everything important is visible from outside. Ask about experiences with the same situations. One possible question is: 'When were you last able to raise a problem early, and what helped?' Another is: 'What information do you need at a handover that you do not reliably receive today?'

Short written feedback can add perspectives different from contributions in a meeting. It is not automatically more honest or complete. Clarify recipients beforehand and avoid details that make individual respondents identifiable. If planning a survey, use the guidance on confidentiality.

Research on psychological safety offers an important reference point for raising problems. Amy Edmondson describes it as a shared belief that the team provides a safe setting for interpersonal risks. This does not mean a single question you create reliably measures psychological safety. Observe specific reactions and avoid treating the concept as another blanket team label.

Collect several situations and deliberately look for counterexamples too. If objections are overlooked in one meeting, time pressure may explain it. If it recurs across different meetings, it is worth examining the underlying rule more closely. There may be an unspoken expectation that a manager's decision can no longer be changed.

Test this assumption with an open question rather than announcing it as a finding: 'Several times, we have seen objections left unaddressed after a decision. What currently makes it difficult to revisit them?' This keeps the analysis from becoming an accusation.

Also consider external conditions. If every shift starts with too little time, rushed handovers may not primarily be a cultural habit. The UK's HSE identifies demands, support and role clarity, alongside relationships, as important areas of work design. Use this distinction to guide your search rather than attributing every problem to team attitudes.

A hypothetical example: Nine people work closely together in a skilled trades business. Work is allocated quickly in the morning. Questions are rare, but follow-up queries and duplicated trips arise later. The initial assumption is that people are unwilling to coordinate properly.

Looking at several morning briefings reveals something else: Jobs are assigned before everyone has the necessary information. Asking questions appears to hold up the whole group. Individual feedback confirms that people prefer to ask later in a smaller setting.

The team agrees a manageable experiment: Before allocation ends, there is a set question about missing information. Someone is assigned to each open point. The manager answers questions without mocking remarks and visibly corrects their own assumption when a point is justified.

After an agreed period, the team checks whether information was available earlier and whether asking questions became easier. This example shows one possible route, rather than a real customer reference or guaranteed success. The team may also need more preparation time or a different order process.

Describe the desired behaviour so the team can recognise it. 'Communicate more openly' is too vague. 'At every handover, we name open points and agree who will clarify them by when' describes a change that can be checked.

For a first experiment, a clearly defined situation, a responsible person and a review are enough. Record which assumption you are testing. If the experiment does not help, that does not automatically mean the team needs more discipline. The assumed cause may have been wrong, or the agreement may not have been workable within the actual workflow.

A short pulse survey can revisit the same experience repeatedly. Observations remain important alongside it: a better assessment of handovers and handovers that are actually complete are different pieces of information. The article on measures after a survey explains how to make follow-up steps dependable.

A common mistake is to draw conclusions about the entire team culture from one particularly loud conflict. Another is to seek only the manager's perspective. Even an established culture model is of little help if its concepts are not connected to everyday experience.

Also avoid rankings based on supposed openness or teamwork ability. The analysis should make shared processes easier to understand. Serious allegations, personal boundary violations or risks require an appropriate separate route. A general culture meeting cannot replace confidential resolution.

Not every tension needs to disappear. Different professional perspectives may be necessary. The question is whether the team can handle them while keeping decisions, support and responsibility clear. The article on feedback culture explores handling feedback; team culture analysis also considers other working patterns.

EngageBeat can make recurring feedback from everyday team work visible. With suitable custom questions in EngageBeat Fokus, you can follow selected experiences relating to an agreed change. This does not produce a complete cultural diagnosis.