Week 09 · lesson

Roles Beyond the Player

An esports team is not only the people holding controllers.

That sentence matters because school esports fails when every job gets treated as player support. A real organization needs competitors, analysts, coaches, broadcasters, bracket staff, moderators, designers, equipment managers, and people who can keep a schedule from turning into fog.

The goal this week is to build a team operating agreement. Lesson 1 starts with roles.

Role clarity is a system

A useful role description has four parts.

PartQuestion it answersWeak version
ResponsibilityWhat work does this role own?Help the team
AuthorityWhat can this role decide?Whatever is needed
HandoffWho receives the result?Everyone somehow
LimitWhat is outside the role?Anything not done yet

If a role has no authority, the person cannot act. If a role has no limit, the person becomes responsible for everything. That is how teams create resentment and missed work.

Worked example: analyst and captain

Scenario:

The team loses two objective rounds. The captain says the team needs better comms. The analyst says the real issue is arriving late to the objective.

Those roles see different evidence.

The captain may own in-match decision flow. The analyst may own review evidence after the match. The answer is not to let one role erase the other. The team needs a handoff.

RoleOwnsHandoff
Captainimmediate call during the roundtells analyst which decision moment to review
Analystevidence after the roundgives captain one specific pattern and recommendation

Now the disagreement becomes useful. The captain acts during pressure. The analyst improves the next plan.

Misconception: non-player roles are lesser roles

That is wrong. A broadcast director can save an event. A moderator can prevent a chat problem from becoming a school problem. A bracket admin can keep a tournament fair. An analyst can find the pattern the players missed.

Player skill matters. It is not the whole organization.

Build a role charter

Choose four roles for a school esports team or event. For each role, write:

  • responsibility;
  • authority;
  • handoff;
  • limit;
  • one evidence artifact the role produces.

Check your understanding

What makes a role usable?

A role is usable when the person knows what they own, what they can decide, who receives the work, and where the role stops.

Why do handoffs matter?

Because most team failures happen between roles, not inside the job description.

Success criteria

Your role charter is ready when another student can step into the role and know what to do without you explaining the missing parts.

process flow

Week 9: Evidence to Improvement

  1. Observe

    Read the supplied scenario or record.

  2. Interpret

    Separate evidence from assumption.

  3. Practice

    Use a team artifact.

  4. Apply

    Make one reasoned choice.

  5. Review

    Record an inclusive improvement.

Read this concept flow as plain text
  1. Observe. Read the supplied scenario or record.
  2. Interpret. Separate evidence from assumption.
  3. Practice. Use a team artifact.
  4. Apply. Make one reasoned choice.
  5. Review. Record an inclusive improvement.