Skip to content

Part I: Coming up with an idea

4. Is it the right problem?

Question the way you've described the problem before choosing a solution.

You have a person and a problem. Now look again at the explanation you've written down. Is it what you've actually learned, or the first explanation that occurred to you?

The way you describe a problem affects the solutions you can see. If you say the designer needs a client portal, you've already decided what to build. If you say they're waiting for a clear decision, you have room to find out why that decision isn't happening.

Change the way you look at it

Thomas Wedell-Wedellsborg calls this reframing in What's Your Problem?. His elevator example makes the idea easy to see. Imagine tenants complaining about a slow lift. You could investigate making it faster. You could also investigate making the wait less annoying, perhaps by putting mirrors beside it. The complaint gives you more than one problem you could work on.1

The same applies to your sentence from the last chapter:

Person X can't do Y because Z.

Look closely at “because Z.” You might have observed a delay without knowing what caused it. Before you decide how to remove it, write down some other explanations that could fit what you've seen.

In our hypothetical designer example, the client might have missed the request. They might be unsure what feedback is needed. Or they might be waiting for someone else to make the decision. Each possibility suggests different work: a reminder, a clearer request, or finding the person who can approve the draft.

A delay can have more than one explanation.

You don't have to choose the right explanation from your desk. You need to recognise that you have several to check.

Ask what they're trying to achieve

One of the book's reframing strategies is to reconsider the goal. Ask what the person would gain if the problem were solved.1

For our designer, “get more feedback” might be a poor description of the goal. More comments could mean more conflicting requests and more work. Finishing the project requires a decision about whether the current draft is acceptable and, if it isn't, what needs to change.

That changes the questions you'd ask the designer. Who needs to agree? What happens after a reply arrives? At what point can the designer actually move on?

It can also change who you need to talk to. The designer sees their side of the exchange. The client might be struggling to gather a decision from colleagues. If your proposed solution depends on the client doing something differently, you'll need to understand that side too.

Look for times it goes well

The book also suggests examining “bright spots”: occasions when the difficulty is absent or has already been handled successfully.1

Suppose the designer gets useful feedback quickly from some clients. Ask what happens on those projects. Perhaps the request goes to a single decision-maker, or they agree in advance what the client will be reviewing. These are possibilities to investigate, not conclusions about our fictional designer.

Looking at an easier project gives you something to compare with the difficult one. It might reveal a useful practice you could help people repeat. It might also show that the problem only happens in a narrower situation than you thought.

Take the questions with you

Keep your original sentence, then write an alternative version. Beside each, note what you'd need to learn to decide whether it fits. For the designer, you might need to see the last request for feedback and understand what happened after it was sent.

Keep this exercise short. A more elegant sentence doesn't establish that you're right. The next chapter turns these uncertainties into a list you can investigate when you talk to people.

Before you move on0 / 3

Footnotes

  1. Thomas Wedell-Wedellsborg explains these ideas in his article How to solve the right problems, adapted from What's Your Problem?. The designer application here is hypothetical. ↩ ↩2 ↩3