Learning to say NO

Gabriel Toma - Oct 17 - - Dev Community

In the early stages of your career, saying yes can be a great strategy. It builds trust, shows you're capable, and gains you allies. It opens doors. But eventually, the constant "yes" becomes a burden. It dilutes focus and breeds burnout.

As I grew into management, I learned that saying no wasn't just acceptable - it was essential. "Can we squeeze in one more task?" No. "Can you prioritize this last-minute request?" No. Protecting my team means protecting their time, their focus, and their energy.

In the past, I said yes to all of the above. And it felt right at the time. But over the years, I realized that each "yes" was slowly breaking my focus and shifting my team away from its core objectives. Saying no became my way of defending the team's path. And it's not about being difficult. It's about being disciplined.

People will always push for more, it's human nature. But it's not your job to please everyone.

Stand firm. Stick to the plan. Say "no".

Once in a while, say yes to remind them you're still on their side.

If this resonates with you, discover more on my blog!

. . . . . . . . . . . . . . . . . . . . .