FUD

In plain terms

FUD stands for fear, uncertainty and doubt. It's the move of making the other option feel risky instead of showing that yours is better.

The defining feature is vagueness. Nobody names a defect. The pitch is a raised eyebrow: "Are you sure they'll still be around in three years?" "I've heard things about their security." "Your call, obviously." No claim gets made, so no claim can be checked.

The term comes out of the mainframe business, where sales teams were said to plant doubts about smaller competitors rather than argue on features. It moved into software marketing, then security, then crypto, and now turns up in any meeting where someone would rather shrink an option than defend their own.

Why it works

A decision only has to feel unsafe to lose. Getting someone to reject a choice is far cheaper than getting them to accept yours, and unspecified risk does that job at almost no cost to the speaker.

Vagueness is the engine. A named flaw invites a rebuttal with dates and documents. An unnamed worry invites the listener's imagination, which reliably produces something worse than the facts would have. And under pressure, the speaker never claimed anything. They only asked a question.

Canonical example

Incumbent vendor, near the end of a renewal call: "They're a good little company, genuinely. I just wouldn't want to be the person who put a production system on a startup. And, look, ask them about their security posture sometime."

Nothing there is a claim. The rival is never accused of being unstable or insecure. "Ask them about their security posture" implies a finding while stating none, which leaves the rival with nothing to answer and the buyer holding a bad feeling that has no source to check.

Counter-example (not FUD)

"Their SOC 2 lapsed in March and hasn't been renewed. They had a 14-hour outage in August, and it's on their status page. Both are worth asking about."

Raising risk is legitimate. This names the risk, dates it, and points at where to verify. The rival can respond, and the buyer can judge whether the answer holds. That is what a competitive comparison is supposed to look like.

Uncertainty can also be the honest answer. "We don't know yet how that regulation will be applied" states the actual condition of the evidence rather than manufacturing a mood.

The line: does the warning name a risk the other side could answer, or only a feeling they can't?

How to fix it

If you've been linked here, convert the feeling into a claim. Write down what you are actually worried about, then say that: the specific dependency, the funding runway, the missing certification, the outage history. If the concern survives being written down, it lands harder in that form than as a hint. If it doesn't survive, you found that out before saying it in front of people who can check.

If you're on the receiving end, ask for the specific version once. "What exactly are you referring to, and where can I read it?" A real concern comes with a date, a document, or an incident. A device changes the subject or retreats to "I'm just saying, do your homework." The retreat is the answer.