- Saying "no" at work is sometimes necessary. The key is knowing when to push back.
- Rejecting requests is a balancing act - you'll need to weigh your current workload and team goals against the needs and wants of others.
- Some factors to consider include the amount of work or effort that would be required, your values and time commitments, and the deadline.
For my first job out of college, I worked as a writer at a financial startup in downtown San Francisco. It was one of those offices that had an open floor plan, catered lunches, unlimited paid time off ... and sky-high expectations.
Everyone seemed to be working on interesting side projects, helping out their coworkers, leading team meetings, and brainstorming hackathon projects every day. It was inspiring to see people who were so engaged with their work. So like Shonda Rhimes, I decided to suppress my introverted tendencies to have a "year of yes."
But juggling the needs and wants of my boss, my team, my coworkers, and the company alongside my own was exhausting. At a certain point, something had to give, and I had to learn to say "no." The key was figuring out when to push back.
Here are nine things it's totally reasonable to say "no" to at work: