Images of the Space Shuttle are seared in this generation’s hearts and minds. Whether as young boys or girls who witnessed the dawn of the space shuttle era, or their Moms and Dads who were old enough to understand the terrifying feat, we are all well versed with this multifaceted, micro-tuned marvel.
The universal respect commanded by this engineering miracle could serve as a near perfect foundation for CTOs as they explain the software building process to their CEOs.
In broad terms, the Space Shuttle flight sequence consists of Lift Off, Orbit, Re-Entry and Landing. The silent force and ever present watchful eye of Mission Control pursues the success of the mission and the safe return of the vehicle and its astronauts.
But first, some facts about the flight sequence
It all starts with the Solid Rocket Boosters going to full power in 2/10th of a second. The heat they produce in the first two minutes of flight could heat 87,000 houses for one full day (ref).
Once in orbit, the Shuttle is in microgravity. Hydrogen fuel cells power life support and orbiter fuel is only used for course corrections.
Re-entry is initiated by slowing down the shuttle which requires 2,000 megawatts of power, or enough to power one million homes for an entire year. Kinetic energy is converted into heat and slows the shuttle down as it bursts back into Earth’s atmosphere. All that remains, is to glide the shuttle down back to Earth.
Using the Space Shuttle Metaphor
Conveying the scope and impact of engineering your CEO’s next software initiative can be a daunting task. How does the CTO describe the complexity and unpredictability of what it would take to build a feature while also raising empathy levels? Enter the Space Shuttle Metaphor.
Metaphors work because they compare concepts to something more familiar: cars to horse-drawn carriages, for instance. That helps people understand new, complex or conceptual information — the software engineering process—by means of something they already understand.
Your CEO will most certainly appreciate the magnitude of the universally beloved engineering feat that gave us the Space Shuttle Program. Describe how the app or feature can be developed by using the Shuttle flight sequence.
- Lift Off ~ to get development started, an exorbitant amount of energy is required. It takes an extraordinary effort to turn ideas into prototypes. There are also a plethora of external factors that could lead to a delay in lift off which isn’t a crisis, it just has to be navigated.
- Orbit ~ the explosive start is rapidly replaced by an iterative (and lengthy) process that is nudged only when gentle course corrections are required. Engineers need to be left alone in order to follow their implementation process. As the Shuttle is locked in an orbit around Earth, so your engineers are locked in iterations designed to keep them on track.
- Re-entry ~ to snap out of the iterative lull, an exorbitant amount of energy is required. It takes an extraordinary effort to not over engineer the feature or product. In many cases a line needs to be drawn and the focus shifts from attention to detail, to getting it shipped. Just like lift off, re-entry is subject to external factors that might delay initiation of the landing sequence.
- Landing ~ arguably the most delicate phase of the process since control is relinquished from your team to your users. The calm of coding in orbit, is replaced by addressing user concerns and adoption which in our world, could make landing the Space Shuttle look easy. The key is to navigate the turbulence and let the product or feature glide gently into the applause of happy users.
One last thing…
If you have a shrewd CEO who is tracking with your simile, they’ll ask you about Mission Control. This gives you a wonderful opportunity to assure them: “Mission Control? Well, that’s where you and I are!”
