From Noise to Clarity | Track 16
The Answer Arrives Too Fast #2
The Future of Thinking | Post 2 of 30. (The shift)
Before you read: think of the last question you typed into a tool. Was it the question you actually needed answered?
The operations planner at a logistics warehouse has had a difficult week. Late deliveries are up, two key customers have complained and her manager wants a plan by Friday.
So on Wednesday afternoon she types a question into an AI assistant: how do we reduce late deliveries? Before she has finished her tea, the answer is on her screen. It’s a tidy list of ideas: better route planning, earlier cut off times, a buffer of spare drivers, clearer loading schedules. Each one comes with a sensible explanation.
She’s impressed. By Thursday her team has started on three of them. By Friday the plan is on her manager’s desk, and it looks thorough.
A month later, the late deliveries are still there. When a supervisor finally walks the loading bay at the end of a shift, he notices something nobody had asked about. Many of the late parcels are going to the same few business parks, where the gates close earlier than anyone realised.
The answer had been good. It just wasn’t an answer to her problem. It was an answer to her question, and her question had arrived before she’d really looked at the problem.
That’s the shift this post is about. When answers arrive instantly, they can skip the step where we work out what we’re really asking.
“It was an answer to her question, and her question had arrived before she’d really looked at the problem.”
Why this shift matters
Not long ago, finding an answer took effort. You had to ask a colleague, search through files or sit with a problem for a while. That effort was frustrating, but it had a hidden benefit. While you were waiting for the answer, you were also shaping the question. By the time you found someone to ask, you often knew more precisely what you needed.
Now the wait has gone. You can type a half formed question and receive a well formed answer in seconds. The answer looks so complete that it’s easy to forget the question was only half formed.
Some writers on problem solving call this premature answering: reaching for a response before the problem has been properly understood. People have always done it, of course. What’s different now is how rewarding it feels. A fluent, confident answer gives you the pleasant sense that the work is done, and it arrives so quickly that there’s no natural moment to stop and check whether you asked the right thing.
The concern here is real. Many people are finding that they spend less time on questions and more time on answers, and that more of their effort goes into fixing things that were never quite the problem. Teams can move quickly in the wrong direction and feel productive the whole way.
But the hopeful part is just as real. The skill that protects us is an old one, and it doesn’t need any technology at all. It’s the habit of picturing the problem before you ask about it. When you do that, the speed of the tools becomes a gift rather than a trap, because you’re pointing them at the right thing.
How do you know when the answer came too fast?
Try this: Next time you’re about to type a question into a tool, stop and ask yourself who has the problem and what they’re trying to reach, then see whether your question changes.
There are a few signs that an answer has overtaken its question, and they’re easy to spot once you look for them.
The first sign is the generic answer. The response would fit almost any organisation. Nothing in it mentions your customers, your people or your particular situation, because nothing in your question did either.
The second sign is quick agreement. Everyone nods at the list because every item sounds sensible, and nobody asks which one matters here.
The third sign is a problem that won’t go away. You’ve acted on the answer, perhaps more than once, and the trouble keeps coming back. That’s often a sign that the question never touched the cause.
A client of mine, an experienced accountant, came to me while she was thinking about leaving her firm. She had already asked an AI assistant what careers suit someone with an accounting background. It had given her a long, thoughtful list, and she’d spent weeks researching each option. She was more confused than when she started.
When we sat down together, I asked her to forget the list for a moment and tell me about the parts of her work that gave her energy. She talked about the afternoons she spent explaining figures to new managers, watching their confusion turn into confidence. She talked much less about the figures themselves.
Her real question wasn’t which career suits an accountant. It was how she could spend more of her days helping people understand things. Once she could see that, the list shrank to two or three directions worth exploring, and she later moved into a role training finance teams. As she put it, “I’d been asking about my past. I needed to ask about what I wanted next.”
“I’d been asking about my past. I needed to ask about what I wanted next.”
The sketch that builds the skill
This is the Pause in Pause. Picture. Partner. Before you hand your thinking to a tool, you pause and picture the problem yourself, so that when you do partner with the tool, you know what you’re asking it to help with.
Get Ai Yat Goh’s stories in your inbox
Join Medium for free to get updates from this writer.
The sketch for this post is called the question gap. It takes a couple of minutes, and you can draw it on the back of an envelope.
Start on the left of the page with a simple stick figure holding a pen. This is the person who has the problem. It might be you, a customer, a colleague or a whole team. Drawing a person first matters, because problems always belong to someone.
Next to the figure, draw a box. This is where they are now. Inside or beside it, jot a few words about the current situation as that person would describe it, not as a report would.
On the right of the page, draw a circle. This is where they want to be. Again, describe it in their words. What would be different for them if the problem were solved?
Now draw a dotted line between the box and the circle, and draw it in blue. That dotted line is the gap, and the gap is where your real question lives. Put a question mark on it. Then ask yourself what’s actually standing between the person and the place they want to reach. Write down the two or three things you suspect, and circle the one you feel unsure about.
Only now, with the gap in front of you, do you turn to the tool. Your question will be sharper, more specific and far more likely to bring back an answer that fits.
As a visual strategist, I’ve noticed that people rarely skip this step because they’re careless. They skip it because the words of a question feel like enough. But words can hide a vague problem very comfortably. A drawing can’t. When you have to put a person on the page, place them somewhere and show where they want to go, the gaps in your understanding become visible straight away.
This sketch also changes how you work with others. If you put the question gap on a whiteboard before a meeting, people start arguing about the problem rather than about solutions, and that’s usually the more useful argument to have.
What happened when an office drew the gap
I once anonymously observed a case at an organisation where the manager of a public service counter, the kind of office where residents come to renew documents and sort out applications, was under pressure to shorten the queues. Her team had already asked an AI assistant how to reduce waiting times and had a list of ideas ready: more counters at peak hours, an appointment system, a faster ticketing machine.
Before choosing any of them, she asked her team leaders to spend ten minutes drawing the question gap for a single resident in the queue. Who is this person? Where are they now? Where do they want to be when they leave?
The drawings surprised everyone. Several team leaders drew residents who had come in for a simple task, but had been sent home on an earlier visit because a form was missing. They were in the queue for the second or third time. The gap wasn’t really about speed at the counter. It was about knowing what to bring before setting out.
So the team took that sharper question back to the tool and asked for help writing clear, friendly checklists for the services residents found confusing. They put them on the website and by the entrance. Over the following months, the queues grew shorter, and the counter staff noticed that fewer residents arrived frustrated.
One of the team leaders summed it up afterwards. “We were trying to serve people faster. We needed to stop them coming back.”
“We were trying to serve people faster. We needed to stop them coming back.”
A note on the book that shapes this series
This track draws on The S.T.A.R. System: Applying Visual Thinking for Career & Business Success, which I co authored with Sherrie Low. The book moves through four stages: Story, Takeaway, Application and Reflection, and this first circle of the track sits firmly in Story.
The question gap is a Story sketch at heart. It asks you to see the situation through the eyes of the person living it before you decide what it means or what to do. Sherrie and I wrote the book because so many good decisions start with a clearer picture of the story, and so many poor ones start with a quick answer to a question nobody checked. In a world where answers arrive in seconds, that first step matters more, not less.
So before you ask anything this week, try drawing the gap first. It takes a moment, and it gives the speed of the tools somewhere useful to go.
The shift: Instant answers can arrive before we’ve understood the question.
The skill: Picturing the problem from the side of the person who has it.
The sketch: The question gap, with the dotted line between now and wanted drawn in blue.
What’s one question you asked recently that might have been answered well, but asked too soon?
Next in the series: Drowning in Good Information, on what to keep when there’s too much worth reading.
This idea comes from The S.T.A.R. System: Applying Visual Thinking for Career & Business Success, co authored by Ai Yat Goh and Sherrie Low, published by Marshall Cavendish Business. If asking the right question before reaching for an answer is useful to you, the book goes further into applying visual thinking across career and business decisions. Get it on Amazon.
Ai Yat Goh is a Visual Thinking Strategist, educator and entrepreneur based in Singapore, and Asia’s first Master Trainer for Dan Roam’s Power of Visual Series. She works with professionals, teams and organisations navigating a pivot, helping people see clearly before they act. Connect on LinkedIn and follow on Medium.
#FromNoiseToClarity #FutureOfThinking #VisualThinking #ProblemSolving #CriticalThinking
BK HAN Candy Chan RH Malini Lawrence Lee Jessica Leong Angela Toh
