Culture is not a value statement. It is the sum of how people interact inside an organization, and specifically how they respond when something gets hard. For the past thirty minutes, your team played a game. Under real time pressure, with genuine resource constraints, and with decisions that actually mattered inside the scenario. Nobody asked them how they handle failure. Nobody asked them to rate their collaboration on a scale of one to five. They just did it. What happened in those thirty minutes is the most honest culture data you have collected all year. This guide explains how to name it.
Normal working conditions are a poor environment for seeing culture clearly. Busyness, hierarchy, the awareness of audience, competing agendas: all of it introduces noise that filters the behavior you actually need to observe. A well-designed game removes most of that filter. It is a self-contained, isolated system of interactions. Players face real constraints, make real decisions under time pressure, and operate with genuine stakes inside the scenario. Because the context is bounded and unfamiliar, people fall back on their default patterns faster than they do in environments they have learned to manage. The political awareness, the careful performance of organizational identity, the habitual deference to seniority: most of it drops away within the first ten minutes of play. What the facilitator observes after that is closer to how the team actually operates than almost anything visible in a standard meeting or workshop. The game does not simulate culture. It surfaces it.
This workshop is designed to sit alongside your existing culture data, not replace it. Surveys have real value: they produce quantitative signals at scale, track trends over time, and give leadership a broad read on where the organization stands. But surveys measure what people believe is true, or what they are willing to say is true. The gap between those answers and actual behavior under pressure is often the most important thing to understand about your culture, and surveys cannot see it. If your last engagement survey reported strong psychological safety scores, that is worth knowing. If your team then spent thirty minutes going quiet every time the direction seemed wrong, that is also worth knowing. One does not cancel the other. Together they tell you what is real. The survey gives you the signal. The game tells you how accurate it was.
Culture Surveys
What they give you
Game Observation
What this adds
Quantitative signal across the whole organization
Behavioral evidence from a specific group under real pressure
Trends over time: are scores moving?
Spot validation: does the score match what you actually observe?
What people believe is true, or are willing to say
What people actually do when the constraints are real
Broad and anonymous: hard to act on at the team level
Specific and observable: directly actionable in the room
1
Play the Game
Run one Tech CoLab game. Watch, don't play.
30 min
2
Map the Gap
Five culture dimensions. What we say vs. what we just did.
40 min
3
Commit to One Shift
One person. One behavior. Two weeks.
20 min
Step 1: Play the Game 30 min
The game is the research instrument. Your job during play is not to join the table. It is to watch it. Culture surveys fail because people give you the answer they believe is true. The game gives you the answer that is true.
Before play begins, brief the group in two sentences: this is a real game, play to win, and there will be a debrief afterward about what the game surfaced. Do not tell them it is a culture audit. That framing invites performance. What you want is behavior.
What makes the game useful as a culture instrument is the competitive structure. Each player has their own objectives, their own resources, and their own incentives to win. They are not a team. They are individuals with competing priorities sitting at the same table, which is also an accurate description of most organizations. Your stated values are supposed to govern behavior even when those priorities conflict. Transparency when sharing information would help someone you are competing against. Psychological safety when speaking up might expose your own position. Ownership when the most comfortable explanation for a loss is someone else's move. Collaboration when the person you would be helping is directly competing with you for the same outcome. The game puts people in exactly those conditions. What you are watching is whether the stated values survive contact with real competing interests. In the real world, this is also when they matter most.
Customize This Before You Run It
Replace the five values below with your organization's actual declared values. Not the ones you wish were true. The ones on the wall, in the onboarding deck, or referenced in the last all-hands. For each one, define what you would expect to see during the game if the value was genuinely operating, and what you would see if it was not. The more specific your criteria, the more useful your notes will be in Step 2.
1
Transparency
We say: "We share information openly and proactively."
When this value is operating
A player shares information that benefits others at the table, including direct competitors, because the stated value says that is how this organization operates. They do it even when keeping it close would have given them an edge.
When it is not
Information that would affect others' decisions is held back. The competitive context provides the justification: this is a game, and withholding is rational. Note whether that rationalization sounds like anything you have heard at work.
2
Psychological Safety
We say: "People speak up, challenge ideas, and admit mistakes without fear of judgment."
When this value is operating
A player raises a concern or names a mistake in their own play, in front of people who are competing directly against them. They do it knowing it gives others a read on their position. The value holds even when it has a personal cost.
When it is not
Players say nothing that could expose their strategy or invite scrutiny of their decisions. Concerns go unvoiced. Mistakes get quietly absorbed rather than named. The competitive context makes silence feel smart, but the habit it reflects is exactly what limits candor at work.
3
Ownership
We say: "We take personal accountability for outcomes, not just effort."
When this value is operating
When a player loses ground, they name the specific decision they made that led to it, out loud, in front of the people they are competing against. They do not reach for another player's move or an unlucky draw as the explanation.
When it is not
Setbacks get explained by what other players did, by the mechanics, or by luck. The individual's own decisions are absent from the account. In a competitive game, this is the most common pattern and the hardest one to interrupt.
4
Collaboration
We say: "We work across functions and leverage each other's expertise."
When this value is operating
Despite competing directly, a player shares information or a read with someone else at the table because doing so is consistent with how the organization says it operates. The value holds even when it costs them a competitive edge.
When it is not
Every decision is optimized for personal position. Cooperation, even in moments where it would benefit everyone, gets abandoned because the competitive frame makes it feel naive. This is the version of collaboration that only operates when it is convenient.
5
Bias for Action
We say: "We make decisions with the information available and move."
When this value is operating
A player commits to a direction with incomplete information rather than waiting to see what others do first. They accept the risk of being wrong as preferable to the cost of moving last.
When it is not
Players hold back and watch what others commit to before deciding. The competitive context becomes cover for hesitation. Everyone waits for someone else to go first. The round stalls not from complexity but from unwillingness to be exposed before others are.
Stay out of the table and take notes privately throughout. For each value, jot down a specific moment: what happened, what was said, what the response was. Do not note names. Note behaviors. "A player challenged the group's direction in round two and the group reconsidered" is a note. "Alex argued with Sam" is not. These observations are what you bring into Step 2.
Step 2: Map the Gap 40 min
Frame it in 90 seconds before you start. Something like: "We just spent 30 minutes in a situation where each of you had your own incentives and your own objectives. You were not a team. You were competing. What we are going to do now is look at how we each behaved in that situation and compare it to what we say we believe as an organization. This is not a performance review. It is a diagnostic. The goal is to see clearly."
Before opening each dimension, review the notes you took in Step 1. You will bring specific observations into the conversation, not as accusations but as data points. The language that works: "During the game, I noticed [specific pattern or behavior]. Does that resonate with what others observed?" Let the group confirm, dispute, or add to what you saw. Your role is to introduce the evidence, not to interpret it for them.
This section draws directly from a companion piece: the "Culture Is Already Showing" post covers why the gap between stated and operational culture is almost universal and why it only becomes visible under pressure.
1
Transparency
Did information flow when it mattered?
What we say
We share information openly and proactively.
How to use your Step 1 notes here
The real question is whether the value held when it had a personal cost. If you saw information kept close because sharing it would have helped a competitor, name it: "I noticed that [a specific piece of information] was available but didn't surface until after it had already affected several decisions. In this organization, what usually determines whether information gets shared or protected?"
2
Psychological Safety
Did people speak up when it counted?
What we say
People speak up, challenge ideas, and admit mistakes without fear of judgment.
How to use your Step 1 notes here
Speaking up when it might expose your own position, or raise a concern that benefits people you are competing with, has a personal cost. If people stayed quiet rather than surface something, name it: "I noticed that [a concern or mistake] didn't get raised until after it had already cost someone. What does it usually take to say something here when speaking up works against your own interest?"
3
Ownership
Who claimed the outcome when things went wrong?
What we say
We take personal accountability for outcomes, not just effort.
How to use your Step 1 notes here
In individual competition, there is always a more comfortable explanation than "I made the wrong call." If you saw players attribute losses to others' moves or to the game rather than their own decisions, name it: "When [a player lost ground], I noticed the explanation pointed outward. In your actual work, when something goes wrong, what is the first explanation you reach for? And is that the one you say out loud?"
4
Collaboration
Did expertise get shared or protected?
What we say
We work across functions and leverage each other's expertise.
How to use your Step 1 notes here
The harder version of this question is: does collaboration hold when it directly helps someone you are competing with for budget, credit, or recognition? If you saw players optimize individually when a moment of cooperation was available, name it: "I noticed there were moments where [sharing a read or a resource] was possible and didn't happen. When does collaboration break down here, and what is usually driving it?"
5
Bias for Action
Did the team decide, or did it wait for certainty?
What we say
We make decisions with the information available and move.
How to use your Step 1 notes here
The individual competition version of this is specific: do people move when others are watching and might benefit from seeing their decision first? If you saw players hold back to let others commit first, name it: "I noticed there were moments where someone had enough to act but waited to see what others would do. Does that show up in how decisions get made here? What does it usually take for someone to go first when others are watching?"
The most common debrief error is letting the group stay in the abstract. When someone says "we struggle with accountability," ask them to name a specific moment from the last thirty minutes. The specific observation is what makes the next step possible.
Step 3: Commit to One Shift 20 min
The most common facilitation mistake at this stage is asking the group to "develop an action plan." Action plans require committee approval, timelines, and cross-functional buy-in. They take weeks to produce and months to forget. Instead: one person, one value, one behavior, two weeks.
Each person picks the value where they saw the clearest gap between what they did in the game and what the stated value asks for. Not the easiest one. The one that surfaced most honestly. They fill out the card for that value and read it aloud.
1
Transparency
1
I noticed that I [held information close / shared it later than I could have] when [specific moment in the game].
2
In the next two weeks, when I have information that affects someone else's decision, I will share it before being asked, even when doing so [gives away an edge / creates more work / complicates my position].
3
I will know I have done it when someone made a better decision because of something I surfaced before they had to ask for it.
2
Psychological Safety
1
I noticed that I [stayed quiet / didn't raise a concern / didn't admit a mistake] at [specific moment in the game] when I could have said something.
2
In the next two weeks, I will name [a concern / a disagreement / a mistake of my own] in [specific situation], even when doing so works against my immediate interest.
3
I will know I have done it when I have said something in the room that I would previously have kept to myself.
3
Ownership
1
I noticed that I explained [a result / a setback] by pointing to [another player's move / the mechanics / luck] rather than naming the specific call I made.
2
In the next two weeks, when something I am responsible for goes wrong, I will name my own decision as the first part of the account, before I name any other factor.
3
I will know I have done it when I have said "I got that wrong" in a specific situation without adding a qualifier.
4
Collaboration
1
I noticed that I [made a decision / moved forward] without checking with [someone who had a relevant perspective] at [specific moment in the game], even though their input would have helped.
2
In the next two weeks, I will ask for input from [a specific person or role outside my immediate circle] before [a specific type of decision], even when doing so slows me down or helps someone I am competing with.
3
I will know I have done it when a decision I made is visibly better because of a perspective I asked for rather than assumed.
5
Bias for Action
1
I noticed that I [waited / held back / kept watching what others would do] when I already had enough to move at [specific moment in the game].
2
In the next two weeks, when I have [specific threshold: e.g., "a clear enough picture / enough to start"], I will commit and move rather than wait for more certainty or to see what others do first.
3
I will know I have done it when I have made a call and acted on it before I felt fully ready, and used what happened to adjust rather than waiting until I was sure.
Reading them aloud is not optional. Commitment that stays inside a notebook stays inside a notebook. The act of saying it in the room, in front of people who also competed against you twenty minutes ago, creates a different kind of accountability than writing it down privately.
Push for specificity before anyone reads. A commit like "I will be more transparent" is not a commit. A commit like "I will send the project status before my manager asks for it in the next three Thursday check-ins" is. If someone reads a general one, ask them to make it specific before you move on.
Facilitator Notes
You do not need to be a culture expert to run this workshop. You need to hold the structure and resist the urge to rescue people from uncomfortable observations.
The "It's Just a Game" Objection
You will hear this. Usually from the most senior person in the room, usually after an observation about a behavior they were central to. The response is not to argue with them. It is: "You're right. It is a game. The interesting thing is that the pattern you're describing has also come up in [specific project or situation the group knows about]. Do you think there's a connection?" Do not force the link. Invite it. If they say no, move on. The observation was still made in the room.
When Someone Gets Defensive
Redirect from the person to the pattern. Instead of "I noticed that Sarah made all the final calls," say "I noticed that decisions in the game tended to move toward one person in the final minutes. Does that match what others saw?" This makes the observation about a system behavior, not an individual indictment. The same observation lands very differently depending on whether it is attributed or described.
The Best Debriefs Stay Specific
The conversations that produce real behavior change are the ones where someone says "In the second round, when we lost the resource allocation, I went quiet for four minutes." Not "I tend to withdraw under stress." The general observation is probably true. The specific one is actionable. Push for the specific one every time.
Culture doesn't change because a workshop surfaced the gap. It changes because someone decided to behave differently in the next meeting, and then the one after that, until the new behavior didn't require a decision anymore. The workshop creates the moment of seeing. The ninety-day window after it is where the work actually happens.
Tech CoLab's games are built to surface exactly the dynamics this workshop asks teams to examine. Run the game. Run the debrief. Build the culture you said you had.
