The meeting invite showed up at 4:52 on a Wednesday in June: a new recurring call, every Wednesday at 5:30 p.m., with a partner team two time zones west. Wednesdays are one of Ben's late nights at the clinic, which makes them my pickup night all summer, and day camp pickup ends at 6. From Huntsville, 5:30 doesn't work. It barely works from my driveway.
A younger version of me would have accepted it and spent the summer paying late-pickup fees and apologizing. This summer I said no three times at work. Nobody called me difficult, at least not to my face, and all three projects are fine. Here are the requests, the exact words and what I offered instead.
Three requests I turned down
1. The 5:30 Wednesday call. I declined the invite and sent this to the organizer: "I can't make 5:30 on Wednesdays; that's my pickup night. I can do 8:30 on Thursday mornings, or I can send a written update by 4 every Wednesday so you have it before your call. Which helps you more?" She picked the written update. In July the call moved to Thursday mornings anyway, because two other people had the same problem and hadn't said so.
2. The fall picnic committee. A coworker stopped by my desk and said, "You were in HR, you'd be perfect for this." I did plenty of event planning in my old jobs, and I'm trying to be known here for project work. What I said: "I'm going to pass on the committee this year. What I can do is send you the planning checklist I used for years. It's two pages and it has the vendor timeline on it." She used the checklist. The picnic is in October, and it will be fine without me holding the sign-in sheet.
3. A second project's weekly report. A PM on our team went on leave for six weeks, and my manager asked if I could take over the weekly status report for that project on top of my own. Here's what I said: "I want to help, and I can't do both well. If I take the report, which deadline on my project should slip? Or I can cover the Thursday client call for those six weeks and someone else handles the report." She split it. I took the calls, a coworker took the report, and my own schedule didn't move.
What the words have in common
Looking at those three, the pattern is boring, which is why it works:
- Say no in the first sentence, not the fourth.
- Give one short reason. Not a paragraph about your life.
- Offer something specific that you can actually do.
- End with a question, so the other person gets to choose.
What I left out matters too. I didn't say "I'm so sorry." I didn't say "I'm just slammed right now," which is vague and invites a debate about how slammed. And I didn't wait. The 5:30 call got its answer within an hour, before anyone built a schedule around me.
From the HR side
In HR, I never once had a file on someone for saying no. I had plenty of files on people who said yes and then quietly missed. "Difficult" showed up in complaints when the no came late, came as a surprise or came with nothing attached. The same answer delivered on Monday with an alternative barely registers. Delivered on Friday afternoon, after someone counted on you, it becomes a story people tell.
It took me fourteen years to learn this. At the plant, I ran the holiday food drive three years in a row because nobody else raised a hand, and I said yes to so many quick favors that my actual work happened after 5. It took a career change and a 38-minute commute to make me count my hours like they were money. This was also the summer I stopped answering work email after 8 p.m., and it turns out that's the same muscle.
Saying no hasn't made me less helpful. It's made my yes worth more, because when I say it now, I mean it and I'll do it well. Your office may work differently, and I can only tell you what happened in mine. But I'd try the four steps once, on something small, and see who notices.
