Gus

HOW TECHNICAL WRITING IMPROVES SCOUTING REPORTS The single biggest improvement I've made to my scouting reports came from studying technical writing. Technical writing is designed to eliminate ambiguity and drive decisions. This is essentially what scouting reports are meant to do. – Translate complex observations and technicalities about a player into clear and concise language. – Build a case for or against taking action on the player. A scouting report is an argument, not a description. You are not just describing a player in detail, you are observing and informing a future decision about that player. Every sentence should either advance that argument or provide evidence for it. Most scouting reports I read do not do this. They are adjective-heavy, vague, and assume the reader already knows what they mean. So often I see things like: – "Excellent pace" – "Inconsistent on the ball" – "Good defensive work rate" These are just labels without substance. The weak link in scouting is rarely the observation itself. It's the transmission of the observation - from brain to text, and from text to reader. So many insights are never discovered. Technical writing fixes this. Context-rich. No fluff. Judgments anchored in observable behaviors described with actions, not concepts. An economic use of language where no word is wasted.