Understanding

"Houston, we've had a problem."

These famous five words were radioed back to the Mission Control Centre on 13^th April 1970 from Jack Swigert, who found himself 200,000 miles away in a spacecraft that had just blown its oxygen tank. What followed over the next 87 hours wasn't a Hollywood moment of sudden brilliance. It was the most intense clarification conversation in human history - a masterclass in how listening builds understanding when lives depend on it.

Here's what most people miss about Apollo 13: Mission Control didn't save the crew by knowing more. They saved them by listening better. By asking the right questions, and by clarifying relentlessly until they understood this never-before-seen situation.

Mission Control operated on a principle that when you didn't understand something, you asked. When something didn't make sense, you questioned it. In this case understanding was more important than pride or fear of looking stupid.  It required humility to accept they didn't know everything. And it required discipline to keep asking questions and genuinely listening to the answers until that understanding was complete.

Over 87 hours, Mission Control asked hundreds of clarifying questions. They listened to understand - to build a complete picture of what was actually happening. Three astronauts came home because Mission Control refused to act on incomplete understanding. We all face the same challenge that Mission Control did on that fateful day - just with lower stakes, closer to Earth, and (hopefully) no exploding oxygen tanks!

For example, when your team member says, "The client's unhappy," do you understand what kind of unhappy? When your partner says, "Work was stressful," do you understand what stress actually feels like for them?  The difference between knowing and understanding is the difference between nodding and helping find solutions.

Most of us hear the words and think we understand. We fill in the gaps with assumptions. We move on to the next thing. But those assumptions - the understanding we think we have - cost us far more than we realise.

The same principle applies when you're sitting across from your team member who's just said, "We've got a problem with the launch." Or when your teenager says, "I'm fine." Or when your manager says, "This project isn't quite working." The questions you don't ask are limiting what you can know. And what you don't know is costing you.

Take a contemporary example: Sarah, a senior project manager, was six weeks from launch when her lead developer said in a standup "We're good to go. Just ironing out a few last details."

Most managers would hear: "We're on track." Sarah heard something else. The word just. The phrase a few. Vague language that suggested she didn't have full understanding of the situation. She pulled him aside after the meeting.

Sarah: "Walk me through what 'a few last details' actually means."

Developer: "You know, scenario testing. Should be fine."

Sarah: "When you say 'should be fine,' help me understand - what's the scenario where it wouldn't be fine?"

[Long pause]

Developer: "Well... if a customer initiates a refund during a currency conversion whilst the API is rate-limited... we're not entirely sure what happens."

Twenty minutes of clarifying questions later, Sarah understood:

• "A few last details" meant 12 untested failure scenarios

• The team had built for the happy path, not reality

• One scenario could result in duplicate charges to customers

She delayed the launch three weeks. The team found four critical bugs, including one that would have cost approximately £200K in customer disputes and regulatory fines in the first month.

Just like Mission Control did in 1970, Sarah prevented a catastrophe from happening (OK, maybe not on the same scale!) by employing listening skills that allowed her to gain genuine understanding of the situation rather than accepting surface-level reassurance.

Here's what most people miss: you think you're listening, but you're actually assuming.

Mission Control asked thousands of clarifying questions over 87 hours because they understood that assumption was their enemy. They couldn't afford to act on incomplete understanding. You might not be bringing astronauts home from space, but the principle is identical: understanding precedes effective action. 

When you assume you understand but don't, you're solving the wrong problem. You're having a different conversation than the other person thinks you're having. You're making decisions based on incomplete or inaccurate information. And that gap - between what you think you know and what's actually true - is where opportunities die, relationships fracture, and problems spiral.

If you'd like to discover where your assumptions are creating misunderstanding and see how your own listening skills measure up, you can take The Listening Assessment.

You'll receive a personalised analysis of your listening patterns and the specific areas where clarification could change everything.

P.S. Next time someone gives you a vague answer - "fine," "good," "probably," "should work" - try asking: "talk me through what you mean by that." Then actually listen to the answer. You might be surprised by what you discover.