Explaining on 2 rounds how we managed to win entry kills and how we played the 5vs4 situation on T side , here I took an example from an official game on Mirage against the old roster from UNiTY
Explaining how I used the past rounds to build a a sort of routine and make a key round with that , here I took an example during an official game on Ancient against old roster from ARCRED
I'm sharing a strong strategy on Mirage T side when you want to change the rythm of the game , here I took an example in an official game against old roster from Phantom
WHY DO SO MANY NEW CS2 TEAMS FAIL? — DAY 10: THE STAR PLAYER PROBLEM
Your highest-rated player might actually be holding your team back.
Uncomfortable statement? Maybe.
But something I believe developing CS2 teams need to understand is that individual performance and individual impact aren't always the same thing.
We've become extremely comfortable evaluating players through ratings, ADR, K/D and highlight clips.
And while those statistics provide valuable information, they don't always tell us how a player contributes to winning rounds.
Let's take an example.
You have a rifler consistently putting up impressive numbers.
He's confident, mechanically gifted and regularly finishes at the top of the scoreboard.
But when you review his decisions, you notice something interesting.
He frequently abandons his responsibilities to look for engagements.
He takes unnecessary fights in advantageous situations.
He requires significant resources from teammates but doesn't consistently convert those advantages into round wins.
And when the team needs him to play a less rewarding position, his impact drops considerably.
Now ask yourself: Is he actually your most valuable player, or simply your most statistically impressive one?
This is where I believe many developing teams make a mistake.
They build systems around the player producing the biggest numbers without properly evaluating how those numbers are being generated.
For coaches:
Stop treating individual ratings as a complete performance evaluation.
Look at the context behind the statistics.
How often does a player's decision improve your probability of winning the round?
How much utility, space and support does that player require?
Are they converting advantages or creating unnecessary risks?
What happens to the team's structure when they pursue individual opportunities?
And perhaps most importantly:
Would you still consider this player exceptional if their statistics were average?
What would they contribute beyond the scoreboard?
For IGLs:
Don't confuse giving a talented player freedom with allowing them to ignore the team's tactical requirements.
Individual initiative is valuable when it creates opportunities.
It becomes a liability when four other players constantly have to compensate for unpredictable decisions.
Your job isn't to eliminate creativity.
It's to understand when that creativity benefits the team and when it introduces unnecessary risk.
For players:
Sometimes the correct decision won't improve your statistics.
Holding an angle without getting a kill.
Using your utility to enable someone else.
Giving up an opportunity for an individual duel to preserve a man advantage.
Or simply staying alive because your position prevents the opponent from exploiting an area of the map.
These decisions rarely make highlight reels.
But they can be essential to winning rounds.
And here's another uncomfortable truth:
A player who consistently produces good statistics while ignoring the team's needs isn't necessarily carrying the team. Sometimes the team is carrying the consequences of that player's decisions.
That doesn't mean every high-rated player is selfish or that statistics should be ignored.
Exceptional players often create enormous value through individual skill.
But performance needs to be evaluated in context.
The purpose of a competitive roster isn't to maximise five individual ratings. It's to maximise the team's ability to win.
So here's my question to upcoming coaches and IGLs:
Would you bench your highest-rated player if you believed their decision-making was consistently hurting the team?
Or would their statistics make you afraid to challenge them?
#CS2
This week I wrote about why #CS2 academies are dying and what @TeamVitalityCS got wrong.
Criticism is easy. So here's what I think needs to change, starting with the uncomfortable part. 🧵
WHY DO SO MANY NEW CS2 TEAMS FAIL? — DAY 9: COMMUNICATION UNDER PRESSURE
Some of the worst communication I've heard in Counter-Strike came from teams where nobody would stop talking.
Five players constantly providing information, reacting to situations and trying to help each other.
Yet somehow, important details were being missed.
Why?
Because communication isn't measured by how much you say. It's measured by how effectively information reaches the people who need it.
And in competitive CS2, timing can be just as important as accuracy.
Think about a 3v3 post-plant.
One player is holding the smoke, another is watching the flank, and the third is preparing utility for the retake.
Suddenly, everyone starts talking.
One player is explaining how he died. Another is speculating about enemy positions. Someone else is suggesting what everyone should do.
Meanwhile, the player preparing the flash misses an important sound cue.
Every call might have been intended to help. Collectively, they made the situation harder to manage.
This is something I want upcoming IGLs and coaches to pay attention to.
Information has a cost.
Every unnecessary sentence competes with sound cues, visual information and the decisions players are already processing.
That doesn't mean you should encourage silence.
It means developing a communication structure where players understand what deserves immediate attention.
For IGLs:
Learn to distinguish between information that requires action and information that simply provides context.
Your teammates don't always need a full explanation of your reasoning in the middle of a round.
Sometimes they need three words, a clear instruction and the freedom to execute.
There will be time to explain the decision afterwards.
Also, don't try to process every piece of information yourself.
Establish which players are responsible for communicating specific developments and allow local decisions to happen without unnecessary interference.
For coaches:
Stop reviewing communication only when someone fails to call an enemy position.
Start examining the quality and timing of information.
Was the call relevant?
Was it delivered early enough to influence a decision?
Did it communicate something confirmed or merely assumed?
Did multiple players give conflicting instructions?
Was important information lost because the channel was overloaded?
These are the details that can separate organised communication from constant noise.
One exercise I'd recommend is reviewing a demo with team voice communication alongside it.
Identify moments where players had the correct information but still made the wrong collective decision.
Then ask whether the issue was understanding, timing, clarity or conflicting priorities.
For players:
Learn the difference between what you know, what you suspect and what you want your teammates to do.
"Two B" and "I heard two sets of footsteps near B" are not necessarily the same information.
Neither is "He's rotating" and "He might be rotating."
Precision matters.
And after you die, resist the temptation to narrate the rest of the round.
Give the information your teammates need, then allow them to concentrate.
Here's a principle I believe every developing roster should understand:
The purpose of communication isn't to prove that you're contributing. It's to help someone make a better decision.
Sometimes that requires a detailed call.
Sometimes it requires one word.
And sometimes it requires silence.
Don't train your team to communicate more.
Train them to communicate with purpose.
#CS2
Vitality's decision to close their academy is understandable. How they ran it is not.
7 months. Not a single HLTV-covered match. Sporadic posts, mostly milestones. And their LoL academy closed 6 weeks earlier.
Thoughts on what went wrong and what other orgs can learn. 🧵
WHY DO SO MANY NEW CS2 TEAMS FAIL? — DAY 8: ROSTER CONSTRUCTION & ROLE COMPATIBILITY
One of the most expensive mistakes in Counter-Strike is recruiting a player because they're good, without understanding what actually makes them good.
A player dominates FACEIT, puts up impressive numbers and looks mechanically superior to everyone else you're considering.
You sign them.
A few weeks later, they're struggling to reproduce those performances in officials.
Was the player overrated?
Not necessarily.
Maybe you've taken someone who thrives on freedom, initiative and constant engagements and placed them into a system that requires patience, utility discipline and highly structured positioning.
You've recruited the player's results without understanding the conditions that produced them.
This is something I believe developing organisations need to pay much more attention to.
Player evaluation should go beyond statistics and preferred positions.
Consider how someone creates their impact.
Do they need resources to succeed, or can they consistently produce value with limited support?
Are they effective because of their own decision-making, or because their previous teammates created favourable situations?
How do they react when denied their preferred areas of the map?
Can they recognise when their usual approach is no longer effective?
These questions reveal things a scoreboard cannot.
For coaches building a roster:
Think about role compatibility before individual rankings.
Two players might both be excellent in isolation but require the same resources, positions or freedom to perform.
That creates competition within your own system.
Take an AWPer who performs best when given early-round freedom and a rifler who also relies on aggressive openings.
Both might be exceptional players.
But can your economy, utility distribution and tactical approach consistently support both?
Or will one player's impact come at the expense of the other?
Every roster decision has an opportunity cost.
And here's where I think many teams get recruitment wrong.
They look for the best available player rather than the best solution to their current limitations.
Sometimes adding another star doesn't increase your team's potential.
It simply redistributes opportunities between players who already need them.
For IGLs:
Understand what each player needs to succeed, but also what they can contribute when those conditions aren't available.
A good system should have multiple ways of generating advantages.
If your entire T side depends on one player consistently winning opening duels, what happens when opponents start denying those engagements?
Your roster construction influences the tactical options available to you.
For players:
Learn to evaluate your own game beyond your preferred positions.
What conditions allow you to perform at your best?
What resources do you require?
What can you offer when you're not receiving those resources?
And most importantly, can you contribute meaningfully when the game isn't being played around you?
That versatility can become extremely valuable as you move into more structured environments.
Another thing worth remembering:
A trial shouldn't simply be an opportunity for someone to demonstrate their aim.
Use it to observe how they process unfamiliar situations, interact with your existing system and respond when their preferred approach isn't available.
A few impressive highlights might show you a player's ceiling.
They won't necessarily show you how that player fits into your roster.
My biggest takeaway:
Roster building isn't about collecting the five highest-rated individuals you can afford.
It's about understanding how their strengths, limitations and resource requirements interact.
The best player available isn't always the best player for your team.
And recognising that difference before making a roster change can save you months of rebuilding.
#CS2
Coaches, managers, IGLs: think of the last player you picked up from an LFT post.
What did you actually check before you messaged them, and in what order?
Not looking for the "right" answer. Curious how differently people do this. #CS2
WHY DO SO MANY NEW CS2 TEAMS FAIL? DAY 7: ADAPTABILITY
One of the biggest differences between developing teams and experienced ones isn't necessarily the size of their playbook. It's what happens when their original plan stops working.
I've seen teams execute their preparation well, win the opening rounds and look completely in control.
Then the opponent makes one adjustment.
They start contesting different areas of the map, change their rotations, deny your usual information or punish a pattern you've been repeating.
Suddenly, everything falls apart.
The team starts forcing individual plays, changing strategies without understanding why, or repeating the same approach hoping it'll eventually work.
That's not always a tactical problem. Often, it's a problem with how the team understands and processes the game.
Something I want upcoming IGLs and coaches to understand:
A playbook should provide structure, not replace decision-making.
You can prepare twenty different strategies, but if your players don't understand the reasoning behind them, you're limiting their ability to adapt.
Take a simple example.
Your T side relies heavily on early map control.
The opponent starts investing additional utility and manpower into denying that control.
What happens next?
Do you keep forcing the same opening because that's what you practised?
Do you immediately abandon your entire game plan?
Or do you recognise what the opponent is committing, understand what they're potentially sacrificing elsewhere and adjust accordingly?
That's where real tactical understanding becomes important.
For IGLs:
Stop evaluating your calls only by whether you won the round.
Review what information was available, what you expected the opponent to do and whether your decision made sense under those circumstances.
Learn to identify patterns without overreacting to individual rounds.
And understand the difference between adapting to an opponent and abandoning your identity because something didn't work twice.
For coaches:
Don't build players who only know how to execute instructions.
During practice and demo reviews, challenge their understanding.
Ask what changes when an opponent denies a certain area, changes their setup or responds differently to the same pressure.
Give players opportunities to solve situations rather than immediately providing the solution.
And don't evaluate your tactical system only by how well it works against weaker opposition.
A system should be tested against opponents who force you to make difficult decisions.
For players:
Adaptability isn't exclusively the IGL's responsibility.
Your ability to recognise information, communicate changes and adjust your positioning, timing or utility is part of what makes a team function.
Five players who understand the game can provide an IGL with options.
Five players waiting for instructions can quickly become a limitation.
Here's something I strongly believe:
Teams often become predictable not because they lack strategies, but because they lack understanding of when, why and how to use them.
Adding more tactics won't automatically solve that.
Sometimes you need fewer strategies, better fundamentals and a deeper understanding of the decisions behind them.
The goal isn't to create a team that knows exactly what to do in every possible situation. That's impossible.
The goal is to create a team capable of finding solutions when it encounters situations it hasn't prepared for.
Because preparation gives you a starting point.
Adaptability determines what you do when preparation is no longer enough.
#CS2
WHY DO SO MANY NEW CS2 TEAMS FAIL? DAY 6: Practice quality
Some teams practise five days a week and barely improve. Others make noticeable progress with fewer hours.
The difference isn't always talent or effort.
Sometimes it's how those hours are being used.
One mistake I see developing teams make is treating every practice like an official match.
They want to win every scrim, execute their entire playbook and judge the session by the final score.
But what exactly are you developing?
If you're working on your T-side trading, why are you abandoning your spacing principles after losing three rounds?
If you're practising CT rotations, why are you constantly changing your setups instead of understanding why the original ones failed?
Winning practice and improving through practice are not always the same thing.
Something I want upcoming coaches and IGLs to understand:
A good practice session should have a purpose before the first round even starts.
Identify what you're trying to improve, communicate it to your players and create opportunities to work on it.
For example:
You're struggling with mid-round decision-making.
Instead of adding five new strategies, focus on how your team reacts when the initial plan fails.
What information do you have? Who is responsible for making the next decision? What options are available?
Review those situations afterwards.
And don't overload your players with ten different objectives.
When everything becomes a priority, nothing receives enough attention.
There's another important element: how you deliver information.
A two-hour demo review doesn't automatically make you a better coach.
If players leave overwhelmed, confused or unable to explain what they need to change, how effective was that session?
Structure your reviews. Prioritise the most important problems. Use clear examples and involve your players in finding solutions.
Then give them opportunities to apply what they've learned.
Explanation is not development. Application is.
And here's something I strongly believe:
If your team keeps repeating the same mistakes despite hours of practice, adding more hours shouldn't automatically be your first solution.
Question your methods.
Are your objectives clear? Are you practising the situations you're struggling with? Are players receiving useful feedback? Are you evaluating whether anything has changed?
Practice should be designed to create improvement, not simply fill your schedule.
A professional approach to practice isn't measured by how many hours you spend on the server. It's measured by how deliberately you use those hours and what your team learns from them.
Stop treating practice like another match you need to win.
Start treating it like an environment where your team is supposed to learn.
#CS2