Argentina won the 2022 World Cup after losing their opening match to Saudi Arabia. Documented fact: the defeat happened, and the tournament was won anyway. That combination is the interesting part for anyone responsible for a team.
Most organisations describe culture using words that only work when results are good. The real test is what a group does in the 48 hours after something goes publicly wrong — and that behaviour is built long before the bad week arrives.
The people question this raises
What lets a group absorb an early, public failure without fragmenting? Not values on a wall. In practice it tends to be three unglamorous things: a goal every member can state in one sentence, standards that peers enforce rather than only the manager, and roles clear enough to survive bad news. Add a fourth if you want the failure to teach anything: a rehearsed way of reviewing what happened without assigning blame in the first meeting.
Amy Edmondson's research on psychological safety points the same way: teams recover and learn when people can name problems early without paying a social price. Google's own team-effectiveness work found the same factor at the top of its list. Neither finding is about comfort. Both are about whether difficult information travels fast enough to act on.
Where this shows up at work
- A launch slips in week one and the team either regroups or starts assigning blame in private channels.
- A key client churns, and people quietly begin protecting themselves rather than the goal.
- A reorganisation lands and nobody can say what the team is now for, so everyone defaults to their old work.
- An incident review turns into a search for the person at fault, and the next incident is reported four days late.
Three things to install before you need them
- 1One sentence everyone repeatsAsk five people what the team is trying to achieve this quarter. Five different answers is your starting problem — and it is fixable in a single meeting followed by relentless repetition.
- 2Peer-enforced standardsAgree two or three non-negotiables and let the team hold each other to them. Standards only a manager enforces are rules; standards peers enforce are culture.
- 3Roles that hold under pressureWrite down who decides, who delivers and who is consulted — before the crisis, not during it. Ambiguity is survivable in a good quarter and expensive in a bad week.
- 4A recovery ritualDecide in advance how you review failure: facts first, decisions second, no blame in the first meeting, one owner per action. Rehearsed process beats improvised composure.
Any team looks aligned when results are good. If you want to know what your culture actually is, look at the last two days after something public went wrong — who spoke, who went quiet, and what got decided.
A worked scenario: the first 48 hours
- Hour 0–4: state the facts to the whole team in writing, including what is not yet known. Silence from leadership is filled by rumour within a day.
- Hour 4–24: restate the goal and what has not changed. People need to know which parts of the plan still stand.
- Day 2: run the review — timeline first, decisions second, no blame. Produce at most three actions, each with a named owner and a date.
- Day 2, end: say publicly what the team did well under pressure. Recovery norms are taught by what gets recognised, not by what gets written in a handbook.
Diagnose your own team in ten minutes
- Five people, asked separately, give the same one-sentence goal for this quarter.
- You can name two standards the team enforces without you in the room.
- For your biggest current decision, everyone can name who decides.
- Someone raised bad news early in the last month, and nothing bad happened to them for it.
- Your last failure review produced written actions with owners, and those actions were completed.
Any unchecked box is a specific, fixable piece of work — which is the practical advantage of defining culture as behaviour rather than as atmosphere.
What readers often get wrong about this
- Cohesion is not the same as agreement. Teams that never argue are usually not aligned; they are avoiding each other.
- "Culture beats talent" is a slogan, not a finding. Argentina's squad included exceptional players. Cohesion multiplies capability; it does not substitute for it.
- Do not import sport's intensity wholesale. A tournament lasts a month; your team has to sustain its pace for years, and permanent crisis energy produces burnout, not cohesion.
- Culture is not owned by HR. It is set by what managers tolerate, reward and repeat — and it is rebuilt or damaged in every difficult week.
Interpretation, not fact: describing that squad as "the most coherent team in the tournament" is my reading of publicly visible behaviour, not a measured finding. Squad cohesion is not something outsiders can quantify, and the World Cup outcome had many causes.
Common questions
How do we build peer-enforced standards without it turning into policing?
Keep the list to two or three standards, make them behavioural rather than attitudinal, and model correction yourself in a low-stakes situation first. Peers copy the tone their manager uses, so a calm, specific correction becomes the norm — as does a sarcastic one.
Our team is remote. Does this still work?
It matters more. Remote teams lose the informal signals that carry standards, so the goal sentence, the decision rights and the review ritual all have to be written down and repeated deliberately.
What if the bad week was caused by leadership?
Say so first, in the same meeting where you ask others to be candid. A leader naming their own contribution is the single fastest way to make a blameless review credible; skip it and nobody else will be honest either.
Over to you
When your team last lost publicly, what happened in the next two days — and what did that reveal about your culture?
- FIFA World Cup 2022 match records — FIFA
- Psychological safety and learning behaviour in work teams — Amy Edmondson, Administrative Science Quarterly
- What Google learned about effective teams — Google re:Work