Wayne Hale Blog

Status
Not open for further replies.
T

Testing

Guest
<p>Some of you may have seen my posts&nbsp; of Wayne Hale's Blogs in the past. Get used to it.</p><p><span class="blog_name">Wayne Hale's Blog</span> </p><div class="default_style_wrap"><span class="post_header">Stifling Dissent</span> <div class="entry"><p class="posted-top_blog">Posted on Jan 29, 2009 10:46:58 PM | Wayne Hale | 0&nbsp;Comments &nbsp;&nbsp; </p><dl class="previously"><dd class="summary"><table border="0" cellspacing="0" cellpadding="0"><tbody><tr><td><p>I've got a video that you need to watch, but first I need to explain why you need to watch it and what lesson I hope you will take away.</p><p>The Columbia Accident Investigation Board said that NASA - and specifically the Space Shuttle Program - stifled dissenting opinions which might have prevented the accident.&nbsp; Particularly the action was pointed toward the Mission Management Team.&nbsp; As the new Deputy Program Manager, I was assigned the task of restructuring the MMT and providing means for listening to dissent.&nbsp; Somewhere along the way I acquired the informal title of 'culture change leader'.&nbsp; I took this to heart and changing the culture to be more welcoming to alternate or dissenting opinions was a task that took a lot of my time and attention.</p><p>During the long days of returning the space shuttle to flight the question frequently came up as to how we were doing changing the culture.&nbsp;&nbsp; My answer, as honest as I could make it, was that we were making progress, making changes, improving the situation, but that changing the culture was hard and we had a long way to go.</p><p>Periodically reports came from various sources that NASA people did not feel safe or welcomed in stating dissent or alternate recommendations.&nbsp; This caused a lot of angst among NASA leadership who felt that they were doing everything possible to change the culture and saw progress being made.&nbsp; NASA is a large and diverse organization and it is obviously difficult to winnow out all the old culture in all the niches around the agency.&nbsp; After all, the focus was on the shuttle program and especially the MMT.&nbsp; It should only be expected that parts of the organization far afield might be lagging behind.</p><p>Personally, I was heartened by a lot of the change which I was observing.&nbsp; But it was still hard to draw out introverted engineers who are by their nature conflict averse.&nbsp; Formal settings tend to put sociological pressure on low-ranking folks to keep quiet, so we tried to develop informal settings; ask more questions, listen more..</p><p>Still, it is hard to tell how effective the change effort has been.&nbsp; Even though I personally try to solicit information from a variety of folks in a variety of places and ways, the reports were generally that alternate opinions are welcomed, dissent is accepted and evaluated, and we are doing better than ever.</p><p>But the anonymous polls and internet feed back says there is still a lot of work to be done.</p><p>Recently I had a couple of events which affected my thinking on this.&nbsp; I have been out of the Shuttle Program manager job for almost a year now and a trusted coworker just a week ago told me that people in his organization had been prevented from giving me important alternative choices for some program choices that occurred a couple of years ago.&nbsp; This was staggering. It was happening right in front of me and I was totally unaware that people - who I trusted, who I hoped would trust me - kept their lips sealed because somebody in their middle management made it clear to them that speaking up would not be good.</p><p>Astounding.&nbsp; </p><p>About two weeks ago an activity that Mike Coats started at JSC had an all day report out period.&nbsp; The Inclusion and Innovation Council was to propose ways to improve innovation at NASA.&nbsp; Various teams reported out, including one team of young employees who has the task to talk about the barriers to innovation at NASA -- specifically at JSC.</p><p>The video attached was their result.&nbsp; I found it extraordinarily funny and not at all funny.&nbsp; These young people have obviously found themselves in situations RECENTLY in which managers at various levels applied sociological and psychological pressures to keep them from bringing ideas forward.</p><p>I am convinced that if we asked the managers who were the models for this little morality play whether they stifled dissent or welcomed alternate opinions, they would respond that they were welcoming and encouraging.&nbsp; Probably because they have that self image.</p><p>But actual behavior, not inaccurate self perception, is what we really need.&nbsp; </p><p>So now, watch the video, then come back and lets talk about what I think we really need to do about it:</p><p><font size="2" color="#0000ff"><u>http://www.youtube.com/watch?v=_424YskAfew</u></font></p><p>Are you done with it?&nbsp; Maybe you should go back and watch it a couple of times.&nbsp; I did.</p><p>I feel like the early civil right pioneers must feel; the overt bad behavior is gone underground.&nbsp; People say the right things in public discussion of how they should act, then behave in the bad old ways in small or private settings.</p><p>Since these behaviors are still being practiced at NASA, here is what I believe managers need to do</p><p>1.&nbsp; Break out of the sandbox.&nbsp; Even if it is not your area, the agency needs the best ideas to succeed in our goals.&nbsp; If you have subordinates who have ideas for improving other areas, it is important to get those ideas into the open where they can compete in the marketplace of ideas, or at least get a technical review.</p><p>2.&nbsp; If subordinate has an idea that has been tried before and didn't work, consider that times may have changed and it might work now or with improvements that you know of.&nbsp; In the final extremity, your subordinate needs more than the curt dismissal that its been tried before and didn't work - you need to explain it to them.</p><p>3. Managers at all levels need to provide safe places and times for interaction that skips levels in the chain of command.&nbsp; </p><p>&nbsp;</p><p>Well, that is enough to start with.&nbsp; Looks like we still have a long way to go and the first step is to know that you still have a problem.</p><font size="2" color="#0000ff"><font size="2"><p><font size="2" color="#0000ff"><u>http://www.youtube.com/watch?v=_424YskAfew</u></font></p></font></font>
 
V

vogon13

Guest
<p>&nbsp;</p><p>I recall an issue from many years ago on some Shuttle electronics.&nbsp; It was brought to our attention that various epoxies used in manufacturing integrated circuits release various gases during curing.&nbsp; For the exterior of the devices, the gases dissipate harmlessly.&nbsp; For devices with sealed volumes, the gases are trapped inside.&nbsp; What kind of pressure ??&nbsp; Dunno.&nbsp; Are the gases damaging to the silicon in the devices ??&nbsp; Dunno.&nbsp; Do we know for sure this is not a problem ??&nbsp; Dunno. Do we know for sure this is a problem ??&nbsp; Dunno.</p><p>&nbsp;</p><p>Since our company purchased the devices, and did not make them, it seemed to be out of our responsibilities to raise the issue.&nbsp; The device manufacturers had certified them as acceptible for manned flight, and apparently all the paperwork was okey dokey.&nbsp;&nbsp;</p><p>&nbsp;</p><p>So, do we raise a flag ??</p><p>&nbsp;</p><p>We didn't.&nbsp; Nothing bad ever happened.&nbsp; Would the effort expended on checking our (non) issue have let something else go through unchecked ?? &nbsp; Dunno.</p><p>&nbsp;</p><p>&nbsp;</p><p>Unsettling experience, just never had the 'warm fuzzy' that we did the right thing . . . .</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p> <div class="Discussion_UserSignature"> <p><font color="#ff0000"><strong>TPTB went to Dallas and all I got was Plucked !!</strong></font></p><p><font color="#339966"><strong>So many people, so few recipes !!</strong></font></p><p><font color="#0000ff"><strong>Let's clean up this stinkhole !!</strong></font> </p> </div>
 
T

Testing

Guest
<p>It was brought to our attention that various epoxies used in manufacturing integrated circuits release various gases during curing.&nbsp; For the exterior of the devices, the gases dissipate harmlessly.&nbsp; For devices with sealed volumes, the gases are trapped inside.&nbsp; What kind of pressure ??&nbsp; Dunno.&nbsp; Are the gases damaging to the silicon in the devices ??&nbsp; Dunno.&nbsp; Do we know for sure this is not a problem ??&nbsp; Dunno. Do we know for sure this is a problem ??&nbsp; Dunno.&nbsp;Since our company purchased the devices, and did not make them, it seemed to be out of our responsibility.</p><p>Outgassing data for virtually every Space rated material. If it flew, calm yourself. It never would have otherwise.<br />http://www.outgassing.nasa.gov/</p> <div class="Discussion_UserSignature"> </div>
 
V

vogon13

Guest
<p>&nbsp;</p><p>I appreciate that, and it is somewhat helpful.&nbsp; But the gases technically, weren't outgassed.&nbsp; They remained trapped inside the ICs.&nbsp; We accidently discovered the gases when an outside lab sliced open a device for inspecting an unrelated problem and the gases nearly damaged some of their sensitive equipment.&nbsp; It seemed everyone we talked to (a small sample, however) was 'surprised' the gases were trapped inside the device housing.&nbsp; Seems like 'surprises' are by definition ungood in spaceflight.</p><p>&nbsp;</p><p>IIRC, the gases were CO CH4 H2.&nbsp;&nbsp;</p><p>&nbsp;</p><p>&nbsp; </p> <div class="Discussion_UserSignature"> <p><font color="#ff0000"><strong>TPTB went to Dallas and all I got was Plucked !!</strong></font></p><p><font color="#339966"><strong>So many people, so few recipes !!</strong></font></p><p><font color="#0000ff"><strong>Let's clean up this stinkhole !!</strong></font> </p> </div>
 
T

Testing

Guest
<p><BR/>Replying to:<BR/><DIV CLASS='Discussion_PostQuote'>&nbsp;I appreciate that, and it is somewhat helpful.&nbsp; But the gases technically, weren't outgassed.&nbsp; They remained trapped inside the ICs.&nbsp; We accidently discovered the gases when an outside lab sliced open a device for inspecting an unrelated problem and the gases nearly damaged some of their sensitive equipment.&nbsp; It seemed everyone we talked to (a small sample, however) was 'surprised' the gases were trapped inside the device housing.&nbsp; Seems like 'surprises' are by definition ungood in spaceflight.&nbsp;IIRC, the gases were CO CH4 H2.&nbsp;&nbsp;&nbsp;&nbsp; <br />Posted by vogon13</DIV></p><p>If they did not meet a leak rate of 1x10-7 SCCM or better they did not fly. Not released in flight. Inside good, outside bad. Released in a destructive test and they knew what it was? Good.</p><p>http://en.wikipedia.org/wiki/Hermetic_se al</p> <div class="Discussion_UserSignature"> </div>
 
M

MeteorWayne

Guest
<p>Thanx Testing. When Wayne tells me to watch something, I watch it.</p><p>Very sobering and unsettling...</p><p>The Other Wayne</p> <div class="Discussion_UserSignature"> <p><font color="#000080"><em><font color="#000000">But the Krell forgot one thing John. Monsters. Monsters from the Id.</font></em> </font></p><p><font color="#000080">I really, really, really, really miss the "first unread post" function</font><font color="#000080"> </font></p> </div>
 
R

rocketwatcher2001

Guest
<p>That reminds me of a great training film I saw a few years ago about aviation maintenance management.&nbsp; It was made by the Canadians.&nbsp; It was very sobering, because I had seen much of it in real life, I wish I had seen it 10 years before.&nbsp; </p><p>I hope this video is being taken to heart at all levels of NASA.&nbsp; </p> <div class="Discussion_UserSignature"> </div>
 
T

ThereIWas2

Guest
<p>Its a good thing that Tom Dolan and John Houbolt did not give up on their idea for Lunar Orbit Rendesvous, when even Werner von Braun did not think of it.</p><p><u> </u><br /></p> <div class="Discussion_UserSignature"> <p><span class="postbody"><span style="font-style:italic"><br /></span></span></p> </div>
 
S

shuttle_guy

Guest
<p><BR/>Replying to:<BR/><DIV CLASS='Discussion_PostQuote'>Its a good thing that Tom Dolan and John Houbolt did not give up on their idea for Lunar Orbit Rendesvous, when even Werner von Braun did not think of it. <br />Posted by ThereIWas2</DIV></p><p>&nbsp;</p><p>It was not that he did not think of it, he did know of the option He just did not have the confidence that LOR was a good idea based on the state of the technology at the time. Also he wanted to build the NOVA launch vehicle not stop with the Saturn Five.<br /></p> <div class="Discussion_UserSignature"> </div>
 
T

ThereIWas2

Guest
Yes, that did not come out correctly.&nbsp;&nbsp; At least in the Earth to the Moon TV series, the LOR idea met the kind of resistance shown in this video, I think largely because the idea was coming from outside of normal channels.&nbsp; At least that is how EttM portrayed it. <div class="Discussion_UserSignature"> <p><span class="postbody"><span style="font-style:italic"><br /></span></span></p> </div>
 
S

shuttle_guy

Guest
<p><BR/>Replying to:<BR/><DIV CLASS='Discussion_PostQuote'>Yes, that did not come out correctly.&nbsp;&nbsp; At least in the Earth to the Moon TV series, the LOR idea met the kind of resistance shown in this video, I think largely because the idea was coming from outside of normal channels.&nbsp; At least that is how EttM portrayed it. <br />Posted by ThereIWas2</DIV></p><p>Yes, the "Not Invented Here" stance is often&nbsp;very difficult to over come.<br /></p> <div class="Discussion_UserSignature"> </div>
 
T

trailrider

Guest
<p>When Challenger blew up, I was working on the SRB Decelerator Subsystem (parachute recovery system).&nbsp; As part of the investigation, we went through a whole bunch of document searches, etc.&nbsp; Our system had <em>nothing</em> to do with the accident.&nbsp; As a matter of fact, the drogue chute attached to the frustum (conical section of the nose cone used to hold and act as a deployment "bag" for the main parachutes) of the lefthand booster was about the only thing that worked, and was seen floating down to the ocean!</p><p>As part of our reporting, I looked at the Downstage Postflight reports from previous flights, something we never did, as below the SRB forward deck was not our cognsizance.&nbsp; Right there, on the reports for the previous August and the April before that was the report of seals leaking 120 degrees around the circumfrence of the joint, on IIRC both boosters!&nbsp; The thought crossed my mind...for just an instance...that had I seen that, perhaps I could have said something to somebody.&nbsp; Then "sanity" prevailed: Had I said anything to my management, I would have been told, "Forget it! That's none of our business!"&nbsp; How do I <em>know</em> that's what I would have been told?&nbsp; Because there were numerous other things that I'd seen of perhaps not so vital an issue, but within the program, the division and the corporation!</p><p>And we wonder why the aerospace and defense industry has trouble attracting young people from the STEM disciplines?&nbsp; Why should they?&nbsp; To be told, "Forget innovating, forget trying to make constructive suggestions! Just keep your head down, eyes on your work, and forget about asking for a raise, even if you do an outstanding job! Heck! You'll be lucky to have a job when you come back from lunch...if there is any lunch besides what you catch!</p>
 
M

MeteorWayne

Guest
Replying to:<BR/><DIV CLASS='Discussion_PostQuote'>Another installmenthttp://blogs.nasa.gov/cm/blog/waynehalesblog/posts/post_1233541742080.html <br />Posted by Testing</DIV><br /><br />Just a suggestion, you should probably include the title to encourage people to take the time to read it. Not necessary for me, since it's one of the things on my morning checklist <img src="http://sitelife.space.com/ver1.0/content/scripts/tinymce/plugins/emotions/images/smiley-smile.gif" border="0" alt="Smile" title="Smile" />&nbsp;but others might appreciate the subject du jour... <div class="Discussion_UserSignature"> <p><font color="#000080"><em><font color="#000000">But the Krell forgot one thing John. Monsters. Monsters from the Id.</font></em> </font></p><p><font color="#000080">I really, really, really, really miss the "first unread post" function</font><font color="#000080"> </font></p> </div>
 
C

CalliArcale

Guest
Thanks, Testing, for sharing this.&nbsp; I've been only minimally online for the past few days due to some kind of illness.&nbsp; (Doctor doesn't know what it was, but it kicked my butt for almost a week, I can tell you that.)&nbsp; But I did still go through my daily ration of blogs, and that was one of them, so I saw this when Hale posted it.&nbsp; It's an excellent video, and I think&nbsp; that managers throughout the engineering world, not just those dealing with NASA, need to see it.&nbsp; Because these problems are definitely not limited to NASA.&nbsp; It is a cautionary tale in how easy it is for well-meaning individuals to unconsciously create an environment hostile to change and hostile to dissent.&nbsp; I bet that most managers like the fictional ones depicted tend to think of themselves as approachable and open to change, totally unaware of the implications of these sorts of situations.&nbsp; It's good.&nbsp; I'm going to share it with folks in my department. <div class="Discussion_UserSignature"> <p> </p><p><font color="#666699"><em>"People assume that time is a strict progression of cause to effect, but actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly wobbly . . . timey wimey . . . stuff."</em>  -- The Tenth Doctor, "Blink"</font></p> </div>
 
Status
Not open for further replies.