Defining the player experience from idea to MVP through Content Design

Client:

Chess Hero

About Chess Hero

Chess Hero is the first dice chess mobile game, a highly popular offline chess variant with little to no online presence. The scope of the game is to introduce a wider audience to this traditional gameplay experience.

I joined the project at its earliest stage, when it was just an idea, and worked as the sole UX Writer and Content Designer throughout MVP development.

The team: product design, UX Writer/Content Designer, development, QA, game designer, and stakeholders

Duration: ~1 year

The challenge: Building the first mobile version of Chess Hero

Creating an MVP for a mobile game that had no digital benchmark introduced the challenge of making a complex, traditional offline game feel familiar to new players, while putting the company’s spin on it by adding a unique feature. This feature became the core of the gameplay.

We needed to:

  • define player flows from 0

  • bring clarity to unfamiliar game systems

  • reduce friction during onboarding and gameplay

  • define intuitive feature naming and terminology

  • support both guest users and registered players

  • establish scalable content foundations

At the MVP stage, every content decision shaped how the product works.

My ownership

As the only UX Writer, I owned the product’s content end-to-end, including:

  • login flows (guest + registered users)

  • gameplay guidance

  • rewards and quests

  • progression systems and leaderboards

  • rematch flows

  • shop

  • player profile logic

  • splash screen tips

  • settings

  • technical issue messaging (reconnection, connection loss, game updates)

  • end-of-season reward communication

  • Google Play Store description

  • feature naming and terminology systems

  • voice and tone

  • audience definition and communication principles

I also created and managed the full content approval workflow between product teams, design, the Head of Content, and final business stakeholders. This resulted in faster iteration, clearer ownership, and stronger consistency across the MVP.

Here's how I fixed it: Making content part of product design

One of the most important parts of my work was making sure content design was included in the product development from the ideation stage.

I actively pushed for content discussions to happen during feature definition through:

  • joining feature discussions

  • participating in Scrum ceremonies

  • working closely with Product and UI/UX Design

  • shaping flows before final UI decisions were made

  • creating naming conventions and content frameworks

This shift helped position content as part of the UX strategy, not filling the blanks in the UI elements.

A big product decision

One important example involved an in-game feature that risked disrupting the gameplay. Both the Product Designer and I strongly advised against its original form because it caused friction during active play. However, management initially wanted to keep it.

We approached this UX problem by:

  • testing how long the action actually took

  • identifying where frustration would happen

  • adjusting timing expectations for the player

  • restructuring messaging to encourage completing the action before gameplay

  • intentionally avoiding mentioning throughout previous screens the ability to perform the action during active gameplay. The only way a player would know about it was if they found themselves in that specific edge case

This reduced gameplay interruption while protecting the business goal.

Eventually, we were able to convince the team that the original implementation would likely create significant friction, we might lose active players, and receive negative reviews.

This is just one strong example of UX writing influencing product direction.

Content operations & approval workflow

Because I managed content across the full product lifecycle, consistency and review speed became a focal point, so I created a structured approval workflow to support:

iteration → review → approval → implementation → QA → stakeholder signoff

This included:

  • internal content review

  • Head of Content approval

  • design integration

  • in-app validation

  • final stakeholder approval

This process reduced ambiguity, improved collaboration across teams, and helped maintain content quality and consistency across a fast-moving MVP.

The outcome

  • stronger consistency across the entire product experience

  • clearer player guidance in complex flows

  • reduced ambiguity in gameplay and progression systems

  • improved alignment across design, product, and stakeholder teams

  • content integrated early into feature development

  • scalable content system for future development

  • faster content iteration through approval workflow

Several writing decisions became product decisions, especially around feature naming, player guidance, and flow simplification.

Reflections

Working on Chess Hero MVP taught me that UX writing is often product design with another hat. When you build from scratch, content decisions influence trust, motivation, usability, and long-term scalability.

I learned how to navigate constant iteration, changing priorities, and conflicting opinions while still protecting the player experience. It also taught me the importance of earning a seat at the table early.

Content is not the final layer added to a product. It should help define the product from the beginning.

Scope of work

Microcopy
Feature development
Content workflows
User journey
User flows
Voice & tone
Stakeholder management

I really enjoyed collaborating with Flavia. She is proactive and quick in her deliveries. Beyond content, what I valued most was her willingness to openly share her perspective and constructively challenge solutions, helping us simplify flows and make the product clearer for users.

fa7-solid

Janis Tilibs

Product Designer

I really enjoyed collaborating with Flavia. She is proactive and quick in her deliveries. Beyond content, what I valued most was her willingness to openly share her perspective and constructively challenge solutions, helping us simplify flows and make the product clearer for users.

fa7-solid

Janis Tilibs

Product Designer

© 2026 Flavia Sasu. All rights reserved.
© 2026 Flavia Sasu. All rights reserved.
© 2026 Flavia Sasu. All rights reserved.

Create a free website with Framer, the website builder loved by startups, designers and agencies.