• Does everyone know exactly what their team colleagues need from them?
  • Are expectations said out loud, or just assumed?
  • What would change if each person made clear commitments to the whole team?

Here, Will Sudworth explains the red10 Team Tool called “Expectation Exchange”, a practical way for a team to turn good intentions into clear commitments that everyone shares.

What can it do for a team?

A leadership team we worked with wanted to strengthen the partnership between its departments before their offsite. We ran an Expectation Exchange. Afterwards, the team leader reflected that two department heads had heard the whole team ask them to work more closely together, and had committed to it in front of everyone. Every member of the team also came away with a clear sense of where they could grow, in a setting that felt supportive rather than critical.

Why does a team need a contract?

In our article Are you a group or a team?, we describe two ways of working.

In a GROUP: the relationships that matter run from the leader out to each individual, like the spokes of a wheel.
In a TEAM, every relationship matters and together they form a spider’s web.

Research suggests the web can lift performance by up to 30%.

A web doesn’t appear just because people share a meeting, though. Its strands are made of expectations, and most expectations are never spoken.

red10 ‘s “Expectation Exchange team tool forms a simple “contract” between each person and the team as a whole: here is what I’ll do, here is what you’d like from me, and here is what I commit to.

Why do the rules matter?

A request leaves control with the person receiving it, whereas a demand creates resistance. Keeping requests about the future stops the session turning into a list of grievances. Stating your positive intent turns what could sound like criticism into investment: I’m asking because I want you to succeed.

Allowing “no” matters just as much. An honest no with a reason is worth far more than a reluctant yes that quietly never happens. And the “Yes, and what I’ll do is…” rule means every yes comes with a concrete action.

Why pre-thinking rather than pre-reading?

That kind of clarity rarely turns up on the day. A pre-read doesn’t help either, because there’s nothing to read. What the team needs is pre-thinking.

This is best done in a team meeting a few weeks before the retreat. The leader explains the purpose and walks through the three steps. The team agrees the need it is facing, so everyone is thinking about the same challenge. Then each person goes away to reflect on two questions:

  • What will I and my department do, and how will I behave?
  • What would I like from each of my colleagues, and why?

People then arrive with considered requests rather than first reactions.

Where does it fit in the retreat?

The Exchange asks people to be vulnerable: to hear requests in silence, then say yes or no in front of their peers. On a two-day retreat, it belongs on day two, once day one has built trust and people are willing to take that risk.

That trust comes from red10 ‘s usual foundations for psychological safety:

  • Welcome: setting the purpose and tone for the time together
  • Meeting hygiene: agreeing how we will work together in the room
  • Connection circle: meeting each other as people before roles
  • Business update: giving everyone the same shared reality

The business update is easy to underrate. If people hold different pictures of where the business stands, their requests will pull in different directions.

What happens after the retreat?

The notes become the team’s contract. Review them at regular team meetings. Which commitments are working, and which need renegotiating? Over time, the web of relationships becomes real, built on expectations that have been said out loud.