Why ‘No’ Doesn’t Build Influence

In many situations, "no" is a complete sentence.

But for smart professionals who want to build influence, "no" is only the start of the conversation.

Switched on technical experts play an important role in helping food businesses manage risk, meet deadlines and ensure compliance. Often this means pushing back on internal requests or expectations by saying something can't be done.

To build influence however, it's crucial to not only identify problems and assert yourself by saying 'no', but to offer solutions that help others move forward.

Over the past few decades, I've spent much of my career working at the intersection of R&D and marketing in food businesses and I've often seen the following pattern play out:

Marketing wants to make a product claim that contravenes food standards. The technical team will advise this can't be done.

Marketing suggests another option. The technical team once again pushes back.

Eventually, after several rounds of back and forth, a solution is offered or a suggestion is accepted, however this process often takes much longer than necessary.

As a result, innovation slows, deadlines become harder to meet and frustration grows on both sides.

While the technical advice is almost always correct, saying 'no' without offering a solution creates delays and increases workload on all sides.

For technical professionals looking to build influence, it's important to add to the 'no'.

Don't only share what can't be done, but rather, also think about what can be done. Make recommendations, offer alternatives and help others understand the options available.

This means combining your technical expertise with commercial awareness and clear communication skills.

If you work in R&D, Quality, Regulatory or Innovation within a food business, your expertise is invaluable. But your ability to translate that expertise into practical recommendations is what helps others make decisions with confidence.

Sometimes the most influential thing you can say isn't simply "no."

It's:

"That approach won't work—but here's what I recommend instead."