Good feedback is specific, kind, and easy to find later. A quick comment on the bench is gone by the car ride home. A short written note tied to a moment is something a player can come back to all season.
Be specific about the moment
Instead of compete harder, point to the shift, the situation, and what you wanted to see. For example: second period, after the turnover, I wanted you to stop and box out instead of chasing.
Specific beats general every time, because the player can picture exactly what you mean.
Balance the correction with the why
Tell players what to do, then tell them why it helps. Buy-in comes from understanding the reason, not just the rule. A note that explains the payoff is one a player will actually try.
Keep it private and organized
In TeamDock, feedback is tied to the player and visible to them and their linked parent, not the whole team. Each note lives in one running file, so development becomes a record you can look back on instead of a stream of lost texts.
Make it a habit, not an event
A couple of short notes a week beats one long review a season. Small and steady is what players remember, and it keeps feedback from piling up into something you never quite get to.