Trust Is Predictability

This week we started with five players.

Then we added responsibilities, ownership, communication, support, goals, evidence, and backups.

Suddenly we were not just describing people anymore.

We were designing a team system.

The interesting part

Some of the most important roles are almost invisible when everything works.

Nobody says:

"Wow, the match result was submitted correctly."

Nobody celebrates:

"Amazing. Everyone knew exactly when practice started."

But remove those responsibilities and everybody notices.

This is true inside the game too. Sometimes the value of a role becomes easiest to understand when it disappears.

Reflection challenge

Choose one role from your Team Role Blueprint. Preferably choose one that does not look flashy.

Now remove it.

What happens?

Part 1: The role

State the role, what it owns, and who depends on it.

Part 2: The failure

Imagine the person stops performing that responsibility.

Be specific. What happens first? Then what happens next?

Model the chain.

ROLE FAILS
    ↓
FIRST EFFECT
    ↓
SECOND EFFECT
    ↓
TEAM CONSEQUENCE

Part 3: Trust

Now answer the harder question:

How does reliability in this role create trust?

Do not tell me "because teammates trust them." Explain the mechanism.

Maybe:

Because teammates can stop monitoring that responsibility and focus on their own jobs.

Now we are talking.

Reflection prompt

Write 150 to 200 words answering:

Which role in your Team Role Blueprint becomes most important when it fails, and how does reliable performance in that role create trust across the team?

Your response must include the role, its main responsibility, at least two other roles or responsibilities that depend on it, a failure chain, and an explanation of how predictability creates trust.

Example structure

Role: Tournament Result Reporter

Failure: The result is not submitted after the match.

Dependency: The tournament organizer cannot update standings. The team may have to resolve the missing result later.

Trust: When one person clearly owns reporting and completes it consistently, everyone else can focus on their own responsibilities without repeatedly checking whether the task was completed.

That is the level of reasoning I am looking for.

Alternative submission

With instructor approval, submit a 60 to 90 second recorded explanation using your Team Role Blueprint on screen.

Same evidence requirements.

Final check

Before submitting, check:

• Did I choose a specific role?
• Did I explain what it actually owns?
• Did I show a chain of consequences?
• Did I connect the role to other parts of the team?
• Did I explain trust through reliability and predictability?

If yes, you are done.

Week 03 complete

Week 01:

Esports is bigger than the game.

Week 02:

A team is shaped by its culture.

Week 03:

Trust grows when people can depend on the system around them.

Next comes a harder problem: a team can have clear roles, good culture, and a practice plan. Then competition starts. Pressure hits. Someone gets tilted. Everything changes.

So what happens when performance and emotion collide?