articy:draft

Narrative doesn’t break when it’s written. It breaks when it’s implemented: when dialogue, logic, conditions, and consequences need to survive iteration, collaboration, and change. That’s where documents stop being enough.

An interesting article exploring the need for strong narrative editors: gamedeveloper.com/design/making-…

Most teams don’t lock narrative early because they want to. They do it because: – changes feel risky – dependencies aren’t visible – downstream teams need stability The real issue isn’t ambition. It’s the lack of systems designed to support narrative change across production.

Game writers at Game Developers Conference 2026 — ready to write under pressure? Tonight the legendary Write Club Party is back at Johnny Foley’s. Live prompts. Live writing. Live judging. And we're proud to be a sponsor. May the best writer win!

We’re excited to support the GDC Game Writing SIG Write Club again this year. Proud that articy:draft X gets to sponsor one of the most chaotic (and fun) narrative design events of Game Developers Conference 2026. Have fun at Johnny Foley’s! 🍻

Structure isn’t a creative limitation. It’s what makes narrative flexible. It lets teams iterate, collaborate, and adapt without losing context or consequences. The more complex the story, the more structure it needs—not to restrict creativity, but to protect it.

What can game designers learn from a productivity app? This breakdown of Focus Friend shows how task management borrowed progression loops from farming games to crack retention. deconstructoroffun.com/blog/2026/2/19…

Narrative doesn’t belong to one role. When narrative tools isolate writers instead of connecting teams, collaboration breaks exactly where it matters most: during change. Good narrative systems don’t just store story. They keep everyone aligned as it evolves.

Not every protagonist needs to be likable. But they do need to be intentional. This breakdown of Aava in Cairn shows how character friction can strengthen theme and player experience. Great read: gamedeveloper.com/design/cairn-s…

Locking narrative early isn’t a creative choice. It’s often a production survival tactic. Narrative tools shouldn’t just help you write. They should help you change your mind safely.

Can announcing a new game in a franchise spark interest in older titles? gamesindustry.biz/resident-evil-…

Narrative debt is quiet early on. By beta, it’s very loud. Every “just one small change” has consequences. If your tools can’t track them, iteration becomes risky.

Narrative debt compounds faster than technical debt. And it’s much harder to clean up late in production.

Great tips from Heidi McDonald for creators developing emotionally heavy games with lessons learned developing a game about loss: game-writing.com/posts/protecti…

Narrative rarely fails because of bad writing. It fails because the system around it can’t handle change.

An interesting interview on building games that last with lessons from Zynga's EVP Studios: deconstructoroffun.com/blog/2026/1/27…

Writing in more than one language doesn’t have to mean more chaos. Keep all your narrative text, VO notes, and states in one place with #articydraft . Track what’s final or outdated, and export only what’s needed. Less spreadsheet ping-pong, more time shaping the story.

An interesting article on the unique challenges when storytelling for VR: gamesindustry.biz/how-game-story…

Ever wished your story objects just knew what they needed? Templates in articy:draft let you shape project-specific properties once, then reuse and tweak them as your narrative evolves. Flexible, modular, and made for iteration when ideas inevitably change.

Part Three of The Making of Disco Elysium is live! This episode dives into writing, with the team sharing how they shaped characters and narratives in articy:draft—from first concepts to final drafts. youtube.com/watch?v=fpjHZc…