GREMLINS IN THE COMPUTER: Identifying and Replacing Limiting Beliefs in Young Players

Introduced the three-brain model: Chimp, Human, and Computer — and what each one does under competitive pressure.

Part 2: The Chimp Paradox Explained
A plain guide for parents — what you're actually watching from the sideline, and why your instinct to help sometimes makes things worse.

Part 3: HOW TO TRAIN THE COMPUTER BRAIN
Five practical drills for installing pressure-ready programmes — and why calm practice alone cannot prepare a player for competition. 

In part 3, we established a foundational principle: the Computer brain learns through repetition, emotional charge, and conditioned match practice. It stores everything it encounters - and retrieves automatically, without conscious deliberation, at the moment it is needed most.

We also introduced — briefly — the concept of Gremlins: the unhelpful programmes that fire when the Chimp activates and the Computer goes looking for a response. We placed them in contrast with Autopilots, the well-installed programmes that allow a player to reset, adapt, and continue competing.

Part 4 is where we go much deeper. Because Gremlins are not abstract. They have specific origins, specific triggers, and specific language attached to them. They were built — piece by piece, message by message, experience by experience — by the people and environments closest to the player. And that is a deeply uncomfortable fact that both parents and coaches need to sit with before anything productive can happen.

"The Gremlin was never chosen. But it was always installed by someone."

3AM Coaching Principle

What a Gremlin Actually Is

Professor Steve Peters defines a Gremlin as an unhelpful programme stored in the Computer brain. It is automatic — it does not ask permission before it runs. It does not weigh up the situation, consult the player's values, or check whether this is a good moment to fire. When the Chimp activates and the Computer searches for a response, the Gremlin is simply there — and it runs.

What makes this so significant for coaches and parents is what it means about behaviour. When a junior player falls apart in a competitive match, they are not choosing to fail. They are not being weak, difficult, or uncommitted. Their Computer is running the most deeply installed programme available for this situation — and that programme is a Gremlin.

This is not a character judgment. It is a description of a software problem. And like every software problem, it can be addressed — if we understand what we are dealing with.

Core Principle · Peters Framework

A Gremlin is not the player. It is a programme the player is running. The distinction matters enormously — for how coaches respond in the moment, and for how parents speak about what they see from the sideline.

Gremlins Never Travel Alone

One of the most important — and most underappreciated — points in Professor Peters' framework is this: Gremlins cluster. They accumulate around a central wound, each reinforcing the others and creating a network of limiting beliefs that functions as a coherent system.
Address one Gremlin without mapping the cluster, and the others remain in place — quietly continuing to shape the player's response to pressure. This is why a single conversation, however insightful, rarely produces lasting change. The coach who identifies "Pablo gets tight on his serve" has spotted one Gremlin. But behind it sits the belief that errors mean something about his worth. Behind that sits the belief that he should be able to fix things alone. Behind that sits the belief that he is known as someone who struggles. Remove the serving anxiety without addressing the cluster, and the cluster simply reasserts itself through a different Gremlin at the next stressful moment.
🔴 What a Gremlin Cluster Looks Like — A Typical Example
"I always fall apart under pressure"
"Mistakes mean I'm not good enough"
"I can't change things once they go wrong"
"If I lose this set, I'll lose the match"
"Everyone can see that I'm struggling"
"I should be able to fix this on my own"
"I'm known as someone who cracks"
"Pressure reveals who I really am"

These programmes do not exist in isolation. Pull on one, and you pull on all of them.

How Gremlins Get Built

In Part 3, we explained that the Computer installs programmes through two conditions: repetition and emotional charge. A message repeated often enough, or delivered once with sufficient emotional intensity, becomes a stored programme. The Computer does not evaluate whether the message is true or useful. It simply records what has been experienced — and retrieves it when the conditions match.

This is how Gremlins are born. Not through malice, not through poor parenting or bad coaching, but through the ordinary accumulation of messages, reactions, and experiences that surround a young athlete throughout their development.

There are three primary sources from which Gremlins are installed in junior players.

Parents

  • "You always do this in big matches."
  • "Why can't you just stay calm?"
  • "You had it, and you threw it away."
  • "You're too emotional — you need to toughen up."
  • "Your sister never gets this nervous."


Coaches

  • A tenni coach's verbal interaction with their players is extremely important
    Coaches should avoid repetitive negative language

  • "You always choke at this stage."
  • "You're a practice player, not a match player."
  • "If you were tougher, this wouldn't have happened."
  • "We've worked on this a hundred times."
  • "You're wasting your talent."


Peers & Environment

  • Being known in the squad as "the one who cracks."
  • Losing repeatedly to the same opponent.
  • Repeated public errors in high-stakes moments.
  • Watching others cope while you struggle.
  • The accumulated weight of the scoreboard over the years.


None of the adults in this list intended harm. Most were trying to motivate, correct, or express their frustration in a difficult moment. But the Computer brain of a ten, twelve, or fifteen-year-old does not filter for intent. It records the message, weighted by the emotional charge of the moment it was delivered in — and stores it as a programme.

"There is no neutral language in a critical moment. Every word either installs something useful or installs something harmful. The Computer does not distinguish between the two."

3AM Coaching Principle

How to Identify a Gremlin Running

Before a Gremlin can be replaced, it must be named. And before it can be named, it must be noticed by the coach, by the parent, and eventually by the player themselves. This is not as simple as it sounds, because Gremlins do not announce themselves. They arrive disguised as truth.

The player who says "I always fall apart in the third set" is not describing reality. They are reciting a programme. The coach or parent who hears this and nods sympathetically — or worse, agrees — is reinforcing the installation. What is needed instead is the ability to recognise the language of a Gremlin when it surfaces, and to respond in a way that interrupts the programme rather than deepening it.

What to Listen For — Gremlin Language in Young Players

"I always do this when it matters."
Identity Gremlin
"I can't fix my serve once it goes wrong in a match."
Helplessness Gremlin
"I knew I was going to lose once I dropped that set."
Prophecy Gremlin
"Everyone was watching — they all saw how bad I was."
Exposure Gremlin
"I should just be able to handle this — other players can."
Comparison Gremlin
"I'm just not a match player. I'm better in practice."
Label Gremlin
"Pressure shows who you really are — and it showed."
Identity Gremlin

The keyword to listen for is "always" — and its relatives: "never," "every time," "I can't," "I'm just not." These are the linguistic fingerprints of a Gremlin. They signal that the Computer has moved from describing an event to describing an identity. And once a Gremlin has attached itself to a player's sense of who they are, it becomes significantly harder to dislodge.

The Role of Labels

A particular category of Gremlin deserves its own attention: the label. Labels are fixed-identity descriptions applied to a player from the outside — by a coach, a parent, a peer, or the player themselves — that the Computer stores as statements of fact about who that person is.

Avoid the use of negative labels

"She's a choker." "He's a practice player." "She doesn't have the mental game." "He can't compete." These are not observations. Within Professor Peters's framework, they are installations—directly written into the Computer as programmes that the player will subsequently run in the situations the label predicted.

The child labelled as "someone who struggles in matches" does not decide to struggle. Their Computer has been programmed to. The label was installed by someone who thought they were being accurate. What they were actually doing was writing software.

Gremlins Cannot Be Removed — Only Replaced

This is the most important practical insight in the entire framework, and the one most frequently misunderstood. Parents and coaches often believe that if they can help a player understand why a belief is wrong — if they can reason with them, encourage them, or simply repeat the correct message often enough — the Gremlin will disappear.

It won't. Not because the player isn't listening, and not because the coach isn't skilled enough. But because that is not how the Computer works. The Computer does not delete programmes through conversation. It only replaces them when a better-installed alternative is available to retrieve instead.

Understanding is where the work begins. It is not where it ends.

🔴 The Gremlin Running
🟢 The Autopilot to Install
"I always fall apart when I serve for the set."
Pre-serve routine: bounce twice, breathe, pick a target, commit. Practised 300+ times under pressure until automatic.
"If I drop the first set, I've lost the match."
"One set tells me nothing about the next. Reset and compete." Embedded through competitive formats that begin from one-set-down.
"I can't change my tactics mid-match — I don't know how."
"Something isn't working. What's one thing I can change right now?" Trained through tactical lockout drills — competing without default options.
"Mistakes mean I'm not good enough to be here."
"Errors are data. What happened, and what do I do next?" Installed through error-recovery sequences with scored outcomes.
"Pressure reveals who I really am."
"Pressure is information — my Chimp is warning me. I've heard it. Now I compete." Practised through Chimp Intercept drills.

A players self-talk can be highly destructive to their competitive game
The ability of players to effectively manage self-talk and beliefs is crucial to competitive success


None of the Autopilots above were created by telling a player the right thing. It was built through deliberate repetition, emotional charge, and practice conditions that matched the moment in which it would need to be retrieved. The coach's job is not to argue the player out of the Gremlin. It is to design the sessions that build the replacement — and then to be patient while the new programme accumulates the installation depth it needs to override what came before.

What Parents Can Do — and Stop Doing

A parents interaction with a young tennis player has profound repercussions
Parents, in the heat of the moment, are the biggest source of Gremlins 

Parents occupy a uniquely powerful position in a junior player's Computer. The emotional charge attached to a parent's words — delivered in the heat of a match, in the car on the way home, or at the dinner table afterwards — is among the highest of any source in a child's life. Which means parental language has a disproportionate capacity both to install Gremlins and to build the conditions for Autopilots.

The most important shift a parent can make is from outcome language to process language. Outcome language ties a child's identity to results. Process language focuses on what happened in the system — what the Chimp did, what the Computer tried to retrieve — without attaching it to who the child is.

🔴 Language That Installs Gremlins
🟢 Language That Builds Autopilots
"You always fall apart under pressure."
"Your Chimp got loud today. What did it feel like when it arrived?"
"Why can't you just stay calm?"
"What did you try to do when things got tight? Did your reset routine help?"
"You had it and threw it away."
"You were competing well. What changed for you in that moment?"
"You're too emotional — you need to toughen up."
"That looked really intense. What was going on inside?"
"You're just not a match player."
"Your Computer hasn't been fully trained for match conditions yet. That's what we're working on."

The second column is not softer parenting. It is more accurate parenting — and in the framework of the 3AM methodology, more accurate parenting is more effective parenting. The child who is told "you're too emotional" has had a label installed in their Computer. The child who is told, "Your Chimp got loud — what was it saying?" has been given a framework that separates their identity from their competitive experience. One installs a Gremlin. The other opens the door to understanding the system.

The Most Important Rule for Parents

The 20-minute rule: nothing of substance should be said about the match for at least 20 minutes after it ends. The Chimp needs time to stand down. The Human brain needs space to re-engage. Conversation that happens in the car park immediately after a loss is almost always Chimp-to-Chimp — and it installs accordingly.


What Coaches Can Do — and Stop Doing

Tennis coaches must be aware of the language they use around players at all times
The language a Coach uses with their players is extremely important

Coaches carry a different kind of authority from parents — one that is professional, sustained, and directly linked to performance. The coach is the person whose words a player hears most consistently during the actual game. That gives coaching language enormous installation power, for better or worse.

The most common Gremlin-instilling coaching behaviour is not cruelty or negligence. It is the frustrated, well-intentioned observation delivered at the wrong moment — in the middle of a high-pressure drill, immediately after an error, or during a match changeover when the Chimp is already active and the Computer is searching urgently for a response. In those moments, the player's emotional state means that whatever the coach says carries exceptional installation weight.

Coaches also install Gremlins through session design — specifically, through the absence of pressure training we explored in Part 3. A player whose Computer has only ever learned to perform in calm conditions has not been given the tools to compete. When competition arrives and the tools are missing, the Computer defaults to the Gremlin cluster. The coach may interpret this as a mental weakness in the player. What they are actually seeing is a gap in their own coaching programme.

🔴 Language That Installs Gremlins
🟢 Language That Builds Autopilots
"You always choke at this stage."
"Your Computer hasn't got a reliable programme for this moment yet. Let's build one."
"You're a practice player — you don't perform when it counts."
"Your practice game is strong. We haven't yet matched the training conditions to the competition conditions."
"We've worked on this a hundred times — why can't you do it in a match?"
"We've trained this in calm conditions. Now we need to train it in the conditions where you'll actually need it."
"If you were mentally tougher, this wouldn't happen."
"Mental toughness is a programme — and we haven't built yours for this situation yet."

The diagnostic shift for coaches is significant: when a player underperforms under pressure, the first question is not "what is wrong with this player?" It is "what has not yet been installed into their Computer?" That reframing changes everything — the session design, the language used, the timeline of expectation, and the relationship between coach and player in the difficult moments.

Pablo — Mapping the Full Cluster

What Is Actually Running in There?

When we first met Pablo in Part 1, we described his competitive pattern: a player who performs with genuine quality in practice, but whose level drops sharply when match pressure arrives — and who is unable to find solutions, so that an error made in the first game of a match is still unresolved in the third set.

In Part 3, we framed his situation in terms of Computer installation: his programmes have been built for calm conditions, and competition is not calm. His Chimp activates early; his warning loop runs for the duration; and without a reliable reset Autopilot, his Computer defaults to whatever is most deeply installed — which, in Pablo's case, is a well-populated Gremlin cluster.

Now we map that cluster directly. Not as a judgment of Pablo's character — the 3AM framework is explicit on this point: these programmes are not Pablo. They are what Pablo's Computer learned from the experiences and messages that surrounded him. And they can be replaced.

Pablo's Gremlin Cluster — Mapped

"When my serve breaks down, something takes over, and I can't stop it."
Core Gremlin
"If something stops working, I don't know how to fix it mid-match."
Helplessness
"Pressure reveals who I really am — and it's not good enough."
Identity
"I should be able to handle this. Other players can. I can't."
Comparison
"I'm known as someone who struggles in matches."
Label
"I can't ask for help — I should be able to sort this myself."
Isolation
"If I lose the first set, the match is over for me."
Prophecy

Notice what happens when you pull on any one of these: the others tighten. Pablo's serve breaks down (Core Gremlin fires). He doesn't know how to fix it (Helplessness fires). He feels exposed as someone who can't cope (Identity fires). He compares himself to the player across the net who looks composed (Comparison fires). He won't tell his coach how bad it feels because he should be able to manage (Isolation fires). He drops the first set and concludes the match is already decided (Prophecy fires).

This is a system, not a series of individual problems. And it will not be resolved by addressing a single item on the list.

The path forward for Pablo follows the same sequence we outlined in Part 3: recognition first, then Autopilot installation, beginning with the reset programme and building outward. The coaching questions we posed in Part 1 are the opening tools — not to diagnose, but to begin building Pablo's awareness of what is running, so that his Human can participate in the process of replacement.

The Autopilots Pablo Needs to Build — In Sequence

Reset Autopilot: When the Chimp fires, a reliable 10-second protocol that delivers the signal: "I've heard you. We have this. Step back." Practised until automatic.
Serve Recovery Autopilot: A specific technical cue sequence for when the serve breaks down under pressure — trained in consequence-based formats that mirror the exact moments the Gremlin fires.
Problem-Solving Autopilot: "Something isn't working. What's one thing I can change?" Installed through tactical lockout drills — competing without default options.
Set-Loss Reset Autopilot: "One set tells me nothing about the next." Built through competitive formats that begin from one-set down and require Pablo to win from that position repeatedly.

Pablo's talent was never in question. His software was. And the work of replacing it — patient, deliberate, unhurried — is the most important coaching Pablo will ever receive.

The Four Phases of Gremlin Replacement

For both coaches and parents, it helps to understand the replacement process in terms of four distinct phases. These do not happen quickly — and they do not happen in a straight line. But they do happen, given the right conditions and the right patience.

1
Awareness — Naming What Is Running

Before anything can change, the player needs to be able to name the Gremlin — not as a self-criticism, but as a factual observation. "I notice that when my serve misses twice, something shifts." The coach facilitates this through the questions from Part 1. The parent facilitates it through the language shift above. This phase takes as long as it takes — rushing it produces defensiveness, not insight.

2
Design — Building the Replacement

Once the Gremlin is named, the Autopilot can be designed — specifically and collaboratively. Not "think more positively," but "when the serve misses twice, here is the exact sequence you will run." The more specific the Autopilot, the more reliably the Computer can retrieve it. Vague positive intentions do not install. Precise, practised responses do.

3
Installation — Repetition Under Pressure

The Autopilot is practised hundreds of times — first in low-stakes conditions, then progressively under the pressure conditions in which it will need to be retrieved. This is the unglamorous work. It is slow, sometimes frustrating, and interrupted regularly by the Gremlin reasserting itself. That is expected and normal. Each time the Autopilot runs and produces a better outcome, it accumulates installation depth.

4

Consolidation — The Autopilot Becomes Default

Over time — typically months, sometimes longer for deeply held Gremlins — the Autopilot becomes the most deeply installed programme for the relevant situation. The Gremlin still exists. But it no longer runs first. The player does not choose the Autopilot in the moment. They find that it is simply there — waiting, reliable, ready. That is what a fully installed programme feels like.

"Gremlins are not permanent. They only feel that way because they have had more time and more emotional charge than anything that has tried to replace them. Give the Autopilot the same — and the Gremlin's grip loosens."

3AM Coaching PrincipLE

What This Changes — for Everyone in the Room

The framework in this article asks something significant of both parents and coaches: to accept partial responsibility for the Gremlins currently running. Not as a guilt exercise, but as a practical prerequisite for change. If the messages and experiences that installed the Gremlin came from the player's environment, then that environment is also where the replacement begins.

For parents, it begins with the language used in the car on the way home. For coaches, it begins with the language used at the changeover and the design of the next training session. Neither change is dramatic. Both changes are cumulative. And cumulative change, over months and years, is exactly what the Computer brain is designed to respond to.

Pablo's Gremlin cluster did not appear overnight. It was built, message by message, match by match, experience by experience, over the years. His Autopilots will be built the same way — one reset at a time, one recovered serve at a time, one completed problem-solving sequence at a time. The coach and the parent who understand this are not just more patient. They are more effective.

Comments

Popular posts from this blog

MASTER THE TWO-HANDED BACKHAND: The 4 Key Elements You Need For Power and Control

CAN YOU PLAY YOUR BEST TENNIS AT 3AM?

4 REASONS TENNIS PLAYERS STOP COMPETING WHEN MATCHES GET TIGHT