Project: Creator Continuum Arena™

Project Overview

A gaming tournament can be more than a bracket.

It can create opportunities for players, streamers, creators, game communities, developers, partners, and the organization hosting it.

 

That idea became the foundation for Creator Continuum Arena™.

 

I created Arena as the gaming and competitive-events division of Creator Continuum™, designed to bring together competitive play, creator participation, community engagement, livestreaming, player experience, partnerships, and measurable event programming.

​

Rather than approaching tournaments as isolated events, I began designing Arena as a repeatable system. That meant thinking beyond:

 

Who plays whom?

 

and asking:

 

• How do players enter the experience?

• How does staff operate it?

• How do creators participate?

• How do teams communicate?

• What should we measure?

• What value can the event create beyond determining a winner?

 

My work has included developing Arena's operating model, staffing structure, tournament workflows, player journey, registration and check-in processes, creator-streaming requirements, community outreach, broadcast planning, sponsor-readiness strategy, measurement frameworks, and early digital systems.

 

The Challenge

Gaming communities frequently run tournaments through a combination of Discord messages, spreadsheets, direct messages, manually maintained rosters, and last-minute coordination. That can work for a small event. It becomes much harder when the event involves:

• multiple teams

• dozens of players

• streamers

• tournament staff

• schedules

• check-in

• match communication

• result reporting

• broadcasts

• community promotion

• sponsors

• post-event measurement

 

I wanted Creator Continuum Arena™ to be built around the complete participant experience, not only the bracket.

 

The challenge became:

How do you create a competitive gaming program that is organized enough for staff to operate, enjoyable enough for players to return, valuable enough for creators to participate in, and measurable enough to improve and eventually monetize?
 

Project Objectives

The initial objectives were to:

• Create a dedicated gaming and competitive-events division within Creator Continuum™.

• Build a repeatable tournament operating model.

• Design a clear player journey from registration through final results.

• Establish Arena-specific leadership and staff responsibilities.

• Create structured registration, roster, check-in, communication, and reporting processes.

• Integrate streamers and creators directly into Arena programming.

• Build relationships with gaming communities, teams, developers, and potential partners.

• Create opportunities for Creator Continuum creators through gaming events.

• Develop systems that can eventually reduce manual tournament administration.

• Collect meaningful participation, creator, audience, and operational data.

• Use early tournaments as pilots before determining the long-term paid Arena model.

• Build evidence that can eventually support sponsorship and partnership conversations.

 

My Role

As Founder & Creative Community Director, I created the Arena concept and have led its strategy and development within the larger Creator Continuum ecosystem.

• My Arena work includes:

• Division Strategy

• Tournament Program Design

• Player Experience

• Tournament Operations

• Staffing Architecture

• Role & Responsibility Design

• Team Recruitment

• Gaming Community Outreach

• Creator & Streamer Activations

• Registration Strategy

• Player Journey Design

• Check-In Systems

• Match Communication

• Roster Management

• Broadcast Planning

• Event Documentation

• Product & Systems Strategy

• Web Prototyping

• Partnership Development

• Sponsorship Strategy

• Measurement Frameworks

• Pilot Evaluation

• Business Validation

• My role is not simply to organize individual tournaments.

 

I am building the operating system around Arena so the division can eventually support repeat competitive programming.

 

Positioning Arena With Creator Continuum™

One of the first strategic decisions was determining what Arena should actually be.

I did not want gaming to become disconnected from Creator Continuum's broader creator-development mission.

 

Arena therefore functions as:

• A Competitive Gaming Program

  • Players and teams participate in organized tournaments and events.

• A Creator Activation Platform

  • Streamers and other gaming creators can participate in and create content around Arena events.

• A Community-Building Tool

  • Gaming communities and teams can connect through structured competition.

• A Creator Continuum Opportunity Engine

  • Arena can create work and collaboration opportunities involving streamers, designers, artists, broadcasters, moderators, developers, and other creators.

• A Partnership Platform

  • Game developers, publishers, gaming communities, and sponsors can potentially participate through tournaments, playtests, promotions, creator activations, and event support.

 

This keeps Arena connected to the larger Creator Continuum ecosystem rather than operating as an unrelated esports brand.

 

Player Experience Design

A major part of the Arena model is designing what happens from the player's perspective.

I mapped the tournament journey as:

Registration → Confirmation → Check-In → Match Instructions → Competition → Result Reporting → Bracket Progression → Final Results → Feedback

Each stage creates different operational needs.

 

Players need to understand:

• what they are registering for

• who is on their team

• when registration closes

• when they need to check in

• where communication happens

• what platform or region requirements apply

• when their match begins

• how match instructions are received

• how results are reported

• what happens if something changes

• where final standings are communicated

​​

Designing the entire journey made it possible to identify where staff processes, documentation, communication, and technology were needed.

​

Tournament Operations

I developed Arena tournament workflows around the major operational stages of an event.

 

Before the Tournament

Arena needs systems for:

• event rules

• team recruitment

• registration

• player rosters

• platform information

• region and time-zone information

• designated team contacts

• streamer information

• registration deadlines

• check-in procedures

• staff assignments

• communication routes

• broadcast preparation

• event promotion

During the Tournament

Staff need processes for:

• attendance confirmation

• player check-in

• match assignments

• lobby setup

• schedule communication

• result reporting

• bracket progression

• rule enforcement

• player questions

• technical issues

• streamer activity

• broadcast coordination

• and event documentation

 

After the Tournament

Arena needs to capture:

• final results

• participation

• player completion

• creator participation

• streaming activity

• audience activity

• community conversion

• feedback

• staff observations

• operational issues

• lessons for the next event

 

This three-stage model became the basis for Arena's operating documentation and event-validation system.

 

Staffing & Leadership Architecture

Running competitive events requires clear ownership. I developed Arena-specific leadership and staff functions around areas such as:

Tournament Operations

Responsible for the systems required to execute the competition.

​

Teams & Player Experience

Focused on participant communication, team relationships, registration, readiness, and player experience.

​

Event Support

Supporting moderation, match operations, communications, results, and other event needs.

 

I also designed how Arena staff communicate with the broader Creator Continuum leadership structure.

The goal was to avoid a tournament where everyone is helping but nobody knows who actually owns each responsibility.

 

Creator & Streamer Participation

Arena was intentionally designed to involve creators rather than treating streaming as an optional activity happening around the tournament.

​

For the planned October 3, 2026 Paladins tournament, the current structure includes:

• 8 teams × 5 players = 40 participants

• Each team must designate 2 members to stream their participation, creating a minimum of:

• 8 teams × 2 designated streamers = 16 designated tournament streamers

  • This creates a creator layer around the competitive event.

  • Instead of relying entirely on one central broadcast, Arena can potentially generate multiple simultaneous creator perspectives and additional audience touchpoints.

 

It also gives Creator Continuum a way to evaluate:

• streamer participation

• creator activation

• audience reach

• community engagement

• whether tournament participation leads creators into the larger ecosystem

 

The October tournament has not occurred yet, so these figures describe the planned event structure rather than completed results.

​

Arena as a Creator Activation Platform

The streamer model also reflects a broader Arena strategy.

A gaming event can create opportunities for:

• streamers

• casters

• graphic designers

• video editors

• social content creators

• tournament staff

• community managers

• game developers

• potentially musicians or artists contributing to event presentation

 

This allows Arena to function as more than a player-only program.

It becomes another way for different parts of the Creator Continuum ecosystem to participate in a shared project.

​

Registration & Player Systems

As Arena operations developed, registration became one of the clearest areas where technology could improve the experience.

Tournament registration requires structured information around:

• teams

• players

• rosters

• platforms

• regions

• schedules

• communication

• streamer participation

• event readiness

 

I therefore designed and began prototyping the Creator Continuum Arena Player Registration System.

The prototype translates tournament operations into a structured digital experience intended to support the player journey beyond a simple form submission.

 

Development began using:

• Next.js

• GitHub

• Node.js / npm workflow

 

The Registration System has its own dedicated WorkByTahne case study covering the product and UX work in greater detail.

​

Community & Team Recruitment

Arena also requires an audience of actual competitors.

I developed outreach and recruitment approaches involving:

• gaming communities

• competitive teams

• individual players

• streamers

• community leaders

• game-specific Discord communities

• potential creator participants

 

This work involves more than promoting an event flyer.

The outreach needs to answer:

• Why should this community participate?

• What kind of experience is Arena trying to provide?

• What does a team need to do?

• What opportunities exist for creators?

• What makes the tournament credible?

• What happens after someone joins?

 

Building those answers became part of Arena's community-development strategy.

 

Game-Developer & Industry Relationships

Arena also creates a natural pathway for Creator Continuum to develop relationships with game developers and publishers.

Potential Arena relationships can include:

• community tournaments

• playtests

• feedback events

• creator activations

• game showcases

• promotional events

• community engagement

• and developer/creator connections

 

This connects directly to Creator Continuum's broader value proposition.

 

A developer entering the ecosystem may potentially connect not only with players, but also with:

• streamers

• testers

• artists

• musicians

• designers

• other creators

 

Arena provides an organized gaming environment where some of those relationships can become actionable.

​

Partnerships & Sponsorships Strategy

I also began developing Arena's sponsor and partnership foundation before trying to sell large sponsorship packages.

 

That work includes:

• identifying potential sponsor categories

• researching potential partners

• developing sponsor benefits

• creating outreach messaging

• developing event activation concepts

• preparing support materials

• tracking outreach

• defining which metrics future sponsors would reasonably want to see

 

One important strategic decision was not to rely on sponsorship claims before Arena had evidence. The early tournaments are therefore also designed to generate the information necessary for stronger future conversations.

 

Sponsor-Ready Measurement

I developed measurement frameworks around areas such as:

 

Participation

Number of teams, players, completed registrations, check-ins, and event completion.

 

Creator Activation

Number of participating streamers and whether designated creators actually streamed.

 

Audience

Central broadcast activity where applicable, creator-stream activity, engagement, and potential reach.

​

Community Conversion

New Creator Continuum participants or Discord joins connected to the event.

 

Operations

Check-in performance, delays, match issues, staff workload, communication problems, and overall event completion.

 

Player Experience

Participant feedback and areas for improvement.

​

Creator Outcomes

Whether creators gained meaningful content or engagement opportunities through participation.

 

These measurements are designed to produce evidence rather than vanity metrics.

 

Tournament Business Validation

Arena is currently being developed through a validation-first model. The goal of the first tournaments is not simply to generate revenue.

They are designed to test questions such as:

• Can Arena successfully recruit teams?

• Will registered teams actually show up?

• Will designated streamers participate as planned?

• Can staff run the tournament effectively?

• What breaks operationally?

• Do players want to participate again?

• Does the event generate meaningful audience activity?

• Does Arena bring new people into Creator Continuum?

• What value do creators receive?

• What would sponsors actually be supporting?

• Is there enough demonstrated demand to eventually charge for participation?

 

This approach allows future Arena monetization decisions to be based on observed behavior.

FREE PILOT → PAID MODEL

 

The early Arena strategy is intentionally structured around proving the experience before charging players.

The current progression is:

 

Free Tournament Pilot

Test participation, operations, player experience, creator activation, and measurement.

↓

Repeat Tournament

Determine whether the system can operate consistently and whether communities return.

↓

Evaluate Evidence

Review demand, operational performance, participant feedback, audience behavior, and willingness to continue.

↓

Paid Tournament Pilot

​If the evidence supports it, test a paid participation model. This reduces the risk of charging for an experience before the operating system has been validated.

​

Event Validation Framework

For the planned Paladins tournament, I developed a structured validation plan spanning before, during, and after the event.

 

Before

Capture:

• team registration

• player rosters

• designated streamers

• creator channel information

• registration timing

• existing vs. new Creator Continuum participants

• rules readiness

• broadcast planning

​

During

Track:

• attendance

• event completion

• streamer participation

• broadcast activity where available

• operational issues

• highlight opportunities

After

Evaluate:

• final results

• creator participation

• community conversion

• audience activity

• staff observations

• player feedback

• opportunities for improvement

This transforms the event from a one-time activity into a business and program learning tool.

 

Operational Documentation

I have also developed or directed documentation supporting Arena operations, including:

• tournament operations guides

• event checklists

• player workflows

• registration requirements

• staffing responsibilities

• communication processes

• event validation plans

• sponsor measurement frameworks

• team participation requirements

• streamer participation requirements

• broadcast planning

• post-event evaluation

• registration-system requirements

The objective is to reduce dependence on information existing only in the Founder's head.

 

Selected Arena Work & Deliverables

• Division Strategy

• Creator Continuum Arena™ operating concept

• Arena positioning within Creator Continuum

• Gaming/community opportunity model

• Creator activation strategy

• Organizational Design

• Arena leadership structure

• Tournament operations roles

• Player-experience responsibilities

• Staff workflows

• Event responsibilities

• Tournament Operations

• Registration workflow

• Team roster structure

• Check-in process

• Match communication

• Results reporting

• Bracket progression

• Event readiness planning

• Player Experience

• Participant journey

• Communication routes

• Team readiness

• Tournament instructions

• Feedback strategy

• Creator Activation

• Designated streamer model

• Creator participation requirements

• Broadcast planning

• Content/highlight strategy

• Technology

• Arena Player Registration System concept

• Player/user-flow mapping

• Next.js prototype development

• GitHub development workflow

• Growth & Partnerships

• Gaming community outreach

• Team recruitment

• Developer outreach

• Partnership positioning

• Sponsor strategy

• Activation concepts

• Measurement

• Arena validation plan

• Participation metrics

• Streaming metrics

• Audience metrics

• Community conversion

• Staff evaluation

• Sponsor-ready measurement framework

 

Current Outcome

Creator Continuum Arena™ is still in its foundation and pilot stage. I do not present future tournament participation, streaming activity, audience reach, sponsor value, or revenue as achieved results before the events occur. The most significant result so far is the operational infrastructure that now exists.

Arena has progressed from an idea for gaming events into a structured division with:

• defined positioning

• staffing architecture

• tournament workflows

• player experience systems

• registration processes

• creator participation models

• streaming requirements

• community recruitment strategy

• developer outreach

• partnership strategy

• measurement frameworks

• business-validation criteria

• early product development

The next major step is testing those systems through live tournaments and using actual event data to determine how Arena should evolve.

​

What this Project Demonstrates
Gaming Program Strategy

Designing competitive gaming as a repeatable program rather than a series of disconnected events.

​

Player Experience

Mapping the complete participant journey and designing operations around what players need at each stage.

 

Tournament Operations

Creating systems for registration, teams, check-in, communication, matches, results, and event evaluation.

​

Organizational Design

Defining Arena leadership, responsibilities, staffing, and internal workflows.

 

Creator Program Development

Integrating streamers and creators directly into competitive programming.

 

Community Development

Recruiting gaming communities, teams, players, and creators into an emerging program.

 

Product & Systems Thinking

Identifying tournament processes that can move from manual administration into structured digital tools.

 

Partnership Strategy

Developing opportunities for game developers, communities, sponsors, creators, and other external partners.

 

Measurement & Validation

Designing tournaments to generate evidence about participation, audience behavior, creator activation, operational performance, and program value.

​

Business Model Strategy

Testing Arena's value through free pilots before committing to a paid tournament model.

​

Founder Leadership

Building a new division from concept through organizational structure, systems, partnerships, technology, and live-event preparation.

​

The Bigger Picture

Creator Continuum Arena™ began with competitive gaming, but the larger opportunity is what can be built around that competition.

 

A tournament can connect:

• players

• with streamers

• with communities

• with creators

• with developers

• with partners

• ultimately with the broader Creator Continuum™ ecosystem

That is what I am designing Arena to become. Not simply a place to run brackets.

A structured gaming environment where competition can create community, content, collaboration, data, relationships, and opportunity.

 

Play. Create. Compete. Together.
 

CREATOR CONTINUUM ARENA™

Gaming Strategy • Player Experience • Tournament Operations • Creator Activations • Community Development • Program Evaluation