Most projects arrive wearing a solution. A new website. A campaign. A dashboard. A better content calendar. The solution may be right, but it is not always the most useful place to start.
I prefer to look one step behind it. What changed? Who is feeling the friction? What would become easier if this worked? Those questions are not a delay before the real work. They are the first piece of the work.
A good question gives a team somewhere to stand when the answer is still moving.
Make the question smaller
Broad questions create broad gestures. "How do we improve the experience?" can mean anything, which means it can guide almost nothing. A smaller question creates useful edges:
- What should a first-time visitor understand in thirty seconds?
- Where does the current process ask people to remember too much?
- What is the one decision this page needs to support?
Small does not mean unambitious. It means the work can meet reality. Once a team can see the next decision clearly, momentum becomes less mysterious.
Let the answer earn its shape
The best outcome is not always the original solution with better decoration. Sometimes it is a shorter page, a clearer sentence, or a decision not to build another tool. A good question leaves room for that answer.
That is the beginning I look for: a question that is specific enough to act on and open enough to teach us something.