Solve Problems Like a Journalist: The Who-What-Why Checklist

The instinct, when a problem lands, is to jump straight to solutions. It feels productive. It's usually premature. You end up solving the version of the problem you assumed existed, not the one that's actually there — and a brilliant answer to the wrong question helps no one. Investigative journalists have a built-in defense against this: before they write a word, they nail down who, what, when, where, why, and how. The questions are simple, almost childish. That's exactly why they work — they expose the assumptions everyone skips.

Using the 5 W's problem-solving approach just borrows that discipline. You slow down at the front of the problem so you don't waste effort at the back of it.

Why understand the problem before solving it?

A problem you haven't examined is mostly assumptions wearing a costume. "Sales are down" sounds like one clear problem, but it hides a dozen: down where, since when, for which products, among which customers, compared to what? Rush past those and you'll fix whatever you happened to assume — a price, a campaign, a salesperson — and you'll likely fix the wrong one. The cost of a misdiagnosed problem isn't just wasted effort; it's the confidence that you've "handled it" while the real cause keeps working.

The journalist's questions force the problem to fully reveal itself before you commit resources. Clarity up front is cheaper than a wrong solution later.

How to question a problem like a journalist, step by step

You need a problem and about fifteen minutes. Write the problem at the top of a page, then work the questions.

1. What, exactly, is the problem? State it in one specific sentence. Push past the vague version — not "the project's a mess" but "the project missed its last two deadlines."
2. Who is involved or affected? Name the people. Who experiences the problem, who's contributing to it, who has to be part of any fix?
3. When does it happen — and when did it start? Timing is a clue. A problem that began on a specific date usually has a specific cause.
4. Where does it show up? Locate it. Is it everywhere, or only in one team, one step, one situation? A localized problem has a localized cause.
5. Why is it happening? Now — and only now — ask why. With the facts gathered, your theories rest on something real instead of a hunch.
6. How does it unfold? Trace the mechanics. How does the problem actually play out, step by step, from trigger to effect?

The rule that keeps it honest: don't propose a single solution until all six questions have real answers. The moment you catch yourself solving, stop and finish interrogating.

A worked example

A manager says, "Our team has a communication problem." That's a costume, not a problem. Working the questions: What? — decisions get made in meetings, then half the team acts as if they never happened. Who? — specifically the three people who work remotely. When? — since the team went hybrid. Where? — decisions made verbally in the room, never written down. Why? — remote folks miss the hallway context. How? — a verbal decision evaporates the moment the meeting ends.

The "communication problem" is really a "decisions aren't written down" problem. The fix — a shared decision log — is now obvious, and it's nothing like the team-building offsite someone almost booked.

When is the journalist's method most useful?

It's at its best on problems that feel vague, recurring, or strangely resistant to obvious fixes — the ones you've "solved" before that keep coming back. It's also valuable before any expensive intervention, as a cheap insurance check. It's overkill for small, clear, one-off issues where the cause is already plain. The tell that you need it: you're about to act and you can't actually answer "why is this happening?"

The takeaway

Most bad solutions are good answers to a problem nobody understood. The 5 W's problem-solving method makes you act like a journalist — pinning down what, who, when, where, why, and how before proposing anything. Interrogate the problem until it has no holes left, and the right solution usually becomes obvious on its own.

This is one of Funstorming's 100 quests — bite-sized soft skills methods you actually put into practice, not just read about. Try it, then bring your result (or your sticking point) to the Funstorming community of practice (CoP), FunHub | Your Soft Skills Playground.

#funstorming #softskills