Problem-Solution Fit Canvas SOP

A problem-solution fit canvas SOP puts everything you learned about one customer's problem on one page and checks whether your first solution idea fits how that customer already behaves. Filling it takes half a day; testing it with customers takes three to five days. Founders who skip this step design solutions for the problem and forget the person: their budget, habits, triggers and the channels they actually use.

What is the problem-solution fit canvas SOP and when should you use it?

The problem-solution fit canvas was created by Daria Nepriakhina as a bridge between customer research and product design. It has 10 blocks for one segment: customer segment, customer constraints (budget, time, devices, skills), available solutions, jobs to be done and problems, problem root cause, behaviour (what they do about it today), triggers (what makes them act), emotions before and after, channels (where the behaviour happens, online and offline) and your solution.

Ash Maurya's Lean Canvas covers the whole business on one page. This canvas zooms in on the left side of it: the customer, the problem and the behaviour around it. Fit means your solution matches a real trigger, uses a channel the customer already uses, respects their constraints and moves them from the "before" emotion to the "after" one.

Use this SOP:

• When the problem is validated but the team argues about what to build first.
• When your solution idea feels clever and you want to check it against real customer behaviour.
• Before a concept test or prototype, so you test the idea most likely to fit.

What do you need before you start?

• One customer segment and a validated problem statement.
• Research notes: interviews, diary entries, survey results and an existing solutions analysis.
• A canvas template in Miro, FigJam or on paper (the block list is in the template below).
• Three colours of sticky notes or tags: green for evidence from customers, yellow for evidence from desk research, red for assumptions.
• 8 customers from the segment for walkthrough calls.

How do you run it, step by step?

1. Fill the customer side first

Start with segment, constraints and available solutions. Write the segment as narrowly as your research allows. List constraints that will kill a solution: monthly budget ceiling, time per day, devices, language, approval rules. Copy available solutions with one pro and one con each.

2. Fill the problem side

Write the top one to three problems or jobs in customer language. Under root cause, write why the problem exists, which is the thing your solution must attack. Under behaviour, write what customers do today when the problem hits, including workarounds and doing nothing.

3. Fill triggers, emotions and channels

Triggers are the moments that push people to act: a deadline, a complaint, a lost sale. Emotions are how they feel before (anxious, embarrassed, overloaded) and after the problem is gone. Channels are where the behaviour already happens, such as WhatsApp, Instagram, a supplier portal or a weekly team meeting.

4. Tag every block with its evidence

Mark each note green, yellow or red. Count the blocks that rest mostly on green. Any block that is mostly red is a research task, and you go back to interviews or a diary before going further.

5. Write the solution last

Only now write your solution in two or three sentences. Then check it against the canvas: does it fire at a real trigger, run in an existing channel, fit inside the constraints and attack the root cause? Rewrite until it does, or write two competing solutions.

6. Walk 8 customers through the canvas

Show each customer the canvas without the solution block first and ask, block by block, "Is this right for you? What's missing?" Then reveal the solution and ask how it would fit into their week. Count agreements per block and record every correction.

7. Update and decide

Fold the corrections into the canvas. If 6 or more of 8 customers say the solution fits their behaviour, carry it into concept testing. If not, rewrite the solution and leave the evidence as it is.

Template you can copy

PROBLEM-SOLUTION FIT CANVAS (one segment)

CUSTOMER SIDE
Customer segment: ...
Customer constraints (budget, time, devices, skills, approvals): ...
Available solutions (pro / con for each): ...

PROBLEM SIDE
Jobs to be done / problems (customer words): ...
Problem root cause: ...
Behaviour today (what they do when it hits): ...

ACTION SIDE
Triggers (what makes them act): ...
Emotions before: ...        Emotions after: ...
Channels (online / offline where behaviour happens): ...

YOUR SOLUTION (fill last): ...

EVIDENCE TAG PER BLOCK: G = customer evidence, Y = desk research, R = assumption

WALKTHROUGH SHEET (per customer)
Block | Agree Y/N | Correction | Quote
Solution fit: "How would this fit into your week?" → fits / partly / no

Worked example: independent hairdressers and empty chairs

This is an illustrative case. A founder interviews 15 self-employed hairdressers who rent a chair in a salon. Her canvas: the segment is chair-renting hairdressers with 80 to 200 regular clients. Constraints: no receptionist, hands busy all day, about €30 a month to spend on tools. Available solutions: the salon's booking app (clients ignore it) and a paper diary.

The problem is gaps in the week, and the root cause is that clients leave without rebooking because the stylist is already busy with the next client. Behaviour: on Sunday evenings, 11 of 15 scroll through their phone and text clients one by one on WhatsApp. The trigger is seeing an empty Tuesday. Emotions before: anxious about income. After: calm, a full week. Channel: WhatsApp and Instagram DMs.

Eight of ten blocks are green. Her first idea was a new booking app, which fails the canvas: it adds a channel clients ignore. She rewrites the solution as an automatic WhatsApp rebooking message sent five weeks after each visit. Six of 8 hairdressers in walkthroughs say it fits; two who rely on the salon's system do not. She moves to concept testing with chair renters only.

What should you measure, and when do you stop?

Stop when the canvas passes, or after two rewrites of the solution that both fail walkthroughs. Two failures point to a wrong segment or a shallow root cause, and the fix is another round of research.

Which mistakes should you avoid?

• Writing the solution first. You will bend every other block to fit it. Leave it for last.
• Filling the canvas from memory. Every note needs a source. A canvas full of red notes is a guess with nice colours.
• Using one canvas for several segments. Triggers and channels differ by segment. Make one canvas each.
• Ignoring constraints. A solution that needs a laptop for people who live on their phones fails on day one.
• Treating walkthrough politeness as fit. Ask how the solution would fit into last week, with real days and times.

How can AI speed this up?

Paste your research notes into an AI assistant and ask it to draft each block with the source quote next to every line, marking anything it inferred. That draft saves an hour, and the source column makes red notes easy to spot. You can also ask it to stress-test your solution against the constraints block. The walkthrough calls stay human; AI cannot tell you which block made a hairdresser laugh at you.

Where does this SOP fit in your validation plan?

This canvas closes the Problem Validation stage. Before it, run problem statement validation, the existing solutions analysis and, for the emotions block, customer empathy mapping. After it, open Solution Validation with a concept test or a solution storyboard. Once revenue and costs come into view, widen the picture with business model canvas validation or the free lean canvas template. For other one-page methods, browse 100 startup methods.

FAQ

What is problem-solution fit?

The point where you have evidence that a specific customer has a problem worth solving and that your proposed solution fits how they behave, what triggers them and what limits them. It comes before product-market fit, which needs a product in use.

Who created the problem-solution fit canvas?

Daria Nepriakhina designed it for founders and product teams who need to turn customer research into a solution direction, and shared it as a one-page template.

How is it different from the Lean Canvas?

The Lean Canvas covers the whole business model on one page, including revenue and costs. The problem-solution fit canvas goes deeper on the customer side: triggers, emotions, behaviour, channels and constraints.

How long does it take to fill the canvas?

Half a day if you have research notes. Testing it with 8 customers adds three to five days of short calls.