How to Write a Category Point of View (POV)
A category point of view (POV) is a short, argument-driven narrative that names a problem the market has no words for yet, frames the old way of solving it as broken, and argues for a new category and a different future. It sells a worldview, not a product — and it's the first asset you write in category design.
Quick Answer: A category POV, from Play Bigger, holds four parts together: a named problem the world can't yet articulate, a genuinely different insight (not a better mousetrap), a "from / to" shift out of the old world into a new one, and the stakes of staying put. Write it before your deck, name, or website — it's the source document a lightning strike later amplifies.
What a Category Point of View Is — and Why It's Not a Product Pitch
A POV is an argument about the world, not a description of your software. Its job is to make buyers, analysts, and press think differently — to hand them language for a problem they feel but can't name — so that when they adopt that frame, your company is its obvious leader. If your draft reads like a list of features, you've written a pitch, not a POV.
This is the line that separates a POV from positioning strategy. Positioning argues you're the best choice inside a category buyers already recognize; a POV argues the category itself should exist. One competes on a scorecard the market already uses. The other rewrites the scorecard.
The POV is the source document for everything downstream. In Play Bigger's sequence, you write the POV before the pitch deck, the naming, or the site, because all of them derive from it. It's what a "lightning strike" — the concentrated go-to-market blitz that announces a category — amplifies, and what the longer category narrative extends. Get the POV wrong and every asset built on top inherits the flaw. It is the foundation of the wider discipline of category design.
The Four Elements of a Strong Category POV
A strong POV holds four elements in tension: a named problem, a "different" insight, a from-to shift, and unmistakable stakes. Drop any one and the argument sags — a vivid future with no named problem is a daydream, and a sharp problem with no stakes is a shrug.
A named problem the market can't yet articulate. The POV's first move is to give a diffuse, widely-felt frustration a name. A market can't ask for — or budget for — something it can't say. If the problem is already well-named, you're late; if it's too vague to feel urgent, it won't travel.
A genuinely "different" insight, not a "better" claim. Play Bigger's core distinction is different over better. A "better" argument keeps you inside the incumbent's category, competing on their criteria. A "different" insight reframes the problem so the old comparison no longer applies — it's a contrarian truth about why the current approach is structurally, not incrementally, wrong.
A "from / to" shift. State the move explicitly: from the old world — its assumptions, tools, and accepted losses — to the new one your category makes possible. The contrast is the payload. "From X to Y" is the sentence a whole category can rally behind.
Unmistakable stakes. Say what it costs to stay in the old world, and why now. Without stakes, the frame is interesting but ignorable, and buyers file it under "maybe later." The stakes turn a clever observation into a reason to move.
How to Draft Each Part of Your POV
Draft a POV in passes, problem first — never lead with the product. Work in this order so the logic builds toward a category rather than a sales page:
- Start from the tension, not the feature. Write the problem as your best customers actually feel it, in their words. Name it as a phenomenon, not a gap in your product line.
- Find the contrarian insight. Ask what everyone in the space assumes that is quietly no longer true. The answer is your "different" — the thing that makes the old category the wrong frame.
- Write the from/to as a hard contrast. One clause for the world you're ending, one for the world you're opening. If the "to" sounds like an upgrade, push until it sounds like a different game.
- Make the stakes concrete and urgent. Spell out what compounds if nothing changes, and why this moment — a shift in technology, cost, or behavior — makes the new way possible now.
- Pressure-test the logic. Read it back and check that a new category, not just your product, is the natural conclusion. If the only thing that follows is "so buy our tool," you've written a pitch.
Here is a deliberately hypothetical example, meant to show the shape rather than describe a real company:
Problem: Growing companies suffer "institutional forgetting" — every quarter, the reasons behind past decisions walk out the door with the people who made them. Insight: The problem was never storage; we have infinite wikis nobody reads. Context is lost at the moment a decision is made, not at the moment someone later searches for it. From / to: From knowledge management — filing documents after the fact — to decision memory: capturing why a choice was made, as it's made. Stakes: Teams that don't capture decision context relitigate the same debates forever and slow down exactly as they scale. Every lesson gets paid for twice.
That POV names a problem, reframes it, and points at a category — "decision memory" — that a product can then lead. Turning a POV like this into a launched, defended category is a longer job; see the full sequence for creating a new category.
Weak POV vs. Strong POV: A Diagnostic
Most weak POVs fail in predictable, element-by-element ways. Use this qualitative comparison to audit your own draft — it maps each element to what collapse looks like versus what holds up in a sales call.
| Element | Weak POV | Strong POV |
|---|---|---|
| The named problem | Restates a known problem, or stays too vague to feel urgent | Names a felt-but-unnamed problem buyers instantly recognize |
| The core insight | "We're faster/cheaper" — a better claim on old criteria | A different truth that makes the old comparison irrelevant |
| The from / to | Describes an upgrade to the current world | Draws a hard line between an old world and a new one |
| The stakes | Implied, so the frame feels optional | Explicit and time-bound, so standing still feels costly |
| The conclusion | "So buy our product" | "So a new category should exist — and we lead it" |
Takeaway: The most common failure is the second row — dressing a "better" claim up as a worldview. If your insight would still be true for a competitor with a faster product, it isn't a POV yet; it's positioning wearing a manifesto's clothes.
How to Test a Category POV Before You Fund the Strike
Test the POV the way you'd test any risky assumption — cheaply, before you spend on a lightning strike. The core bet is that buyers will adopt your frame, and that is far cheaper to probe than to launch. If the frame doesn't move people in conversation, no amount of production budget will rescue it.
- Pitch the problem, not the product. In customer calls, lead with the tension and the insight. Watch for the moment someone lights up because you named what they couldn't. Polite nodding is a warning, not a win.
- Listen for your language coming back. The strongest early signal is a prospect repeating your problem name or "from/to" unprompted. Borrowed language is borrowed belief — and the first evidence a category might spread.
- Smoke-test the frame. A landing page that leads with the problem and the new category, not features, measures whether the POV alone earns replies, searches, or sign-ups.
- Set a kill criterion in advance. Decide what "the frame isn't landing" looks like before you're emotionally invested, so you can revise or walk away before the market-education bill comes due.
Treat the POV as a living hypothesis and keep the evidence for and against it in one place — a validation workspace like Edmired is built for exactly that kind of assumption-tracking. A category you have to force is usually the market telling you the frame isn't ready.
Key Takeaways
- A POV sells a worldview, not a product. It names a problem, frames the old way as broken, and argues for a new category and a different future — if it reads like a feature list, it's a pitch.
- Four elements have to hold together. A named problem, a "different" insight, a from-to shift, and explicit stakes — drop one and the whole argument sags.
- "Different" beats "better." A faster-or-cheaper claim keeps you on the incumbent's scorecard; a contrarian insight rewrites the scorecard so the old comparison no longer applies.
- Name the problem, or the category can't spread. Markets can't budget for or rally around something they can't say, so language is the category's carrier.
- The POV comes first and anchors everything. Write it before the deck, name, and site; it's the source document a lightning strike amplifies and the category narrative extends.
- Test the frame before you fund the strike. Pitch the problem in conversations, listen for your language coming back, and set a kill criterion — the frame is the riskiest and cheapest thing to validate.
Frequently Asked Questions
What is the difference between a category POV and positioning?
A POV argues that a new category should exist and names the problem it solves; positioning argues you're the best choice inside a category buyers already recognize. A POV rewrites the market's scorecard, while positioning competes on the existing one. In practice you write the POV first — it defines the frame your positioning later operates within.
How long should a category point of view be?
There's no fixed length, but a working POV is short — often a page or less in its core form: the named problem, the insight, the from/to, and the stakes. It's an argument, not a document. The discipline is compression. If you can't state the frame tightly enough for a prospect to repeat it back, it isn't sharp enough to spread yet.
Who should write the category point of view in a startup?
The founders, at least in the first draft. A POV encodes a contrarian belief about the market, and that conviction usually starts with the people who chose to build the company. Marketing can sharpen the language and stress-test it, but a POV outsourced entirely to an agency tends to read like positioning — polished, on-trend, and missing the genuinely different insight that makes a category worth creating.