How to Use the App

One of the biggest challenges in analytics is not building the model. It is helping people use it correctly. The best way to use this app is to think in layers. Start broad, then narrow A good workflow looks like this: 1. Start on the schedule, live games, standings, or team page. 2. Identify the game, team, or player you want to understand. 3. Use team and player pages to form an initial hypothesis. 4. Drop into the game page or line tool when you need to inspect the "why." For example: - If a team has been winning a lot, go to the Teams page and see whether that success is backed by chance quality or finishing. - If a player's point totals look weak, go to the Skaters page and see whether the underlying play-driving data tells a different story. - If a line is crushing territorially but not scoring, use the Line Tool and game reports to see whether the problem is finishing, shot quality, or usage. - If a game result looks surprising, open the game page and inspect the play-by-play, shifts, and report tabs. The app works best when you move between these surfaces instead of treating one chart as the whole answer. Use filters intentionally A lot of pages allow you to filter by: - Season - Season state - Strength state - Rates vs totals - xG model - Minimum thresholds like games played or time on ice These are not cosmetic controls. They change the question you are asking. If you choose totals, you are asking who produced the most overall value or volume. If you choose rates, you are asking who performed best on a per-minute or per-game basis. If you change strength state, you are separating even-strength results from special-teams results. If you set a minimum threshold, you are deciding how much you want to trade inclusiveness for reliability. That matters because hockey is a small-sample sport. A player can look elite in 100 minutes and ordinary in 1,000. The app gives you the tools to manage that tension, but the user still has to decide what kind of comparison is fair.