📎 Webclip
How I give high-quality feedback quickly
The post says feedback has high ROI, but time is the main constraint. Wes argues that you can still give strong feedback in 1-2 hours per week, and that the effect compounds because it helps teams notice what the manager notices.
Reading notes#
- Focus on the 20% of work output that will have the biggest impact, then show how to apply that logic to the rest.
- This approach builds pattern matching instead of fixing every detail yourself.
- If the work is far from expectations, give structural feedback first.
- Ask whether the team should be doing this at all, whether it should be done this way, and why this option matters most.
- Save line edits for after the strategy is aligned.
- Written feedback is scalable, but slower to produce than speaking.
- Voice notes, Looms, and phone calls are useful alternatives when writing would take too long.
- Loom works especially well for feedback with a visual component.
- Even when feedback is verbal, it should still be tactical, actionable, concrete, and specific.
- The process should stay sustainable so managers can keep giving feedback over time.
