Saying No to ‘No’

A serious question to all managers out there: Why is “No” your favorite word?

Do you really think that by saying you won’t do it, and/or you won’t support it, means that the project won’t happen?

Let me let you into a secret: a manager’s ability to stop a project just by saying ‘no’ went out with Netscape Navigator.

Saying No Doesn’t Mean It Won’t Happen

When you say no, you don’t stop the project. All that happens is you lose any chance to ensure your department’s priorities get considered.

By saying an ‘no’, you’re maximizing the cost of the fix and looking like an obstructionist – both at the same time.

If you want to leave the project’s cost and effort in other departments’ hands, that’s fine. But participate enough to keep the project from fallout raining down on your department in the future.

Of course it would better if you got actively involved in the project yourself. But, hey, at least this way you’ll have a say in how things go. You’ll know more about what may go wrong.

Perhaps you’ll have one less mess to deal with this time next year.

Assuming that you haven’t already been fired by then, for being part of the problem.

( Originally published on the KEXINO small business marketing blog )