Saying yes to everything got you your first promotion. Saying yes to everything with a family will get you burnout, resentment, and a reputation as the person who never pushes back. The skill isn't saying no. It's knowing which yes advances your career and which one just fills your calendar.
Why 'yes' stops working
When you were starting out, every project was an opportunity. Take on the extra work, stay late, volunteer for the committee nobody wants to join. It made sense then. You were building a reputation, and your time was more flexible than it is now.
Then you had a kid. Or two. And the math changed permanently. There are still only 24 hours in a day, but now a significant chunk of them belong to someone who can't feed themselves. The career strategy that worked at 25 doesn't work at 35 with a toddler and a school-age child, and pretending it does is how working parents end up in the emergency room with chest pain they mistake for a heart attack but is actually a stress response.
A 2025 KPMG survey found that 76% of working parents say parenthood increased their work motivation. That's not surprising. Parents have more reason to perform well: more financial obligation, more to protect, more to prove. But higher motivation paired with unchanged hours creates a pressure cooker. The release valve is selectivity about what gets your energy.
The requests that deserve a yes
Not all work requests are equal, but they tend to feel equally urgent in the moment. Before you agree to anything that wasn't already on your plate, run it through three filters.
Does this advance a goal you've already identified? If you're working toward a promotion, a project that gives you visibility with senior leadership is worth the extra hours. A project that adds work without adding visibility isn't. Be honest about the difference.
Will this develop a skill you actually want? Being asked to lead a cross-functional team is different from being asked to organize the quarterly potluck. Both take time. Only one builds your resume. If the skill isn't one you're interested in developing, the experience won't feel valuable enough to justify what you're giving up at home.
Is the compensation (formal or informal) proportional? This includes raises, bonuses, schedule flexibility, and political capital. If your manager asks you to take on a major deliverable and offers nothing in return, not even a public acknowledgment, that's information about how your work is valued.
The requests where no is the right answer
If the project will compromise your quality on existing commitments and your manager won't redistribute work, that's a no. You can phrase it as "I'd need to deprioritize X to take this on. Which would you prefer?" This makes your manager solve the resource problem instead of silently absorbing it yourself.
If the work isn't stimulating, doesn't build relevant skills, and the only reason you're being asked is because you're reliable, that's also a no. Being reliable is good. Being the person who gets dumped on because you never push back is a career trap, not a compliment.
The guilt that comes with saying no is real, and it hits parents harder. Research consistently shows that working mothers face a maternal wall bias where any boundary-setting is interpreted as reduced commitment. Knowing this doesn't make it easier, but it does make it clear: the guilt isn't a signal that you're wrong. It's a signal that the system penalizes parents for having limits.
How to say no without damaging the relationship
The language matters less than the delivery. Be direct, be brief, and offer an alternative when possible.
"I don't have the bandwidth for this right now, but I can revisit it next quarter." That's a complete answer. You don't need to explain that your bandwidth issue is because you're managing school drop-offs and a toddler's sleep regression. Your reasons are yours. The professional answer is about capacity, not caregiving.
"I can take this on if we push the deadline on the Henderson project by a week." This is the trade-off approach, and it works well with managers who respect data. You're not refusing. You're making the constraint visible and letting them choose.
"That's not in my area of strength. Have you considered asking Jordan?" Redirecting isn't dumping. It's being honest about fit, and it often gets a better outcome for the project and for you.
The bigger question behind every yes
Most working parents don't have a saying-no problem. They have a clarity problem. When you don't know what you're working toward this year, every request feels like it might be the important one, so you say yes to all of them and end up scattered.
Spend 30 minutes identifying your top two professional goals for the next six months. Write them down. Tape them to your monitor if you need to. Every request that crosses your desk gets evaluated against those two goals. If it doesn't serve either one, the default answer is no unless there's a compelling reason to override.
This isn't about being calculating. It's about being intentional with a resource (your time and energy) that is genuinely finite, and more finite now than it was before you were responsible for keeping small humans alive. The first real step is to identify those two goals before your next one-on-one with your manager.