Most team development happens in dedicated events. The away-day. The team effectiveness workshop. The quarterly offsite with a facilitator and a structured agenda and a wall covered in Post-it notes by the end of the first morning.
These events are not without value. They are also, structurally, insufficient — because the conditions that shape team culture are not the conditions of the offsite. They are the conditions of the ordinary week: the Monday morning meeting, the difficult conversation that gets deferred until it becomes unavoidable, the moment of pressure in which each team member defaults to their automatic pattern and the collective dynamic re-establishes itself along entirely familiar lines.
What transforms team culture is not what happens in the exceptional event. It is what happens in the ordinary interval. And that requires a practice — something brief, sustainable, and consistent enough to interrupt the ordinary before it calcifies into the inevitable.
What the practice involves
Fifteen minutes. Once a week. The same time, the same structure, no exceptions made for busyness because busyness is precisely the condition the practice is designed to interrupt.
The structure has three movements.
The first five minutes: individual reflection. Each team member takes a short period — silent, unshared — to consider one question: In my interactions this week, where did I notice a pattern I recognise in myself? Not a judgment. Not a performance review. A single honest observation about something that happened in the relational field of the team and what it brought up.
The question is deliberately specific. Vague reflection produces vague insight. The specificity of the relational context — in my interactions this week — grounds the reflection in observable reality rather than abstract self-assessment.
The second five minutes: selected sharing. Two or three team members share briefly — not the full reflection, but a single observation. The ground rule is that others listen without comment, question, or advice. The purpose of the sharing is not to produce a team discussion. It is to normalise the practice of speaking honestly about one’s own interior experience in a professional context, and to begin building a collective vocabulary for the patterns that shape the team’s dynamics.
Over time, this sharing creates something specific and valuable: a language. Teams that practice this consistently develop the capacity to name, in real time and without defensiveness, what is happening in their relational field. I notice I’m going into control mode — what do we actually need right now? I’m aware I’ve been avoiding this conversation. Let me try to have it. These are not therapeutic disclosures. They are acts of leadership that become possible when a team has enough shared practice to make them ordinary.
The third five minutes: collective intention. The team names one thing — one specific, behavioural thing — that they will do differently in the coming week based on what has surfaced. Not a goal. Not a commitment to be reviewed in the next performance cycle. A single, concrete, next-week intention, small enough to be achievable and specific enough to be recognisable when it happens.
What this practice is actually doing
Underneath its apparently simple structure, this practice is addressing one of the most persistent and underaddressed problems in team dynamics: the accumulation of unprocessed relational material.
Teams in which individual shadow patterns are never surfaced or named do not thereby become shadow-free. They become shadow-dense — accumulating the projections, assumptions, and unspoken dynamics that gradually make the formal agenda of every meeting secondary to the invisible agenda that everyone can feel but no one addresses. The team that cannot name what is happening between them cannot change it. The practice creates a regular opportunity to surface and process the relational material before it compounds.
The research on high-performing teams consistently identifies psychological safety as a key differentiator — the condition in which team members feel able to take interpersonal risks without fear of punishment or humiliation. What is less often examined is how that safety is actually built. It does not emerge from a workshop declaration that this team values psychological safety. It emerges from repeated small experiences of speaking honestly and finding the sky intact.
Fifteen minutes a week is where that experience accumulates.
A note on the leader’s role
The practice only works if the leader participates as a participant — not as a facilitator, not as the person who models the right answer, but as someone doing their own honest reflection alongside everyone else.
This is, for many leaders, the hardest part. The practice requires them to be visibly uncertain, visibly in process, visibly subject to the same patterns as everyone on their team. For leaders whose authority has been built on a presentation of confident competence, this is genuinely uncomfortable.
It is also, reliably, the single thing that makes the practice transformative rather than procedural. A team that watches its leader reflect honestly on their own pattern does not just gain a practice. It gains permission — to be human, to be in process, to be genuinely developing rather than performing development.
That permission is worth considerably more than fifteen minutes a week. It is worth, in some teams, the entire culture.
The Alchemy of Leadership: Five Elements Workbook
The full developmental architecture of the five-element sequence, with diagnostic questions for each stage and worked examples from senior executive practice. Available free.