Team Building Project

We have spent five weeks pulling esports teams apart.

Culture.

Communication.

Roles.

Trust.

Health.

Practice.

Feedback.

Accountability.

Now comes the real question:

Can you actually use any of it?

Knowing that communication matters is easy. Knowing that teams need trust is easy. Putting five people in a room and creating a routine that makes those things more likely is a different problem.

Team building should solve a real problem

Team building is not automatically pizza, matching shirts, or an icebreaker.

Those things can be fine, but a team-building routine becomes more useful when we ask:

What problem are we trying to solve?

Maybe the problem is:

• new members do not know what to do
• practices start chaotically
• nobody checks roles before a match
• frustration carries into the next round
• feedback becomes personal
• communication disappears under pressure
• nobody reviews what happened after practice
• one person dominates every conversation

Now the team has something to design around.

A routine is a tiny system

Think about a pre-match check. It might take three minutes.

1. Confirm players.
2. Confirm roles.
3. Check equipment.
4. State one team focus.
5. Confirm final caller.

That is simple, but every step exists for a reason. Remove the role check and two people may assume different responsibilities. Remove the equipment check and a headset issue appears after the match starts. Remove the team focus and practice may drift back into random play.

Small routines can prevent larger problems.

Inclusive by design

Your routine has to work for more than the loudest player, the most experienced person, or the people who already know each other.

A scholastic esports program may include experienced players, beginners, quiet students, highly social students, students still learning the game, students in different team roles, and people who communicate differently.

So we ask:

Can everyone understand how to participate?

Not:

Does everyone behave exactly the same?

Those are different questions.

Lesson 1: Building an Inclusive Team Routine

You will choose a real team problem and design a short routine around it.

Possible routine types:

• pre-practice setup
• new-player onboarding
• pre-match check
• communication reset
• post-match debrief
• feedback routine
• role-confirmation routine
• tilt/reset routine

The rule: every step needs a reason.

Lesson 2: Testing a Team-Building Choice

Then we try to break your routine.

What happens when someone is absent, a new player joins, people are rushed, somebody misunderstands, two people disagree, the team is losing, or nobody remembers the steps?

If the routine only works on a perfect day, it is not ready.

Lesson 3: Team Building Project

Your group turns the routine into a prototype that another team could actually understand and use.

Your project shows:

problem
  ↓
routine
  ↓
roles
  ↓
test
  ↓
evidence
  ↓
revision

Week 06 artifact: Team Routine Prototype

Your group will design one routine that could realistically be used by a school esports program.

It must include:

• the problem
• the routine
• roles and ownership
• inclusion and access supports
• stress test
• evidence
• revision
• retest

Learning targets

By the end of Week 06, you should be able to explain:

• why team-building should solve a real team problem
• how routines create predictable behavior
• why inclusion can be designed into processes
• why visible expectations help new or less-experienced participants
• how to assign ownership inside a team routine
• how to stress-test a team process
• how observation and evidence can improve a routine
• why revision is part of design rather than proof that the first idea failed

One idea to keep:

A good team does not just have good people. It has systems that help people succeed together.