Great in Nets, Struggling in Matches? Why It Happens and How to Fix It

You know this story because you've lived it. Tuesday evening in the nets: everything's coming off the middle, you walk home thinking this is the season it all clicks. Saturday: you face 14 balls, nick one to slip, and you're back in the shed wondering whether Tuesday was a hallucination.

Or maybe you're the bowler: quick and threatening on a Wednesday — and then a trundler on match day, holding back on your action because you're scared of bowling a bad ball.

I played representative cricket for Karnataka, and I want to say the most important thing first: this is not a character flaw. It's not that you lack "killer instinct" or "mental toughness." The gap between nets and matches is one of the most normal experiences in cricket — from club teenagers to internationals. Asking why play well in nets but fail in matches is one of the smartest questions a cricketer can ask — the answer tells you exactly what your practice is missing.

Why "just back yourself" and "more nets" don't fix it

You've heard both of these. The first usually comes from a coach or a senior player, delivered like a slogan. The second comes from your own frustration at 11pm.

"Just back yourself" is not a method. It's the result of preparation, not a substitute for it. If your body has learned that a mistake in the nets costs nothing and a mistake in a match costs your place, no slogan overrides that.

"More nets" can make the gap wider. If your practice doesn't contain the thing you're failing at — pressure, consequences, unfamiliar situations — more of it just grooves the current pattern deeper. You get better at net batting while match batting stays where it was.

The real question isn't whether you need more practice. It's whether your practice is preparing you for what matches actually demand.

Why play well in nets but fail in matches? The five causes

This gap isn't one thing — it's five distinct things. Naming them separately matters, because each one has a different fix.

1. Your practice has no consequences

In the nets there's no scoreboard. A mistimed shot costs nothing; the bowler is your teammate, not someone setting you up over three overs with a field designed for your weakness. Nothing is at stake, and your brain knows it.

Decisions change when mistakes are free. In the nets you play the shot that's available; in a match you play the shot that's safe, or the one the required rate demands. Same player, same hands — different decision environment. Nets, as one coaching site puts it, "don't replicate pressure, fatigue, or decision-making demands."

2. Your attention is in a different place

In the nets, your attention is on technique: feet moving, head over the ball, watching it closely. That's the right focus for skill-building — and the wrong focus for competition.

In a match, attention shifts to outcomes: don't get out, we need runs, the coach is watching. Technique focus disappears (the skills get wobbly) and outcome focus arrives too early (you play tight or rushed). The players who handle this best aren't thinking less in matches — their attention is on the next ball, not the result.

3. Fear of judgment, not fear of the ball

For a lot of players, the real fear in a match isn't the cricket ball. It's the coach watching from the boundary. Parents in the stands. Teammates who'll remember the duck. The fear is social: what does failing mean, and who will see it?

This is the one nobody admits, which is why it festers. A bowler in a forum thread described it: fine at pace in the nets, but in matches he's scared of bowling a bad ball, so he holds back — which ruins his rhythm. The fear of the mistake causes the mistake. If that loop sounds familiar, you're not weak — it's one of the most common patterns in the sport. Harshal Patel has described severe pre-game anxiety through his IPL career, and learned that even AB de Villiers felt the same before games.

4. Match situations you've never actually practiced

If you've never practiced rotating strike under scoreboard pressure, you won't learn it by facing your tenth throwdown of the evening. This is why some players look technically excellent but tactically lost — the technique was trained, the situations weren't.

5. You're not facing (or bowling) at match intensity

Friendly nets run at a comfortable rhythm. Real matches have an edge: bowlers charging in harder, the extra yard of pace that comes from adrenaline, every delivery mattering. Batters who've only faced throwdowns discover that genuine match pace feels like a different sport. The body calibrates to what it practices — if it never practices intensity, intensity feels foreign.

What to try: add stakes, not just hours

One idea below: close the gap between what practice demands and what matches demand. You can start this week.

Run scenario nets

Stop batting with no context. Give every net session a situation: you need 36 off 24 balls; you're 4 down chasing 180; you can't get out before the 30-minute mark. Bowlers get scenarios too: defend 12 in the last over; bowl six balls at one spot.

Here's a trick shared by a club player online that works wonders: if you're out in the net, you're out. Leave the net, come back later, or get throwdowns. It teaches your nervous system that a wicket has a cost. Getting out in a consequence-free net trains carelessness; getting out in a net with consequences trains focus.

Jasprit Bumrah described this philosophy during the 2019 World Cup: he practices every situation in the nets — new ball, old ball, death — so match day is about execution with a clear head, not problem-solving under pressure.

Simulate a real match environment

Once a week if you can: full run-ups, a keeper, fielders (or cones) in real positions, someone calling the score — even a whiteboard works. Batting with a scoreboard changes decision-making immediately. Bowlers: bowl in spells, with a plan, like a real match.

Build a pre-match routine (not a superstition)

Nerves before a match are normal — even international openers admit to them. The goal isn't to eliminate nerves; it's to give your brain something familiar to do while they're there.

Keep it boring and repeatable: same warm-up sequence, same walk-in ritual, and a first-10-balls plan — watch closely, leave anything wide, defend anything straight. A routine converts "I hope I don't fail" into "I know what I'm doing for the next 10 balls."

Set process goals, not outcome goals

Before every match, write down two goals you control. Not "score 50" — that's an outcome, and chasing it is exactly what makes you tight. Try instead: "watch the ball onto the bat for my first 10 balls" or "run hard on every scoring opportunity" (batters); "hit the top of off for my first two overs" (bowlers). You can complete a process goal on a day you get a good ball first up.

Keep a one-line match log — and review it honestly

This is the highest-leverage habit in this article. After every match, write one line: what you tried, what actually happened, one thing to try next time. That's it.

The log turns each match into data instead of just an emotion — "I played badly" becomes a record of what happened. Over a few weeks, patterns appear: the same dismissal, the same situation, the same over where things unravel. That's your actual development plan, written by your own matches. The hard part is honesty: "I got a good ball" is sometimes true and sometimes a story that protects you from the pattern. Write what actually happened.

How to tell it's working

Don't measure by scores alone — scores are noisy. Instead, watch for these:

• Your process goals get completed more often. "Watch the ball for 10 balls" going from 50% to 80% is real progress, whatever the scorebook says.
• Your match-log entries get more specific. "Got out" becomes "chased a wide one in the 8th over." Specificity means you're seeing the game better.
• You recognize situations earlier. The first time you think "this is like last month — defend now, attack later," your preparation is transferring.

Scores follow, but they lag the skill by weeks. Trust the process measures first.

And one honest note: if fear of matches is severe or persistent — affecting your sleep, your appetite, your willingness to play — that's beyond coaching advice. Talk to your coach, and consider a qualified professional. Getting help isn't weakness; it's the same instinct as getting coaching for your technique.

FAQ

Is the nets-vs-matches gap just a confidence problem?

Confidence is usually the symptom, not the cause. Players lose confidence because they keep failing in situations their practice never prepared them for. Fix the preparation — scenarios, consequences, match-intensity practice — and confidence follows, because it's based on evidence: "I've handled this before." Chasing confidence directly, without changing anything, rarely works.

I get so nervous before matches I feel sick. Is that normal?

Yes — far more normal than anyone admits; international players have described exactly this, from pre-game jitters to severe anxiety. They usually settle once you're in the action. A pre-match routine and a first-10-balls plan give your brain something concrete to focus on. If the fear is severe or persistent, talk to your coach or a qualified professional — that's a health matter, not a coaching matter.

My coach just says "back yourself." What do I actually do?

Ask for scenario-based practice ("can we bat to a situation instead of open nets?"), and bring your match log to show the pattern. Most coaches respond to a player who arrives with data instead of just frustration. And you can run scenarios with a training partner — you don't need permission to add stakes to your own practice.

Should I stop going to nets?

No. Nets are excellent for what they're for: grooving technique in a controlled environment. The problem is using nets as your only preparation and expecting match skills to appear. Keep nets for technique; add match simulation for everything else. If you're scared of facing genuine pace, that's worth addressing as its own problem too.

How long before scenario nets start transferring to matches?

Give it four to six match cycles. You're not learning a shot; you're rewiring your response to pressure, and that takes repetitions under pressure. If after six weeks your log shows the same entries with no new patterns, change the scenarios — they may not match the situations you're actually failing in.

What if my problem is specifically the fear of getting out?

That's one of the most common versions of this gap — how to stop thinking "don't get out" when batting goes deeper on the self-talk side. The short version: process goals ("watch the ball for 10 balls") give your mind something to do other than fear.

Talk through your game with Gully

Everything above is a framework. Your game is specific — your dismissals, your nerves, your patterns. The fastest way to close your own nets–match gap is to work through it with someone who remembers your last conversation: bring your match log, describe what actually happened on Saturday, and work out together what to try next Tuesday.

That's what Gully does — cricket conversations about your actual game, continuity across sessions so nothing gets forgotten, and a try → report → adapt loop that turns each match into the next week's plan. I'm not trying to replace your coach — I'm trying to cover the days when your coach isn't standing next to you.