Progress and Plateaus

Progress in aim training rarely moves in a straight line. Expect fast early gains that slow down, and the occasional stretch where your score barely moves at all.

• Slowing gains are normal. Early jumps shrink as you get more skilled.
• A flat stretch isn't evidence of a ceiling. Plateaus are an expected stage of learning.
• Judge the trend, not one run. A single benchmark result is noisy.
• Rest first if you're run down. Then vary your focus, scenarios, or sensitivity.

This page covers that normal pattern, what usually causes a longer stall, and what helps you get past one.

Explanation¶

Normal progress patterns. Early practice on a new scenario tends to produce large, fast gains, and those gains shrink as you get more skilled.

General motor-learning research describes an early stage of large, inconsistent jumps in performance. A slower stage of smaller gains follows, spent on conscious adjustment and refinement. The pattern isn't specific to aim training.¹

Eventually most learners hit a stretch some researchers call a "learning plateau." Performance holds roughly steady for a while, however consistently you show up and train.

Plateaus are frequently experienced in late-stage motor learning, rather than being evidence that something in your training has broken.²

Knowing a stall is expected doesn't fix it on its own. But it does mean a flat week or two isn't evidence you've hit a hard ceiling.

Tracking scores over time. A single benchmark run is noisy. A bad night's sleep or an off day can move your score as much as real progress does.

So judge your training by the trend across several benchmark runs spaced weeks apart, rather than any one result.

Keeping your own record of scores makes that trend easier to see. It also helps you tell it apart from ordinary week-to-week variance, before you change your training in response to what might just be noise.

Causes of plateaus¶

Fatigue. Training hard without enough recovery between sessions can cause overreaching. Extreme overreaching combined with another stressor can lead to overtraining syndrome, which takes over two months to recover from and is extremely rare.³

A plateau that appears alongside feeling generally run down, not just a flat score, is worth treating as a fatigue problem first.

One-sided practice. Running the same handful of scenarios repeatedly can make you better at those scenarios, without making you better at aiming in general.

The skill stops being challenged once you've adapted to that narrow input. Practice Principles covers the same point through Revosect's own advice against training only on benchmark scenarios.

No technique focus. A plateau can also come from optimizing the wrong thing. That means pushing volume or difficulty on a scenario without checking whether your underlying technique is improving: smoothness, timing, positioning.

See Practice Principles on deliberate practice, and How Aim Works for what that underlying technique consists of.

Ways past a plateau¶

Switch focus. If your current weak subcategory has stopped moving, shift the bulk of your routine to a different subcategory for a while. Don't just grind the same one harder.

You may come back to the original one able to make faster progress, once it isn't the only thing you're doing.

Rest days. Fatigue is one of the more common causes of a stall. So a deliberate stretch of lighter training or full rest is a reasonable first thing to try, before restructuring anything else. That's per the same overtraining research above.

Sensitivity or scenario variation. Voltaic's piece on the "muscle memory" myth lists a deliberate sensitivity change as one way players get past a stall.

The logic is that a new sensitivity puts you back where there's obvious room to improve. Your hand hasn't already fully adjusted to it. See Sensitivity for when that trade-off is worth making.

The same logic extends to using different scenarios for the same skill. A new one forces your hand to adapt again, instead of repeating one you've already mastered.

Common mistakes¶

• Treating a single bad benchmark run as proof you've plateaued, or a single good one as proof you've broken through.
• Responding to a fatigue-driven plateau by training harder instead of resting.
• Repeating the exact same scenarios indefinitely and assuming a flat score means you've hit your ceiling, rather than that your practice has stopped varying. See Myths.

Do this next. If you feel run down, take a stretch of lighter training first. If not, shift your routine's focus to a different subcategory for a while.

Related¶

• Practice Principles: deliberate practice, variety, and rest as the habits that prevent a plateau in the first place.
• Benchmarks: how to track a score trend rather than a single result.
• Sensitivity: sensitivity change as one supported way to break a plateau.
• Testing a Scenario: reading a new scenario's scores against the same noise.
• Keeping the Score Readable

Resources¶

• Voltaic: source of the muscle-memory and sensitivity-change guidance.
• Guides: guides on practice, routines and bad sessions.

References¶