Archive for the 'Army' Category
Well, we had a little trouble with the technical side of live podcasting last week (and, as my old Macintosh computer used to say, “It’s not my fault”) but CDR Salamander and I are, if nothing else, persistent.
So please join us on Sunday, as we fight with electrons and, uh, other things in our presentation of Midrats Episode 210: “John Kuehn & Joint Operations from Cape Fear to the South China Sea”
Though nations for thousands of years have been wrestling with the challenge of Joint operations, as an island nation with significant global interests ashore, the USA has a rich history of doing Joint right, and blind parochialism. (Note by E1: Sal wrote this and your guess is as good as mine in what he meant in that last part there. Or, just maybe the electrons have struck again – Red Lectroids?)
Using this as a starting point, this Sunday for the full hour we will have returning guest, John Kuehn.
Dr. John T. Kuehn is the General William Stofft Chair for Historical Research at the U.S. Army Command and General Staff College. He retired from the U.S. Navy 2004 at the rank of commander after 23 years of service as a naval flight officer in EP-3s and ES-3s. He authored Agents of Innovation (2008) and co-authored Eyewitness Pacific Theater (2008) with D.M. Giangreco, as well as numerous articles and editorials and was awarded a Moncado Prize from the Society for Military History in 2011.
We will also discuss his latest book, just released by Praeger, A military History of Japan: From the Age of the Samurai to the 21st Century.
Please join us live at 5pm Eastern U.S. on 12 January 2014 or pick the show up later by clicking here.
Every listen is a strike against the Lectroids!
By Chap Godbey
This photo sort of looks like a ship, right? It is, but then again it’s also something else.
For this example, the vessel–an Iraqi patrol craft made by an American company and part of a U.S. foreign military sales contract–is not just one of the assets Iraq’s military needs to protect a very crowded and consequential waterspace. It’s also a multi-decade relationship, where both countries get to know each other on an operator-to-operator level as well as on other levels. That relationship can have strategic effects as the lieutenants become admirals, and the relationship builds trust, access, and communications paths outside the formal diplomatic process and regionally as well as bilaterally.
One of the patrol spaces this ship protects drives the entire country’s economy–the oil platforms and pipeline infrastructure–and its shipping. This is recognizable to a military planner, though the economic part takes a bit of wider thinking to understand how U.S. security cooperation fits into it with training and equipment. But let’s add something important on here: U.S. policy is to support Iraq’s reintegration into the region, and it’s a top foreign policy priority for the U.S. with regard to Iraq. The military sphere tends to be a bit easier in reconnection than some other spheres; navies, since they’re mobile sovereign territory in international waters, can be the fastest of those–especially when the U.S. is acting as an honest broker. To pull off that kind of multinational reintegration is not solely a military function, but can utterly depend on the military aspect. If the U.S. really wants a whole-of-Executive-Branch (much less whole-of-government) approach to a policy problem, DoD’s mass has to be subordinated to the overall effort, even when it might not necessarily make short term military sense.
The example above isn’t perfect. Security assistance in Iraq and Afghanistan has been far from the standard situation seen by a security cooperation office, and special authorities in the law made security cooperation in these countries much different than in other countries. A more forceful example would be where the host nation is paying for every penny of the asset, since feelings about “what ‘we’ are giving ‘them’” emotionally colors the discussion, and it’s worthwhile to emphasize that foreign military sales is not necessarily coming from the U.S. taxpayer. On the other hand, the nonmilitary effects of this ship and crew, and the regional effects of what this ship does and the separate bilateral relationships that navy has with regional navies and the U.S., are pretty clear and useful to bring out the challenge of thinking about security cooperation as more than arms sales or exercises.
Many folks seem to miss the nonmilitary and regional effects of the military-to-military relationship built out of security cooperation, or even that the process is heavily structured in U.S. law. This post about security cooperation misses important considerations about what security cooperation is and what it’s supposed to do (this one by the same author is better, though of different focus). A comment of mine on that War On the Rocks post identifies structural problems in the argument, and there are other opportunities for quibbling, but that post proves that it’s worthwhile to outline some basics of SC with a view towards those regional and extramilitary effects.
Security cooperation (SC) is not very familiar to most operators in the Department of Defense. SC’s a difficult skill set. SC can pay off not only as a force multiplier, but also to provide diplomatic effects which can be game-changing. DoD personnel may only experience SC once, as an exercise or engagement event, or by doing a tour that includes a collateral duty associated with foreign military sales (FMS). More experience is in the foreign area officer (FAO) commmunity, whose officers can wind up doing SC from several angles over multiple tours, but there aren’t many FAOs around. Because the skills needed are relatively obscure inside DoD, understanding of what SC is becomes fragmentary and often misses the point. American SC can suffer from that bad understanding. (The way U.S. government agencies in the Executive Branch staff and train for SC missions doesn’t help the problem, either.)
DoD isn’t the agency where SC initially gets defined—because SC is not solely a DoD mission; it’s a State mission for which Defense is the executive agent.
Let’s define some terms here. SC includes
- security assistance (SA), which itself includes
- foreign military sales (FMS) weapons sales,
- International Military Education and Training (IMET),
- a multi-page list of other programs that somehow fit or get shoehorned into the process, and
- security cooperation (Sc), a confusingly named subset of the bigger SC which mainly deals with exercise events with host nation or meetings between military personnel.
The first one, SA, is covered under federal law. (Note: IANAL and doing this off the top of my head.) U.S. Code Title 22 is the main law that covers diplomatic and consular functions and is for the Department of State what Title 10 is for DoD. The second part of security cooperation, the non-FMS part also called security cooperation, has rules under Title 22 but is more under a section of Title 10. That part of title 10 used is different from what you might expect, and it’s administered by personnel working under a different rule set than those under the full operational command of a COCOM. DoD personnel in country doing SC serve under the direction and supervision of the Chief of the United States Diplomatic Mission to that country (usually the U.S. ambassador to that country). Security cooperation, including security assistance, is a diplomatic function, under the Ambassador’s control in country. FMS cases and IMET and exercises have significant State Department approval and coordination–and additional coordination and approval by other agencies, and in some cases White House/Congressional approval–even though DoD has the mass and the executive agent role. The effect can sometimes be that the poor bureaucrat in the other agency is either like Horatius at the bridge or Niedermeyer in the riot, trying to get the massive influx of DoD people to go a different direction. It also can become counterintuitive, since American businesses might be fighting for the contract, or if one player–even a host nation–decides it’s worth lobbying for their interests more effectively to Congress than another player.
Note here that the Security Assistance Management Manual, the reference used in the War On The Rocks post, isn’t the controlling document. The law both trumps one agency’s manual and also highlights the diplomatic and interagency nature of SC. It also implies that the SC function is something we do as an ongoing and sustaining function of a country team, rather than something switched on once a COCOM has commenced large scale operations.
Since SC is a diplomatic function, one has to consider SC less like a military operation and more like a diplomatic operation. Results will be diffuse. They will have “one step forward two steps back” aspects. Results will be hard to measure in many respects. The effort will be like a coalition effort, with occasionally immense frustration on the ground and in the staff paying off strategically, but in different spheres than expected, or with effects long after the staffer is gone. For a planner looking for consistent positive results with a focused engineering-style goal oriented mindset this is anathema. A DoD planner or operator wants to get from point A to point B in a direct and uncluttered manner. Diplomacy, especially the work performed by Department of State colleagues on the country team on ground in country, is more chaotic and messy. If done right, SC advances the national interest of the United States; builds networks, access and relationships beneficial to the U.S.; eases stresses among and between partners; provides a common operating framework in the field; and provides a useful diplomatic tool as part of an embassy country team.
(Oh, by the way: There’s no Title 10 “command” in security cooperation organizations. There is no sheriff’s badge, no salad fork, no “forces”, even though the responsibility can weigh heavily, and DoD personnel could be in remote and dangerous locations. You’re a part of the embassy country team. There’s not even an organic Article 15 or medal-awarding authority, unless you’re a general for whom a COCOM has specifically delegated it in writing.)
For representatives of either agency to best advance U.S. national interest in the long term, both Defense and State have to be able to restrain some of their agency-level cultural impulses to achieve SC most effectively. Training, both in State’s A100 class for their newly commissioned officers, and at the Defense Institute for Security Assistance Management or similar venues for DoD personnel interacting with a country team, helps introduce the cultural difference to each agency. Other agencies with a hand in SC, such as the Departments of Commerce or Treasury, have a much smaller presence and make do with corporate knowledge and help from the larger groups interacting around them. (Homeland Security mainly interacts through Coast Guard personnel, who are more acquainted with DoD’s foibles and when in theater interact often with country teams with and outside the security cooperation office in the embassy.) Some aspects can cause real friction without planners realizing its source, such as when a J5 officer assumes there’s a J5 in State, or that a Post’s plan is written with the same process as DoD’s, or that the plan is followed as closely as a DoD plan would be. On the ground, people on the country team have to make it work through force of effort and personality.
The benefits of SC have national influence, not just military, from public affairs/public diplomacy to changing policies in a country. SC also has a regional influence: in the ability to use the U.S. effort as a go-between between two partners unhappy with each other, in the ability to build regional ties with the U.S. invited to play, and in the ability to influence regional decisions based on a calculation from a nation that has to deal with what the U.S. has done in the neighborhood. It could well be that host nation has no culture of maintenance and the equipment they paid for is failing. It could be that the country’s using the military to dispense largesse domestically, and the U.S. interest in improving capacity isn’t perfectly aligned with that national desire. It could be that there’s a Red Queen effect, where the security cooperation guys are running as hard as they can to stay in place capacity-wise. It could also be that those frustrating efforts pay off in unusual ways. The military planner will do well to reach out to those other American agencies, to actually listen and adjust planning based on that reaching out, to see the role of SC as more than military capacity building, and to plan for a long and difficult but rewarding SC effort.
Typically the Services study historic leaders from their own particular domain of expertise (air, sea, land), and rarely do they venture beyond this. The Navy has figures like Mahan and Halsey. The Army: Grant and Patton. The Marine Corps: Lejeune and Puller. The Air Force: Mitchell and Boyd. This past year I came across a hero worthy of study by all the services.
A few months ago I read 21st Century Mahan: Sound Military Conclusions for the Modern Era by Benjamin Armstrong, a collection of Alfred Thayer Mahan’s essays, and became particularly intrigued by one of the essays entitled Strength of Nelson. The short chapter introduced me to a military figure whom, in my opinion, exemplified the leadership traits and characteristics required to successfully implement the philosophy of mission command today: Admiral Lord Viscount Horatio Nelson.
Immediately after finishing Armstrong’s book I wanted to know more, so I read Nelson: Britannia’s God of War by Andrew Lambert. From that wonderfully written biography and Mahan’s essay I observed five lessons that every military leader should consider in order to excel at mission command.
- Reward success and take the blame for failure. Nelson’s subordinates enjoyed working for him because they knew they would be able to contribute to the plan, as well as exercise initiative, aggression, and personal skill. They also found comfort in knowing that if things went wrong, Nelson would take the blame. However, if the mission was a success, Nelson ensured that his leaders received their proper reward and acknowledgment. Lambert wrote that “[Nelson] never overrode the judgment of those whom he had ordered to execute well-defined tasks. He always worked through the proper chain of command to avoid giving offense, or undermine the confidence of promising officers. If things went wrong, he was the first to leap to the defense of a bold and decisive subordinate.”
- Remember that political courage is as important as battle courage. Throughout his career he witnessed several of his commanders get bogged down in orders and rules, resulting in the loss of initiative or sailors in battle. He felt that leaders needed the “political courage” to sometimes disobey superiors to accomplish what was in the general interest of the cause. He once said to the Duke of Clarence: “To serve my king, and to destroy the French, I consider as the great order of all, from which little ones[subsequent orders] spring; and if one of these little ones militate against it…I go back and obey the great order and the object.” His disobedience, or putting the mission before his career, avoided disaster or accomplished the overall intent on more than one occasion.
- Communicate clear and simple concepts. Reinforce with discussion. In addition to producing memorandums that explained what his subordinates should do, he also brought them in for dinners and councils to discuss the greater picture and his intent so they could exercise proper judgment when required. On the eve of battle, Nelson penned his famous Trafalgar Memorandum, and wrote “something must be left to chance…in case signals can neither be seen nor perfectly understood, no Captain can do very wrong if he places his ship alongside that of the enemy.”
- Lead by example. Nelson understood the realities of combat, and he understood that when leaders set the example, their subordinates are more likely to rise to the challenge. Nelson’s sailors loved him, because he shared the dangers alongside them. In his final battle, The Battle of Trafalgar, Nelson put himself at the deadliest spot of the battle, the flagship Victory. This location allowed him to quickly modify battle plans as well as be with the ship that would take aim to destroy the enemy’s command and control ship. Even though his personal example on Victory ultimately cost him his life, it provided the fuel for those whom he commanded to eventually overcome the French and win one of the most famous battles in naval history.
- Trust is a powerful enabler. Mahan wrote that Nelson’s trust in subordinates rested, “upon the presumption in others of that same devotion to duty, that same zeal to perform it…which he found himself.” Before the first shots of Trafalgar were fired, he sent a note to all his ships letting the men know, he trusted that they would do their duty. Nelson had absolute faith in those who followed him.
The Army’s definition of mission command can be found within the pages of ADRP 6-0, Mission Command; it is the exercise of authority and direction by the commander using mission orders to enable disciplined initiative within the commander’s intent to empower agile and adaptive leaders in the conduct of Unified Land Operations. The philosophy of Mission Command is guided by six principles: build cohesive teams through mutual trust, create shared understanding, provide a clear commander’s intent, exercise disciplined initiative, use mission orders, and accept prudent risk. Adopting a philosophy of mission command allows units to take advantage of fleeting opportunities to seize, retain, and exploit the initiative in combat.
Throughout his career, Nelson built cohesive teams based on trust. He was able to develop a shared understanding and a clear commander’s intent through constant conversation and interaction with subordinate leaders, along with mission orders, like the Trafalgar Memorandum. And it was through these mechanisms that he ensured his subordinates exercised prudent risk and disciplined initiative.
Napoleon Bonaparte once wrote, “Peruse again and again the campaigns of Alexander, Hannibal, Caesar, Gustavus Adolphus, Turenne, Eugene, and Frederick. Model yourself upon them. This is the only means of becoming a great captain, and of acquiring the secret of the art of war. Your own genius will be enlightened and improved by this study, and you will learn to reject all maxims foreign to the principles of the great commanders.” Today, as we operate with the leadership philosophy of mission command, Nelson should be one of those commanders. As his second in command, Admiral Cuthbert Collingwood, wrote of Nelson, “We must endeavor to follow his example, but it is the lot of very few to attain his perfection”.
[republished from 11/11/12]
When I see someone walking around with a poppy on their lapel at this time of year, I always feel very nostalgic and pleased that someone has donned a symbol synonymous with service and sacrifice. It may be worthwhile to remind ourselves of the precise connection between the poppy and the day in which we take time to recognize and thank all of the Veterans who have sacrificed for our freedom.
Growing up the son of a Canadian Armed Forces officer, I was always pleased when my Dad would break out his collection of poppies every year and pin one on the lapel of my blue blazer in the days prior to November 11th. Both his father and my mother’s father fought in the First World War. Both saw horrific combat and both were highly decorated for their service.
My Dad and his brother fought in the Second World War. My Dad arrived in Normandy after the invasion in July 1944 and in his words, crawled across Northern Europe through France, Belgium, the Netherlands and into Germany before the end of the war in 1945. He did not talk much of the war, but when he did, he always told me how violent and horrible an experience it was. Fiercely proud of his unit, The Lord Stratcona’s Horse Regiment, he donned the poppy every year on the anniversary of “Rememberance Day.” He captivated my attention with the story, as told by his father, of the end of World War One on the 11th hour of the 11th day of the 11th month of November 1918. Both belligerents fired every artillery shell possible across the lines to kill as many men as possible before the clock struck 1100. Many men died in those last minutes of the war. How senseless… how tragic… and how prophetic of a peace that would not last, requiring my dad to don the uniform and go overseas to finish the job that his father could not.
Every year at this time, my dad also loved to recite the poem, “In Flanders Fields” by the Canadian surgeon, LCOL John McRae from Guelph, Ontario. He was very proud of the fact that a Canadian had written this timeless testament to the brave young soldiers who lost their lives in the Second Battle of Ypres, near Flanders, in Belgium. McRae was a Major when he wrote the poem after an unsuccessful attempt to save the life of a young Canadian wounded in battle. He jotted down his emotions while looking across a brilliant field of poppies that peacefully swayed back and forth in the breeze and in stark contrast to the carnage that existed nearby in the trenches. The poem was published in London in 1915 and became world renowned almost overnight.
My dad had it memorized and I always listened intently when he repeated it to me.
In Flanders Fields the poppies blow
Between the crosses row on row,
That mark our place; and in the sky
The larks, still bravely singing, fly
Scarce heard amid the guns below.
We are the Dead. Short days ago
We lived, felt dawn, saw sunset glow,
Loved and were loved, and now we lie
In Flanders fields.
Take up our quarrel with the foe:
To you from failing hands we throw
The torch; be yours to hold it high.
If ye break fait
h with us who die
We shall not sleep, though poppies grow
In Flanders fields
Sadly, McRae never made it back home as he died in the field of pneumonia and other complications while taking care of the troops.
Almost one hundred years have passed since Major McRae wrote the poem. He is but one of millions of selfless men and women under arms who have served and sacrificed for their country.
As we spend time with family and loved ones on 11 November, we remember the sacrifice of the countless young men and women who have served or are now standing the watch. Many have paid dearly for their service in Iraq and Afghanistan with life altering injuries. Others, sadly, have paid the ultimate sacrifice. It is essential that we take time out to remember them and thank them.
If you are so inclined, don a poppy… I will.
During the mid 20th century, with the United States having been part of the defeat of the Axis during World War II and the beginning of Cold War with a former ally, the Soviet Union, California had two infantry divisions, the 40th and 49th, as the primary units of its Army National Guard. At the time, California had a population of thirteen million residents in 1955. As time passed, the 40th became an armor division, the 49th was inactivated, and the 40th once again became an infantry division. Later the 40th was transformed into a multi-state division, which it had originally started as in World War I, with only one of four combat brigades being primarily from California. Thus at its height during the 20th Century the California Army National Guard had at least thirty-four thousand Soldiers compared to about twenty thousand Soldiers who are serving today out of the thirty-eight million residents of the state.
As the California National Guard was not a recipient of draftees during the mid 20th century, and the National Guard remains a volunteer force, this has me wondering as to the disparity between the ratios of California Army National Guard Soldiers then compared to now. When both the 40th Infantry Division and 49th Infantry Division were active, the ratio between Soldiers to state residents in 1955 was about 1 to 382; today that ratio is about 1 to 1900. Especially after the United States, and many units of the California National Guard, has been involved in multiple conflicts since the September 11 attacks, should not California be able to support a larger number of Soldiers due to the increase of combat veterans who live in the state?
Therefore, here is an idea to increase the number of Soldiers serving California that may be cost effective. As I have not ran the numbers the idea is definitely open to criticism and reviewing, which I am interested in receiving, and that can only help improve the concept. Although not part of the California Army National Guard, the California Military Department has the California State Military Reserve (CSMR) and California Naval Militia. Both forces are voluntary organizations, operating under military discipline, at a relative low cost due to the units being voluntary organizations not subject to Title 10 of the U.S. Code. As California is the largest state by population in the United States it should be safe to say that it also has the largest population of combat veterans in the United States, as slightly greater than 2.5 million veterans reside in California in 2000. As I understand it, Soldiers in the CSMR pay for their own uniforms, attend drill like their National Guard counterparts, and do not receive drill pay, but paid by the state if activated.
Thus, if the CSMR begin to establish and activate units comprised of combat veterans, who meet the normal volunteering requirements for the CSMR, California should be able to increase the number of Soldiers it can call upon during times of emergency. To incentivize combat veterans to volunteer to serve in these units, the state can grant those Soldiers a deduction from their state income tax equal to the pay they would receive if they were California Army National Guard Soldiers for the drills that they attend. Depending on the number of combat veteran California residents who volunteer for these units, it could be possible to establish a new brigade. To test the concept, after necessary legislation is written and signed into law that will allow for the test of the concept, the CSMR could begin by attempting to form an infantry company, which would be about 160 Soldiers, and see how it functions. If the concept at the small scale proves successful, then the number of units can be increased following this idea, and perhaps other states can find the concept useful to them as well. If the concept proves unsuccessful, the state is only out the tax revenue that it would have received from those combat veterans who volunteered, and their unit disbanded.
Time is a limited resource for leaders. While many leaders are passionate about leader development, they don’t always have time to study for self-development or plan development sessions where participants sit around and discuss an article, book or other topic. Both avenues of development are easily disrupted by competing priorities. Social media and mobile technology platforms are great resources for leaders to interact with others and build relationships that will lead to learning and development. One platform that works well is Twitter. The capabilities of Twitter combined with mobile platforms allow both self-development and leader-led professional discussions to take place in any location, at any time, and not be restrained by time and location. This post is about using Twitter for self-development and leading professional discussions as part of a leader development program.
Twitter 101 (Skip ahead to Leader Development if you are familiar with PLNs, self-development and Twitter)
Twitter is one resource that leaders can use for learning by developing a Personal Learning Network (PLN). A PLN is an informal learning network that consists of the people a learner connects and interacts with for the purpose of learning. Learners create connections and develop a network that contributes to their professional development and knowledge(Click here for a good blog about PLNs) .The learner does not have to know these people personally or ever meet them in person. This network is relatively easy to set up over Twitter and is a simple and powerful way to both self-develop and develop others. Twitter can be a great source of information if you know how to search for and evaluate the sources. There is a wide variety of information available on Twitter; for example, almost every magazine or professional publication posts on Twitter.
People use the hashtag symbol # before a relevant keyword or phrase in their Tweet to categorize those tweets and help them show up more easily in Twitter Search. The learner simply searches for the topic or, if they know a hashtag associated with the subject, they can use that as the terms for the search (see screenshots below). For example, one of the screen shots below shows a search for “Land Warfare” and the results delivered range from various individuals to “Doctrine Man”, to ”Pakistan Defence”.
Once the results are delivered learners can sort through the posts and evaluate the information. Clicking on a hashtagged word in any message shows all the other tweets marked with that keyword. Many of these posts will have links to blogs or articles that contain information the learner is looking for. As the learner finds reliable posts, they can follow the user and build their PLN ( It is also interesting to see who the users you are following, follow as well.) One way to evaluate whether a user on Twitter is credible is by the number of follows and followers they have. Learners can also check out previous tweets by the source, which is another way to evaluate if the source is credible or not. The reporters and other contributors that work for most major news organizations post to Twitter as well and can be a good addition to a PLN.
Leader Development Program
Twitter is a great way to share information to develop others. Leaders connect with their subordinates over Twitter and share relevant content with a hashtag. Twitter can also be used for “Twitter Chats” . Twitter chats are chats that occur using a hashtag. Instead of tweeting one-on-one learners are now engaged in a conversation with many people around a particular topic or piece of content such as an article or blog post. Pictures and other media can be used as well to add more context to discussions. Twitter chats lets a group maximize their time on Twitter and participate in existing conversations when it is convenient for them. Twitter chats can take place over extended periods, and from any location, extending learning and development well beyond the walls of an office, building, or other location commonly used for these sessions. This capability lengthens the period of engagement and can lead to higher quality discussions, which might not be attainable in a normal face-to-face professional development session that is constrained by time and location (a leader development session scheduled from 1-2pm in a conference room). There are also tools available, like Storify for example, that can help learners manage and archive the chats for later reference. Through professional discussion, leaders can get to know their subordinates better and evaluate their level of competence, which can help build trust in an organization.
Leaders develop subordinates by creating experiences. Professional discussion is one of those experiences. It canimprove learning and leader development across an organization. When time is a limited resource, social media is an excellent and simple way to engage subordinates in professional discussion.
The incredible power of innovation and entrepreneurship often produces an unfortunate exhaust of innovocabulations. Ideate is one of those words, and made quite a show of force at DEF 2013, hosted graciously at the Chicago Booth School of Business. However, as irritating as a not-words may be, ideate serves DEF2013 core spirit as a fitting metaphor. Ideate is merely the word “idea” verbed. Rather than concentrating as many do on creativity and the idea-creation process, DEF2013′s central thrust was the array of actions necessary to turn ideas into realities.
To foster that concentration on acting on ideas, the conference content was split between presentations and break-out problem-solving sessions.
Pleasant Surprise- Presentation Twitter-Wall:
Although the break-out sessions would be the conventional show-case of attendee collaboration, the integration of the twitter-wall to the presentations was a great way to get the audience engaged. While following the flow of “#DEF2013″ commentary on the boards, members of DEF could note particular phrases or points of the speaker, argue amongst themselves, or perhaps just be snarky cough #hipstermahan /cough.
The twitter conversation during presentations was also great track-two way of “meeting” forum attendees as you retweeted poignant observations on presentations, debated points of contention, or collaborated in solutions to problems brought up by speakers and form members alike. In the break sessions, I “met” forum members, though often much of the ice was already broken by conversations we’d already had I’ve long incredibly skeptical of twitter, but I found its use in this context a rather redeeming and collaborative experience!
Oh… and it was nice to get a tweet from Harris Teeter about the Oxford Comma too. As you can tell, some of us may have gotten off topic occasionally. But hey, why buy pizza not worth defending? #pizzafort
Presentations- A Mile Wide and a Mile Deep:
Part of me will never graduate college and will always enjoy a rich lecture. While the twitter was fun, it’s foundation was the excellent presentations being given by our guest speakers. You can find those on YouTube if you missed the live feed. Some of the video is uncut and you have to jump around to find the speeches, but many are well worth it.
Rather than turn this into a book report, I’ll delve into a by-no-means-comprehensive collection of points I thought were worth taking away.
You Don’t Have To Be The Innovator/Doing Your Homework: BJ Armstrong’s The “Gun Doctor” presentation is an instant classic, and has appeared in various forms at several venues. It only gets better with time. That said, a key piece of information from that presentation is that ADM Sims started with an innovation from someone else that he considered worth his effort and attention. The conference closed with a presentation by Phil Nevil of Power2Switch taking a similar angle, how his own ideas failed but he succeeded when he championed the cause of another. In both cases, an important part of championing an idea was doing the research: becoming familiar with both your market and your product. If ADM Sims hadn’t done his research and tests on Percy Scott’s continuous-aim firing, no one would have taken him seriously. Likewise, if people in private industry just “ideate” without doing tests, research, prototyping, and probing their market, they’re not “innovating”, you’re just talking.
Fighting a Loyal Insurgency Inside the System: Stealth, focus, and aggression are not always necessary when innovating, but can be good tools when combatting entrenched interests. Peter Munson’s speech was about how leaf-eaters learn to defend the system for at the detriment of adaption and effectiveness and meat-eaters charge forward at opportunity. In an organization like the DoD, there is a reality to the necessity and purpose for the system and its leaf-eater accolytes. Innovators must carefully pick and choose their battles. This idea was summed up by the delightful peregrine falcon, Dora. Play in the system (like dora moves stealthily through the clouds) and aggressively attack when opportunity arises (poor, stupid duck). If Dora flew around squawking all day and making a mess without that focused action, too many leaf-eaters would be alerted and defend their steaming piles of process.
Building an Army: Human capital is a critical part of innovation, if not the tipping-factor in-and-of itself. Howard R. Lieberman’s presentation hit the hammer hard on the point of building a body of stakeholders and champions to help push your ideas. Don’t start with the question of what the value of your product is, but rather push what value it brings to people. Finding the meaning of your idea for other people is what builds stakeholders, who may be champions for your ideas or loyal foot-soldiers doing the testing and development who will sacrifice their time and resources to see your idea through to the end. Some of those stakeholders may provide top-cover. Many of his stories involved his company president giving him cover for his “special projects” that the board didn’t always agree with. The ground-forces are great for “taking the hill” of an idea, but close-air-support flying high in the chain of command can really change the equation. No man is an island, and no innovation is a one-man mission.
Execution, Execution, Execution: Every presentation was about how action, not creativity, is the germ of real innovation. That said, the second day of private-sector entrepreneur presentations was a wall-to-wall show of how the ability to find market-demand while developing the necessary supply is the center of the innovation universe. The difference between a real-life innovator and the chatting classes is action.
My one real criticism of the conference does lie in this category. I felt like the innovations we discussed were mostly historical or from private industry. We didn’t have a body of speakers who, as members of the military, wrestled with and executed significant innovations. That may be an indictment of our system and whether those people have been able to be truly successful or just that it is easier to success in the business world. Whatever the case may be, there will be plenty of years of DEF to find more live-streaming innovation successes within the life-lines. And yes, before you say it, I know DEF itself is a successful inside-the-lifelines success… but you know what I mean!
Don’t Get Killed in a Good Battle: Dan Moore’s presentation on breakthrough leadership through the lense of Boyd was particularly great because I found myself in a room full of Boydians debating the legacy of Boyd, army tactics, thrust lines, decision-analysis, etc… but while all of this was fascinating, the newest detail to a complete Boyd amateur like me was the disaster of his personal life. “To be or to do,” shouldn’t happen to the detriment of “being” things like a good father, husband, or just healthy individual. If you’re a hard charger and an innovator, the military needs you healthy, not burnt out fighting every battle to the hilt. You’re needed in far more than the one fight you might be in now. Dan Moore’s final point, and one to always keep close is, “don’t get killed in a good battle.”
USNI Is Awesome: Sam LaGrone’s presentation was about some self-evident truths.
There is far more material, and none of the descriptions are by any means comprehensive. While these are good takeaways, the speeches are definitely worth watching on the YouTube channel.
Breakout Groups- Thoughtifying:
What would an Entrepreneurs conference be without some actual innovating? It certainly wouldn’t be as fun. The afternoons at DEF were dedicated to breakout sessions intended to building actionable solutions to real-world problems.
I found my time in the PME “ideation” group to be an education in many already-existing processes of other branches that I wished the navy had, from selection-means-attendance to the USCG’s libertine “selection-ignores-rank”. I hadn’t realized how different the different services PME systems were, and I found it a bit depressing how some may put PME in the side-car when others described the rigor and seriousness of their selection processes.
Nathan Finney led our group, and the vast array of “free the beast” ideas to put education in the driving seat were, very pragmatically, whittled down to a single free and actionable item: use of twitter for class comprehension analysis by teachers. A great example of how the system would work was Michael-Bob Starr’s discovery that the reason he had an odd feeling he’d lost his audience for about 5 seconds was that I had tweeted “never trust a man with two first names,” during his speech. Of course, in the PME version, it wouldn’t be on all the screens and would be more a way for teachers to get input on comprehension, class observations, and the like.
Other great innovations were produced, from the Emotional Vitality Assitant (EVA) to create a hand-held link directly to mental health professionals to the DEF X-prize, rewarding military members for great ideas or great execution of ideas (we hadn’t decided yet). The dream of pushing half the acquisition system into the sea and replacing it with a 100 page paper was quite the utopian ideal, but no knives yet exist that are long enough to penetrate to the heart of the procurement beast.
The People are the Product
The lectures and break-out sessions were great, but the real reward of DEF2013 was meeting the people I’d only known through writing and reputation (or the ones I didn’t know, for that matter). In his closing words for the conference, a closing speaker said it best, “people don’t buy what you do, but why you do it.” No one came to DEF2013 to see a particular innovation or idea, but to spend a weekend chatting about their passions with people of the same level of intensity. Every branch was represented with civilians and veterans alike, but we were all there for the same “why.” They came because they believed in that process of critical thinking and seeking the greater good. We didn’t seek innovation for innovation sake, but we sought mission victories, safety and effectiveness for our fellow warfighters, good stewardship of the resources in which we were entrusted, and the importance of good ideas having their day in the arena. DEF2013 didn’t create an innovation, it bolstered the community that is going to build them together.
By Mark Tempest
What is the role of ground forces as the conversation revolves around the Air Sea Battle Concept?
Is an emphasis on air and sea power sending the right message, driving balanced thinking, and sending the right messages to our friends and competitors?
Building off his article in the May 2013 Armed Forces Journal, Back To Reality, Why Land Power Trumps in the National Rebalance Towards Asia, our guest for the full hour will be Major Robert Chamberlain, USA.
He has served two tours in Iraq (2003-4 and 2007-8), studied refugees at Oxford on a Rhodes Scholarship, and is currently finishing his dissertation in Political Science at Columbia. He teaches International Relations at the West Point and, of course, the views he is about to express are his own and do not necessarily reflect those of the United States Military Academy, the Army, or the Department of Defense.
Join us live or listen from the archive later – if you can’t join us live – by clicking here.
By Jeong Lee
Speaking at the Association of the United States Army on the 12th, Admiral James Winnefeld, the Vice Chairman of the Joint Chiefs of Staff, told the audience that in future ground wars the tempo will be “shorter, faster-paced and much harder” because America’s adversaries will work to create a “fog of war.” Thus, the Admiral suggested that the Army “place more emphasis on the growth industry…of protecting American citizens abroad” in order to adapt to the fluid geostrategic environment.
Indeed, since the sequestration went into effect in March, many defense experts have been debating what the future may hold for the Army, the Marine Corps and the Special Operations Command (SOCOM). Whatever their respective views may be on the utility of landpower in future wars, all seem to agree on one thing: that in the sequestration era, the ground components must fight leaner and smarter.
For John R. Deni, a research professor at the U.S. Army War College’s Strategic Studies Institute, the answer seems to lie in the “Army-led military-to-military activities” which may provide stability in politically volatile regions “if only because most military forces around the globe are army-centric.”
Others beg to differ. Generals James Amos and Raymond Odierno and Admiral William McRaven seem to second Admiral Winnefeld’s claim when they argue that today “the need to conduct large-scale aid and consequence management missions, both within the United States and internationally, is certain to grow.” General James Amos, the Marine Corps Commandant, also recently echoes this view when he advocates a lighter but mobile Marine Corps because he believes tomorrow’s conflicts will likely involve “violent extremism, battles for influence, disruptive societal transitions, natural disaster, extremist messages and manipulative politics.”
However, if the United States Armed Forces is truly concerned about raising a cost-efficient and versatile ground force, it can merge the Army, the SOCOM and the Marine Corps into one unified service branch. This idea is not new. As far back as 1994, the late Colonel David Hackworth advocated the merger of the Army and the Marine Corps because their missions seemed to overlap. He went so far as to claim that the Department of Defense (DoD) could save “around $20 billion a year.” Nevertheless, absent in Hackworth’s column was a coherent blueprint for how the DoD could effectively unify its ground components into a cohesive service because Hackworth did not flesh out his strategic vision for what 21st Century wars may look like.
Which raises a very salient question as to what America’s strategic priorities should be. In a perceptive op-ed, Mark Fitzgerald, David Deptula and Gian P. Gentile aver that the United States must choose to go to “war as a last resort and not a policy option of first choice.” To this must be added another imperative. The United States Armed Forces must prioritize homeland defense as its primary mission and rethink the mistaken belief that the United States can somehow secure its interests through “lengthy military occupations of foreign lands.”
Thus, this newly merged service must redirect its focus towards countering cyber warfare and CBRNe (Chemical, Biological, Radiation, Nuclear and explosives) attacks and should work towards bolstering its counterterrorism (CT) capabilities. This is because, due to the convergence of the global community, the United States may be vulnerable to attacks from within by homegrown terrorists and drug cartels—all of which may wreak havoc and may even cripple America’s domestic infrastructures.
Reorientation of its mission focus may also require that the new service reconfigure its size. After all, as Chairman of the Joint Chiefs of Staff, General Martin Dempsey wrote in Foreign Affairs, “Washington should remember that the size of the armed forces is not the most telling metric of their strength.” One solution is to adopt the so-called “Macgregor Transformation Model (MTM)” centered around the combat group concept which may reduce the strength of the new service “yet in the end produce a force that has greater combat capability…[and] more sustainable.” This model may provide the United States with a deployable fire brigade in the event of a national emergency or an international crisis. Already, the bases from which to adopt this viable model exist in the form of Army brigade combat teams (BCTs) and Marine Air-Ground Task Forces (MAGTFs) of various sizes.
Should the United States decide that it needs to project its hard power abroad to guard its interests, it could deploy the Special Operations Forces (SOF) components of the new service in tandem with UAV (Unmanned Aerial Vehicles) to selectively target and neutralize potential threats. While the SOF and UAV surgical raids should not be viewed as substitutes for deft diplomacy, they can provide cheaper and selective power projection capabilities. Moreover, doing so could minimize the risks inherent in power projection and anti-access/area denial (A2/AD) missions which may potentially mire the United States in messy and protracted conflicts.
Last but not least, this new service could buttress interoperability and capabilities of allied forces around the globe through military-to-military exchanges. Although Deni was referring specifically to the Army-led initiatives when he suggested this, he may be correct that military-to-military engagements may help to promote America’s image abroad as a trusted guarantor of peace. But even more important, such activities may “mean fewer American boots on the ground.” However, implementing what the retired Marine General James Mattis refers to as the “proxy strategy” may be a better means by which the United States could “lead from behind.” Under this arrangement, while “America’s general visibility would decline,” its allies and proxies would police the trouble spots on its behalf.
Contrary to what many in the defense establishment believe, the austerity measures wrought by the sequestration have not been entirely negative. If anything, this perceived “crisis” has provided the much-needed impetus for innovative approaches to national defense. The proposed merger of the ground forces may provide the United States with most cost-effective and versatile service branch to defend the homeland and safeguard its interests abroad.
Please join us for Midrats at 5pm (Eastern U.S.) on Sunday, 18 August 13, for Episode 189: “The Union and Confederate Navies”:
The War Between the States, the American Civil War – whichever description you prefer – this crucible on which our nation was re-formed has legions of books, movies, and rhetoric dedicated to it. Most of the history that people know involves the war on land, but what of the war at sea?
What are details behind some of the major Naval leaders of both sides that are the least known, but are the most interesting? What challenges and accomplishments were made by the belligerents in their navies, and how do they inform and influence our Navy today?
Our guest for the full hour to discuss this and more will be James M. McPherson, the George Henry Davis ’86 Professor of History Emeritus at Princeton University. He has published numerous volumes on the Civil War, including the Pulitzer Prize-winning Battle Cry of Freedom, Crossroads of Freedom (which was a New York Times bestseller), Abraham Lincoln and the Second American Revolution, and For Cause and Comrades: Why Men Fought in the Civil War, which won the Lincoln Prize.
As a starting off point for the show, we will be discussing his book, War on the Waters: The Union and Confederate Navies, 1861-1865.
Please join us live or listen later by clicking here.
- March 9 Midrats Episode 218: Abolishing of the USAF, with Robert M. Farley
- DEF[x] Annapolis: Encourage the Innovators
- A History of the Navy in 100 Objects #48: Models of HMS St. George (1701) and USS Missouri (1944)
- Engineering and the Humanities: The View from Patna’s Bridge…
- A History of the Navy in 100 Objects #47: British Dockyard Models