Good operators are not the people with an instant answer to everything. They are usually the people who know which question needs answering first.
Organizations are full of solutions looking for a problem they vaguely resemble. Better questions slow that reflex down just enough to keep the team from efficiently solving the wrong thing.
Separate the symptom from the problem
Sales are down. That is an observation. The operating problem might be traffic, conversion, retention, inventory, pricing, a competitor, a bad handoff or a reporting system telling the wrong story.
Naming the symptom as the problem sends every downstream decision in a different direction.
Ask what would have to be true
This is one of my favorite ways to test an idea. If the strategy is correct, what else should we expect to observe? If the campaign is working, which downstream behavior should change? If the vendor is the problem, what evidence would distinguish that from an internal failure?
A good question turns an opinion into something you can investigate.
Ask what would change your mind before gathering more data
Teams waste time arguing positions when nobody has defined the evidence that would resolve the argument. Before asking for another report, decide what result would actually cause the decision to change.
If the answer is “nothing,” you are not investigating. You are defending.
This is also how metrics become operational. A number becomes useful when the team knows which decision it informs and what threshold would trigger action. That is the missing link between analysis and execution.
Go closer to the work
Executives have altitude. Frontline teams have texture. You need both.
The person on the sales floor knows which question customers keep asking. The account manager knows where the handoff breaks. The producer knows which deadline is fake. The customer knows which part of your process makes no sense.
Data can tell you where something is happening. People close to the work often help explain why.
Follow-ups beat prepared answers
Hosting long-form conversations taught me this repeatedly. The prepared question often gets the prepared answer. The useful information shows up in the follow-up: Why? What happened next? What surprised you? What would you do differently?
The same discipline works inside a company. Listen for the part of the answer that does not fit the neat story.
AI makes problem selection more valuable
When answers become cheap, choosing the problem becomes more consequential. AI can analyze enormous amounts of information, compare scenarios and challenge assumptions. It still needs a useful question and a decision worth informing.
That is where curiosity becomes operational: not being fascinated by everything, but refusing to settle for the first explanation when the stakes justify another question.
The AI version of that argument lives in AI, Judgment & the Human Premium. The broader curiosity framework appears in Why Curiosity Is an Operating Skill, Not a Personality Trait.
More operating principles live at Operator Thinking & Leadership.