How it works
The same five steps after every game.
It is not a stat sheet, a video-breakdown tool, or a player report card. feedbackedge is a structured, game-by-game alignment tool that keeps player and coach reading the same game.
-
01
Before each game
Choose 2–3 things to watch
Before the game, player and coach confirm the same two or three observable focus items. The focus locks at puck drop or when reflection begins.
-
02
After each game
Player reflects privately
After the game, the player records a score or Could not assess and optional context. The coach cannot see this answer early.
-
03
After each game
Coach reflects privately
The assigned coach records an independent score or Could not assess and observable feedback. The player cannot see this answer early.
-
04
After each game
Both answers reveal together
Only after both complete reflections are submitted do both perspectives appear together. The difference is neutral, not a player grade.
-
05
After each game
Choose the next move
Player and coach review the reveal and choose one specific next action, or explicitly record that no action is needed.
One game, end to end
What a single reveal looks like
Two independent views of the same observable moment. The scores open a conversation; they do not rank the player.
One game, in practice
Illustrative · no real player data
Scan before receiving the puck
What good looks like
Shoulder-check before receiving on at least 4 of 5 clean retrievals
Player reflection
6
Partly met
Coach reflection
8
Fully met
Right person · right place
Who uses what
Every role works in a browser on the device they already carry. Nothing to install.
-
Any browser
Head coach
Creates the team, invites everyone before game one, checks the roster, creates games, and assigns assistant coaches.
-
Any browser
Assistant coach
Joins the existing team and reflects only on players assigned by the head coach.
-
Any browser
Player
Joins the team, sees the shared game focus, and completes a private self-reflection after the game.
Bring the workflow to your program.
Pilots run with a named organizer, a real roster, and a defined start and end. Ask what a controlled pilot would involve for your team.
In the first email, describe only the program and the workflow problem. Do not include player names, private reflections, screenshots, team codes, or health information.