Problem, Solution, Benefit: how to propose a change people agree to

By Rita Okonkwo · The Craft

The usual way to propose something is to open with the idea: "I think we should switch to a shared board." The room's first reaction to a new idea is to look for what is wrong with it, and it has not yet been given a reason to look for anything else.

Problem, Solution, Benefit changes the order. You name a pain the listener already feels, you offer your fix for that pain, and you show what they get once it is gone. By the time the idea arrives, the room wants something to solve the problem you just described.

Problem, Solution, Benefit, one part at a time

Question: Pitch one change to how your team works.

  • Problem (Name the pain): Every Monday we lose the first two hours of the week chasing status updates across four different tools.
  • Solution (Your fix for it): I want us to replace them with one shared board that everybody updates before they log off on Friday.
  • Benefit (What they get from it): That gives each of us those two hours back, and Monday starts with work instead of with questions.

The three parts

1. Problem: name the pain

Describe a problem the listener recognises from their own week, in their words rather than yours. The best Problems are specific and slightly uncomfortable to hear: "we lose two hours every Monday" lands; "our processes could be more efficient" slides off.

The trap is a problem only you have. If the room does not feel it, no solution will interest them, however good.

2. Solution: your fix for it

Say what you propose, in one or two sentences, and make sure it answers the Problem you named, not a slightly different one. Keep the detail for questions. The listener needs to picture the change, not to evaluate the implementation plan.

3. Benefit: what they get from it

This is where most proposals quietly fail: they end on the Solution and assume the Benefit is obvious. It rarely is. Say what changes for the listener once the problem is gone: time back, money saved, a risk removed, a better Monday. Tie it to the Problem, so the answer closes the loop it opened.

Why the benefit is not the solution again

"We'll have one shared board" is the Solution restated. "You get two hours back" is a Benefit. The difference is whose life you are describing: a Solution describes the change, a Benefit describes the person after the change. People agree to Benefits; they merely evaluate Solutions.

An answer, taken apart

Problem. Every Monday we lose the first two hours of the week chasing status updates across four different tools.

Solution. I want us to replace them with one shared board that everybody updates before they log off on Friday.

Benefit. That gives each of us those two hours back, and Monday starts with work instead of with questions.

The Benefit hands back exactly what the Problem took away. That symmetry is what makes it sound inevitable.

A second example: asking for budget

The same shape works when the listener holds the money. Say you run a small warehouse team and want your manager to pay for barcode scanners:

Problem. At the moment we count stock by hand on paper, and last month two of our orders shipped with the wrong items because the count was out of date.

Solution. I'd like to buy four handheld scanners so every item is logged the moment it moves.

Benefit. That means the stock count is right when an order is picked, so the mistakes that cost us two refunds last month stop, and nobody has to spend Friday recounting shelves.

Notice that the Problem uses a real event from last month rather than a general complaint about paper. A manager can argue with "paper is old-fashioned". It is much harder to argue with two wrong orders. And the Benefit is written in the manager's terms (refunds, staff time), not the team's (an easier job), because the manager is the one who has to say yes.

Checking the fit before you speak

Three questions catch most problems before the room does:

  • Would the listener describe the Problem the same way, unprompted?
  • Does the Solution fix that Problem, or a neighbouring one you care about more?
  • Could the listener repeat the Benefit to someone else in one sentence?

If the answer to the first question is no, you are not ready for this structure yet. The listener needs to see the problem before a fix will interest them.

Saying it out loud

Pause after the Problem. It is the sentence that makes the room lean in, and rushing past it straight into your idea wastes it. Say the Solution plainly, without selling it; the Benefit is where the persuasion happens. And end on the Benefit, then stop. Adding detail after it moves attention back to the implementation, which is where objections live.

Where it works, and where it doesn't

It is the natural shape for pitches, proposals, budget requests, product ideas and any "I think we should..." moment. It also works in interviews when you are asked how you would improve something.

It is the wrong tool when the listener disagrees that there is a problem at all: then the first job is to show them the problem, and What? So What? Now What? or a story does that better. And for a longer talk that needs people to act, Monroe's Motivated Sequence extends the same idea into five steps.

How the Coach listens for it

The Coach checks a take for all three parts. The two it flags most often are a Problem so general it describes nothing, and a missing Benefit, where the answer ends as soon as the solution has been named.

A five-minute drill

Think of one small thing at work or at home you would change. Write the Problem as one sentence containing a number or a real event. Write the Solution in under fifteen words. Write the Benefit as something the listener gets back. Say all three aloud, then cut any word in the Solution that describes how it works rather than what it is.

Practise it

Practise Problem, Solution, Benefit in the Coach. Lock the technique, spin for a scenario, and pitch whatever it hands you.