Market Map
Are our users painkiller customers (urgent need) or vitamin (nice-to-have)? Every respondent plotted on Productive Best × Quality of Life. Bubble size = respondent count at that score. Segments use a composite pain score (sum of both deficits) — severity-first: pain ≥ 6 is "drowning" (both impaired), pain 4–5 gets directional sub-types.
Painkiller
Mixed
Vitamin
Who Hurts Most? (by Work Situation)
100% stacked bars sorted by Painkiller %. If a work situation is disproportionately Painkiller — that's your beachhead market.
More Hats = More Pain?
Does wearing multiple roles push people into Painkiller territory? Stacked bars by hat count (roles worn). If 5+ hat wearers are disproportionately Painkiller — role complexity is a pain driver, not just a demographic.
Which Roles Hurt Most?
Painkiller % by functional role (people appear in every role they hold). If specific roles over-index as Painkiller — that's a go-to-market signal beyond work situation.
How Composite Scoring Works
The pain score = (5 − productivity) + (5 − QoL) captures total deficit across both dimensions. Higher = more pain (range 0–10).
| Pain Score | Prod + QoL | Segment | Examples |
|---|---|---|---|
| 6–10 | 0–4 | Painkiller (drowning) | 1/1, 2/2, 3/1, 1/3 |
| 4–5 | 5–6 | Painkiller (directional) | 3/2, 2/3, 4/2, 2/4, 3/3 |
| 2–3 | 7–8 | Mixed | 3/4, 4/3, 4/4 |
| 0–1 | 9–10 | Vitamin | 4/5, 5/4, 5/5 |
Why severity-first? At pain ≥ 6, both dimensions are ≤ 2 — calling someone "productive" or saying their "life is OK" is misleading. Direction only matters at pain 4–5, where at least one dimension reaches 3+:
- Overextended: productivity > QoL (e.g., 3/2, 4/2 — QoL pays disproportionately for output)
- Blocked: QoL > productivity (e.g., 2/3, 2/4 — output lags despite relatively better QoL)
- Stagnant: productivity ≈ QoL (e.g., 3/3 — both mediocre, no clear direction)
Why Each Segment Hurts
The bubble chart shows WHERE people fall — but not WHY. Below: LLM-extracted blocker themes, energy dimensions, and strategy reliance cross-referenced against market segments. A Painkiller user blocked by priority confusion needs a different product than one blocked by energy depletion.
Top Blockers by Segment
What's actually blocking each segment? Bars show % within segment so sizes are comparable despite different group sizes.
What Drains Each Segment
Self-reported energy drain (Q14). Cognitive = decisions & context switching. Social = meetings & collaboration. Emotional = pressure & uncertainty. Physical = sleep & health. If Painkiller users are disproportionately Cognitive — your product must reduce decision load.
Thesis Areas
35 blocker themes mapped to 6 thesis areas from Blocker Landscape. Which execution obstacles dominate each market segment?
Energy Drain × Work Situation
Which roles are drained by what? Cell intensity = % of that work situation reporting the drain type. If Founders are disproportionately Cognitive while Employees are Social — that's a product segmentation signal.
How Each Segment Copes
Strategy reliance reveals the coping mechanism. If Painkiller users rely on willpower while Vitamin users rely on tools — that validates the product thesis.
See Blocker Landscape for thesis-level deep dives and outcome impact. See Target Profile for archetype-level analysis.
Segment Needs by Work Situation
Same segments, different roles. A Painkiller Freelancer faces different blockers than a Painkiller Founder. Select a segment to see how blockers, energy drains, and fix types vary by role.
What Each Segment Wants
The segments above define WHO hurts and WHY. Below: what each segment actually asks for — the fix types they name and the product features they imply.
Fix Type by Segment
Tool/system fixers = your buyers. Behavioral/mindset fixers may not be your customers. If Painkiller users lean toward tool fixes — your product thesis is valid.
Top Desired Fixes by Segment
What specific changes do people want? Themes from Q15 "if you could fix one thing."
What Each Segment Would Buy
Do feature requests converge on a buildable product or scatter? Top-3 share = how concentrated the demand is. Addressable = tool + system + behavioral fixes (what software can solve). Feature descriptions are LLM-extracted from Q15, sorted by confidence.
In Their Words
Representative quotes from each segment — what they'd fix if they could change one thing.