It's true - you can't say no to *all* low-impact tasks. However, whether I'm on a team as an IC or building my own product, it's fair to take a step back and see what tasks are *actually* high-impact versus not. I'm always surprised at how many things I can go ahead and not do, and it won't really matter in the long run.
This point is interesting to me
"I said no to low-impact tasks."
Is this possible? Many times there is work to do that provides low impact and, still, it's work that must to be done.
What do you think?
Great article by the way! 👏
Thank you Marcos!
It's true - you can't say no to *all* low-impact tasks. However, whether I'm on a team as an IC or building my own product, it's fair to take a step back and see what tasks are *actually* high-impact versus not. I'm always surprised at how many things I can go ahead and not do, and it won't really matter in the long run.