Lineup optimization · Quality at-bat tracking · Built by a baseball family
Get the Apps

Turning a weekend of games into a practice plan

Most practice plans are built from the most recent memorable failure. The team lost on a botched relay, so Monday is relays. It feels responsive. It is mostly recency bias with a whistle.

Why the default is wrong

The problem with planning practice around what you remember is that memory selects badly. It over‑weights whatever happened last, whatever happened loudly, and whatever happened to the players you were already watching. A quiet, chronic weakness that costs you a run every other game is nearly invisible next to one spectacular mistake.

An error in the last inning of Saturday’s loss is not evidence of a pattern. It is one event, and single events at youth level are dominated by variance. Building sixty minutes of practice around it means the actual recurring problems keep going unaddressed.

You do not need more data to fix this. You need the data you already generate to be written down somewhere other than your head.

Read patterns, not games

If you are logging quality at‑bats and hustle plays each game, the useful unit of analysis is four to six games, not one. Over that window a few specific shapes tend to appear, and each points at a different practice response.

Low quality-at-bat rate across the whole roster

This is an approach problem, not nine individual slumps. Usually it means the team is swinging at pitches outside the zone early in counts. The practice response is pitch selection — take drills, two‑strike approach work, live at‑bats where taking a good pitch is scored as a success.

High quality-at-bat rate, low batting average

Encouraging, and the one pattern that should not change your practice plan. Your hitters are competing well and the results have not arrived. Tell them that, show them the number, and keep doing what you are doing. This is the situation where a coach without effort data typically panics and rebuilds swings that were fine.

One player’s rate falling over several games

A trend on one player is worth a conversation before it is worth a drill. Something is usually going on — a mechanical change, a confidence problem, something outside baseball entirely. Catching it in week two is a different conversation from noticing in week six.

Hustle numbers dropping while at-bats hold up

Almost always a culture signal rather than a skill one, and often it tracks with the standard slipping in games that are already decided. Address it directly and immediately, because effort norms are far easier to maintain than to rebuild.

A practice plan built from the record

Concretely, here is a Sunday review that takes about fifteen minutes and produces Monday’s plan.

  • Look at the last four games, not the last one. One game is noise; four is a signal.
  • Start with team‑wide rates. Is this a roster problem or two players? The answer changes whether Monday is a team block or individual work.
  • Find the biggest gap between effort and outcome. That gap is where encouragement is warranted and intervention is not.
  • Pick one thing. A practice that addresses four weaknesses addresses none of them. One block, done properly.
  • Write down what you expect to change. Then check it in three games. This is the step everyone skips, and it is the only one that tells you whether your coaching is working.

Then re-run the lineup

One more thing follows from the same review, and it is easy to forget: your roster’s numbers have changed.

On‑base and slugging percentages move every weekend, and the optimal batting order moves with them. A lineup that was right in April is not automatically right in June — a player whose on‑base percentage has climbed forty points probably belongs higher than where he is hitting. Re‑running the optimizer takes seconds and closes the loop.

That is the whole cycle: optimize before the game, track during it, review after it, teach on Monday, and re‑optimize when the numbers move. How the two apps work together.

The honest caveat

None of this makes coaching a data exercise. The most important things you do on a Monday — whether a struggling kid feels like part of the team, whether the standard is being held when nobody is winning — are not in any of these numbers and never will be.

What the record does is stop you wasting the part of the job that is measurable on whatever you happen to remember from Saturday.