I just uploaded a 1‑page Post‑Game Parent Guide I’ve been using with teams and Compete Code families. The goal:Turn car rides from emotional autopsies into simple, numbers‑based check‑ins that actually help your kid compete better. Inside the one‑pager: - 4 go‑to post‑game questions: So you’re not scrambling for “the right thing to say” after a tough game. - “Say this instead of that” swaps: Exact phrases to replace:“Why didn’t you play like you do in practice?”“You disappeared out there.”…with questions that point them back to their bottleneck and behaviors, not their identity. - The “3 numbers, 1 plan” car‑ride rule: A simple structure to keep conversations short, specific, and forward‑focused: 2–3 scores (compete, bottleneck behavior, bounce‑back) → 1 thing to aim at next game → done. If you’ve ever left the rink thinking,“I want to help, but I don’t know what to say without making it worse,”this is for you. Download it, print it, and try it after the next game. Then come back here and drop what changed for you and your athlete. I have linked it here but you can also find it in classroom in the parent section.

Car Ride Script (Parents) This is a simple 3+1 question script you can use after every game to keep the ride home calm, useful, and aligned with Compete Code. Instead of “Why didn’t you play like you do in practice?”, it helps your athlete focus on: - Their one Compete Code rule - How well they did on that rule (1–5) - One clear focus for the next game - (Optional) Whether they filled out their tracker - Use this every game. Same questions, every time. It keeps the conversation on controllables and behaviors under pressure, not just the scoreboard. Parent Script Link

Compete Code Leaderboard Legend (Week-to-Week) GAME READY Meaning: Consistent. Reliable. Coaches can trust you in tight minutes. Numbers look like: Mostly 4–5s, minimal drops, strong game-to-practice carryover. Behavior: Resets fast, makes simple plays under pressure, stays engaged. BUILDER Meaning: The system is working, but it’s still being installed. Numbers look like: 3–4s with some swings, visible improvement trend. Behavior: You’re attacking the bottleneck, but not automatic yet. LEAK Meaning: One bottleneck is dragging everything down. Numbers look like: 1–3s or big collapses on the key metric (often a “hinge” stat). Behavior: When the bottleneck fails, other categories fall with it (story runs, feet stop, panic shows up). BREAKOUT Meaning: Big week-over-week jump. New floor. Numbers look like: Multiple metrics up +0.5 to +1.5, fewer lows, strong game proof. Behavior: You didn’t just “play well”—you executed the rule repeatedly. CONSISTENCY KING / QUEEN Meaning: Lowest variance. Same player every day. Numbers look like: Tight range (ex: 4,4,4,4) instead of 5,2,4,3. Behavior: Standards > feelings. Metric Symbols (Quick Read) ✅ Strength = already a weapon / stable high scores ⚠️ Needs reps = inconsistent / not reliable yet 📈 Improving = trend is going up week-over-week ⬇️ Leak = where the loop wins (this stat pulls others down) “Proof” Terms I Use a Lot Floor = the minimum standard you must hit each game (non-negotiable). Ceiling = your best possible night (nice, but not the goal). Carryover = practice habits showing up in games. Loop = mistake → story → hesitation → more mistakes (what you’re trying to shorten). Bottleneck (hinge metric) = the one stat that controls the rest (fix this and everything rises). If you tell me the exact labels you’re using on your sheet (ex: Game Ready / Builder / Leak / Breakout etc.), I can match the wording 1:1 to your spreadsheet so it’s perfectly consistent.

Let's see what OHA brought this week!

Please see the tables attached for week 1 leaders 1) Overall Compete Code Leaders (Top 5) - Table is attached, pay attention to the tiers listed below Compete Code Score Rule Weekly average (0–5) = average of all micromoment ratings submitted that week - blanks = ignored (no penalty, just not counted) Tiers - 4.5–5.0 = Unbreakable - 3.8–4.49 = Game-Ready - 3.0–3.79 = Builder - <3.0 = In The Lab (private) - 2) Ironman Streaks (tracking consistency) - 2nd table attached Metric: number of days with submitted micromoment ratings 3). Fastest to Submit Monday (speed) - listed below 1. Marcus 2. Ben 3. Brayden 4. Ethan 5. Linkin