How to Analyse Your Own Team's Performances

Ask a coach how Saturday went and you will usually hear about the last ten minutes. The soft goal, the missed sitter, the decision that went against them. Ask what happened in the first hour and the answers get vague. We started slowly. We didn't really get going. They wanted it more.

That is not analysis, it is memory, and memory after a match is a terrible witness. It overweights whatever happened last, whatever cost a goal, and whatever made you angriest at the time. Then Tuesday's session gets planned off the back of it.

Analysing your own team properly does not require video software, a laptop or a Tuesday night lost to highlights. It requires a small framework, notes that survive your own emotions, and a routine that turns what you saw into what you train. This guide gives you all three.

What analysing your own team actually means

Self-analysis is the habit of working out what your team actually does, repeatedly, in matches: what you are good at, where you are vulnerable, and whether the things you train are showing up on Saturday. It is the feedback loop of coaching. Without it you are planning sessions on instinct and anecdote.

The distinction that matters is between the game you saw and the game you felt. A 3-2 defeat feels like a defensive disaster, but the notes might say you created eight chances to their five and conceded twice from your own corners. A 1-0 win feels like progress, but the count might show three shots all game and a goalkeeper who won you the points. The score is the loudest liar in football.

Professional clubs solve this with analysts and coded video. You can solve it with a page of structured notes, because the goal is the same at every level: replace impressions with patterns, then coach the patterns. Done weekly, it also builds the evidence base for your longer-term plan, the game model your team is supposed to be growing into.

The principles

1. Judge the performance, not the result. Results at grassroots level swing on a keeper's mistake, a growth spurt or a referee, and they arrive maybe 30 times a season, far too small a sample to steer by. Performances repeat every week. Decide what a good performance looks like for your team, in plain terms, and mark against that whether you won 4-0 or lost to a worldie.

2. Use a framework small enough to survive matchday. The classic four phases are enough: in possession, out of possession, attacking transition (the moment you win the ball) and defensive transition (the moment you lose it). Add one number for each end, chances created and chances conceded, counted honestly. Four phases and two tallies fit on one sheet and cover the whole game. Thirty statistics do not survive contact with a Sunday morning touchline.

3. Hunt patterns, not moments. One misplaced pass is noise. The same full back overrun three times, the same slow start after half-time two weeks running, the third goal this month conceded from a switch of play: those are patterns, and patterns are coachable. A useful rule: nothing goes into the review unless it happened at least twice, or connects to something from a previous week.

4. Analysis only counts when it changes Tuesday. The output of a review is not a document, it is a decision: one theme, taken into next week's training. If your analysis never alters what you coach, it is a diary, not a tool. Close the loop the other way too, and check on Saturday whether the thing you trained actually appeared.

What the best teams do

Every professional club now codes matches by phase, but the habits worth copying are behavioural, not technological. The first is delay. Elite coaches largely stopped delivering verdicts in the dressing room at full-time, because they know the first version of the game in their head is wrong. Reviews happen a day or two later, once the staff have watched the match again with the emotion drained out of it, and plenty of managers will admit the rewatch regularly contradicts what they said in the press conference.

The second is ruthless selection. When Premier League players sit down for a team review, they do not watch 90 minutes, they watch eight to twelve clips chosen to show one or two themes. The analysis department may have coded 2,000 events, but the players receive a message small enough to act on. Selection, not collection, is the skill.

The third is consistency. Clubs review wins with the same framework as defeats, because performances and results are treated as separate questions. Brighton became the modern reference for this: publicly judging performances on the quality of chances created and conceded rather than results, on the basis that the underlying numbers predict the future better than the scoreline does. You do not need their data scientists to borrow the discipline.

How to build the habit: a weekly routine

Saturday, during the game. Keep one sheet and a pen in your pocket. Tally chances for and against as they happen, with a letter for how each one came about (through the middle, wide, set piece, transition). Between those, allow yourself a maximum of five written observations, each tied to a phase. If you have an assistant or a trusted parent, give them the tallies so you can coach. Writing during the game feels awkward for two weeks and then becomes automatic.

Saturday, straight after. Say less than you want to. A two-minute team talk on effort and one genuine positive is plenty, because anything more detailed is coming from the least reliable version of you. Fold the sheet, go home, and do not touch it until the next day.

Sunday or Monday, 20 minutes. Read the sheet cold. Score each of the four phases out of five, honestly, and write one sentence per phase about why. Then compare the chance counts with the scoreline and notice where they disagree. Pick the single biggest repeating problem, and one strength to keep feeding. That is the review done. If you have video, this is where it earns its keep: check the two or three moments your notes flag, rather than rewatching the lot.

Midweek, plan from the theme. Turn the chosen problem into the topic of the week and build your practices around it, using the structure in our guide to planning a training session. Tell the players the theme and where it came from. Teams train harder on a problem they remember creating.

Next Saturday, close the loop. Watch specifically for the theme and count it. Did the slow starts stop? Did the switches get defended? Two or three loops like this and analysis stops being an event and becomes the operating rhythm of your season.

No video? You lose less than you think. The framework above was designed for a notebook, not a camera. If you want more than notes, ask a parent to film ten minutes either side of half-time from behind a goal on a phone: shape and distances show up better from there than from any touchline. But counts, phases and honest scoring will carry a grassroots coach 90 per cent of the way.

Three mistakes that kill self-analysis

Reviewing at full-time. The angriest version of you writes the review, names the culprits in front of the group, and Tuesday's session becomes a punishment. The fix is structural, not moral: keep the full-time talk tiny, and book your real review for the next day, every week, win or lose.

Collecting what you never use. Some coaches drown in their own diligence: pass counts, heat maps drawn from memory, ratings for every player. If a number has never changed a session, stop collecting it. Two tallies and four phase scores that get used beat 30 statistics that get filed.

Only analysing defeats. Reviewing losses and celebrating wins teaches your squad that analysis is what happens when they are in trouble, and it lets the flaws in your wins compound quietly. The 2-0 win where you created three chances contains next month's defeat. Same sheet, same 20 minutes, every week.

Adapting it to your level

With youth teams, analyse development, not just performance. Add one count that reflects what you are teaching, brave passes attempted, players who tried to receive under pressure, and read it alongside the chances. Involve the players gently: ask two or three of them what they noticed before you share your view. From U13 upwards they will start pre-empting your reviews, which is exactly the habit you are trying to grow.

For adult grassroots sides, the barrier is time and the fix is honesty about scale. One sheet, one theme, one message in the group chat by Monday night: here is what the game told us, here is what we work on Thursday. Involve your captain in the review once a month. Players who moan about training suddenly engage when the session visibly answers what happened on Saturday.

The takeaway

Judge performances, not results. Capture the game in four phases and two honest tallies. Review cold, a day later, and pick one pattern. Train that pattern, then measure it the following Saturday.

For session plans, review templates and the frameworks to build your whole coaching week around, take a look at Coach Notes Pro.