Super Specific Feedback: How to give actionable feedback on work output

👋 Hey, it’s Wes. Welcome to my weekly newsletter where I share frameworks for becoming a sharper operator, rooted in my experience as an a16z-backed founder. If you’re interested in sponsoring this newsletter to reach 30,000+ thoughtful operators, fill out this form and I can share more. This week, we’ll dive into how to give detailed and actionable feedback on work output. Get “permission” and sell why getting lots of feedback benefits them. Explain the “why.” Avoid the shit sandwich. Share positive feedback. Aim for being tactical, actionable, concrete, and specific (TACS). Structural feedback first, line edits second. “I believe you were trying to do x, and if so, this part fell flat because y.” Anytime you’re diagnosing, share what you noticed. Use suggested edits. Show a before and after. Use comments. Develop shared language. Annotate screenshots for anything visual. Mention if your feedback is stylistic or a pet peeve. Record a screen share video or voice memo. Balance what's e

👋 Hey, it’s Wes. Welcome to my weekly newsletter where I share frameworks for becoming a sharper operator, rooted in my experience as an a16z-backed founder. If you’re interested in sponsoring this newsletter to reach 30,000+ thoughtful operators, fill out this form and I can share more. This week, we’ll dive into how to give detailed and actionable feedback on work output. Get “permission” and sell why getting lots of feedback benefits them. Explain the “why.” Avoid the shit sandwich. Share positive feedback. Aim for being tactical, actionable, concrete, and specific (TACS). Structural feedb