The arrow you already shot

You know before you look.

That cold, specific certainty between the release and the arrow landing isn't a feeling. It's a report. Your brain files it before you finish the thought oh no.

Here's the biology: about 50 to 100 milliseconds after a wrong response, the brain generates an electrical signal called the error-related negativity — a characteristic deflection over the front-middle of the skull, documented by Gehring et al. in 1993. It's attributed to the anterior cingulate cortex, which monitors for mismatch between what you intended and what you did. It fires before you're consciously aware of anything. Then, 300–500 milliseconds later, a second signal — the error positivity — marks the moment awareness actually arrives.

Your brain filed the complaint several hundred milliseconds before "you" had an opinion about it.

This research is from button-press tasks in labs, not bow releases — the transfer to archery is inference, not measurement. But the timing matches what every experienced archer has felt. “Calling your shot” isn't mystical. It has a waveform.

Here's what it feels like from the line. Fourth end of a Wednesday league, eighteen metres, three-spot. You're clean — nine ends of tens, and you have been very carefully not thinking about that, which is its own kind of thinking about it. You draw. The pin rises the way it always does. And then, somewhere in the half-second between aiming and releasing, something in your hand gets ahead of you.

You feel it leave. The arrow doesn't even have the decency to sound dramatic. Arrows in the middle of a Vegas face make a particular tock. That one made a flatter noise, further away, with a bit of paper in it. Everyone within three bales heard the difference and said absolutely nothing — which is somehow worse than if they'd laughed. Your scorecard now says 297 is the best you can do. That arrow cost three points. For the next ninety seconds it's going to try to cost thirty. (You know this. You are going to let it try anyway.)

The smoke alarm, and the problem with smoke alarms

Your error monitor is a smoke alarm: fast, single setting (maximum), saves you often enough that you'd never pull the battery. The cold feeling before the arrow lands is useful. You want it.

The problem: smoke alarms don't distinguish between kitchen fires and aggressive toast. One setting. Maximum. Always.

On a lab task, the next trial arrives 800 milliseconds after the error and the alarm never compounds into anything. On a shooting line, your next arrow is sixty seconds away. Sixty seconds is a very long time to stand in a room with a smoke alarm going off, with no ladder to reach it, while being expected to shoot again.

The work order

A bad shot doesn't just cost a point. It writes a work order.

Within two seconds you have a hypothesis: my hand crept, I punched it, I dropped the arm. Within five, the hypothesis is a fact. And on the next arrow, without deciding to, you are supervising your hand. That's explicit monitoring (Part 1), delivered directly to your attention by a bad shot, with the faulty component helpfully labeled. It is the world's worst gift.

The bad shot sends you down one of two roads — and they have opposite cures:

Distraction — the shot expands outward into the round. I'm blowing this. The clean round's gone. Everyone heard that land. Your shot process runs on whatever the scorecard hasn't claimed.

Explicit monitoring — the shot collapses inward onto the mechanics. Watch the thumb. Don't punch it. Keep pulling. The centipede, asked which leg goes next, with an audience and one arrow left.

If you reach for the same fix every time regardless of which road you're on, you are running a coin flip. Expert shot processes are exactly the thing "concentrate harder" dismantles when the problem is already too much concentration.

Rumination: the loop with no exit

The clinical definition of rumination is repetitive, passive, self-focused thought about a negative event that does not terminate in an action (Nolen-Hoeksema et al., 2008). The key phrase: does not terminate. There is no sentence that closes the file. The loop runs until something interrupts it from outside.

Two things make this expensive on a shooting line. First: induced rumination degrades performance on completely unrelated tasks — the resource isn't partitioned, and the loop is drinking from the same pool your shot needs. Second: worry extends the physiological stress response well beyond the event itself (Brosschot, Gerin & Thayer, 2006). The arrow took forty milliseconds. Your nervous system doesn't know that. Without interruption, you will still be shooting that arrow at the end of the round.

Rumination feels like taking it seriously. People who ruminate tend to believe they're generating insight. Mostly they aren't — they're running a process that has the phenomenology of diligence and the output of a screen saver. (The screen saver has now replayed that seven in slightly better form twelve times. The arrow is in the same place.)

Diagnosis is allowed. Rumination isn't.

They look identical from outside. The difference:

Diagnosis ends in a sentence. "My hand crept because I rushed the transition — next arrow, slower into the wall." Say that and you're done. There is a closing sentence.

Rumination has no sentence that ends it. "I always do this when it matters" is not a diagnosis. It is a weather system. It will rain until something else interrupts it, which may be the end of the round, which is too late.

Between arrows: you don't have room (the gap is already fully booked), one arrow isn't data (it's inside your normal variance), and the diagnosis you reach with your heart rate up right after a bad shot is almost certainly wrong. You will confidently identify the wrong cause, apply a correction to a system that didn't have that problem, and fire twice.

When the thought arrives anyway — and it will arrive whether you invite it or not — offload it. Three words on the scorecard margin: Rushed. Transition. Hand. That converts a live loop into a closed item. The loop was running because it had no exit condition; now it has one: written down, dealt with at the bale. Then actually look at it later, or this stops working inside a month because you'll have taught yourself the promise is hollow.

Call your shot before you look

Old rifle discipline. Before you look downrange, say where you think the arrow is.

• Call matches arrow: it was you. Real information. Worth a margin note.
• Called middle, arrow's in the blue: look at the flags, the rest, the serving, the nock. Look at the environment before you look at yourself.
• Can't call it at all: the most important result. It means you weren't present when the arrow left. Something else was running on your bandwidth while the shot happened.

Calling forces a commitment before the outcome is visible. It strips out the part of attribution that's just storytelling assembled after the fact, which is almost all attribution.

Sometimes it wasn't you

A 15-mph crossgust arrives at the wrong moment. A vane clipped something on the way out. A rest blade shifted three thousandths somewhere in the last hundred shots. You have an arrow with a bent insert you won't find until November.

Take personal responsibility for a wind gust and here's what you've done: run a diagnosis on a shot with an external cause, reached a conclusion about your form, and applied a correction to a system that was working. That's how good archers dismantle a good shot process over a single weekend. The wind moved the arrow. You moved the archer. Now both are off.

The opposite error is more common — blaming conditions for a shot you punched. More comfortable in the moment, and it costs you the information. Every arrow you hand to the environment is one you learn nothing from.

Use the shot-call to sort it. If you called it middle and it landed at three o'clock in the blue, look at the flags, the arrow, the nock, the rest — look at the world before you look at yourself. If you can't call it at all, that's the most important result of all: it means you weren't present when the arrow left. Not a technique problem. An attention problem. Whatever was running on your bandwidth during the shot, it wasn't the shot. Reset harder on the next one.

The reset

A reset is a short, fixed, physical sequence you run after every arrow. Not just bad ones. Every arrow.

If it only appears after bad shots, it becomes a bad-shot signal within a few weeks. Running it starts to mean that was awful, and you've built a conditioned cue for failure and installed it in your process. Run it after the good arrows. Especially after the good arrows.

Four requirements:

1. Physical. An action has a definite end; a resolution doesn't. "I'll let that go" is unfalsifiable. "Step back off the line" is done or not.
2. Identical every time. See above.
3. Fits the actual clock. Timed when tired and the wind is wrong, not on a good day.
4. Ends with attention outside your body. Not on your release hand. Not on your grip. On the target.

A five-beat version:

Step back. Off the line, or square your feet and turn away. Hard physical break. The end of an arrow should have a place, and the previous arrow should be on the other side of it.

One long exhale. Longer out than in. The best controlled comparison of brief breathing protocols (Balban et al., 2023, Cell Reports Medicine) found that exhale-weighted cyclic sighing outperformed box breathing and mindfulness meditation on mood and respiratory rate reduction. Be precise about what that shows: 28-day daily practice study, general population, mood outcomes. Not shooting accuracy between arrows. The mechanism transfers; the measurement doesn't prove it for your specific window. Train it at home until it's boring first.

One instructional word. Not "come on." Self-talk meta-analysis (Hatzigeorgiadis et al., 2011): d ≈ 0.48 — moderate, real, not miraculous. Instructional beats motivational for fine motor tasks. "Elbow through" beats "COME ON." A word from your process, not from the part of you that's worried.

Eyes to the target, held. The strongest evidence in this piece. Quiet eye — the final stable fixation before execution — is meta-analysed across sports at a moderate-to-large effect (Lebeau et al., 2016). After a bad arrow, gaze discipline is the first thing to disappear — you look at the blue hole, at your hand, at the scorecard, at anything except where the next arrow needs to go. Put your eyes back on the middle deliberately, before you draw.

Step back on. The line is not a place where old arrows exist.

Five to eight seconds, once it's a habit. Build it now. Run it on every arrow all season. When you need it, it'll be there.

← Part 2 — The Week, The Night, The First Arrow  ·  ↑ Library  ·  Part 4 — When It’s Going Right →

Series: Part 1 · Part 2 · Part 3 · Part 4 · Part 5 · Part 6

Published 2026-09-02  ·  Axial Bowstrings