Social Contracting
Why Social Contracting matters
Every team operates under a set of rules about how people treat each other; who speaks up, who stays silent, how disagreement is handled, what gets said in the room and what gets said in the hallway. In most organisations those rules are never made explicit, and so people infer and absorb these unspoken rules by watching what happens when someone crosses an invisible line.
The result is leaders repeatedly face the same stubborn patterns: indirect communication, corrosive gossip, unresolved conflicts, meetings where the real conversation happens afterwards, and a quiet erosion of accountability. These behaviours are costly. They breed cynicism, slow decisions, and limit what the organisation can achieve.
New policies, reiterating values, behavioural training, culture interventions rarely shift the dynamics because they address symptoms rather than causes. They treat a cultural problem as though it were a compliance problem. In the language of adaptive leadership, they apply a technical fix to an adaptive challenge: one that requires a shift in mindset, not just a change in behaviour.
Social contracting takes a different route. Instead of imposing rules from the top, it surfaces the agreements a team actually needs and makes them public, owned, and reviewable. It is the mechanism through which a leadership group builds trust, psychological safety, and the capacity to have the difficult conversations that strategy actually requires.
What is Social Contracting?
Social contracting is the practice of a team co-creating and publicly agreeing how they will work together and then regularly reviewing how they are going against that agreement.
It has two components:
The Social Contract
A short list of behavioural commitments the team has openly agreed to uphold. Not a policy document. Not a laminated values poster. A living set of agreements, co-authored by the people who have to live by them, written in specific and observable terms.
The Retro
A short, recurring meeting, typically around 30 minutes, every two weeks, where the team reflects on two questions:
- How are we going as a team? Members offer specific examples of where the contract has been upheld, and where it has been transgressed.
- What, if anything, needs to change? Agreements can be added, edited, or removed as the team's needs evolve.
The shift: from rules to public agreements
The deeper idea is a move from one kind of organisational language to another.
| Rules and policies | Public agreements |
|---|---|
| Customary and usual | Rare; requires deliberate intent |
| Designed to create order from the top down | Designed to create integrity from within |
| Written in manuals or left as implicit norms | Co-created through ongoing dialogue |
| Violations handled privately as discipline | Violations raised publicly as learning opportunities |
| Multiple unspoken interpretations | Shared understanding is the point |
| Rely on hierarchical authority | Rely on peer accountability |
| Experienced as an exercise of power | Experienced as a (sometimes uncomfortable) growth opportunity |
| Transactional: shape behaviour | Transformational: shape meaning |
The point is not that rules are bad. It is that rules alone cannot produce the trust, candour, and adult-to-adult accountability that complex work demands.
A note on trust
Trust functions like a bank account.
- Deposits are made slowly, through consistent behaviour.
- Withdrawals (a broken agreement, undermining gossip, betrayal) are almost always bigger than deposits.
That asymmetry is why building trust has to be an intentional, ongoing practice rather than something left to chance
How to do it
The practice itself is straightforward. The skill is in the facilitation, the tone, and the discipline of keeping at it.
Step 1: Assemble the team and create the first version
Block out a substantive session (around two hours) with the whole team present. This is the only time you will need this much time for it; the ongoing Retros are much shorter. Use an external facilitator if you can to better referee the participation. Everyone in the room should be a participant, not a chair.
Step 2: Facilitate a dialogue to co-create the agreement
Open with one of these questions:
- "Think of a high-performing team you have been part of or seen. What did they do? What did you notice? What do we want here?"
- "For you to be most effective, what would you like to see more of, or less of, in this team?"
As people contribute, do three things:
a) Make statements behavioural. Vague aspirations ("we should respect each other") do not help anyone. Ask: "What would it look like if we were showing each other respect? What would someone walking in see?" Push for observable behaviour, not intangible intent.
b) Reframe complaints into positive commitments. Default mode for many teams is complaint or blame. Reframe towards what people will do, not what others should stop doing.
c) Frame violations as learning opportunities. Make it clear from the start that transgressions are not misconduct to be policed. They are the whole point — the moments where the contract earns its keep.
Step 3: Schedule the Retros and run them
Put the Retro in the calendar. Around 30 minutes, every two weeks works well. Protect it. The value compounds with consistency; skipping it signals the contract doesn't really matter.
In each Retro, answer the two questions:
- How are we going as a team? Invite multiple people to offer specific examples — what someone did that upheld an agreement, or where an agreement was crossed.
- What needs to change in the contract? Add, edit, or retire items as the team's needs shift.
Step 4: Keep it alive
Revisit the full contract with the whole team at least every six months, and whenever there is meaningful change in team membership. Treat it as a live document, not a product.
What to put in the contract
Teams often begin with foundational agreements such as "We will not talk about each other behind each others' backs" or "We will have open and honest conversations about our individual and collective performance." These sound simple. They are not. They go to the heart of the political dynamics that cost organisations enormous amounts of time and money.
For teams facing adaptive strategic challenges where the task requires not just new activity but new ways of being and working, the following higher-level commitments are worth considering:
- A wholehearted intention to transform. If the system is to change, the people leading it must change themselves. Show up in good faith, even when it is hard.
- A commitment to engage. Your participation is not just for you; it signals to everyone else what is allowed. Absences are noticed. "There are no passengers on this journey, just crew."
- Allow space to learn. Experts debate; learners inquire. Suspend disbelief, stay curious. Ask more than you tell; listen more than you speak.
- Speak from 'I'. Own your own experience. Avoid hiding behind "you", "we", or "they". Personal authenticity builds trust and makes conversations more interesting.
- Listen empathically. Listen for content, but also for what is not being said, how it is being said, and the meaning between the words.
- Take the risk to be wrong. Use your intuition. Ask the stupid question. Raise the unmentionable. Silencing yourself costs the team more than being wrong does.
- Assume good intent. Everyone is learning. Everyone will make mistakes. If you are uncertain what is going on for someone else, ask them.
- Understand your discomfort. If you are not uncomfortable, you are probably not learning. Examine discomfort rather than trying to make it disappear.
- Resolve unfinished business. Unresolved conflicts ossify. The longer you leave them, the truer your assumptions about the other person become.
- Be the change you want to see. Every interaction you have sets a template for the rest of the organisation.
Skills to develop
Leading this well calls on some specific facilitation capabilities:
- Reframing complaint or blame into statements of positive intent and personal responsibility.
- Helping team members translate vague ideas into behavioural statements with visible proof points.
- Eliciting contributions from everyone in the room, not just the loudest voices.
- Pacing the Retros so the team can gradually take on more challenging conversations.
When agreements are transgressed
This is the part most teams find hardest, and it is where the real value is created.
When someone crosses an agreement, the job is not to discipline them. It is for a peer (not necessarily the leader) to say in the room: "We agreed we weren't going to do that. What's going on?"
That conversation will be uncomfortable. It will surface what Kegan and Lahey call immunity to change; the unconscious ways we protect ourselves from the very behaviours we have publicly committed to. That is exactly why it works. The contract is not a compliance tool; it is a structured way for the team to meet its own uncomfortable edges and learn from them.
If an agreement stops being useful or proves unrealistic, change it. The contract is a tool in service of the team, not the other way around.
A final note
The goal of social contracting is not just to produce a document. It is to produce a different kind of conversation, and, through that, a different kind of team. The product is not the list. The product is the strategic relationships the team builds and maintains through the ongoing dialogue.
Done well, this practice gradually replaces the politics, drag, and ambient dysfunction of "how things have always worked around here" with something far more valuable: a team that can have the conversations its work actually requires.