Pitch a Cooperative Game Show Without Manufacturing a Rival
Pitch a Cooperative Game Show Without Manufacturing a Rival
Somewhere around the third page of a cooperative pitch, the villain shows up. Two contestants start working against the others, a rival team appears, a secret ballot gets added. None of it is what the creator wanted, which was a show where the cast succeeds or fails together. It is what happens when a shared objective runs out of places to put pressure.
The pressure has somewhere else to go. It goes into the task. A group that shares one outcome can still face a resource that will not stretch, information that lives in three different heads, and a rule about who may act when. The consequence does not vanish when you remove the opponent. It changes address.
That is the whole move, and the rest of this is what it takes to make it hold. Build a task where the group is trying to finish one thing, name the specific reason it might not finish, split the decisions so no single person can carry them all, show the group and the audience how far along they are, and decide in advance what the host is allowed to do. Then vary the dependencies instead of the cast.
State the shared objective and the obstacle
A shared objective is a finished object or state: the model stands, the mural is hung, the route is open. The obstacle is the specific reason it might not exist — missing information, a stock that runs out, a coordination requirement, or a physical or timed challenge the rules fix in advance. An obstacle is legitimate when it lives inside the stated rules and stays there. If the only thing preventing completion is that the host has not said whether they are done, you have a quiz, not a task.
The test that separates a cooperative round from a themed playlist is this: cover the prize and ask whether the tasks still need each other. If each contestant can finish their own piece in their own corner and the group merely counts the results at the end, the shared outcome is decoration. Nothing about the tasks themselves explains why these people are in one room.
Here is an invented task that does need them. Three participants assemble a tabletop community display model: a three-bay covered arcade. The kit contains four columns, three panels, and a base plate. The plate has four sockets in a row and one more at the front centre, which the kit's card identifies as a placard socket — the placard post ships separately and is not in the box. Columns clip into sockets and stay clipped; nothing comes back out. Each panel spans exactly one bay, and the three bays share columns, so the finished arcade uses all four columns and all three panels and leaves the tray empty.
This is an invented task, and nobody has played it. The numbers below are the point, not a report.
The obstacle is not a shortage of pieces in the ordinary sense — the kit is exactly sufficient. It is that the information needed to spend them correctly is split three ways, and the plate accepts a piece where no piece belongs.
Distribute decisions that cannot all be delegated away
Each participant should hold something the others cannot see, control something the others cannot reach, or make a call the others cannot make for them. In the arcade, the Planner holds the elevation sheet: where the bays sit in relation to each other, and a small diagram printed underneath it. The Keeper holds the card: four columns, three panels, four row sockets, one placard socket, clips do not release. The Builder holds the plate and the pieces, and is the only person permitted to attach — and only after the Planner has named a position aloud and the Keeper has named the piece aloud.
Now follow one decision into another person's options. The Planner reads the elevation and decides the bays share columns, which means four columns do the work of six and the kit is sufficient after all. That reading is not obvious; a group that assumes every bay needs its own pair will conclude the kit is short and start improvising. If the Planner makes it, the Keeper can confirm that four columns are present, and the Builder can then start clipping. If the Planner gets it wrong, the Keeper has the count to say so. The chain is short, but each link closes or opens the next link's options.
Apply one more test before you write the pitch. Ask what happens if the most capable person in the room could also read the sheet and the card. If that person can complete the whole model while the others pass pieces, the dependency is not working yet, and the honest fix is to change the information arrangement rather than add a rule forbidding it. In the arcade, the Builder cannot see the elevation or the card, so the Builder's skill is real but insufficient. That is the difference between a task with roles and a task with witnesses.
Describe the roles by what each person holds and may do. Do not write predictions into the pitch about who will take charge, who will hesitate, or which two will disagree. You do not know, and the pitch reads as more confident when it does not pretend to.
Make progress readable before the final result
A cooperative round needs intermediate states that both the players and the audience can read at a glance. Sockets filled. Bays standing. The tray emptying. Whatever the state is, it should change in a way that can be pointed at, and it should change as a consequence of something the group decided rather than as a periodic reveal.
Alongside progress, define three end states instead of the usual two. Full success is the three-bay arcade with an empty tray. Failure is pieces committed with nothing standing, and it is reachable here: clip one column into the placard socket and two into the outer row sockets, and the two sockets between them leave a gap no panel can span. Nothing comes back out, so the column still in the tray can raise one bay from there and no more. Partial success sits between them and is the one most cooperative pitches forget to design.
Suppose the Planner reads a mark in the small diagram on the sheet as a column standing forward of the row. Read that way, it counts as one of the four columns the elevation calls for, so the plan leaves only three columns in the row and sends the fourth to the front-centre socket. The Builder clips it in. The clip holds. The placard socket sits off the row line, too far forward for a panel to reach, so the group now has three columns and three panels for a three-bay arcade that needs four columns. The Keeper recounts the tray and the arithmetic does the explaining without anyone accusing anyone: three columns cannot make three bays.
What follows is the partial outcome, and it should be worth watching. The group can place the remaining columns in three row sockets, span two bays, and finish with one panel left in the tray. The model stands, is legible, and is visibly shorter than the plan. That is a different thing from defeat, and the difference matters to the pitch: the error cost one bay, not the round. The panel in the tray shows the audience exactly what was given up.
Notice what none of this needed. No rival team. No one who wants the group to fail. The lost column is a consequence of a reading, a rule, and a locked clip.
Specify what the host may change
Cooperative formats tend to blur the host's role, and the blur is where the accounting goes wrong. Write three separate registers into the pitch.
Explaining the rules happens before the round, applies to everyone equally, and adds no information the group did not have. It is not assistance.
An authorized clue is designed in advance, is bounded, and has a window. For the arcade, the host may, once, answer whether a mark on the Planner's sheet shows part of the model or part of the tray, and that offer expires the moment the first column is clipped in. That is a real design decision with a real shape: it resolves exactly one uncertainty, it resolves it early, and it becomes unavailable precisely when the round starts committing pieces.
Walk through what it does. The Planner asks the question before anything is attached. The host says the lower diagram shows the tray. The Planner drops the forward column from the plan, the three bays go up across four row sockets, and the tray empties. The group still had to find the shared-column structure themselves; they did not have to find the tray diagram unaided.
An improvised intervention has the same visible result and a different meaning. Same kit, same roles, same rules — but nobody asks, and the host volunteers that the diagram below the elevation is not part of the model. The arcade still gets built. What changed is that the round no longer demonstrates anything about whether the group would have caught it, because the one uncertainty the task was built around was removed by someone outside the task. If that moment is not recorded, any later claim about the group's unaided coordination is simply wrong.
Help that adds material deserves the same treatment. A fifth column in the kit absorbs the mistake completely, because the binding constraint is columns and not panels. That is worth saying out loud in the pitch: an extra panel changes nothing at all, and an extra column changes the stakes. Whatever the host does, the record of what the task demonstrated has to match what the group was actually handed.
Find variation in the dependencies
You do not need a new cast or a new conflict to get a second episode out of a good cooperative task. Change one dependency and keep the rule logic intact.
Move the tray diagram off the Planner's sheet and onto the Keeper's card. Same kit, same plate, same agreement gate, same objective. The Planner now holds only the elevation, which shows four marks and three bays and nothing else. The mistake has not disappeared; it has changed hands. The Keeper, reading the card aloud, describes a diagram of how the pieces lie in the tray. The Planner hears a description of something in the box and, without the image, treats part of it as part of the model. Now the group's real guard is the Keeper noticing that the front-centre socket is the one the card labels as a placard socket, and that requires the Keeper to connect a detail nobody asked about to a placement being discussed across the table. The round is harder, and it is harder for a reason you can point to.
Change a resource instead and you get a different round again. Keep the sheets where they were and put five columns in the kit; the mistake is now free, the three bays go up anyway, and the round has lost its teeth. Keep four columns and add a fourth panel, and nothing changes except the waste — the constraint is columns, so extra panels are scenery.
Two cautions belong in this section rather than at the end of the pitch. A coherent round is not automatically an interesting program, and a format description is not an episode. If you go looking at a published cooperative format as a reference, the printed rules and the broadcast round are two different documents; the rules tell you what the task is supposed to be, and only the round itself tells you what a group actually did with it. Keeping those two separate is the difference between describing a design and claiming you have seen it work.
Where this leaves the pitch
Picture the two-bay version again. Three people, a plate with a column clipped where no column belongs, two bays standing, one panel left in the tray. Everything that happened is traceable to a choice someone made and a rule that was written down before anyone arrived. No one had to be cast as an obstacle.
What remains open is most of what a commissioner will actually ask. Will a real group catch the shared-column structure before they commit pieces, or will they commit first and count later? Will three strangers coordinate through a spoken-agreement rule under a clock, or will the rule slow them until the timer decides the round? Does an audience stay with a group that is losing a bay at a time, or does the absence of an opponent leave them without anyone to root against? This design does not answer those questions.
It does not need to before it goes on a page. What it needs is a task whose pieces are exactly sufficient, an obstacle inside the rules, three decisions that cannot be collapsed into one person, states that change where the audience can see them, and a host whose help has a stated window and a written record. Get those right and the rival you were about to invent has nowhere left to stand.
Frequently asked questions
What is the core move for pitching a cooperative game show without inventing a rival?
Put the pressure into the task rather than an opponent. The group shares one objective, but faces a specific obstacle inside the rules, decisions split so no one person can carry them all, progress the group and audience can read, and a host whose help is bounded. Then vary dependencies between episodes instead of the cast.
How can I tell whether a cooperative task is actually cooperative?
Cover the prize and ask whether the tasks still need each other. If each contestant can finish a piece alone and the group merely counts results at the end, the shared outcome is decoration. A cooperative round needs tasks that explain why these people are in one room.
What makes an obstacle legitimate rather than a host's whim?
It lives inside the stated rules and stays there. It should be a specific reason the shared objective might not exist: missing information, a stock that runs out, a coordination requirement, or a physical or timed challenge fixed in advance. If the only thing preventing completion is that the host has not said the group is done, that is a quiz, not a task.
How can I keep one capable player from solving the whole cooperative task?
Give each participant something others cannot see, control, or decide for them, and test whether the most capable person could still complete everything while others pass pieces. If so, change the information arrangement rather than adding a rule forbidding it. In the invented arcade example, the Planner holds the elevation, the Keeper holds the card, and the Builder holds the plate and pieces but cannot see the sheet or card.
Why design partial success, and what should the host's help do?
Define three end states: full success, failure, and partial success, because partial success is often forgotten and is worth watching. Host help needs separate registers: explaining rules before the round, an authorized clue designed in advance with a bounded window, and improvised intervention with a different meaning even if the result looks the same. Help that adds material changes the stakes: a fifth column absorbs the mistake, while an extra panel changes nothing.