Most teams have never had an explicit conversation about how they work together. They have had conversations about what they are working on, how the project is going, what the priorities are. But the conversation about the team itself, how decisions get made, how conflict gets handled, what happens when someone is struggling, what people actually need from each other to do their best work, is one that tends not to happen unless something has already gone wrong.
This is a guide to running that conversation before something goes wrong.
1. The real-world scenario
Why this conversation is worth having
Teams that have talked explicitly about how they work tend to navigate difficulty more effectively than teams that have not. Not because the conversation produces a set of rules, but because it surfaces assumptions, names patterns, and creates a shared vocabulary for things that previously could only be felt. A team that has talked about how it handles conflict is better placed to handle conflict when it arrives. A team that has talked about what psychological safety means to them is more likely to notice when it is eroding.
2. What may be happening
When to run it
This conversation works at three points. At the beginning of a new team or a new phase of work, as a way of establishing shared norms before patterns become entrenched. After a period of difficulty, as a way of naming what happened and choosing something different. Or as a regular practice, quarterly or twice yearly, as a way of maintaining honest team awareness over time.
3. Why it lands harder than expected
Before the conversation
Tell the team what the conversation is for and what it is not. It is not a performance review, a complaint session, or a way of surfacing grievances. It is a deliberate attempt to get honest about how the team is working and what would make it work better. Send the questions below in advance so people can think rather than react.
4. What actually helps
Question one: What is working well in how we work together, and what specifically makes it work?
Start with what is already good. Not as a warm-up before the real conversation, but because most teams have genuine strengths that are worth naming and protecting. Asking what specifically makes it work also moves the conversation from general observation to useful data.
5. What to try next
Question two: What do we avoid saying in this team, and what does that cost us?
This is the question most teams do not ask. Every team has a set of topics, dynamics, or observations that circulate informally but rarely reach the room. This question invites them in explicitly. It requires enough psychological safety to answer honestly, which is why the question should be preceded by genuine listening on the first question.
6. What to notice
Question three: What does each of us need from the others to do our best work?
This question often produces the most practically useful conversation because it moves from diagnosis to request. It is also the question most likely to surface differences in what people find helpful, which is where SDI and neuroleadership principles become practically relevant.
7. What to practise
Question four: What one thing would make the biggest difference to how we work together?
End with a single priority. Not a list. One thing that the team commits to trying for the next quarter. The brain changes through repetition, not intention. One specific, small, repeated behaviour change is worth more than a long list of improvements that never quite become habitual.
8. How to keep it alive
Facilitation notes
If you are the team leader running this conversation, you face a specific challenge: you are both the facilitator and a participant, and your responses carry disproportionate weight. Be deliberate about going last on the harder questions. Resist the urge to resolve discomfort quickly. If something uncomfortable is raised, slow down rather than move past it. What you do in those moments teaches the team what the conversation can and cannot hold.
If the team is particularly low-trust or has significant unresolved conflict, consider having an external facilitator run the conversation. The value of the conversation is in what is said honestly, not in who runs it.
9. A small habit to try
A small habit to try
At the end of each team meeting for the next month, spend two minutes on one question: what did we not say today that would have been useful to say? That practice, done consistently, builds the habit of noticing the gap between the official conversation and the real one. Over time, it narrows it.
The conversation about how we work together is usually more important than the work itself. Most teams never have it.
10. What to design around the role
Three things tend to make a more substantial difference.
Start with observable patterns
Start with what is happening, not who is at fault.
Ask what helps and hinders the work
Ask where the current way of working helps and where it now costs too much.
Name one habit to keep and one to change
Choose a small number of habits to practise deliberately.
Turn the conversation into a small working agreement
Review the change quickly so the conversation does not become another workshop memory.
11. Questions to reflect on
Use these to notice where editing has become the default.
- 01What are we all adapting around?
- 02Which habit helps us most when pressure is high?
- 03Which habit creates avoidable friction?
- 04What agreement would make next week easier?
Takeaway
You do not need a crisis to have this conversation. You need thirty minutes, the right questions, and enough willingness to sit with the honest answers. That is where team culture is actually made.
Keep the next step clear.