Management isn’t rocket science. It’s harder than rocket science.
At least, that’s what Paul Hill, former director of mission operations at NASA, believes. Paul has spent most of his life around rockets: first as a child growing up near the Kennedy Space Center, and then as an adult in mission control. From designing space stations to investigating the explosion of the Columbia space shuttle, Paul has had a front-row seat to the victories and tragedies of the space program.
It would be easy to assume that his most fulfilling moments came from the memorable missions that he directed, but, surprisingly, Paul says that he is most proud of the accomplishments that weren’t visible to the public.
“I was one of a couple of leaders that led the entire organization through a leadership culture change [f]rom the top down. And, some of it was our own internal paradox of success… [a]nd over about a two, between a two and three year period. I led the entire evolution on us coming to grips with that and being able to be critical of our own leadership style.”
Paul’s team took a long, difficult look at NASA management, and discovered that many managers didn’t report problems out of fear of “putting ripples in the pond,” and kept budgets large because “that’s what we’re supposed to do.” Over that two-to-three year period Paul’s team was able to cut operating expenses by at least 20% in most areas, and 50% in others, making the departments under his direction at NASA lean and limber. This proved vitally important when the government mandated cuts to the NASA budget, effectively ending the moon and Mars programs. Undaunted, Paul’s team looked for ways to remain relevant and came up with a surprising solution to the budget ax looming over their heads.
“[O]ne of the reasons why I say…I’m most proud of it is it was only possible because we spotted our own cultural problems and fixed them and fixed them in time to demonstrate it to our stakeholders that they can trust us.”
Join us as we discuss Paul’s solution to the budget cuts; his epiphanies on management at NASA; and how learning management techniques from NASA Mission Control can help your team disrupt itself and stay relevant in rapidly changing environments.
Listen to the episode in the player above, or download and enjoy it on iTunes. If you’re so inclined, please leave us a review!
Takeaways from this episode:
- After a mission, Paul’s team would always go back and assess how they did, including what was successful, along with what was less successful (bad calls and decisions). They also made a point of walking people through their thought processes for good AND bad decisions so that everyone would know what to do and what NOT to do during the next mission.
- Tragedies like the Columbia explosion are not the result of one big mistake; rather, it’s the result of many little mistakes that went unchecked over a span of years. Paul attributes this problem to hubris—once you believe you are the smartest people to solve a problem, you’re more likely to make a mistake. They began to demand rigorous answers to the question “why,” and saying “because we’ve always done it that way,” was never good enough.
- When managers “filter” information too much, it can lead to a loss of discussion about important company-wide issues (in Paul’s case, technical issues that lead to accidents).
- To learn more about Paul’s ideas on effective management, check out his book, Leadership from the Mission Control Room to the Board Room.
Links Mentioned in this Episode:
- Paul Hill – Website | LinkedIn | Facebook
- What Got You Here Won’t Get You There by Marshall Goldsmith
- Leadership From the Mission Control Room to the Board Room by Paul Hill
- Mission Control Management by Paul Hill
- The Demon-Haunted World: Science As a Candle in the Dark by Carl Sagan
- Factfulness: Ten Reasons We’re Wrong About the World–and Why Things Are Better Than You Think by Hans Rosling
- Freakonomics: A Rogue Economist Explores the Hidden Side of Everything by Steven D. Levitt and Stephen J. Dubner
- Hans Rosling TED talks
- Take the Disruption Diagnostic