← Rajeshkanna Viswanathan
Teams and leadership

Say No, but Say It Well: The Skill of Raising Your Hand

July 2026 · 4 min read · Communication, Courage, Leadership

Some of the hardest sentences to say at work are also the shortest. No. This will not work. I think we are going in the wrong direction. Plenty of capable engineers can see the problem clearly and still cannot bring themselves to say it out loud, and in the kind of work I do, that silence is not harmless. It is how avoidable failures happen. Learning to say no, and to raise your hand when something is wrong, is one of the most important professional skills there is. Learning to say it well is the harder half.

Why the raised hand matters

In safety-critical work the whole idea of a safety culture rests on one thing: that anyone, at any level, can raise a concern and be taken seriously, to the point of stopping the line. The expensive failures, the ones that get written up afterwards, almost always had someone who saw it coming. Sometimes they stayed quiet. Sometimes they spoke and were not heard. Either way the lesson is the same. Silence is not agreement. It is just risk that nobody said out loud. A team where people do not raise their hands is not a team without problems. It is a team whose problems are invisible until they become expensive.

Being right is not enough

But here is where a lot of good engineers, myself included when I was younger, get it wrong. We think dissent is about being right, and being loud about it. It is not. Being right is only half the job. The other half is whether the person on the other side can actually hear you. A blunt no, delivered as an accusation, gets you labelled difficult and gets your concern ignored, even when the concern was correct. The same objection, framed well, changes the decision. How you say it is not a nicety on top of the message. Very often it is the difference between the message landing and bouncing off.

Being right is only half the job. The other half is whether the other side can actually hear you.

How to raise it well

So what does saying it well look like. Say no to the idea, not to the person, and make it clear you are pushing on the decision, not on them. Bring the reasoning, and where you can the evidence, so it is an argument and not just a mood. Offer a way forward, not only a wall: "no, because of this, but what if we tried that" is heard completely differently from "no". Pick the moment and the room, because a concern raised quietly first often lands better than one dropped in public. And know the difference between "I disagree" and "I refuse", because they are not the same sentence, and you should only reach for the second when you truly mean it.

Sometimes you win, sometimes you lose

Then, having said it well, accept that you will not always win, and that this is normal. Sometimes you will be wrong, and the disagreement is how you find that out. Sometimes you will be right and lose the argument anyway, because the decision was not only yours to make. That is not failure. If you raised the real issue, clearly and fairly, you did your part. Once a decision is genuinely made and you were heard, commit to it, unless it crosses a line you cannot accept, in which case you escalate rather than sulk. The goal was never to win every time. It was to be the person who reliably surfaces what matters.

None of this comes naturally, and none of it arrives fully formed. Saying no with maturity is a muscle. The early attempts are clumsy, mistimed, too soft or too sharp. You learn by doing it, getting it wrong, and adjusting: when to push, when to let go, how to frame it so it is heard. Over time, if you keep practising, something changes. Your raised hand stops being noise and starts being signal, and "I am not sure about this" from you makes a room pause. So learn to say no. Learn to raise your hand. But learn to do it in a way that gets heard, win or lose, and keep practising it, because a concern nobody listens to protects no one.

Written by Rajeshkanna Viswanathan, avionics and embedded software engineer. Back to home · Get in touch