(This is Part Two of our series on how to collaborate with designers. You can read Part One here.)

You’re at a playtesting session.

The player is sprinting, looting, solving, surviving.

You’re tracking the story arc, the dialogue beats, the character backstory…and hoping the player is catching most (some? any?) of it.

You would love to compare notes with the designer, to see what THEY think about how the story is coming across.

But they’re talking about loops, friction, and agency.

You nod along, but deep down… you’re not quite sure what they’re seeing.

And if you can’t see what they see, it’s almost impossible to communicate.

(It's like the 2015 freakout over that dress...was it black and blue, or white and gold? People were looking at the same dress and seeing completely different things.)

This isn’t about learning how to be a designer.

It’s about learning how to see like one.

Why Writers Struggle To Communciate

As a writer, you’re trained to think in arcs, motivations, emotional turns.

Your job is to craft a story that resonates — to make players feel something. Right?

But in most game dev meetings, designers aren’t evaluating your idea based on its emotional arc. They’re running it through a completely different filter:

• Can this be expressed in gameplay?
• What does the player do?
• Does it support the core loop?
• How does it impact pacing, flow, friction?

It’s not that your story isn’t good.

It’s that your story — in that moment — doesn’t translate into the game they're envisioning - the systems and mechanics that they're busy building.

And that’s why it often feels like your ideas get a shrug. Often, your story ideas just make their design work harder. (And their job is already hard enough as it is.)

Design Translated for Writers: What Designers Actually Care About

Understanding the designer’s point of view doesn’t mean abandoning your own work — it just means weaving your work into THEIR work - the mechanical experience.

Here’s what designers are usually focused on:

🎯 Core Gameplay Loops

What the player is doing over and over to drive the game forward.

If your story moment interrupts that loop, or doesn’t reinforce it, it gets in the way — even if it’s a work of art.

🧩 Game Objects & Systems

What items, characters, or elements exist in the game — and how they interact.

Designers often think in terms of objects and affordances. If your story idea requires a new object, mechanic, or behavior, that’s a big ask. It needs to feel worth it — systemically. (See the "your story makes their design work harder" comment, above.)

🎮 Player Experience, Not Just Plot

How the player feels through action, not just cutscenes.

A character’s death might be tragic in the script — but if the player didn’t have agency or emotional investment through gameplay, it won’t land. (I remember playing a game where my character was upset about his missing wife. I was like "What wife? Huh?") Designers think about feedback loops, emotional pacing, and how choice or friction shapes experience.

✨Example:

When you learn to pitch your ideas through that lens — your story becomes a game story.

Get Into Action: Start Speaking Design

You don’t need to master the world of design all at once. Here are a few easy ways to start:

When pitching a story idea, frame it through gameplay first.

“This sequence reinforces the player’s loop of escape-and-hide, but now we’re introducing a moment of power — it could feel transformational.”

Ask system-focused questions, like:

“Where does this moment sit in the pacing curve?”

“Could this narrative twist be delivered through a mechanic instead of a cutscene?”

Use their terms instead of yours.

Instead of "plot" or "pacing," say "engagement." Watch what happens.

Show how your idea fits inside the existing system.

Play games with this lens in mind at least once a week.

Make notes about systems, feedback loops, and where emotional beats occurred. Before you know it, you're going to start seeing games like a designer!

You Can't Be Seen Until You Learn To See

The best story in the world won’t land if it doesn’t make sense to your team.

But when you can speak even a little design — your ideas resonate.

You become a collaborator, not just a contributor.

And your stories? They don’t just live in cutscenes — they come alive in the player’s hands.

🎯 Ready to Practice This?

You don’t need to be a designer — but if you want to tell great stories in games, you've got to learn how to speak their language. That will change everything for you. And that's exactly what we’ll work on in our upcoming workshop, How To Speak Design: A Writer’s Guide. We'll share more about that soon.

Want to build up YOUR game-writing skills? We can help. We've created an easy 5-step guide you can use to write scripts your players will love.

Best of all, it's free. Just click the button below!

Susan’s first job as a game writer was for “a slumber party game - for girls!” She’s gone on to work on over 25 projects, including award-winning titles in the BioShock, Far Cry and Tomb Raider franchises. Titles in her portfolio have sold over 30 million copies and generated over $500 million in sales. She founded the Game Narrative Summit at GDC. Now, she partners with studios, publishers, and writers to help teams ship great games with great stories. She is dedicated to supporting creatives in the games industry so that they can do their best work.