SEED: Establishing the communication foundations for a complex interface

The problem

How do you design an understandable, adaptable interface for an ever-evolving massive multiplayer society simulation, while supporting players with very different interests and levels of engagement?

My role

  • UX designer working alongside a UI-focused designer who owned the design system.
  • Initiated and led the communication matrix: identified the need, proposed the approach, gathered requirements across teams and applied the findings to interface design.
  • Developed a separate approach to feature UX guidelines and deliverable definitions, coordinating both initiatives with the design-system work.

Context

  • Interconnected gameplay: SEED combined life simulation, a multiplayer economy, city building and social and political systems. Players could participate in all of them to varying degrees.
  • An evolving product: Teams were still defining features within the iteration we were designing for.
  • Limited screen space: The game world occupied most of the screen. The HUD needed to make information legible and accessible without overwhelming players.
  • An agreed direction: My colleague and I wanted an interface that could grow with the product while minimizing cognitive load, supported by a design system and a shared approach to UX/UI.

My approach

Identifying the missing foundation

As I considered how to structure the interface, I identified a gap: we lacked a shared overview of the information it would need to accommodate. Individual teams understood their own systems, but we needed to see the communication requirements across the product before defining the responsibilities of interface components.


I remembered the marketing communication matrix from my work on a loan-comparison website. I adapted the concept for SEED, designing a table to capture information sources, channels, priorities and purposes. I prepared the rationale, an approach to gathering the information and an effort estimate, then pitched the initiative to my PM and head of design.

Building the overview with the teams

Once approved, I identified people in each team who knew the systems they were building. Through informal conversations, I refined the table structure with them and collected the information needed to map the communication requirements. Contributors included game teams, marketing and legal.


The initiative was announced at a company meeting, and I shared the table across teams for review, comments and additions.

Keeping the design work aligned

Weekly check-ins with my PM kept progress visible. Daily coordination with my design colleague kept the matrix, design system and feature UX work aligned. The shared table also gave teams a view of their own communication requirements within the wider product.

The communication matrix

Solution overview

The Excel matrix focused on information reaching a player who was logged in but outside any particular task flow. This let us establish the communication the interface needed to accommodate before individual features and their flows were fully designed.

Channels included the HUD, mobile app, website, email and chat. The simulated world was itself a channel: players could learn from its visible behavior as well as from explicit UI.


I chose a practical level of detail. Messages with the same communication requirements could share an entry; distinct messages needed separate entries. For example, different kinds of danger to a Seedling could be grouped if they required the same treatment. We could revise those assumptions as features developed.


Priorities used shared reference points, including account suspension and potential fail states such as Seedling death. Other priorities were estimated with teams rather than treated as a formal scoring model.

What the matrix enabled

  • Persistent interface requirements: We could identify components, such as player chat, that needed space regardless of the active gameplay.
  • Communication across channels: We could decide what belonged in the game, mobile app, website or email, reducing what the HUD needed to carry.
  • Clearer component responsibilities: My colleague could design components with a better understanding of what information they would contain, what functions they needed to perform and how they fitted into the interface.

Summary

As I considered how to structure the interface, I identified a gap: we lacked a shared overview of the information it would need to accommodate. Individual teams understood their own systems, but we needed to see the communication requirements across the product before defining the responsibilities of interface components.


I remembered the marketing communication matrix from my work on a loan-comparison website. I adapted the concept for SEED, designing a table to capture information sources, channels, priorities and purposes. I prepared the rationale, an approach to gathering the information and an effort estimate, then pitched the initiative to my PM and head of design.