It is the second week of the fall season, and the same question has reached you three times. A parent asked a coach about the makeup-practice policy and got one answer. The team parent gave a different version in the group chat. Now the parent is emailing you directly to find out which one is real. You answer it cleanly and move on, because it is week two and thirty other things have your name on them.
Treat that question as a readout. Every time it comes back to you through a new door, answered a little differently by whoever caught it, the program is telling you something specific: the makeup-practice policy was never built as a system, so four people reconstruct it from memory, slightly wrong, on demand.
The instinct in the first two weeks is to firefight, and it is the right instinct. Answer the question, correct the group chat, run the dropped handoff down yourself, keep the season moving. A director who stops to hold a full systems review in week one is solving the wrong problem at the wrong time. The deeper move is to notice that these two weeks are the only stretch all year when the gap between the systems you think you run and the systems you actually run is fully visible, and to read the friction on the way past rather than only clearing it.
By October the gaps will have closed over, not because you fixed them but because everyone will have memorized the workaround. The parent will have learned to email you directly, the coaches will have settled into who answers what, and the season will run on a set of unwritten patches that live in people's heads and leave with them the day one of them takes another job. The first two weeks are the last time those gaps are visible before they get papered over.
What the Friction Is Actually Telling You
The readout works because friction in the first two weeks is not random. Each kind of recurring snag points at a specific part of the program that was never built as a system, only improvised well enough to survive last season. Three kinds show up almost every year, and each one names its own fix.
The Question That Comes Back
A question that reaches you more than twice in two weeks is a policy with no home. The makeup-practice question, the which-field-this-week question, the what-happens-if-we-miss-a-tournament question: each one comes back because the answer lives in a person instead of in a place a parent or a coach can reach without going through you. The tell is that the answers vary. When three people give three versions, the policy was never written down anywhere, only remembered, and memory drifts. The fix is one answer, in one place, that everyone can point to without checking with you first: a short parent-facing FAQ, a pinned message in the team channel, a single page a coach can forward on their own. The discipline is less about writing the policy than about making the written version the only version anyone quotes.
The Handoff That Drops
Something falls in week one because two people each assumed the other had it. The check-in table has nobody running it the first Saturday. The new family never got its welcome email because the coach thought the office sent it and the office thought the coach did. Nobody dropped the ball out of carelessness, because the ball was never handed to anyone in particular. A dropped handoff marks a responsibility that was assumed instead of assigned. The fix is an owner with a name rather than a reminder to communicate better: for each handoff that slipped, write down the task, the person who owns it now, and the moment that triggers it. A responsibility with one name attached survives a busy week, while a responsibility everyone is sort of watching does not.
The Decision Nobody Owns
The third signal is a coach or a site lead who stops mid-week and asks who decides something. Can a kid play up an age group for one game. Do we move practice for the heat or cancel it. Does a late registration get in after the roster is set. The pause before the answer is the useful part, because it means the decision has no owner and gets made by whoever is standing there when it comes up. That is how a program ends up with three different heat calls at three different fields on one afternoon, each one reasonable, none of them pointing to the same rule. Give each recurring decision a single, named owner, so the answer stops depending on who happens to be on site. Some of those owners are your site leads, some are your coaches, and a few are you.
Running the Readout Without Stopping the Season
Here is the part that is easy to miss when the season is already moving: none of this has to get fixed in the first two weeks. Trying to would pull you off the field at the moment your presence matters most. The readout is a logging exercise rather than a repair project.
Keep one running note, shared with your site leads, open for the first two weeks. One line per snag: what the friction was, who hit it, and what they needed that they could not find. No solutions in the moment, just the entry. A repeated parent question, a dropped welcome email, a coach asking who decides the heat call, three lines, thirty seconds each. The season keeps moving while the note fills in.
At the end of week two, that note is your map. Block thirty or forty minutes and sort every line into the three kinds you now know they are: repeated questions become one written source everyone points to, dropped handoffs get an owner and a trigger, and ownerless decisions get a decider. Most programs find eight or ten lines, and most close in a single sitting once they are written down, because seeing the gap while it was still visible was always the hard part.
Do that, and the question that reached you three times in week two becomes the last time it has to. The parent gets one answer, from anyone, the same every time. The season stops being held together by what four people happen to remember and starts running on something you can actually hand off, which is the only version of the program that outlasts the people currently running it. Open the note before this Saturday, while the gaps are still visible.
