Speak in the affirmative: "Do this" versus "Don't do that"
👋 Hey, it’s Wes. Welcome to my newsletter on managing up, leading teams, and standing out as a high performer. To level up faster, check out my 2-day course on Executive Communication & Influence. You’ll learn alongside mid-career operators from orgs like Netflix, Stripe, Figma, Anthropic, etc. → Save your spot in the July cohort
I originally published a version of this essay in September 2015, and have since expanded it. Enjoy.
Read time: 4 minutes
It’s to your benefit to be as clear as possible when you speak or write, because clear communication helps you get what you need.
One way to do this is to speak in the affirmative, rather than the negative.
If you speak in negatives, your recipient has to take an extra mental step.
To understand “Don’t do that”.... you have to think about “that,” then reverse it to do the opposite.
A better way is to say, “Do this.”
If you can save your recipient a mental step, you’re doing a kind thing. Most people have too much they need to mentally process, so avoid adding more friction than you have to. Reducing cognitive load applies in UX design, marketing call-to-actions, or requests to your coworkers.
Speak in affirmatives when giving feedback
A diving coach might say, “Don’t flex your feet,” which can be confusing when you’re mid-air doing a reverse double-somersault tuck into the water.
If they phrased in the affirmative, they would say, “Point your toes.”
Saying don’t can sound reprimanding with a finger-wagging undertone. This makes you seem unnecessarily negative, even if you're justified in what you’re saying.
This is a practical issue. If the person you’re giving feedback to starts to get defensive, they’ll stop hearing what you’re trying to say.
Yes, the person receiving feedback should stay open-minded and remember to listen. But as the person giving feedback, it’s also your responsibility to think about how you’re sharing the information. This is a much larger topic, but stating things in the affirmative is a simple way to improve both the clarity of what you’re saying and the emotional tone.
Let’s say you’re giving a junior team member feedback on how to present to your CEO.
🚫 “For a 30 minute call, don’t spend 25 minutes on backstory. Don’t delay getting to the meat of what you want to discuss.”
✅ “For a 30 minute call, spend 2-3 minutes on backstory. Then focus on the meat of what you want to discuss.”
In the “before” example, the focus is on spending the majority of time on backstory, which is not what you want your recipient to think about. The focus is also on what they’re doing wrong.
You want your team member to visualize themselves doing things right. We’re applying the power of visualization to workplace scenarios. Encourage people to imagine going in the direction you want them to go in.
Remember: what you give airtime to will expand in your recipient’s mind.
Fill the void
There may be times when you have to address the negatives. Don’t do mental gymnastics to avoid saying the negative thing.
Instead, say what you don’t want the person to do, then say what you want them to do.
🚫 “Don’t disappear for three weeks then show the final product.”
✅ “Don’t disappear for three weeks then show the final product. Share what you have in a few days, so we can make sure we’re aligned.”
If you only say what not to do, you end up leaving a void. A void begs to be filled, and your recipient might fill it with an idea you disagree with. Always fill the void with what you want your recipient to think.
You’ll sound confident, instead of apologetic
Speaking in the affirmative applies to stating what you’re able to do.
Let's deconstruct these two statements:
🚫 “I can only meet between 11-3pm.”
✅ “I can meet between 11-3pm.”
When you say “I can only...” it sounds like you THINK you should be more available. Or that your counterpart has a right to want you to be more available.
This puts you in an unnecessarily weak position. If you can meet between 11-2pm, own it. If the person pushes back, you can explain further, but there’s no need to start off with insecure vibes.
Try this today
Notice the next time you start phrasing an idea using a negating sentence structure of “Don’t do X” or “I can’t do X.” Spend an extra few seconds to see if you can flip it around to say the same thing in the affirmative.
Thanks for being here, and I’ll see you in two weeks on Wednesday at 8am ET.
Wes
PS For further reading, check out how to avoid incepting negative ideas.
✨ Course update: May cohort is sold out
The May cohort is sold out, but good news: A new July cohort is now open for enrollment. The course dates are July 16 -17, 2026.
If you’re wondering “Is this for me?” check out these student reviews from last month’s cohort:
“Extremely worthwhile course. The opportunity to see other students’ responses and spawn new ideas on framings / variations from one’s own typical communication style made the difference.”
- Alice Rhee, Sr. Staff UX Researcher @ Mozilla
“I knew this course would be valuable for my day-to-day work and for how I want to grow in my career, and it did not disappoint. The frameworks around executive communication and influence immediately changed how I think about structuring ideas and driving alignment. The additional material provided is a gold mine. I can already see myself coming back to it for years to come.”
- Denny Beeler, Software Engineer @ Progressive
“Excellently structured, detailed, and thoughtful course with a wealth of actionable insights. I enjoyed the hands-on approach: deliver exercises quickly then review each other’s, and learn from each other’s strengths and weaknesses together. The course was energizing and I feel confident in taking action on what I learned.”
- Daniella Latham, Principal Product Marketing Manager @ Atlassian
“This course was a fantastic use of my time as a cross-functional communicator and leader. Not only was it packed full of extremely useful takeaways, but it was also very efficiently run. Wes is a fantastic communicator and her application of best practices was digestible and relatable to my day to day. I look forward to putting the many things I learned here into practice.”
- Anna Mumford, Director, PMO @ Hims & Hers
“This course was rammed with useful and practical content for all facets of work within an organization with others. How to explain yourself more effectively, be more succinct, and generally start to move with more ease through work.”
- Charlotte Hilton, Sales Account Executive @ Harvey AI
If you’ve been thinking about joining, I hope to see you in class. Learn more about the course.
Connect with Wes
Is this your first time here? Subscribe (it’s free)
Follow me on LinkedIn for more insights
Learn more about 1:1 coaching to sharpen your executive presence
✨ Intensive course: Improve your ability to sell your ideas, manage up, gain buy-in, and increase your impact in a 2-day workshop. Over 2,000+ tech operators have taken this course, and every cohort so far has sold out. → Save your spot in the July 2026 cohort



As a writer, editor, and writing teacher, I think about this distinction between don't and do a lot. In writing classrooms, how do you get students to give feedback to one another when they don't necessarily know how to fix something that isn't working? Every reader has valid responses to drafts but not every reader has the vocabulary to say why they are bumping on something. Most of are experts in reading but novices in articulating what would be better. In the writing classroom, I'll highlight this tension: It's not your peers' job to tell you how to fix it. It's just their job to say that they're bumping, and it's your job to hear that without getting defensive. It's my job as the teacher to articulate the affirmative action. But in other scenarios -- say a manager directing work on a new project -- the challenge is that it takes a lot of expertise to even know what someone should do vs. what they should not do, and then it takes a lot of reflection to know how to put that into words for someone else. Few people have had the time to develop those mental models and vocabulary in their domain. They may know how to do X themselves, so they know when other attempts are not quite right. But they may not know how they know how to do X themselves.