Your duo queue has been going great, so you invite three friends and call yourselves a team. Two weeks later, one player never shows up, two people want the same role, and every loss ends with five voices talking at once. Sound familiar?
Most amateur teams do not fall apart because of skill. They fall apart because nobody agreed on roles, time or how to talk. This guide covers those three pillars so your squad has a real shot at sticking together long enough to get good.
🤝 Who should you invite in the first place?
Picking teammates is the most important decision you will make, and it is usually made in five minutes over chat. Slow down.
Look for people who match on commitment level, not just rank. A player two divisions lower who shows up every practice is worth more than a star who disappears for a week. Ask everyone directly what they want: casual fun, climbing together, or entering tournaments. Mixed goals cause friction later.
Also consider attitude after a loss. Play a few casual sessions before making anything official. Watch who blames, who goes quiet and who says "okay, what do we fix?" That last person is gold.
Finally, try to bring in one substitute from day one. Real life will pull someone away eventually, and a sub keeps the team practicing instead of cancelling.
Questions to ask before anyone joins
A short conversation up front saves weeks of awkwardness later. Ask every potential teammate the same questions so nobody feels singled out:
- Which nights can you reliably play, and for how long?
- What do you want from this team in the next three months?
- Which roles or characters are you comfortable with right now?
- How do you prefer to receive criticism: in the moment, after the match, or privately?
- Are you open to trying a second role if the team needs it?
There are no wrong answers. You are checking for fit. A player who can only play on weekends is not a bad teammate, but they may not suit a team that wants to practice four nights a week. Being honest about this now is kinder than kicking someone later.
Age and location matter too. A big spread of time zones makes scheduling painful, and teams with younger players need to respect school nights and family rules.
🎭 How do you split roles without fights?
Every team game has jobs that need to be done, whether the game calls them roles, positions or classes. Even in games without strict roles, someone has to make calls and someone has to take the first fight.
Think about roles in two layers: in-game roles and team roles.
| Layer | Examples | What it covers |
|---|---|---|
| In-game | Entry, support, flex, tank, healer, jungle | What each player does inside a match |
| Team | Captain, shot-caller, scheduler, reviewer | How the group runs outside the match |
In-game roles
Start by letting each player list their top two preferred roles. Overlap is normal. When two people want the same spot, test both in scrims for a set period, then decide together based on results and comfort, not on who argues louder.
Players who can cover two positions are valuable. Encourage everyone to have a backup role, so a missing teammate does not wreck your whole lineup.
Team roles
The shot-caller makes the final call during rounds. This does not have to be the best mechanical player. It should be the person who stays calm and sees the big picture.
The captain handles the team outside the game: deciding on scrims, settling disagreements and talking to tournament admins. Sometimes the captain and shot-caller are the same person, but splitting the load helps.
The scheduler keeps the calendar updated and reminds people about sessions. The reviewer picks clips for review sessions. Small teams can combine these, but writing down who owns each job prevents the classic "I thought you were doing it."
📅 What does a realistic practice schedule look like?
Amateur players have school, jobs and families. A schedule that ignores that will collapse fast. Aim for consistency over volume.
A sustainable weekly structure for many amateur teams:
- Two team practice sessions of about two hours each, on fixed days.
- One scrim or match night against another team.
- One short review session, 30 to 45 minutes, watching clips from the week.
- Solo time that each player handles on their own, like aim training or ranked.
Use a shared calendar that everyone can see, and agree on a rule for absences, such as letting the team know at least a day ahead. Rotating practice times can be useful if teammates are in different time zones, but changing the schedule every week usually leads to empty voice channels.
Tip: Start every practice with a single, specific goal written in your team chat, like "trade kills within three seconds" or "call enemy positions with a landmark." One goal per session is easier to remember than a long list.
Planning a practice session
A two-hour block works better with structure. Here is one way to divide it:
- 10 minutes: warm-up and the session goal.
- 60 to 80 minutes: focused drills, custom games or scrims.
- 15 minutes: quick reflection, one thing that worked and one to fix.
- Remaining time: free play or unranked games to relax.
🎧 How do you keep voice comms useful?
Comms are where amateur teams lose the most rounds without realizing it. Too much talking buries the important information. Too little leaves teammates guessing.
Good comms are short, specific and calm. Compare these two calls:
- "There's a guy, he's like, somewhere over there, I think he's low!"
- "One at stairs, low."
The second takes a second to say and gives location plus health. Build a shared vocabulary for map spots and use it every time. If your game has standard callout names, learn those; if not, agree on your own and keep a note in your team channel.
Rules many teams adopt
- Dead players stay quiet unless they have information that changes the play.
- One voice leads during key moments, usually the shot-caller.
- No blame during the match. Save feedback for the review.
- Positive resets between rounds, like "next one, we've got this," keep heads up.
Comms change depending on the moment
Early in a round or match, comms are usually about plans: where to go, who takes which space, what to buy or pick. In the middle of a fight, comms should shrink to pure information. After a fight, they shift to status: who is alive, who needs healing, what cooldowns are gone. Teams that talk the same way at all three moments either talk too much during fights or too little before them.
Practice this on purpose. In one session, have the shot-caller say a short plan before every round and ask everyone else to keep fight comms to three words or fewer. It feels stiff at first, then becomes natural.
If arguments keep happening, try a rule where each player can only say one critical thing per match and must pair it with a solution. It sounds silly, but it forces constructive feedback.
🔍 How do you handle conflict and feedback?
Disagreements are normal. Silence is the bigger danger, because frustration builds until someone just leaves.
Hold a quick check-in once a week where each player can raise anything bothering them. Keep it focused on behavior and specific moments: "In round eight, I didn't hear a call before you pushed" is useful. "You always throw" is not.
When feedback goes to a single player, deliver it privately first. Public criticism in team chat tends to make people defensive.
Write down your team rules in a pinned message: attendance expectations, how decisions get made, and what happens if someone repeatedly breaks the rules. Having it in writing makes hard conversations less personal.
🛡️ What tools and safety habits should every amateur team use?
You do not need paid software to run a solid team. Most amateur squads run on a few free tools:
- A voice and chat server with separate channels for strategy, scheduling and clips.
- A shared calendar for practices and matches.
- A shared document for strategies, callouts and team rules.
- Built-in replay or clip tools in your game or system for review.
Keep the setup lean. Every extra app is one more place where messages get lost. If your team already lives in one chat server, put the calendar link, the strategy document and the rules there too, pinned at the top of the right channel. New players and subs can then find everything without asking the same questions again.
Keep your team safe as well. Turn on two-factor authentication on game and chat accounts. Never share account logins inside the team, even "just to boost" someone, since that can violate game rules and put accounts at risk. If your team includes minors, keep communication in group channels and involve parents for anything related to travel or money.
🏁 Keep it simple and keep showing up
A great amateur team is built on boring basics: the right people, clear jobs, a schedule everyone can keep, and comms that help instead of hurt. None of these require a big budget or a high rank.
Pick one area to fix this week. Maybe it is naming a shot-caller, or setting fixed practice days. Small improvements stack up, and teams that stay together long enough almost always get better.
❓ Frequently Asked Questions
How many players should an amateur team have?
Aim for the starting lineup your game requires plus at least one substitute. A sub covers absences and keeps practice going. Very large rosters can create tension over playing time, so do not overload it.
Does the best player have to be the captain?
No. The captain should be organized and fair, and the shot-caller should stay calm under pressure. Those traits do not always come with the best aim.
How often should an amateur team practice?
Two or three focused sessions per week is a good start for most groups. Consistency matters more than marathon sessions. Adjust once you see what everyone can sustain.
What if one player keeps missing practice?
Talk privately first and ask what is going on, because there may be a real-life reason. If the issue continues, apply the rules your team agreed on in writing. That is exactly why a written attendance rule helps.