The lineup I got wrong

The day I buried my best hitter

I ranked Tuur as a three-star hitter and batted him fifth, because his training attitude was terrible. He showed up late, resisted coaching, and sulked between drills. I let that picture sit in my head while I built the lineup.

What I did not look at was his actual batting average from the previous season: .818, the highest on the entire team. The iScore data was sitting in a PDF I never opened. I let my irritation override the numbers and buried my best hitter in the middle of the order.

After the game, I realized I had punished the kid for being a teenager, not for being a bad player. The real problem behind the attitude was boredom. He was better than the drills we were running.

That was the first information failure: I treated behavior and performance as one thing.

Splitting behavior from performance

Once I saw the .818 in black and white, I stopped pretending my brain could keep everything straight. I changed how I handle attitude flags.

Now, before I even open the lineup builder, I split everything into two tracks:

• Behavior notes: late, sulking, resisting coaching, great teammate, whatever.
• Performance data: AVG, OBP, OPS, defensive grades, actual numbers from iScore.

They live in two different columns. One does not override the other. If a player has a bad week at practice, that does not magically turn a .818 hitter into a .250 hitter on paper. I can still respond to behavior, but I see clearly what I am trading away if I do it inside the lineup instead of outside it.

The attitude conversation now happens separately from where I place a kid in the batting order. Same person, different decisions.

Invisible players on the sideline

The same game gave me a second problem. I also missed the Heja registration cutoff by two hours, which meant Aram and Arpi were invisible to me even though they were standing at the field on Saturday.

I had built my entire 4-inning rotation around 12 confirmed players, and suddenly there were 14 bodies in the dugout. I had to rewrite the lineup on a whiteboard while parents watched.

The information was not actually missing. It was just in the wrong place at the wrong time. The app was strict about the cutoff, but the reality was simple: some kids always show up, whether they tap a button or not.

So now I assume that chaos exists and plan around it. Every Wednesday at 20:01 I build two versions of the lineup:

• One with the registered roster.
• One with the “ghost” players who historically show up anyway.

On game day, I am not inventing a plan in front of an audience. I am choosing between two pre-built options.

Trusting the tool over what I know

The third mistake was more basic. Nikky ended up at first base in inning four because I trusted the auto-generated PDF without checking my own constraint. She has a throwing-distance limitation: no shortstop, no first base. It was a hard rule I had given Claude three times, but I was so focused on the batting order drama that I forgot to proof the defensive sheet.

I now run a manual “violation scan” before any export. I look only for hard constraints: no-pitch, no-catch, no-first, innings caps, injury notes. If any of those are broken, the lineup goes back into the workshop. The tool does not know my players; I do.

The cost of “no data”

William was buried at position nine because I had tagged him “no data” in my star-rating system. Then Saturday’s box score showed him with a 3.000 OPS. I had been looking at the wrong sheet.

That was the moment I stopped using the stars as the primary input. iScore exports now feed directly into the batting order before human judgment is even applied. If the numbers say a kid is raking, the lineup starts from that fact, not from my memory of a random practice.

“No data” is now treated as a red flag, not a safe label. If I see it, it means I am not ready to rank that player at all.

Coaching last year’s team

The deeper error under all of this was that I was still coaching the ghosts of last year’s team. My aces had moved up to U15. I was applying a lineup logic built around experienced, confident players to a reconstruction-year roster where more than half the kids were new.

The information I overlooked was not hidden in a PDF. It was on the field in front of me. The team identity had changed.

I now start every season prep with a “what is true now” reset, not a “what worked before” assumption. New roster, new constraints, new distribution of talent.

The rule I say out loud now

That entire Saturday became my test case for data-driven coaching. I came home, updated the slagvolgorde spreadsheet with the actual stats, and realized I had been wrong about three separate hitters.

Out of that mess came one standing rule I say to myself before I touch a single player’s name:

Numbers don’t lie. People lie. Numbers don’t.

The lineup is still my responsibility. The difference is that I am no longer asking my frustration, my habits, or last season’s memories to do the job that the numbers are already doing quietly in the background.