When studios say they “do Agile,” the conversation usually jumps to Scrum ceremonies, Jira workflows, and burndown charts. Those are tools. They’re not the main question.
The real question is: who owns the value of the game?
In software, that’s the Product Owner. In games, that should almost always be your Game Designer / Creative Director. One fast way to see if that’s actually true in your studio is to run a simple Roadmap Clarity Check on your current project.
What the Game Designer Actually Owns
When I say “Game Designer” here, I’m talking about the discipline that defines the experience, not just fills content:
- Game UX / player experience
- Systems design
- Narrative as it shapes play
- Gameplay and core mechanics
This discipline owns:
- The moment‑to‑moment experience
- The core loop and how it feels over time
- Which mechanics exist and which don’t
- What must be true for this game to be worth shipping
Because of that, they also carry the most painful decisions:
- What goes into the game now
- What gets a lower priority
- What is cut out of the experience entirely
If you do a Roadmap Clarity Check and see that someone else is making those calls, you’ve already found why your roadmap feels off.
Product Owner = “What Is Most Valuable Next?”
In Agile, the Product Owner is the person who:
- Defines value for the product
- Decides what to build next
- Decides what not to build
- Orders the backlog so limited time becomes maximum impact per sprint
On a game team, the only role truly qualified to answer “what is most valuable next for the player experience?” is the Game Designer / Creative Director.
If you hand the Product Owner title to someone else (often a producer or generic “product manager”), you create a split brain:
- Design: “This is what makes the game good.”
- “PO”: “This is what we’ll actually build.”
A quick Roadmap Clarity Check will usually surface this as conflicting priorities, constant rework, or “busy but nowhere” sprints.
What About Level Designers and Other Specialists?
There are important design subspecialties that do not function as Product Owner:
- Level designers
- Content designers
- Other content-focused specialists
Their work is crucial, but their primary job is content, not destination. They operate inside the box the Product Owner defines.
They answer:
“How do we bring this experience to life in this area?”
They do not answer:
“What experience are we building overall, and in what order?”
That top-level ownership must sit with one accountable role: your Game Designer / Creative Director as Product Owner.
How This Should Look in an Agile Game Studio
If you actually want Agile to help you ship, not just add ceremonies, structure it like this:
-
Game Designer / Creative Director = Product Owner
- Owns the backlog content and its order.
- Defines value in terms of the player experience.
-
Producers Own Capacity and Flow, Not Value
- Own estimation, capacity, and day‑to‑day flow.
- They surface tradeoffs; they don’t silently re‑prioritize.
-
Backlog Written in Player Terms
- Items describe what changes for the player when they’re done.
- Technical work still exists, but it’s traced back to a player-facing outcome.
-
Cuts and Deferrals Are Explicit
- The Game Designer / Product Owner calls what is cut or moved out.
- Those decisions are visible in the roadmdap, not hidden in tools.
If you walk through a Roadmap Clarity Check on your own project and see misalignment on any of these four points, you’ve found the gap.
Where the Roadmap Clarity Intensive Comes In
The Roadmap Clarity Intensive is designed for funded teams who run that Roadmap Clarity Check and realize:
- Their Game Designer is informally acting like a Product Owner, but
- The roadmap, backlog, and sprints don’t reflect that reality yet.
In the Roadmap Clarity Intensive, we plug into your live project for 4–6 weeks and:
- Treat your Game Designer / Creative Director as the true Product Owner
- Run a structured Roadmap Clarity Check across your goals, backlog, and current plan
- Rebuild a realistic, player-centered roadmap from your actual capacity and constraints
- Prove the plan in live sprints with your real team, not theory
The result: a roadmap your Designer believes in, your producers can run, and your stakeholders can trust.
If your internal Roadmap Clarity Check revealed that value and planning are living in different places, that’s exactly when the Roadmap Clarity Intensive pays for itself.
FAQ: Game Designer
Isn’t the producer supposed to be the Product Owner?
No. Producers should own capacity, flow, and risk (how much, how fast, how clean), not value. The Product Owner decides what is most valuable next for the player. In games, that’s the Game Designer / Creative Director, because they’re the ones actually shaping the experience.
Can one person be both Game Designer and Producer?
On a solo team (or sometimes 2–3 people), yes, one person is going to wear both hats out of necessity. But once you have a 4th or 5th person, those roles should not be the same person anymore.
In Agile terms, the Product Owner (Game Designer) and the Scrum Master (Producer) are designed to pull in opposite directions:
- The Product Owner’s job is to do what’s best for the product: maximize player value, push for the most impactful work, and protect the quality of the game.
- The Producer / Scrum Master’s job is to do what’s best for the team: protect sustainable pace, surface bottlenecks, and push back when the plan overloads people.
When one person holds both roles, there’s a built‑in conflict of interest. In practice, the game’s demands tend to win and the team loses: overcommitment, quiet crunch, and a roadmap that looks “committed” on paper but is carried on exhaustion.
So:
- 1 person: they’ll wear both hats. Just name when you’re speaking as PO vs as Producer so the team can see the tradeoff.
- 2–3 people: you’re still in “everyone does everything” land, but start separating the decisions.
- 4-5+ people: treat Game Designer (Product Owner) and Producer (Scrum Master) as distinct roles with distinct responsibilities, or your roadmap and your team health will both suffer.
What if we don’t have a dedicated Game Designer?
You still need a Product Owner. The title is less important than the function.
On any game project, someone has to take the mantle of PO:
- Listening to design, engineering, art, narrative, production, and business
- Weighing all those perspectives against the game’s goals and constraints
- Making the final call on what goes into the game, what waits, and what gets cut
That decision set cannot be a group vote every time. If you don’t have a dedicated Game Designer, explicitly assign Product Owner to the person who most consistently thinks about the player experience and the final game you’re trying to ship.
The key is clarity:
- Everyone should know who has the final say on “what’s most valuable next,”
- And that person must be accountable for the quality and coherence of the experience, not just “keeping everyone happy.”
Does this only matter if we use Scrum or “proper Agile”?
No. Frameworks are secondary. Whether you run Scrum, Kanban, or something home‑grown, you still need one accountable owner of value. The Game Designer as Product Owner is about decision rights, not ceremonies.
When should we run a Roadmap Clarity Check?
Run a Roadmap Clarity Check if any of this sounds familiar:
- Everyone is busy, but visible progress is thin.
- Deadlines keep “sliding right” with no clear decision.
- Design says one thing is critical, but the backlog shows another.
- Stakeholders ask, “Are we actually going to ship this?” and you don’t have a confident answer.
What if stakeholders disagree with the Game Designer’s priorities?
That’s normal. In the Intensive, we make the tradeoffs visible: constraints, goals, and player impact. Stakeholders still give input, but the Product Owner (Game Designer) owns the final call on what gets built next so the game doesn’t get pulled in five directions at once.
