Fear, uncertainty and doubt

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Fear, uncertainty, and doubt (often shortened to FUD) is a disinformation strategy used in sales, marketing, public relations, politics and propaganda. FUD is generally a strategy to influence perception by disseminating negative and dubious or false information and a manifestation of the appeal to fear.

While the phrase dates to at least the early 20th century, the present meaning of disinformation appeared in the 1970s to describe disinformation in the computer hardware industry, and has since been used more broadly.

Definition

The term appeared as far back as the 1920s.[1][2] A similar formulation "doubts fears and uncertainties" reaches back to 1965.[3] By 1975, the term was appearing abbreviated as FUD in marketing and sales contexts:[4] and in public relations. [5]The term FUD is also alternatively rendered as "Fear Uncertainty and Disinformation". [6]

<templatestyles src="Template:Blockquote/styles.css" />

One of the messages dealt with is FUD—the fear, uncertainty and doubt on the part of customer and sales person alike that stifles the approach and greeting.

FUD was first defined with its specific current meaning by Gene Amdahl in 1975, after he left IBM to found his own company, Amdahl Corp.: "FUD is the fear, uncertainty, and doubt that IBM sales people instill in the minds of potential customers who might be considering Amdahl products."[7] The term has also been attributed to veteran Morgan Stanley computer analyst Ulrich Weil. Originally FUD described disinformation in the computer hardware industry, and has it since been used more broadly.[8]

As Eric S. Raymond wrote:[7]

<templatestyles src="Template:Blockquote/styles.css" />

The idea, of course, was to persuade buyers to go with safe IBM gear rather than with competitors' equipment. This implicit coercion was traditionally accomplished by promising that Good Things would happen to people who stuck with IBM, but Dark Shadows loomed over the future of competitors' equipment or software. After 1991 the term has become generalized to refer to any kind of disinformation used as a competitive weapon.

By spreading questionable information about the drawbacks of less well known products, an established company can discourage decision-makers from choosing those products over its own, regardless of the relative technical merits. This is a recognized phenomenon, epitomized by the traditional axiom of purchasing agents that "nobody ever got fired for buying IBM equipment". The result is that many companies' IT departments buy software that they know to be technically inferior because upper management is more likely to recognize the brand.[citation needed]

Examples

Software producers

Lua error in package.lua at line 80: module 'strict' not found.

Microsoft

From the 1990s onward the term became most often associated with software industry giant Microsoft. Roger Irwin said:[9]

<templatestyles src="Template:Blockquote/styles.css" />

Microsoft soon picked up the art of FUD from IBM, and throughout the '80s used FUD as a primary marketing tool, much as IBM had in the previous decade. They ended up out FUD-ding IBM themselves during the OS/2 vs Win3.1 years.

In 1996, Caldera, Inc. accused Microsoft of several anti-competitive practises, including issuing vaporware announcements, creating FUD, and excluding competitors from participating in beta-test programs in order to destroy competition in the DOS market.[10][11] One of the claims was related to having modified Windows 3.1 so that it would not run on DR DOS 6.0 although there were no technical reasons for it not to work.[10][12] This was caused by the so called AARD code, some encrypted piece of code, which had been found in a number of Microsoft programs. The code would fake nonsensical error messages if run on DR DOS, like:[13][14]

<templatestyles src="Template:Blockquote/styles.css" />

Non-Fatal error detected: error #2726
Please contact Windows 3.1 beta support
Press ENTER to exit or C to continue[13][14]

If the user chose to press C, Windows would continue to run on DR DOS without problems. While it had been already speculated in the industry that the purpose of this code was to create doubts about DR DOS' compatibility and thereby destroy the product's reputation,[13][14] internal Microsoft memos published as part of the United States v. Microsoft antitrust case later revealed that the specific focus of these tests was in fact DR DOS:[15] At one point, Microsoft CEO Bill Gates sent a memo to a number of employees, reading

<templatestyles src="Template:Blockquote/styles.css" />

You never sent me a response on the question of what things an app would do that would make it run with MSDOS and not run with DR-DOS. Is there feature [sic] they have that might get in our way?[10][16]

Microsoft Senior Vice President Brad Silverberg later sent another memo, stating <templatestyles src="Template:Blockquote/styles.css" />

What the [user] is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is DR-DOS and then go out to buy MS-DOS.[10][16]

In 2000, Microsoft settled the lawsuit out-of-court for an undisclosed sum, which in 2009 was revealed to be $280m.[17]

At around the same time, the leaked internal Microsoft "Halloween documents" stated "OSS [Open Source Software] is long-term credible... [therefore] FUD tactics cannot be used to combat it."[18] Open source software, and the GNU/Linux community in particular, are widely perceived as frequent targets of Microsoft FUD:

SCO v. IBM

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The SCO Group's 2003 lawsuit against IBM, funded by Microsoft, claiming $5 billion in intellectual property infringements by the free software community, is an example of FUD.[according to whom?] IBM argued in its counterclaim that SCO was spreading "fear, uncertainty, and doubt".[24]

Magistrate Judge Wells wrote (and Judge Kimball concurred) in her order limiting SCO's claims: "The court finds SCO’s arguments unpersuasive. SCO’s arguments are akin to SCO telling IBM, 'sorry we are not going to tell you what you did wrong because you already know...' SCO was required to disclose in detail what it feels IBM misappropriated... the court finds it inexcusable that SCO is... not placing all the details on the table. Certainly if an individual were stopped and accused of shoplifting after walking out of Neiman Marcus they would expect to be eventually told what they allegedly stole. It would be absurd for an officer to tell the accused that 'you know what you stole I’m not telling.' Or, to simply hand the accused individual a catalog of Neiman Marcus’ entire inventory and say 'it’s in there somewhere, you figure it out.' "[25]

Regarding the matter, Darl McBride, President and CEO of SCO, made the following statements:

  1. "IBM has taken our valuable trade secrets and given them away to Linux,"
  2. "We're finding... cases where there is line-by-line code in the Linux kernel that is matching up to our UnixWare code"
  3. "...unless more companies start licensing SCO's property... [SCO] may also sue Linus Torvalds... for patent infringement."
  4. "Both companies [IBM and Red Hat] have shifted liability to the customer and then taunted us to sue them."
  5. "We have the ability to go to users with lawsuits and we will if we have to, “It would be within SCO Group's rights to order every copy of AIX [IBM's proprietary UNIX] destroyed,"
  6. "As of Friday, June 13 [2003], we will be done trying to talk to IBM, and we will be talking directly to its customers and going in and auditing them. IBM no longer has the authority to sell or distribute IBM AIX and customers no longer have the right to use AIX software"
  7. "If you just drag this out in a typical litigation path, where it takes years and years to settle anything, and in the meantime you have all this uncertainty clouding over the market..."
  8. "Users are running systems that have basically pirated software inside, or stolen software inside of their systems, they have liability."[26]

SCO stock skyrocketed from under $3 a share to over $20 in a matter of weeks in 2003. (It later dropped to around[27] $1.20—then crashed to under 50 cents on August 13, 2007, in the aftermath of a ruling that Novell owns the UNIX copyrights.) [28]

Apple

Apple's claim that iPhone jailbreaking could potentially allow hackers to crash cell phone towers was described by von Lohmann, a representative of the EFF, as a "kind of theoretical threat...more FUD than truth”.[29]

Security industry

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

FUD is widely recognized as a tactic to promote the sale or implementation of security products and measures. It is possible to find pages describing purely artificial problems. Such pages frequently contain links to the demonstrating source code that does not point to any valid location and sometimes even links that "will execute malicious code on your machine regardless of current security software", leading to pages without any executable code.[citation needed]

The drawback to the FUD tactic in this context is that, when the stated or implied threats fail to materialize over time, the customer or decision-maker frequently reacts by withdrawing budgeting or support from future security initiatives.[30]

2004 U.S. presidential election

FUD is now often used in non-computer contexts with the same meaning. In politics, one side can use FUD to obscure the issues. For example, critics of George W. Bush accused Bush's supporters, most notably the Swift Boat Veterans For Truth, of using a FUD-based campaign in the 2004 U.S. presidential election.[31]

Caltex

The FUD tactic was used by Caltex Australia in 2003. According to an internal memo, which was subsequently leaked, they wished to use FUD to destabilise franchisee confidence, and thus get a better deal for Caltex. This memo was used as an example of unconscionable behaviour in a Senate inquiry. Senior management claimed that it was contrary to and did not reflect company principles.[32][33][34]

Clorox

In 2008, Clorox was the subject of both consumer and industry criticism for advertising its GreenWorks line of allegedly environmentally friendly cleaning products using the slogan, "Finally, Green Works."[35] The slogan implied both that "green" products manufactured by other companies which had been available to consumers prior to the introduction of Clorox's GreenWorks line had all been ineffective, and also that the new GreenWorks line was at least as effective as Clorox's existing product lines. The intention of this slogan and the associated advertising campaign has been interpreted as appealing to consumers' fears that products from companies with less brand recognition are less trustworthy or effective. Critics also pointed out that, despite its representation of GreenWorks products as "green" in the sense of being less harmful to the environment and/or consumers using them, the products contain a number of ingredients advocates of natural products have long campaigned against the use of in household products due to toxicity to humans or their environment.[36] All three implicit claims have been disputed, and some of their elements disproven, by environmental groups, consumer-protection groups, and the industry self-regulatory Better Business Bureau.[37]

Further reading

According to some commentators, examples of political FUD are: "domino theory", "electronic Pearl Harbor",[38][39] and "weapons of mass destruction".[40]

See also

<templatestyles src="Div col/styles.css"/>

2

References

  1. "Suspicion has no place in our interchanges; it is a shield for ignorance, a sign of fear, uncertainty, and doubt." Caesar Augustus Yarbrough, The Roman Catholic Church Challenged, p. 75. The Patriotic Societies of Macon, 1920.
  2. "Again he was caught in a tempest of fear, uncertainty, and doubt." Monica Mary Gardner, The Patriot Novelist of Poland, Henryk Sienkiewicz, p. 71. J.M. Dent ; E.P. Dutton & Co, 1926.
  3. "This will give unspeakable comfort peace and satisfaction to his Mind, and set him not only out of danger and free him from an ill state, but out of all doubts fears and uncertainties in his thoughts about it; ..." William Payne, A practical discourse of repentance, rectifying the mistakes about it, especially such as lead either to despair or presumption: ..., p. 557. S. Smith, 1965.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found. p. 179
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. For example, FUD has been used to describe social dynamics in contexts where sales, lobbying or commercial promotion is not involved.Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 10.3 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Open Source Initiative. "Halloween I: Open Source Software (New?) Development Methodology"
  19. Press release from Microsoft which has viral nature of open-source quote
  20. Lua error in package.lua at line 80: module 'strict' not found.. Microsoft's licensing chief claimed that specific examples have been given in private, in: Lua error in package.lua at line 80: module 'strict' not found..
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. The SCO Group v IBM – answer to amended complaint and counterclaims (Undecided, U.S. District Court – Utah, Kimball J., filed 6 August 2004) Section E, paragraph 22, groklaw.net
  25. The SCO Group v IBM – ORDER GRANTING IN PART IBM'S MOTION TO LIMIT SCO's CLAIMS (Undecided, U.S. District Court – Utah, Kimball J., filed 6 August 2004) Section IV, paragraphs 33,34
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.

External links

This article is based in part on the Jargon File, which is in the public domain.