Emotional Friction States is a five-level hierarchy for judging how badly a problem hurts, based on the emotional state it produces rather than on how often it occurs. The states run overwhelm, anxiety, frustration, fear and resignation. Its practical use is that the state a person is in predicts whether they will pay to fix the problem, and resignation, which sounds like acceptance, is usually the most commercially interesting of the five.
After you have collected problems from interviews and need to rank them. It is a scoring lens rather than a discovery method, and it assumes you already have a list of problems with real quotes attached.
What the hierarchy is
Emotional Friction States is a five-level scale for judging how badly a problem hurts, based on the emotional state it leaves someone in rather than on how often it happens.
It is ShipFit’s own model rather than an established academic framework, and it is worth saying that plainly. It draws on ordinary practice in customer discovery and on behavioural economics, and it is offered here as a heuristic for ranking problems you have already collected, not as received theory.
The reason it exists is that “how painful is this?” is a question people answer relative to what they believe is possible. Someone who has concluded nothing can be done will rate a serious problem as mild. Reading the state from their language and their workarounds bypasses that.
- Five states, read from language Not from a rating
Overwhelm, anxiety, frustration, fear, resignation. The state is in the verbs and the workarounds, not in a self-reported score.
- Intensity and frequency are different axes Do not merge them early
A daily irritation and an annual catastrophe are different products with different prices.
- Resignation is the one you will miss And often the biggest
People who have given up stop complaining, so they never appear in tickets or feature requests.
- It ranks; it does not prove Commitment still required
A high score with no time, reputation or money behind it is a hypothesis.
Why it matters
Ask a room of founders to rank their customers’ problems and they will rank them by how often they hear about them. That measures which customers are loudest, not which problems are worth solving, and the two correlate weakly.
Loud and expensive are not the same thing. They get confused because only one of them emails you.
Frustration in particular is over-represented in every feedback channel. It produces the most complaints and often the least willingness to pay, because a frustrated person has already found a workaround they can live with. Meanwhile the person who quietly rebuilt half your workflow in a spreadsheet, and mentions it as though it were normal, never files a ticket at all.
The scale of what a proper problem sweep turns up, from ShipFit’s own corpus: ten problems per idea, four in ten of them happening weekly, and a mean intensity of 70 out of 100. Read that last figure sceptically. It is scored by a model from a founder’s own description, which is two layers of optimism stacked on top of each other.
Across 2,888 problems surfaced from 280 ideas, founders named about ten problems each, and rated the average one 70 out of 100 for intensity.
- Rated "must solve"
- 1,096 problems 37.9%
- Occurring weekly
- 41.4%
- Occurring daily
- 22.1%
- Mean intensity
- median 75 70.4 / 100
Sample: n = 280 ideas, 2,888 problems, 10.3 per idea
What it does not say: Intensity is scored by the engine from the founder’s description, so it inherits both their optimism and its own.
The five states
- Frustration Acts rarely
A known obstacle that recurs and is tolerable. The most-reported state and the weakest buying signal, because a workaround already exists.
Sounds like: "It is annoying but we manage."
- Overwhelm Acts sometimes
Too much to hold at once. Volume rather than difficulty. Buys when a solution reduces load rather than adds capability.
Sounds like: "There is just too much of it to keep on top of."
- Anxiety Acts often
Anticipating the problem before it arrives, which means it costs them time even when it is not happening.
Sounds like: "I start worrying about the Monday report on Sunday night."
- Fear Acts urgently
A consequence that matters personally: losing a client, being blamed, missing a number they are accountable for.
Sounds like: "If that goes wrong again it is my name on it."
- Resignation Does not act, until shown a fix
Concluded that no solution exists. Stops mentioning the problem, and builds elaborate workarounds instead. Invisible in every feedback channel.
Sounds like: "That is just how it works, everyone does it that way."
Reading resignation
Resignation is the state worth the most and the hardest to detect, because every signal a product team normally relies on depends on somebody complaining.
The tells are behavioural rather than verbal, and none of them involves a complaint.
They rebuilt part of your product, or a competitor’s, by hand.
"Oh, I keep my own tracker, it is easier." Opened without being asked.
Someone wrote down the workaround, which means it outlived its author.
A Notion page titled "How to do the monthly export properly".
Eleven steps described with no irritation at all.
"Then I export it, reformat it, and paste it into the other system."
They solved it with a person rather than a tool.
"We have someone part-time who handles all of that."
They tell you the category is not worth looking at.
"We looked at tools for this years ago, they were all the same."
Every one of these is someone solving your problem for you, at their own cost, without asking. That is a stronger buying signal than any complaint, and it is invisible in every channel a product team normally monitors.
When to use it
- You have a list of problems from interviews and no way to rank them.
- Feature requests and revenue do not correlate.
- You are choosing which problem V1 will solve.
- You suspect the loudest complaints are not the most valuable ones.
- You are setting a price and want to know what the pain justifies.
- You have no problems collected yet. Use The Mom Test →
- You need to know why someone would switch. Use Jobs to be Done →
- You need to sequence work already agreed. Use ICE scoring →
- You need an actual price, not a direction. Use Van Westendorp →
Against the alternatives
How badly does this problem hurt, and will they act?
Gives you: A ranked problem list with a line drawn through it
Is this problem real, and what does it cost them today?
Gives you: Facts about past behaviour. Produces the list this scores
What progress are they trying to make?
Gives you: A job statement. Explains why the pain matters
Which outcomes are important and badly served?
Gives you: A quantified score. More rigorous, and needs a survey
Friction states in practice: Juicero
Before the hierarchy, a company that built superbly against a friction state that did not exist.
Juicero · 2013 to 2017
A beautifully engineered $400 press, for a job that two hands could already do.
Juicero raised around $120m to build a wifi-connected cold-press juicer. The engineering was not a joke: the machine applied enough force, the company said, to lift two Teslas, and the proprietary produce packs were QR-coded so the press could refuse an expired one. It reviewed well. It was, by most accounts, a genuinely excellent object.
In April 2017 two Bloomberg reporters squeezed a pack by hand and got the juice out in about the same time. The video ran everywhere. The company suspended sales that September, roughly sixteen months after the press went on sale.
The interesting part is not that the product was mocked. It is that nothing in the build was incompetent. The hardware worked, the supply chain worked, the packs worked. The only thing wrong was upstream of all of it.
- Raised
- ~$120m
- Launch price of the press
- $699, later $399
- Time from launch to shutdown
- ~16 months
What it shows: Every question a build process can ask was answered well here except the first one. No amount of execution quality recovers a problem the buyer did not have.
When it won’t help you
- It is a heuristic, not a validated instrument
The five states are a useful way to sort a list. They have no empirical calibration, no published validation, and two people scoring the same interview will sometimes disagree about which state applies.
Instead: Use it to order a list and to force a conversation about intensity. Do not present the output as measurement.
- Intensity does not imply budget
Fear and overwhelm are strong states that frequently belong to people with no purchasing authority. The most acute pain in an organisation is often held by whoever has the least ability to spend money on it.
Instead: Check who holds the pain against who holds the budget. Where they differ, the message has to reach both.
- Self-reported states are unreliable
People calibrate their answers to what they believe is achievable, which is exactly why resignation reads as contentment. Asking someone to rate their own state reintroduces the bias the model exists to route around.
Instead: Score from what they did, not from what they rated. The workaround is more reliable than the number.
- It says nothing about how many people share the state
One person in acute fear is not a market. The model measures depth per person and is completely silent on breadth.
Instead: Score frequency and segment size separately, then combine deliberately.
Further reading
- The Mom Test. How to collect problems in a form that can be scored at all.
- Jobs to be Done. The four forces, which explain why a painful problem still does not produce a switch.
- Van Westendorp. Turning an intensity band into an actual price.
- ICE scoring. Sequencing what survives the ranking.
- Empathy Maps. Where the say-do gap that reveals resignation becomes visible.
How to apply Emotional Friction States Hierarchy
- 1
Collect problems with the words attached
The state is read from language and behaviour, not from a category. A problem recorded as 'reporting is difficult' cannot be scored. The same problem recorded as 'I dread the Monday report, I start it on Sunday night' can.
- 2
Assign a state from what they said and did
Overwhelm, anxiety, frustration, fear or resignation. Read the verbs and the workarounds. Someone who built a spreadsheet is in a different state from someone who complains and does nothing, and the spreadsheet is the more reliable signal.
- 3
Check for resignation specifically
The hardest state to detect, because people in it do not raise the problem. It shows up as 'that's just how it is' and as elaborate workarounds described without complaint. It is frequently the largest commercial opportunity on the list.
- 4
Score frequency separately
Intensity and frequency are different axes. A once-a-year problem at maximum intensity behaves nothing like a daily irritation, and combining them into one number early destroys the distinction you need.
- 5
Draw the line
Above the line are the states where someone will act. Below it the problem is genuinely real and nobody reaches for a credit card. Most feature requests come from below the line, which is why they convert so poorly.
- 6
Validate with behaviour, not the score
The hierarchy ranks a list. It does not prove anything. Anything above the line should be confirmed with a commitment: time, reputation or money. A high score with no commitment behind it is a hypothesis.
Common mistakes
- **Confusing frequency with intensity.** A daily annoyance and an annual catastrophe are different products. Score the axes separately and combine them deliberately.
- **Missing resignation entirely.** People who have given up do not complain, so they never appear in feature requests or support tickets, which are the two places most teams look.
- **Scoring from a category rather than from language.** 'Reporting is difficult' has no state attached. The state is in the verbs, the workarounds and the tone.
- **Treating the score as evidence.** It ranks a list you already had. Anything above the line still needs a commitment behind it before it justifies a roadmap slot.
- **Building for frustration because it is loudest.** Frustration produces the most feedback and often the least willingness to pay, because the person has already found a tolerable workaround.
- **Assuming high intensity means high budget.** Fear and overwhelm are strong states that can belong to people with no purchasing authority whatsoever.
How ShipFit operationalizes this
ShipFit runs the Emotional Friction States Hierarchy across Stage 2 (Who Pays?) and Stage 3 (What Hurts?). Stage 2 establishes the buyer's emotional context; Stage 3 scores every surfaced problem on frequency and intensity and sorts them above or below the line, so the output is a ranked problem list rather than an undifferentiated set of complaints. The intensity band then carries into Stage 6 (How to Charge?) as an input to pricing.
ShipFit runs 55 frameworks across 9 decision stages
Emotional Friction States Hierarchy is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What are the five emotional friction states?
Why is resignation the most commercially interesting state?
How is this different from just asking how painful something is?
Is this an established academic framework?
Should I build for the most intense pain?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
MoSCoW sorts features into Must, Should, Could and Won't against a fixed date. The 60% capacity rule is the part most teams drop, and dropping it breaks the method.
Adele Revella's Five Rings of Buying Insight, the questions that produce each one, and why a persona built without buyer interviews informs no decision.
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
Most early-stage competitive analysis is a 2x2 with your product in the top-right quadrant. The real version is harder, more boring, and tells you whether you can actually win.
How many units a month before the math stops bleeding?
Two to four weeks of focused work for a single idea. Stage 1 (market verdict) takes a day. Stages 2-3 (buyer + pain) take a week of interviews. Stage 4 (positioning) takes two days. Stage 5 (V1 scope) takes a day. Stages 6-7 (pricing + behavioral evidence) take 1-2 weeks because you need 20+ buyers and a Fake Door Test running. ShipFit compresses the decision time to 30-60 minutes; the gating work is the human conversations between stages.
SaaS idea validation that pressure-tests your ICP, pricing model, and retention before you build. ShipFit forces 9 decisions in ~20 minutes. Start free.
Lovable builds apps by chatting with AI: describe it, see it built in real-time, deploy. ShipFit makes 9 decisions before you open Lovable so you build the right thing. ShipFit even exports a Lovable-optimised prompt that encodes every decision. Use both. ShipFit first.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.