The power of saying “NO!”: A Software Engineering Superpower
Tags: codenewbie, computerscience, webdev, powerfuldevs
Published: 2021-02-01 19:54:49

_While becoming more proficient at coding and learning new frameworks definitely helps, there are some key **superpowers** which can make you stand out even more as a distinguished engineer. These help you not only to avoid burnout but also have long term continued success._

`In this article, we will take a look at the “power of saying NO!” superpower — having the flexibility and willingness to stand by what is important and speak your mind at any given time in that regard.`

To expand on this, here are the **key benefits** that you unlock by practicing this superpower:

**1. Increased focus**

A [study reported via BBC](https://www.bbc.com/news/health-38896790) a few years back shared an eye-opening stat.

> The average focus time of a human is now 8-seconds, down from 12-seconds, over a mere span of 15 years & is shorter than that of a goldfish!!!

With such a short attention span, finding ways to stay focused on the task at hand is more important than ever.

If one simply continues to have a people-pleasing attitude by being “always available” to work at anything that is thrown to them, they will end up doing actually less. This might seem confusing but in reality, they will be [spreading too thin](https://medium.com/javascript-in-plain-english/key-point-1-spreading-too-thin-5-things-i-wish-i-knew-as-a-software-engineer-9eee39b40553) across multiple things at once while completing or getting done with any one thing in its entirety.

The key point here is to have a questioning attitude. The questioning has to be both internal and external.

* Internal — asking whether you are compromising something more important and urgent at hand/ in progress by simply trying to stay in someone’s good books? asking whether this is something you can delegate to someone else?

* External — asking whether this is the top most priority? It might be a top priority to the person asking but is it truly important & urgent for the business, project, team etc.? asking details around what is being asked from you and why specifically only you?

If there is not a satisfactory answer to any of the above questions or similar, it should be within your power to decline or postpone that request in that moment. While doing so, it must be done in a polite manner with at least some high level context on why this ask is a lesser priority for now.

The above will help you to stay focused on your prior commitments, finish something completely and then move on to the next best thing.

[Multi-tasking could be multi-distracting](https://www.optimisticlearner.com/multitasking-distracted-attention/)

> Too much context-switching or multi-tasking might actually be distracting and cause more harm then help

**2.Uplifting your team knowledge**

The idea behind this is straight-forward and as stated. When you say “no” to a specific task/ type of request that you have been the point-person over a period of time, it creates **opportunity**.

* It creates an opportunity for someone else to level up, get skilled at something new. This chance to learn something critical or be that alternate shoulder to tap on can be of immense value.

* It creates an opportunity for you to mentor and coach. There cannot be a more apt situation to spread knowledge and share your expertise than this specific one.

> Knowledge is power. Knowledge shared is power multiplied. - Robert Boyce

**3. Growth opportunities**

The “growth” in this benefit is in the sense of your individual growth. If you think about it, while you feel great that you are always asked to help with a specific type of request, need — it creates a narrow niche for you over time. The word to stress is “specific”.

It totally depends on whether you would like [to stay a specialist or become a smart generalist (or better a versatilist!)](https://medium.com/javascript-in-plain-english/mastering-a-niche-vs-smart-generalist-5-things-i-wish-i-knew-as-a-software-engineer-part-5-5-7c835a31ad22). In general, if you try to balance doing the same type of work with learning something new or expanding your area of focus, it could lead to more growth opportunities for you.

I personally would have a core area of expertise but equally be capable and aware of contributing to other aspects of product development vs being confined to an area, a type of work. Not only it gives you more interesting problems to work on, it gives you even bigger opportunities to collaborate while becoming a more favorable member to have on a team due to your ability to work and contribute in more areas.

**4. Not being _taken for granted_**

This is more important than ever. People, teams and organizations constantly fail to realize that “nothing lasts forever”.

If you feel awkward suddenly declining a request you have always helped with, think of this — you are actually helping the team by saying “no”. _Do it for the greater good._

Unless the situation does not reach to a point where one is not taken for granted, they will no explore creative ways to solve the task at hand. There is a strong possibility that many teams and organizations continue to be “blind sided” by this notion.

_Just because there is someone now that is handling anything directed at them, does not mean they will continue to be there forever or they will politely keep doing whatever they are told to forever._

--------

I would be more than happy to chat and let me know your thoughts or current focus areas in the comments.

As always, feel free to connect with me on [Linkedin - Anand Safi](https://www.linkedin.com/in/anandsafi)