I have grown to loathe the phrase “collaborative storytelling”.
Unjustifiably so. It’s an entirely inoffensive term in its own right. It describes an entirely inoffensive activity. I am ostensibly a writer, I’ve spent time with other writers, and collaborative writing projects are always an interesting experience. The result is usually that writers have to negotiate with one another and stubbornly hold to certain ideas, yes, but just as much inspiration sparks back and forth and people propose new ideas that either one might not have landed on alone. Given that art is often a solitary hobby, it makes for a compelling change of pace.
But, of course, that’s writing, and this is a blog about TTRPGs. Those may contain elements of writing in their experience, but the experience of playing an RPG and the experience of writing a story are quite different. They do not function the same way.
So it is with a growing clump of frustration that I read an RPG describe itself as though it were collaborative storytelling, dropping that phrase by name, while ensuring systemically that it does not work that way. That I read discussions about the medium as a whole using the phrase as equivalent to ‘role-playing game’ itself. Most perniciously, that it becomes enshrined as how games ought to be. Any acknowledgement of the competitive or segregated nature of a system’s design becomes an attack on the claim to it being [collaborative] – and therefore, an attack on its worth as a game.
I do not, per se, want this to be a post weighing in on discourse or counterattacking in an active argument. I try to avoid such impulses seeping into this blog. In this case, however, I do think there’s a core blind spot in how RPGs are popularly discussed. The competitive tensions of RPGs are baked in at the roots, and even games that claim to aspire towards full collaborative play factor them in without realizing. Even for the goal of making a better collaborative game, it’s necessary to recognize the limits thereof.
Those limits begin at the very foundations.
Player vs GM
First and most straightforwardly – if there’s anything like a GM role in your game, that player is at odds with the others.
It’s a GM’s job to position obstacles that the players work against, after all. To provide prompts and complications the players would not willingly introduce on their own. If they don’t do that, then there isn’t really a reason for the game to have a GM in the first place. However, if they do do that… that means the core contribution of the GM to the gameplay is things the players are positioned to not want. [GM presents obstacle, players overcome obstacle] is a straightforward loop built into plenty of games – but in that loop, the players win the most if they minimize how much the GM gets to play. The more the GM successfully places problems and the players have to reckon with them, the less the players get to follow their own pursuits and desires.
(If the players enjoy overcoming obstacles, and that’s what they want to do, then, that’s good. That is a healthy, functional table dynamic for the expectations of that game. However, it’s not collaboration. Rather, that’s a [friendly competition] – a pattern quite familiar in, really, every other game space. When you play tennis with a friend, casually, you are still in competition with one another. Even when you both are enjoying what you’re doing and would not be satisfied if the other player folded and gave you infinity points.)
Alongside wielding mechanics to interfere with players, the primary use case of a GM in a game is one of narrative control. They inherently define boundaries of what is acceptable and unacceptable to narrate. If a player wants to declare something beyond these limits, the GM is there to tell them no, and to impose their own vision instead. That’s what the role does, and even a GM who actively takes suggestions from players isn’t truly relinquishing that power, or democratizing it. They’re just doing favors.
Now, this does ostensibly have some resemblance to the experience of collaborative writing. Anyone who’s tried that for an extended period of time has gotten into an argument with a co-writer about how things ought to be written. This sort of conflict is normal, and working it out is doable (if you can stand to come to an agreement with another artist). However, in such contexts, the writers are usually on equal ground, and without further incentives than wanting their story to work a certain way. It’s a thorny collaboration, but I would be hard-pressed to find an angle to describe it as competitive. When one of the people involved is a GM, and the other is a player, however, the circumstances look quite different. The power dynamic means the GM is “right by default”, for one. The player’s incentives are inherently subject to scrutiny – why are they asking for this? How do they stand to gain? How much of this is an instrumental ploy, and what does the GM risk if they choose to allow this to slide? It’s not a disagreement between two writers, so much as offering a proposal before a court.
Any efforts to shape GMed roleplay as collaboration, thus, are done by the grace of the GM. Said [grace] is, most often, an excess of generosity and effort to actively ignore what the system asks a GM to do, for the sake of their own sense of what ought to happen. This still isn’t an equitable collaboration, it is one player choosing to proxy the wishes of others through their own power – but I think that’s besides the point. “This is collaborative storytelling, as long as you bypass the systems and expectations themselves for the sake of making it so” is already a damning criticism of the claim of collaborativity in the first place. An actually collaborative RPG should be designed such that, solely by following the rules and what is expected of you, you are in fact working alongside the other players, together.
Player vs Player
As it so happens, many GMed RPGs actually do fit that bill of collaborativity. Just, they end up with a many-vs-1 team competitive format. The players are a unified group, forming a “partyblob” as an instrumental unit working against the obstacles the GM presents. From an instrumental perspective, it’s not every player for themself.
Interestingly, in party dynamics, even in games without a GM – it’s the storytelling component which drives things more towards competition.
In most roleplaying games, the players have a role they are playing. Usually, a person, or other such entity in the world (sometimes a faction or political body, that sort of thing). Instrumental concerns being what they are, the question there is only focused on what they can do and what goals they aim to achieve. However, if you’re not playing purely instrumentally (and most people do not), your most plausible next goal is something in the aesthetic line. Wanting to express the character (or whatever it is) you’re playing. Wanting to show off the cool parts, examine the foibles, dig into the role you play.
The problem is, there’s a zero-sum game here. Time. You have a finite amount of time to sit down and play the game, and that time cannot be spent on everyone’s characters at once. Not if you want focus. In fact, narrative focus and spotlighting can arguably be defined as a point in time when only one or a specific set of characters are being explored in details, and the others are pushed to the wayside.
Immediately, this competes with the partyblob. It is a lot easier to put narrative focus on someone if they aren’t constantly with a group. This is a clash of incentives between instrumental play and character-examination play, and that has its own knock-on problems. But ignoring that aspect of it, just looking at it from the narrative focus direction, when someone peels off from the group to do their own thing, the other players are actively out of the spotlight. Their desire for narrative focus is lost, because another player took the limited resource first.
This isn’t constrained to character focus. Arguably, it’s true of anything that costs time in play. However, character focus is the most straightforward instance where everyone’s goals are in competition. When sitting down to play an RPG which defines the thing you play, you will have more investment in your particular character than the others. (As a result, games which rotate what you’re playing tend to have this problem to a lesser degree – but even then, it’s present!) Your personal vision of how you think things ought to happen is another instance of conflict, for instance – but it’s not competing for a zero-sum resource. In fact, it’s a conflict that occurs even in collaborative writing itself.
Of course, collaborative writing also has the benefit of not needing to be so particular about character spotlighting and importance. (Unless the particular writers are precious about their favorite little guys. A case could be made that attempting to do collaborative writing between very “my character is the bestest”-type writers ends up becoming competitive in a rather RPG-like shape!) You can just put a character on the side for a while, or have them act in both self-effacing and inefficient ways, and that can just serve the needs of the broader story you are constructing. In an RPG, you can only do the same if the controlling player swallows the “loss” – and even if they do so, that’s just the same as the GM’s noblesse oblige. Willingly showing grace to accept a move against what your position compels you towards is not, really, collaboration. Or, at least, it doesn’t make the structure collaborative. You’re making an effort to collaborate, at personal cost, despite what the system expects of you.
Polite Agreements
Most often, I see the positioning of collaborative storytelling in RPGs framed as a matter of play culture. Some traditions are more inclined towards collaborativity, others less so; it’s best to play with people who match your interest.
This is true, in my eyes, but also fundamentally wrong. That is to say – the structure of a game, in and of itself, will do a significant amount of work towards making collaborative writing difficult, no matter what sort of group plays it. The primary bypass for this is, quite literally, a bypass. The group politely agreeing, explicitly or unspoken, to work against their own incentives. To ignore the structures of the game that push them towards competition, and perform collaboratively instead.
This only somewhat works. Of course it does. Systems still impact the people moving through them, even as those people actively try to defy the expectations put upon them. No matter how much grace the GM gives, and how much they allow proposals to go, they are still in the position of [the source of obstacles for the players to deal with]. That will wear on them. Even if they do a perfect job of collaborating with the players, it will be a source of fatigue.
As a result, a lot of the time, declaring games to be collaborative is an argument to sweep the impacts of systems under the rug. For a bit of a hot take, this is my grievance with how play principles are often positioned in, say, Forged in the Dark games. For a more straightforwardly coherent point – you can find people describing Dungeons And Dragons as collaborative storytelling. You cannot play Dungeons And Dragons as collaborative storytelling. At best, you can do collaborative storytelling with Dungeons And Dragons as a prop alongside you, and the incentives I’ve discussed here will still wear on those involved. Adhering to a polite agreement is not a free operation. It is a constant tax on one’s time and energy. Building collaborative writing out of a large list of polite agreements not only will not fully work, it will drain everyone involved.
Now, there are some variables to this arrangement which a game designer cannot control, because they come down to personal differences. And I do mean personal, not cultural. How much grace someone is willing and able to offer in their bypass agreements is obvious, but I think the most impactful one is actually a force on the player-vs-player competitive scramble for the spotlight. After all, a lot of the time people will attest that they are invested in other characters at the table, not just their own. Watching someone else be in the spotlight is, for them, also a win in terms of narrative impact. Additionally, sometimes you have players actively timid about being in the spotlight, not wanting to maximize their time (but still having a minimum quota they want to fulfill). Oftentimes people like seeing other characters in focus a little, but not as much as they enjoy their own. From a design perspective, this is an optimization game where the numbers change every time and you don’t get to see them. But, most important to note, the conflict still exists, whatever the variation. You may not know the exact shape for a given table, but focus is a resource, and it’s one people are emotionally incentivized to aim for. A lot of the time, it’s why people are here playing RPGs at all. (Which is another concern for games that incentivize a partyblob. The whole group moving together and instrumentally achieving goals means nobody gets to be in much narrative focus – that’s time spent with nobody winning. Now it’s a negative sum game.)
There’s a cultural oddity in RPGs which makes this a much rarer perspective than I would have imagined. GMed RPGs as a many-vs-one competitive game with secondary emotional stakes pushing PvP in the many is, to me, pretty intuitive – but it’s a perspective I never see, and generally get people balking at when I bring it up. Core to that, I think, is a notion that it’s good to be collaborative and bad to be competitive. That an RPG is more prosocial and more admirable if it is collaborative. This, combined with the fact that polite agreements are a possible (imperfect) workaround for any given foible of a system, leads people to say any game they happen to like is collaborative, because collaborativity is good and a game should be that. Despite not actually making the game function in a collaborative manner much at all.
I don’t really understand this impulse, and I suspect in part that’s because it’s not a conscious bias. It’s just something people have absorbed from broader discourse and cultural expectations. In particular, I suspect, conflict between play cultures contributes to it: “I do not enjoy playing with people who follow this more competitive play culture” -> “I enjoy playing games that put less competitive pressure on me” -> “the games I enjoy are collaborative”. Not a coherent line of logic, but many of these things are subconscious, so that’s to be expected. More to the point – I can’t really criticize, when all the conversation I see seems to take for granted that RPGs are a collaborative experience, inherently, no matter what the system or the expected emotional stakes push you towards.
And honestly, I think we’re being unfair to competition this way! D&D is a competitive many-vs-one instrumental RPG. That’s fine. It’s good, even! It’s better that it be that, than that one try to treat it as a collaborative writing exercise, and struggle against the game’s design from start to finish. Competition has no need to be fully cutthroat or instrumental – friendly competition exists in sports, board games, wargames, video games, every other game space in the world, really. When I willingly change my build in Lancer because the GM finds it too oppressive and struggles to play against, I’m not being collaborative, I’m adopting the standards of friendly competition. That works out fine, and it’s in no way antithetical to anything else RPGs do.
Also, hey. Collaborative writing, the actual experience, sitting down with another writer and hashing out a story in full, is quite fun. And very different even to the experience of freeform roleplay with another writer. Those are, both, their own things. Well worth trying in their own right! I solidly recommend them. A broader space of experiences in life can only ever be good for you. The result will not be shaped like an RPG, because very few RPGs actually aim to be shaped like collaborative storytelling. And that’s not an issue. They don’t have to be.