6 ms·
Nobody has done more research on this than the US Military, specifically the special operations community. The key takeaways that you find in very effective SO
by AndrewKemendo 11y ago
Nobody has done more research on this than the US Military, specifically the special operations community.
The key takeaways that you find in very effective SOF teams are:
1. Clear and accepted authority chain (Top guy earned their place at the top)
2. Candid and constant communication/feedback between all members
3. A clearly defined, proven effective and specialized role for every member with each member knowing how each others role plays together
4. Common sense of purpose (Objective etc...)
5. Common experience (BUD/s, Q, FTC etc...)
If you have all of those then pretty much everything else falls into place. Note also that this has no requirement for everyone to being an "A" personality or whatever and has basically no bearing on what they do outside of work. Those aspects can help, but they can equally hurt depending on the egos involved.
- jmngomes 11y agoThis is very interesting, can you provide any information or research that led to those takeways? Thanks.
- AndrewKemendo 11y agoHere is a good starting point: https://hbr.org/2015/08/what-companies-can-learn-from-military-teams https://hbr.org/2015/08/what-companies-can-learn-from-milita... Team of Teams from McChrystal is a great book.
- kaffee 11y agoWhat do these acronyms mean? SOF, BUD, Q, FTC?
- kornish 11y agoI believe SOF is Special Operations Forces and BUD/S is Basic Underwater Demolition/SEAL training (the intense training regimen through which all incoming Navy SEALs must pass). Not sure about the others.
- AndrewKemendo 11y agoSorry. SOF: Special Operations Forces BUD/s: Basic Underwater Demolition/SEAL Training Course Q: Special Forces Training Course FTC: Field Tradecraft Course
- deleted 11y ago[deleted]
- sridca 11y agoI would like to hear about more about point number two. Specifically, is "talking about our insecurities, fears and aspirations" (quoted from the nytimes article) part of it?
- AndrewKemendo 11y agoNo, it's more about creating an environment such that you can tell your "boss" they fucked up, and how, they will say "you're right, lets fix it."
- sridca 11y agoOkay. That's in fact how the nytimes article started: > One engineer, for instance, had told researchers that his team leader was "direct and straightforward, which creates a [psychological] safe space for you to take risks." However the rest of the article went onto to talking more about expressing one's feelings and vulnerability. I think this is a key difference between Google's and the US Military's approach to team building.
- diffraction 11y agoIn short: andrewcommando commented without reading the article the military and google are very different organizations with different goals, so it's unlikely they will be run the same a perfect team in the military will not look like a perfect team at google. both organizations will wisely punt to other organizations when they come up against a challenge outside of their domains of expertise. for example: the military does not design and build its own aircraft/weapons/tanks, nor does google engineer and build its datacenters
- AndrewKemendo 11y agoIn short: andrewcommando commented without reading the article Ha, I actually did, but thanks. Also good guess on my team name (commando) ;) You are right though that it's not a 1:1 substitution but the principles align well.
- tsunamifury 11y agoThese are great qualities for making a team which follows orders and makes field decisions within a extremely narrow scope. These are terrible qualities for teams who are self-assigned, entrepreneurial, and have to disrupt standard accepted behaviors in order to create new products. For example in Number 4: How does this work when the teams assignment is to come up with an objective, rather than just have one assigned to them. Answer: They would splinter and struggle because they are following a chain of command. Which follows to Number 1: To make products you need a diverse set of leaders who share authority in varying decisions, not a chain of people who wrongly think themselves to be universal experts. This does require Number 3, but in a different cultural fashion that isn't so rigidly hierarchical. Basically these are great for teams who just take commands from the actual guy makes the decisions. Google and the NYT are interested in the teams that make decisions. I think the modern workplace is actually trying to UNDO these very narrow minded and ultimately damaging behaviors and their misapplication to the creation process.
- linkregister 11y ago> makes field decisions within a extremely narrow scope. What? Modern Western armed forces, and especially special forces units, make many independent decisions requiring great amounts of creativity and initiative. The hallmark of over 300 years of Western military units is the ability to operate without consulting the chain of command for every decision. Were you a member of an armed force from a more centralized military, such as Russia or China? If so, then your perspective makes more sense.
- vonmoltke 11y agoI know this is probably an unpopular idea around here, but I generally think "self-assigned" teams are a terrible idea. Without a top-level roadmap to guide progress a company would quickly devolve into an uncoordinated mess. Sure, it can birth some really innovative gems from a very large organization. That's the exception rather than the rule, though. This kind of "teams making decisions" structure nearly killed Sony when they started infighting and reinventing wheels. Google, IMO, succeeds in spite of rather than because of this structure at this point, and only because of their ridiculously high hiring bar. There is a middle ground between Google and, say, Lockheed where teams are given a general direction to pull to keep them organized and working towards the company's goals but are otherwise free to determine how to accomplish those goals on their own.
- glxc 11y agoself-selecting group who would join the military
- pellucide 11y agoIn other words, create a collaborative Robot.
- seeing 11y agoThe article contradicts your first point, and suggests too many takeaways are a sign of trouble. Was it better to let everyone speak as much as they wanted, or should strong leaders end meandering debates? Was it more effective for people to openly disagree with one another, or should conflicts be played down? The data didn’t offer clear verdicts. In fact, the data sometimes pointed in opposite directions. The only thing worse than not finding a pattern is finding too many of them.
- AndrewKemendo 11y agoIt doesn't though, I just didn't explain how that role works. Consider the "leader" as the lead coordinator rather than someone barking orders. Once all of the debate is over, a decision needs to be made and followed through with, with the understanding that new information will require tweaks or wholesale re-evaluation of the plan until completion. So in that sense, the leader ensures that everyone is executing their role well, and that everyone is aware of any deviations to it - while also delegating authority or decision making as needed as the task unfolds. It's way more nuanced and delicate than it would seem from the outside.
- gaius 11y agoAll true, but irrelevant. No-one is putting their life on the line for "shareholder value". Your cow-orker isn't going to take a bullet for you either. And whiteboarding a red-black tree is nothing like waterboarding in SERE...
- spitfire 11y agoThe US marines in particular went through a massive transformation int he 80's after their experience in Vietnam. The name people want to look up is John Boyd. I would hazard a guess the average Marine officer knows more about Kurt Gódel's incompleteness and its real life applications than the average techie.
- thornkin 11y agoBoyd's ideas are laid out really well by his acolyte Chet Richards in his book Certain to Win which applies the military theories to business. If interested at all in this space, check it out.
- AndrewKemendo 11y agoThanks for bringing up Boyd. He was my inspiration for joining the military actually. The OODA loop is in my opinion the best template for how to approach problems.
- deleted 11y ago[deleted]
- sangnoir 11y agoI'm not disagreeing with the US Military research, but the effectiveness of teams in command-and-control environments probably doesn't translate well to more voluntary, at-will engagements like your typical work-place. Besides, companies aren't (yet?) able to break-down and rebuild tween males as armies have been doing for millenia.
- daodedickinson 11y agoI wish they would start. I guess I'm far from a tween now but please draft me and instill discipline better than the schools I'm attending where no standards are properly enforced and the grade inflation is out of control. I'm tired of getting good grades for being the only one trying while I freak out trying to teach myself to fill all the massive holes in my education...
- AndrewKemendo 11y agoprobably doesn't translate well to more voluntary, at-will engagements like your typical work-place They do for the kinds of teams I am discussing.
- gjkood 11y agoI recently went through a Boy Scouts Adult Training called Wood Badge. The most important thing I learned there was a Team Dynamics study, reportedly used by the DoD, which was distilled into four words: Forming Storming Norming Performing What blew me away was that I could literally see this happening right in front of my eyes with a small team of kids who I was coaching for an FIRST Tech Challenge (FTC) Robotics competition. I finally understood the team dynamics and realized that I am not the only one experiencing it and it was not an anomaly. https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_development https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_de... http://www.dau.mil/pubscats/pubscats/pm/articles03/pat-ma03.pdf http://www.dau.mil/pubscats/pubscats/pm/articles03/pat-ma03....
- AndrewKemendo 11y agoForming Storming Norming Performing Oh boy, that's a huge piece of teambuilding training throughout the military. It's a good description of how new teams form. Unfortunately most teams don't get past the storming phase.
- groby_b 11y agoThat'd be because getting past Storming and through Norming actually requires leadership. The other two are good with hands-off approaches. Heck, Performing can even take a certain amount of ineptness in leadership without falling apart.
- lifeisstillgood 11y agoHave you got more references - they would be cool reading?
- deleted 11y ago[deleted]
- mathattack 11y ago#5 is very interesting. Top companies try to mimic this, but it's hard for companies that don't grow their own people. Accenture/Facebook/McKinsey/Goldman all have common training programs that they put new hires through. It might vary by function, but almost everyone does it. One caveat is that (in my limited experience) military hires tend to obsess a little too much on chain of command. Chain of command is important on the battlefield, but in corporate environments the best ideas come from anywhere. And in the best companies, people focus more on being "The best" than being "The leader".
- jacobr1 11y ago> but in corporate environments the best ideas come from anywhere I think the difference is that is important to have a clear process to make decisions. It doesn't need to be hierarchical, but it should avoid analysis paralysis or other ills of uncertainty.
- mathattack 11y agoYes. One system I've heard that works is a 5 point system. 1 - You decide without my input 2 - You decide with my input 3 - Joint decision equal input 4 - I decide with your input 5 - I decide without your input Most good decisions are Type 2 or 4, though sometimes they need to be others. (Compliance, etc.) Then one can say, "This is a type 4 decision - I need to hear you out, but it's on me."
- rpedela 11y agoI think common experience in a corporate setting can be achieved without formal training in certain cases. For example, if everyone involved in product development also does customer service on a semi-regular basis then that is common experience that can help bind the team.
- mathattack 11y agoYes. Smart companies come up with rituals that recreate this. Customer Service calls are a great example because they have big benefits above and beyond just team building. Engineers and execs who intuitively understand customers are invaluable.
- e12e 11y agoThere was an interesting study done on the Norwegian Naval Special Forces Command (Marinejegerne). Some years ago, there was a national plan to fold the branch in under central Special Forces Command in Norway (FSK) -- but there was some push-back from the Navy branch. In order to better quantify the cultural differences (if any) between them and other Norwegian Special Forces (eg: Army) -- they did the sensible thing: they reached out and got an external anthropologist (Tone Danielsen) to do a full anthropological study: http://www.ffi.no/no/Rapporter/12-00516.pdf http://www.ffi.no/no/Rapporter/12-00516.pdf (Summary in English in second paragraph). Article about the study in English: http://sciencenordic.com/tough-special-forces-don’t-strut-their-stuff http://sciencenordic.com/tough-special-forces-don’t-strut-th... As for the sibling comment in this thread wrt: "breaking down and building up tweens" -- while the training to get into the Norwegian Special Forces training is though, and the subjects are often young -- I think there might be more of a cross-over in organization/leadership/group dynamics than what might appear on the surface. There are a couple of things that are needed for military operations that are different from similar activities (eg: search and rescue) -- and parts of the military mind does go against what could be considered a sound human mind in today's society. War is inherently about violence and murder. But even if we do not want our programmers to actually be assassins/ninjas -- don't want them to actually have a killer mindset -- much of military training is about changing one's idea of what can be achieved by an individual and a team (to realize that one can indeed do the (previously) "impossible". To not give up, and part of the intense drills are part of making someone an expert. In physical arts, intense drilling is required for technique to become "good enough" for expert level (this is also AFAIK true for dancing, for example). One should also remember that as long as the organization in question is able to do meaningful self-reflection and improvement, training methods can change and result improve.
- abalone 11y agoThis is exactly the opposite of what the article says. Please don't try to hijack it with pro-military stumping. Excerpt: As the researchers studied the groups, however, they noticed two behaviors that all the good teams generally shared. First, on the good teams, members spoke in roughly the same proportion, a phenomenon the researchers referred to as "equality in distribution of conversational turn-taking." On some teams, everyone spoke during each task; on others, leadership shifted among teammates from assignment to assignment. But in each case, by the end of the day, everyone had spoken roughly the same amount. "As long as everyone got a chance to talk, the team did well," Woolley said. "But if only one person or a small group spoke all the time, the collective intelligence declined." Second, the good teams all had high "average social sensitivity" — a fancy way of saying they were skilled at intuiting how others felt... That is way more fluid in terms of authority and touchy-feely than rigid military hierarchies. Which makes sense given that roles are much more fluid in creative enterprises and there's no life-or-death quick decisionmaking that favors decisiveness over debate. Not to say that there's no creative thinking in the military, but role and responsibilities can be more clearly defined at the outset.
- AndrewKemendo 11y agoThis doesn't contradict it at all and you are confusing line-infantry with SOF, which is specifically what I am referring to. CONOPS (Concept of operations) planning goes exactly like described with equality of input throughout the process. In fact it goes beyond that with team members continuously providing input throughout the run-up and execution of whatever operation is in play. In many cases during whatever operation is happening, any team member, regardless of rank, can call "knock it off" if something is not going well and the team will respond to that. That is way more fluid in terms of authority and touchy-feely than rigid military hierarchies Again, this rigidity of hierarchy is a myth within high performing SOF teams (CAG (Delta), DEVGRU, 75th Ranger Regiment etc...) there's no life-or-death quick decisionmaking that favors decisiveness over debate. Again, this misrepresents how battlefield decisions get made and overplays how democratic decisions are within [insert startup]. There is advantage to "violence of action" - meaning making a decision can be made and emphatically executed quickly - but it's not the case that it needs to be approved by TOP (the leader). One of the key benefits of SOF is that everyone has the ability to make a decision that might veer from the plan without it being insubordination or some other offense.
- bootload 11y ago"Nobody has done more research on this than the US Military, specifically the special operations community. The key takeaways that you find in very effective SOF teams are:" This is insightful, though comparing SOF teams and commercial work teams fails in the critical areas of complex interdependency and trust. [0],[1] I think what this google study highlights most is, candidates are not selected for man management and emotional robustness: ie: emotional honesty, self awareness and the ability to equally lead and follow. This cannot be taught. Emotions are traits. They can be shaped somewhat through team assignment as shown with the experience of Matt Sakaguchi. [0] Barbara D. Adams, Ph.D. and Robert D.G. Webb, Ph.D., "Trust in Small Military Teams" A great read on the qualities of complex interdependent teams ~ http://www.dodccrp.org/events/7th_ICCRTS/Tracks/pdf/006.PDF http://www.dodccrp.org/events/7th_ICCRTS/Tracks/pdf/006.PDF [1] You fail, people around you get dead. Those around you fail, visa versa. The mission is compromised. You do not see sacrifice & self sacrifice like this in commercial world.
- groby_b 11y ago> emotional honesty, self awareness and the ability to equally lead and follow. This cannot be taught. Emotions are traits. At the very least - [citation needed]. The medical community seems to disagree on that when it comes to teaching self awareness, at least for the majority of students[1][2]. I'm not sure what you mean by "emotional honesty", so it's hard to reply to that. If that's the equivalent of emotional intelligence - yes, that is teachable. Quite well. [1] http://www.bpsmedicine.msu.edu/pdf/22-%20%20ctstudypstrng.pdf http://www.bpsmedicine.msu.edu/pdf/22-%20%20ctstudypstrng.pd... [2] http://www.aacp.org/resources/education/cape/Documents/Habits%20of%20the%20Mind/2005%20Enhancing_Self_Awareness_in_Medical_Students.pdf http://www.aacp.org/resources/education/cape/Documents/Habit...
- bootload 11y ago"emotional honesty" Emotional honesty is pretty simple. Will you speak up when necessary, even if it contradicts peers or the leader? What was the last time you told the boss, "this is a stupid idea Boss, change it, or this will happen" and then the boss does so without recrimination? Remember the outcome, not ego matters. As for the field of medicine, of which I know nothing about, in Melbourne (Aus), selection into health sciences is filtered by both self awareness, emotional maturity and smarts via both academic results, independent Uni examination (Monash) and panel interview. This the "spectrum" filter for those sufficiently smart enough to get through the academics, yet are more suited to research. Could you teach MDs to program and work at google? Probably. Could you teach the clinical skills MDs require to make medical decisions on patients to Google SEs? Probably not. Doctors work with people. Google engineers work with languages and data on silicon.
- vacri 11y ago> 3. A clearly defined, proven effective and specialized role for every member with each member knowing how each others role plays together This is much easier for a SEAL team, which has "someone else" dealing with all the other stuff, from procurement to catering to writing the paychecks. As a result, the same rule will work for making teams in an enterprise, but a SMB cannot do this - there isn't much room for "not in my job description" at a SMB.
- toast0 11y ago> but a SMB cannot do this - there isn't much room for "not in my job description" at a SMB. 90% of my current job is doing what is nobody's job. (10% is my 'main area of responsibility' :)
- kafkaesq 11y agoA couple of things. For one, the motivations, constraints, and goals of a software development team (or the vast majority of business units, for that matter) are clearly quite different from those of military units. For another, that same culture which you are praising to the rafters (that of the U.S. Special Forces) is also famously knowing for producing colossally obscene fuckups -- of which on one in particular https://en.wikipedia.org/wiki/Kunduz_hospital_airstrike https://en.wikipedia.org/wiki/Kunduz_hospital_airstrike may, in just 45 minutes, very well have undone all the putative good the U.S. and its allies were trying to accomplish in all of their 14 years in Afghanistan. So on balance it seems that the culture of elite U.S. military unites is something to be shunned and avoided in civilian contexts, rather than followed and replicated.