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.
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.
Practise it
Practise Problem, Solution, Benefit in the Coach. Lock the technique, spin for a scenario, and pitch whatever it hands you.