UX Design
UX governance
Nov 16, 2026
AI is making prototyping accessible to everyone. Discover how UX governance can evolve from controlling design output to enabling teams through shared product context and foundations.
Everyone Can Prototype Now. What Does That Mean for UX Governance?
Not long ago, creating an interactive prototype required a certain level of design or development knowledge.
Today, things are changing.
Game designers can build functional feature concepts. Producers can visualise their ideas. Developers can demonstrate technical possibilities. Designers can explore multiple directions without spending days preparing every variation.
AI is making prototyping more accessible than ever.
And I think this is a positive development.
More people can contribute to exploring ideas, challenging assumptions and shaping the product.
But it also raises an important question:
If everyone can prototype, how do we maintain a coherent player experience?
I don't think the answer is to restrict who can create prototypes.
I think the answer is to rethink the role of UX governance.
Prototyping is no longer exclusive to designers
In many game development teams, stakeholders already create their own representations of feature ideas.
Sometimes it's a quick wireframe. Sometimes it's a Figma concept, a functional prototype or a collection of references.
These experiments can be extremely useful.
They help communicate ideas that are difficult to explain through written specifications alone. They make assumptions visible and give teams something tangible to discuss.
AI makes this even easier.
People who previously relied on designers or developers to visualise their ideas can now explore them independently.
But there is a difference between creating a prototype and designing a coherent player experience.
A prototype usually represents one interpretation of a problem.
It doesn't necessarily account for the entire product, existing interaction patterns, gameplay context or the relationships between different features.
And when every stakeholder creates their own interpretation independently, the team can end up with multiple versions of what the same game should feel and behave like.
The problem with traditional UX governance
UX governance is often associated with maintaining design systems, reviewing interfaces and ensuring that teams follow established guidelines.
These activities are important.
But they don't necessarily address how experience decisions are made across the entire development process.
Consider a common situation.
A feature owner creates a prototype to communicate an idea. A developer creates another version to explore technical feasibility. A UX designer proposes a different interaction model.
All three are trying to solve the same problem, but they are working from different assumptions.
UX is then expected to review the alternatives, identify inconsistencies and bring everything together.
Sometimes this happens early enough to influence the direction. Sometimes the important decisions have already been made.
This creates an uncomfortable situation.
UX becomes responsible for the coherence of the player experience without necessarily having the context or opportunity to influence how that experience is initially shaped.
The wrong response: More control
One possible reaction is to introduce more restrictions.
Require UX approval before stakeholders can create prototypes. Limit who can modify design files. Introduce additional review steps and approval processes.
But I think this approach misses the opportunity.
If more people can contribute to product exploration, restricting that capability could slow down collaboration and discourage experimentation.
The goal shouldn't be to make UX the gatekeeper of every prototype.
The goal should be to make UX the enabler of better prototyping.
Start with a shared foundation
Imagine that instead of asking every stakeholder to start from scratch, we provide them with an interactive foundation that reflects the actual game.
It contains more than reusable UI components.
It includes:
Product context: relevant game mechanics, systems, features and player goals.
Design foundations: typography, colours, spacing, components and visual principles.
UX patterns: established solutions for navigation, progression, feedback and interaction.
Behaviour: how interfaces respond to player actions and different gameplay states.
Interactive prototypes: representations of the game that stakeholders can explore and build upon.
Now, when someone wants to communicate a feature idea, they don't have to create an isolated interpretation.
They can start with something that already reflects the product.
They can reuse established patterns, explore alternative layouts, challenge existing interactions and propose changes within a shared context.
This doesn't eliminate different interpretations.
It makes them easier to compare.
One core. Multiple explorations.
I see this as a model of controlled freedom.
The idea is simple: maintain one governed core while allowing people to create independent explorations around it.
There are three important parts.
1. The governed core
This is the shared foundation maintained by UX.
It represents the current agreed product direction, established design foundations, interaction patterns and relevant product context.
It shouldn't be treated as an untouchable final product. It evolves as the game evolves.
2. Exploration branches
Stakeholders can create their own interpretations of a feature without immediately changing the shared foundation.
A game designer might explore a different progression model. A developer might demonstrate an alternative interaction. A producer might propose a more compact experience that better fits production constraints.
These explorations can be compared without fragmenting the core.
3. Validated decisions
When the team agrees on a direction, the validated changes are integrated back into the shared foundation.
The result becomes part of the product knowledge available to everyone.
This creates a continuous relationship between exploration, decision-making and UX governance.
It also helps prevent another problem: ending up with dozens of disconnected prototypes that nobody knows how to maintain.
The emerging role of the UX Governor
This brings me to a broader question about the future of UX/UI design.
What happens when designers are no longer the only people capable of creating interfaces and prototypes?
I believe the value of UX leadership will increasingly shift towards maintaining the coherence of the experience rather than owning every design output.
I've been thinking about this through the concept of a UX Governor.
It's a proposed way of describing an evolving responsibility, not necessarily a new job title every studio needs to introduce.
The UX Governor acts as a steward of the player experience.
The responsibilities could include:
Direction: establishing and maintaining the intended experience and UX principles.
Context: making product knowledge, mechanics and interaction patterns accessible.
Enablement: providing foundations that allow different disciplines to explore ideas.
Facilitation: helping stakeholders compare alternatives and reach informed decisions.
Governance: ensuring validated changes contribute to a coherent product experience.
This isn't about giving UX unilateral authority over game design.
Game designers remain responsible for mechanics and feature intent. Developers understand technical possibilities. Producers balance scope, resources and delivery.
UX helps connect these perspectives through the lens of the player experience.
The role is not to prevent people from making decisions.
It's to help the team make better decisions together.
Design Harness: The environment that makes it possible
This is where the concept of a Design Harness comes together.
A Design Harness is a shared, interactive environment that allows teams to explore, communicate, challenge and validate product experiences while maintaining a consistent UX direction.
It builds upon design systems but connects them with product knowledge, UX patterns, interaction behaviour and interactive prototypes.
It provides the foundation for stakeholders to express their ideas and explore different solutions without starting from disconnected references.
AI can make this environment even more powerful.
It can help people navigate product knowledge, generate variations using established patterns, identify inconsistencies and document decisions.
But the important part isn't the AI itself.
It's the shared environment and the way people work together within it.
Stop controlling prototypes. Start enabling experiences.
I don't believe the future of UX governance is about controlling who can create interfaces or deciding who is allowed to experiment.
As prototyping becomes more accessible, trying to own every output becomes increasingly unrealistic.
Instead, UX leadership has an opportunity to establish the foundation that makes collaboration more productive.
Give people the context. Give them the tools. Let them explore.
And make sure that the valuable outcomes contribute to a coherent player experience.
When everyone can prototype, the value of UX isn't in owning the tools or controlling the output. It's in creating the foundation that allows everyone to contribute to a better player experience.