Ever been in a meeting presenting information when an executive interrupts with a question?
Maybe it’s a simple question.
But it feels substantial, suggesting the answer is something you have and didn’t share… yet.
Only a few seconds pass as the pressure mounts. We’re known for having the right answers, and this feels like a miss. So we promise to get an answer.
Without looking up, the executive responds, “Okay, come back to me by the next meeting,” or “Great, send me a note when you have it.”
Meanwhile, our brain starts racing, trying to figure out the answer and how we’re going to get it.
But was the question a question, or an ask?
Sometimes executives like to think out loud. They’re brainstorming, engaging the part of their brain that’s used to solving problems. They ask questions. Sometimes lots of questions, looking for angles and insights—things they’re curious about.
In the moment, it feels like we’re missing the answers they expected us to have.
But consider more casual conversations, when we’re working out a challenge with a colleague:
“Hey, do you know?”
“No, I don’t.”
“Okay, then we won’t worry about that yet.”
With the executive, maybe the question reveals something they do want answered. And that’s when the question becomes an ask.
Which raises a new challenge.
How much time and effort will it take to find the answer? What gets displaced? Another priority? A lunch break? Nights and weekends?
In these situations, I answer the question with one of my own:
“Are you just asking, or is this something you want us to go figure out?”
Often, the executive is just thinking out loud and doesn’t even realize it. When they want the answer, they tell us. And then we can work with them to understand the effort and trade-offs involved.