This week’s tip is more of a mindset technique than a practical strategy, but it’s one that’s been really helpful to me lately:
When someone asks you to do something, and you know you don’t want to do it, say no right away. And when you say no, be polite and direct, no apologies needed.
Stop me if this sounds familiar…
A message pops up in your inbox, or your DMs, or your WhatsApp, or whatever. Along the lines of:
- “I’d love to pick your brain about…”
- “We could really use your help with…”
- “I’d really appreciate your feedback on my… [book, article, business idea]”
- “We’re in desperate need for volunteers for…[cause you probably support but may not have time for”
I’m guessing this resonates, because you know how things get done in this world? By asking busy people.
If you want something done, ask a busy person
The time-honored saying, “If you want something done, ask a busy person,” persists for a reason. Actually a few reasons.
- Busy people are, by definition, good at time management, because they’ve got a lot to do
- Busy people are do-ers, not watch-from-the-sidelines kind of people
- Busy people got that way by getting sh** done. This creates what you might call a reliability loop: “She did that with no reminders, let’s ask her again!”
- Busy people, again by definition, cut through the clutter and focus on what really has to happen, rather than vague “Let’s think about it and meet again” stuff
What happens when you get the ask, and you know that you don’t want to do it?
Some people are naturally good at saying no. A friend who’s very successful in her career recently told me, “Honestly, I say no to almost everything that’s not my initiative.” Great! I’m not one of those people. I hate letting people down. I like to help. I remember the times I’ve needed career advice, or someone to staff the registration desk at a professional association event, or someone to chair a committee that does important work but is also a pain in the tail to work on.
Thus, I have a hard time saying no, and I often feel the need to wrap the “no” in a blanket of explanations that, in my mind, make it easier to accept. “Really busy with XYZ,” “About to leave for vacation,” “Just got back from vacation,” “Finishing up a big project,” “Getting ready for a conference.”
Another maladaptive strategy: I often delay the “no” until either the person who made the request circles back to me, or I get an automated reminder. Hello, it’s Google Workspace! You received this e-mail five days ago, do you want to respond now? (No, but thanks for asking!).
Take advice from Dorie and Guy
I really love both Dorie Clark and Guy Kawasaki. I love them in general and I like what they’ve written on this topic. Here’s a Substack article from Guy, referencing something Dorie wrote.
Here’s what’s helping me:
- Get the no over with. Now. The second you read that e-mail and think, “I really don’t want to do this,” hit Reply.
- Be brief, polite, and direct. It’s not that deep, as people of my daughter’s generation say. You don’t want to do this, and that’s your choice.
Dorie and Guy both extoll the virtues of this approach: you’re not mentally dragged down by the request, and the other person can move on. Guy comments, in my opinion correctly, that people often respond very positively when you say no right away. Like, “Thanks so much for getting back to me so quickly; I honestly wasn’t expecting a response at all!”
How this works for me
Two real-world examples.
Example 1: A colleague (someone I really like as a person) asked me to pitch in on a professional association volunteering project.
I’ve drawn a firm boundary that I am “retired” from substantive association work, and I only do really small things, like a one-time meeting to pick someone who’s going to get an award. I followed my own rule: responded right away. “Thanks for thinking of me! I’m no longer taking on this kind of volunteer project, but it’s a great initiative! Good luck with it!”
The person (credit for persistence!) messaged me again, emphasizing that it wasn’t a big commitment. Did I waffle and feel guilty? 100%. But again, I responded right that red-hot second, “Unfortunately I can’t take this on” (thanks, Dorie, for that wording) “but thanks for thinking of me!” And it was totally fine! I’ve since seen this person IRL and the topic didn’t even come up!
Example 2: Another colleague I really like (I work with nice people, what can I say?) asked me to provide feedback on a writing project. In this case, it was AI-related, and I’m honestly just burned out on thinking and talking about AI. I use AI, I find it really helpful for certain tasks, and I’m kinda done with talking about AI’s effect on the language professions. Plus, I had just done three days of honest-to-gosh Human Translation and it felt incredible.
Read message, hit Reply. “Thanks for the information about this project; it sounds really useful for a lot of people. I’m going to decline because I need a break from thinking and talking about AI, but best of luck with it!” The person’s reply was right out of Dorie’s playbook: “Wow, thanks for getting back to me so quickly, and I totally understand! Hope to work with you on something else in the near future!”
Here’s a challenge for you: the next time you get this type of request, try these techniques and let me know how it goes!

Corinne McKay (classes@trainingfortranslators.com) is the founder of Training for Translators, and has been a full-time freelancer since 2002. An ATA-certified French to English translator and Colorado court-certified interpreter, she also holds a Master of Conference Interpreting from Glendon College. For more tips and insights, join the Training for Translators mailing list!
Leave a Reply