Better questions, better possibilities

A useful answer starts with a question that describes a real situation. When a team asks, “How can we be more innovative?”, it may jump straight to workshops or new tools. A clearer question helps the team decide what it needs to understand before choosing a solution.

This guide offers a simple way to turn a broad concern into a question you can investigate and a small action you can test.

1. Describe what is happening

Start with observations rather than explanations. “Customers ask for the same information twice” is an observation. “Our team does not care about customers” is an interpretation that needs evidence.

Write down who is affected, where the difficulty appears, and what happens next. Use a recent example. If you do not yet know how often something happens, record that as a gap instead of presenting an estimate as a fact.

2. Separate facts from assumptions

Create three short lists:

• What we know: observations, records, or direct feedback.
• What we assume: possible explanations that we have not checked.
• What we need to learn: information that could change our next decision.

For example, a team may know that several proposals were submitted late. It may assume the template is confusing. It still needs to learn whether the delay came from the template, missing input, unclear approval responsibilities, or another cause.

3. Ask a question that leaves room for alternatives

Compare these questions:

• “How do we make everyone use a new project tool?” already selects a solution.
• “What information do colleagues need to coordinate their work without repeated follow-ups?” opens several possible approaches.

A helpful question names the people, the situation, and the outcome you want, without deciding the method too early. One starting pattern is: “How might we help [people] achieve [outcome] in [situation], within [constraints]?” Use it as a thinking aid, not a rigid formula.

4. Make the question small enough to explore

Imagine a training provider receiving incomplete workshop enquiries. “How can we improve sales?” is too broad for a first experiment. A more workable question is: “How might we help prospective clients describe their workshop needs clearly in the first enquiry?”

The team could review a few recent enquiries, ask the people who handle them what is missing, and test a shorter form with clearer prompts. Those actions investigate the problem before committing to a large redesign.

5. Choose one experiment and a review point

Define a small action, an owner, a timeframe, and what you will look for. For the enquiry example, the team might test revised prompts for one week and compare whether fewer clarification messages are needed. That is a proposed experiment, not a promised result.

Agree in advance what would make you keep, adjust, or stop the change. Look for unintended effects too: a shorter form may be easier to complete but omit information the team needs.

A ten-minute exercise

Choose one concern from your work. Spend two minutes describing a recent example, three minutes separating facts and assumptions, three minutes rewriting the question, and two minutes identifying the next thing to learn. Invite a colleague to challenge your wording.

Take the next step

You do not need the perfect question before acting. You need a question clear enough to reveal your assumptions and guide the next useful conversation. Revisit it as you learn: a better understanding of the situation may call for a different question. Your next step is to write one question, identify one missing piece of information, and decide who will help you investigate it.