Monday, November 6, 2017

The art of gracefully declining work requests

Pressures at work often compel us to take on terrible tasks well outside our job description.

How do you say no—politely—without causing irreparable reputational harm? An infographic from GetVoIP offers tips on how to graciously decline, defer and delegate untimely work requests.

The infographic opens with reasons for saying “no.” Consider:

  • Fifty-three percent of Americans feel burned out or overworked.
  • Forty-nine percent of workers feel that providing more time to complete tasks would reduce burnout.

The graphic says those who lighten their load can expect:

  • Higher-quality work
  • A better work-life balance
  • The ability to hit deadlines
  • The confidence to say “no” more often

Of course, less work also means less stress, better focus and higher productivity. It’s great to be a team player, but what good does it do if you end up overloading yourself? Shoddy work doesn’t help anyone.

[RELATED: Modernize your intranet to increase collaboration and productivity in the new digital workplace.]

According to the graphic, it’s best to take a pass on a project if:

  • The task will make your other projects suffer
  • The new project will hurt the company
  • You’re not the most qualified person for the job
  • You can’t realistically meet the deadline

The trick is saying no without seeming rude, lazy or uncooperative. The infographic offers several suggestions for tactfully passing the buck, including tips to “be honest,” “offer an alternative” and to “know your availability.”

It’s also crucial to ask for help when you need it, to delegate when necessary and to “reinforce your willingness to help in the future.”

Declining work is always a tricky matter—especially when you’re understaffed or worried about layoffs—but your well-being should take precedence over your workload. Remember, you can do only so much at once.

For more tips on the art of saying “no,” check out the infographic below.



from PR Daily News Feed http://ift.tt/2yBT9XV

No comments:

Post a Comment