The Patriot Files Forums  

Go Back   The Patriot Files Forums > Warfare > Warfare

Post New Thread  Reply
 
Thread Tools Display Modes
  #1  
Old 03-21-2011, 06:30 PM
BLUEHAWK's Avatar
BLUEHAWK BLUEHAWK is offline
Senior Member
 

Join Date: May 2002
Location: Ozarks
Posts: 4,638
Send a message via Yahoo to BLUEHAWK
Distinctions
Contributor 
Lightbulb Operations naming...

(In the light of "Operation Odyssey Dawn")

Source:
www.carlisle.army.mil/usawc/parameters/Articles/1995/sieminsk.htm

[excerpt]

The Art of Naming Operations

GREGORY C. SIEMINSKI


From Parameters, Autumn 1995, pp. 81-98.

Shortly after word spread among key military leaders that President Bush had ordered the invasion of Panama, Lieutenant General Thomas Kelly, Operations Officer on the Joint Staff, received a call from General James Lindsay, Commander-in-Chief (CINC), Special Operations Command. His call did not concern some last-minute change in the invasion plan; rather, it concerned a seemingly insignificant detail of the operation: its name. "Do you want your grandchildren to say you were in Blue Spoon?" he asked.[1] Lieutenant General Kelly agreed that the name should be changed. After hanging up the phone, General Kelly discussed alternatives with his deputy for current operations, Brigadier General Joe Lopez.
"How about Just Action?" Kelly offered.
"How about Just Cause?" Lopez shot back.[2]
So was born the recent trend in nicknaming operations. Since 1989, major US military operations have been nicknamed with an eye toward shaping domestic and international perceptions about the activities they describe.[3] Operation Just Cause is only the most obvious example of this phenomenon. From names that stress an operation's humanitarian focus, like Operation Provide Comfort in Turkey, to ones that stress an operation's restoration of democratic authority, like Operation Uphold Democracy in Haiti, it is evident that the military has begun to recognize the power of names in waging a public relations campaign, and the significance of winning that campaign to the overall effort. As Major General Charles McClain, Chief of Public Affairs for the Army, has recently written, "the perception of an operation can be as important to success as the execution of that operation."[4] Professor Ray Eldon Hiebert, in a piece titled, "Public Relations as a Weapon of Modern War," elaborates on that view: "The effective use of words and media today . . . is just as important as the effective use of bullets and bombs. In the end, it is no longer enough just to be strong. Now it is necessary to communicate. To win a war today government not only has to win on the battlefield, it must also win the minds of its public."[5]
Like any aspect of operational planning, the job of naming operations initially falls to mid-level staff officers in Defense Department components, agencies, and unified and specified commands, to which the Joint Chiefs of Staff have delegated considerable freedom in the naming of operations. Because nicknames help determine the way operations are perceived, joint staff officers must develop not only their skill as operational artists but also their art as operation namers.
An appreciation for the art of doing anything is best gained from practitioners, both good and bad. By way of offering a sort of historical apprenticeship, this article reviews the origins and development of the practice of naming operations, with particular emphasis upon the American tradition which emerged from World War II. This heretofore unchronicled story contains useful lessons for officers who must recommend or approve an operation name.
Operations in the World Wars
Naming operations seems to have originated with the German General Staff during the last two years of World War I. The Germans used code names primarily to preserve operational security, though the names were also a convenient way of referring to subordinate and successive operations. Thus, it is probably no accident that operational names came into use at the same time as the rise of operational art. It was simply easier to get a handle on the complexities of operational sequencing and synchronization by naming each operation something that the staff could remember. The Germans chose names that were not only memorable but also inspiring. Plans for the great Western Front offensive in the spring of 1918, which saw the most extensive use of operational code names, borrowed from religious, medieval, and mythological sources: Archangel, St. Michael, St. George, Roland, Mars, Achilles, Castor, Pollux, and Valkyrie.[6] The selection of these names was perhaps an adjunct to Ludendorff's patriotic education program, designed to stir a demoralized and weary army into making one final push.[7] The original, stirring vision conjured by these names was lost, however, when several of the planned operations had to be scaled back. St. George, for example, devolved to the uninspiring diminutive Georgette.[8]
The American military adopted code names during the World War II era, primarily for security reasons.[9] Its use of code names for operations grew out of the practice of color-coding war plans during the interwar period.[10] Even before America entered the war, the War Department had executed Operation Indigo,[11] the reinforcement of Iceland, and had dubbed plans to occupy the Azores and Dakar as Operations Gray[12] and Black[13] respectively.
With the outbreak of the war, the practice of using colors as code names was overcome by the need to code-name not only a growing number of operations, but also numerous locations and projects. The War Department adopted a code word list similar in principle to one already in use by the British. In early 1942, members of the War Plans Division culled words from an unabridged dictionary to come up with a list of 10,000 common nouns and adjectives that were not suggestive of operational activities or locations. They avoided proper nouns, geographical terms, and names of ships.[14] Since so many operations would involve the British, they made sure the list did not conflict with the one developed and managed by their counterparts on the British Inter-Services Security Board.[15] In March 1942, the Joint Chiefs of Staff approved the classified Inter-Services Code-Word Index[16] and gave the War Plans Division the duty of assigning code words.[17] Accordingly, the War Plans Division (shortly afterward renamed the Operations Division)[18] assigned blocks of code words to each theater; the European Theater got such names as Market and Garden, while the Pacific Theater got names like Olympic and Flintlock.[19]
Although the words listed in the British and American code indexes were randomly chosen, the names of significant operations were thoughtfully selected from the lists, at least those Winston Churchill had anything to do with. Churchill was fascinated with code names and personally selected them for all major operations.[20] He had clear ideas about what constituted appropriate names. After coming across several that he considered inappropriate, he went so far as to instruct an aide to submit all future code names to him for approval; he dropped his demand when he learned the magnitude of the task,[21] but he did take the precaution of writing down some principles to guide his subordinates:
[1.] Operations in which large numbers of men may lose their lives ought not to be described by code words which imply a boastful or overconfident sentiment,. . . or, conversely, which are calculated to invest the plan with an air of despondency. . . . They ought not to be names of a frivolous character. . . . They should not be ordinary words often used in other connections. . . . Names of living people--Ministers and Commanders--should be avoided. . . .
2. After all, the world is wide, and intelligent thought will readily supply an unlimited number of well-sounding names which do not suggest the character of the operation or disparage it in any way and do not enable some widow or mother to say that her son was killed in an operation called "Bunnyhug" or "Ballyhoo."[22]
Borrowing a page from the Germans of World War I, whose code-naming practices he knew well from writing his four-volume history of that war,[23] Churchill saw the names of culturally significant figures as useful sources of operational code words:
3. Proper names are good in this field. The heroes of antiquity, figures from Greek and Roman mythology, the constellations and stars, famous racehorses, names of British and American war heroes, could be used, provided they fall within the rules above.[24]
Churchill's commonsense principles for naming operations influenced American as well as British practice. For example, he objected to the code name for the American bomber raid on the Romanian oil fields in Ploesti because he thought the name "Soapsuds" was "inappropriate for an operation in which so many brave Americans would risk or lose their lives."[25] He aired his objections through the British Chiefs of Staff, who persuaded the Joint Chiefs of Staff to change the name to the more appropriate and inspirational Tidal Wave.[26] Churchill's hand also is evident in the naming of many combined US-British operations, including the American-led invasion of Normandy. The plan for the 1944 invasion was originally Roundhammer, a combination of the code names for invasions planned for previous years, Sledgehammer (1942) and Roundup (1943).[27] While Churchill's personal response to the name Roundhammer is not recorded, the British official history of the war calls the name a "revolting neologism."[28] Whether this strong reaction was shared by Churchill or not, he changed the name to Overlord,[29] deservedly the best-known operational code name to emerge from World War II.[30] The name suggests, as David Kahn has noted, "a sense of majesty and patriarchal vengeance and irresistible power."[31] Whether or not Churchill violated his own advice about avoiding names which imply overconfidence, the name Overlord may well have strengthened the resolve of those who planned the assault on fortress Europe.
The Axis powers also recognized the inspirational value of code names. Although the Japanese typically numbered or alphabetically designated their operations,[32] they resorted to inspirational names as their strategic situation worsened, not unlike the Germans during World War I. The Japanese offensive designed to thwart the Allied landings at Leyte Gulf, for example, was optimistically dubbed Operation Victory.[33]
The Germans made extensive use of code names for plans and operations and usually chose names at random; however, major operations often got special consideration by the German leadership.[34] Perhaps the most well-known example of this is the code name for the 1941 invasion of the Soviet Union. Initially, the operation was christened Fritz, after the son of the plan's author, Colonel Bernhard Von Lossberg.[35] But Hitler would not have his grand project named something so pedestrian, Lossberg's sentimental attachment notwithstanding. On 11 December 1940 he renamed the operation Barbarossa, the folk name of the 12th-century Holy Roman Emperor Frederick I, who had extended German authority over the Slavs in the east and who, legend said, would rise again to establish a new German Empire.[36] In selecting a name with these inspirational associations, Hitler risked revealing his intentions--the very thing code names are designed to conceal. In the case of Barbarossa, Hitler seems to have been lucky; in the case of Operation Sealion, his planned invasion of Britain, he was not. British intelligence divined Sealion's target from its telltale name.[37]
Using Nicknames to Shape Perceptions
The efforts of Hitler and Churchill notwithstanding, World War II operation names had limited effect on shaping attitudes because they were classified until after the war ended.[38] Thus, their effect on troop morale was limited to those with clearances, and their effect on public perception was delayed until after the war, at which point the names were merely historical curiosities.
But in America, shortly after the war ended, the War Department decided to use operation names for public information purposes in connection with atomic bomb testing. To this end, the War Department created a new category of unclassified operation names, which are known as nicknames to distinguish them from classified code words. Code words are assigned a classified meaning and are used to safeguard classified plans and operations, while nicknames are assigned unclassified meanings and are used for administrative, morale, and public information purposes.[39]
Nicknames offered new possibilities for shaping attitudes about operations, and the first person to make use of one took full advantage of the potential. Vice Admiral W. H. P. Blandy, the commander of the joint task force conducting the 1946 atomic bomb tests on Bikini Atoll, selected the nickname Operation Crossroads with great care. He chose it, he told a Senate committee, because of the test's possible significance--"that seapower, airpower, and perhaps humanity itself . . . were at the crossroads."[40] Admiral Blandy was especially proud of the name, and when he discovered that the word was already assigned to another activity, he pulled strings to get it assigned to the Bikini tests.[41]
The press publicized not only the name, but also Blandy's rationale for selecting it, and did so with general approbation.[42] Commenting on Blandy's public relations savvy, one historian wrote: "The choice of names was brilliant, implying to some that the military was unsure of its direction and was truly in awe of the atomic bomb."[43] However, some in the press were not so enamored with Blandy or his choice of name. In an article lampooning Blandy, The New Yorker commented with unmistakable sarcasm that the name "has been greatly admired in literary and non-violent circles."[44] The sarcasm seems to suggest that while the general public might admire the name, literary and non-violent audiences were not taken in by Blandy's public relations methods. This would not be the last time members of the media would resent the military's success in popularizing a carefully chosen nickname.
Operations in Korea
Although the military had learned the value of well-chosen nicknames during the peacetime atomic bomb tests, it continued to use meaningless code names during wartime to protect operational security. At least this was true early in the Korean War. In planning the Inchon landing, General Douglas MacArthur and his subordinates followed the World War II practice of selecting operation names from an established code word list. The earliest plan was dubbed Operation Bluehearts, and the one actually executed was Operation Chromite.[45]
MacArthur did depart from World War II practice in one important respect: he permitted code names to be declassified and disseminated to the press once operations had begun, rather than waiting until the end of the war.[46] Thus, combat operation names were, for the first time, public knowledge as operations unfolded. Curiously, MacArthur, with all his public relations savvy, failed to see the opportunities this offered for shaping perceptions.
China's intervention in the Korean War helped Lieutenant General Matthew Ridgway see what MacArthur had not. Ridgway took command of the Eighth Army as it was reeling southward under relentless Chinese attack. His first task, he realized, was to restore the fighting spirit of his badly demoralized command.[47] One way he did this was by giving decidedly aggressive nicknames to the series of counteroffensives undertaken from February to April 1951: Thunderbolt, Roundup, Killer, Ripper, Courageous, Audacious, and Dauntless. Because these names were not classified once operations began, they were widely disseminated among Eighth Army soldiers to boost morale.[48] Ridgway's unprecedented use of meaningful combat operation names set the tone for one of the most remarkable transformations of any military organization in history. The reinvigorated Eighth Army pushed the Chinese back to the 38th parallel.
If Ridgway's names contributed to success on the battlefield, they were not nearly so successful on the home front. Ridgway had publicly announced not only the start of his first major counteroffensive, but also its nickname: Operation Killer.[49] In doing so, he may have imagined that he could boost the morale of the public in the same way he hoped to inspire his troops. After all, the news from the front had been bad for months--so bad, in fact, that the US Far East Command had suspended communiques dealing with operational matters the previous fall.[50] It was probably no coincidence that the communiques resumed the day after the start of Operation Killer.[51] Certainly some of Ridgway's troops thought that Killer and other names had been chosen with the media in mind.[52]
In any event, more than a few observers objected to Ridgway's operation name, which was prominently displayed in many newspaper and magazine articles.[53] One critic was the Army Chief of Staff, General J. Lawton Collins, who informed Ridgway that "the word `killer' . . . struck an unpleasant note as far as public relations was concerned."[54] Certainly public relations suffered: several writers criticized the name directly or implicitly in letters to The New York Times;[55] the International Longshoremen's and Warehousemen's Union issued a report in which the name served as the rubric for the entire conflict, which it called a "phony" war emergency;[56] Republicans pointed to the term as evidence that the Truman Administration had no other aim in Korea but to kill Chinese;[57] and the State Department objected that the name had soured negotiations with the People's Republic of China.[58]
While the incident taught Ridgway "how varied . . . the political pressures [can be in waging] . . . a major war,"[59] he remained unrepentant about his selection of the name: "I am not convinced that the country should not be told that war means killing. I am by nature opposed to any effort to `sell' war to people as an only mildly unpleasant business that requires very little in the way of blood."[60] However opposed his nature may have been to soft-pedaling the realities of war, operations after Killer and its immediate successor, Ripper, were given less bloody names.
Operations in Vietnam
Early in the Vietnam War, operations were often given nicknames descriptive of the missions they designated. For example, a combined US Marine and South Vietnamese operation designed to increase the area of control of the Marine enclave at Da Nang was dubbed Blastout.[61] The names of air operations in early 1966 suggest the widening of the air war against North Vietnam. The two retaliatory air strikes against carefully selected North Vietnamese installations were known as Flaming Dart I and II, while the gradually escalating strategic bombing effort begun shortly thereafter was known as Rolling Thunder.[62]
The penchant for giving descriptive names to operations in Vietnam caused the military to relearn the lesson of Operation Killer. On 25 January 1966, the 1st Cavalry Division began a sweep operation through the Bong Son Plain which it had dubbed Masher,[63] presumably because the operation envisioned the enemy being mashed against a second force comprised of Marines.[64] Owing to the media's free access to military units and the lack of censorship during the war, nicknames like Masher were frequently reported by the media as operations progressed. And because Masher was a major operation conducted by the novel "airmobile cavalry" division, it attracted a fair degree of media attention, causing the name to be widely circulated on television and in the print media.[65] When President Johnson heard it, he angrily protested that it did not reflect "pacification emphasis."[66] General William Westmoreland put it more bluntly when he speculated that "President Johnson . . . objected . . . because the connotation of violence provided a focus for carping war critics."[67] To remove their focus, the division commander quickly renamed the operation White Wing.[68]
The lesson of the Masher incident was not lost on Westmoreland: "We later used names of American cities, battles, or historic figures [for operations]."[69] Indeed, reading the names of operations mounted in Vietnam after February 1966 is like reading a cross between a gazetteer and a history book.[70] Names such as Junction City, Bastogne, and Nathan Hale were imbued with American associations and values, and thus were politically safe, as well as potentially inspirational.
Like Ridgway, Westmoreland tried his own hand at the art of operational naming. Also like Ridgway, he did so to inspire demoralized soldiers. In early 1968, the garrison of 6000 US and South Vietnamese troops at Khe Sanh found itself surrounded by an estimated 15,000 to 20,000 North Vietnamese regulars. Many critics saw a Dien Bien Phu in the making, and the beleaguered troops could not but be infected by the prevailing sense of doom. To combat their dispiriting mood, Westmoreland named the round-the-clock bombing and shelling of enemy positions Operation Niagara. He selected the name, he said, "to invoke an image of cascading shells and bombs," an image obviously designed to reassure the Khe Sanh garrison.[71]
As the Vietnam War drew to a close, the Department of Defense for the first time issued guidelines concerning nicknaming operations.[72] It is clear from reading the guidelines--which remain in force today[73]--that its authors learned well the lessons of Operations Killer and Masher. Noting that improperly selected nicknames "can be counterproductive," the regulation specifies that nicknames must not: "express a degree of bellicosity inconsistent with traditional American ideals or current foreign policy"; "convey connotations offensive to good taste or derogatory to a particular group, sect, or creed"; "convey connotations offensive to [US] allies or other Free World nations"; or employ "exotic words, trite expressions, or well-known commercial trademarks."[74] The regulation further stipulates that a nickname must consist of two words (which helps distinguish it from a code word, which consists of only one) and requires the JCS to establish procedures for DOD components to nominate and report nicknames...
sendpm.gif Reply With Quote
Sponsored Links
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Society of Sponsors of the U.S. Navy (Ship Naming Process) The Patriot Navy 0 11-02-2010 09:26 PM
Rutgers coach Greg Schiano holds off on naming starting QB - ESPN The Patriot Army 0 10-27-2010 11:26 PM
Rutgers coach Greg Schiano holds off on naming starting QB - ESPN The Patriot Army 0 10-27-2010 10:26 PM
Rutgers coach Greg Schiano holds off on naming starting QB - ESPN The Patriot Army 0 10-27-2010 09:26 PM
Dutch outcry over naming giant ship after Nazi David World War II 0 11-07-2008 10:44 AM

All times are GMT -7. The time now is 11:47 AM.


Powered by vBulletin, Jelsoft Enterprises Ltd.