How to run PlateUp! when your kitchen is on fire and your teamwork is also on fire

The honest pitch

PlateUp! is a ridiculous little restaurant game where you control a little playdoh character and you try to serve hungry customers while your kitchen layout, your menu, and your own coordination slowly collapse into chaos.

It is also one of the cleanest teamwork labs I have ever used.

Not because it is “fun”, although it is, but because it forces the exact behaviours most teams claim they want, but rarely practice, especially when the stakes are low enough that people will actually experiment.

If you have ever watched a team hit the moment where the plan stops working, and they either start blaming each other or start adapting, you already understand why this matters.

What makes PlateUp! such a useful teamwork lab

Here is the key design feature, the restaurant is not stable.

Every run you take on new constraints, new equipment, and new failure points. That means teams cannot “set and forget” a process. They have to keep re‑negotiating roles, updating their shared mental model, and deciding what matters most.

In a normal workplace, those adjustments happen too, but the feedback loop is slow. In PlateUp! the feedback loop is brutal, fast, and very obvious.

Think of it like sports training, you do not build decision-making by talking about decision-making. You build it by running drills under constraints, then reflecting, then doing it again with slightly different constraints.

PlateUp! can do that for teams.

Shared priorities become visible, immediately

In a calm kitchen, everyone can look “collaborative”. Under pressure, priorities start competing:

• Serve customers faster, or keep the kitchen clean
• Stick to a role, or jump in to help
• Optimize for today’s rush, or invest in a new layout for tomorrow

Because the game makes those tradeoffs unavoidable, you get a real conversation about priorities.

Role clarity is not optional, but roles must stay flexible

Most teams default to one of two failure modes:

• Everyone does everything, and nobody owns anything
• Everyone clings to their role, and the system breaks when conditions change and roles don’t

PlateUp! forces a better third option, clear ownership with fast handoffs.

The moment the queue builds, you see whether the team can say, “I need you on dishes for 30 seconds”, and whether the other person can actually follow through.

Communication quality matters more than communication volume

In a run that is going well, teams can talk a lot and still win.

In a run that is falling apart, extra chatter becomes noise.

What helps is short, high‑signal calls:

• “Dirty plates are building up”
• “Stop serving, clear tables”
• “I’m behind, need one more in the kitchen”

This is one of my favourite debrief moments, because people realize they were “communicating” constantly, but not communicating usefully.

The game punishes heroics and rewards systems

Everyone loves the person who saves the rush.

PlateUp! will absolutely let someone play hero, for a while, but then it will punish the team for building a workflow that depends on heroics.

That is a gift because it lets you talk about sustainable teamwork in a way that does not feel like a lecture. The evidence is right there, in the burned kitchen or the angry eyes of the hungry customers.

A simple way to run PlateUp! when the restaurant is on fire (and your teamwork is also on fire)

Here is a facilitation move that can help. Pause the game between days, treat the plan as a hypothesis, and run short cycles.

Step 1, Freeze and name the bottleneck

At the end of a day (or round), ask:

• “What is the problem right now?”
• “Where are we losing time, plates, or tables?”
• “What is the one thing that would make the next round easier?”

Do not allow “we need to communicate more” as an answer. Force a concrete plan.

Examples:

• Dishwashing is the bottleneck
• We are colliding in the kitchen
• Orders are backing up because nobody is running food

Step 2, Make one small change, not five

Teams love to redesign the whole kitchen.

Do not let them.

Pick one change that addresses the bottleneck:

• One new station
• One new role rule
• One layout adjustment

In training terms, this is resisted practice, you add one constraint, then see what breaks.

Step 3, Define one behavioural rule for the next day

Make it observable and specific. Examples:

• “If dishes pile above X, one person switches to dishes immediately”
• “No one crosses the kitchen centre line unless called”
• “Call ‘reset’ when orders exceed two”

Then you have something you can actually measure.

Step 4, Run the day, then debrief on evidence

Debrief like this:

• What happened, specifically
• What worked, specifically
• What failed, specifically
• What is the next issue you foresee

This keeps the learning grounded in what the team just experienced, not what they wish had happened.

What to watch for

If you are using PlateUp! for skill development, the game is not the point. The moments and experiences of the players are more important.

Here are the moments I pay attention to:

• The first blame spike: Someone makes a mistake, and the team decides whether to blame or adapt.
• The first role conflict: Two people try to do the same job, then realize nobody is doing another job.
• The first “silent fail”: A bottleneck builds because nobody wants to interrupt, and the team learns that silence is not neutral.
• The first leadership handoff: Someone takes point, then hands off when they are overloaded, without drama.

Those four moments give you enough material for a very practical discussion about teamwork at work.

The bigger question this raises

If a silly restaurant game can expose teamwork breakdowns this clearly, what does that say about how we usually train teamwork?

Most “teamwork training” is language, not practice. It is slides, not actual repetition.

PlateUp! gives teams reps. Fast low-stakes ones. And because the feedback is immediate, teams can actually get better within a session.

Try this with your team

If you want a simple starting point, run three short cycles:

1. One run with no coaching, just observe

2. One run with one change per day

3. One run where the team must explicitly call role handoffs

You will learn more about your team’s coordination in 45 minutes than most workshops reveal in a full day.

And yes, your kitchen will still catch fire.

That is sort of the point.

— J