Build the Point of View: A Category POV Brief for a New Data Category
Objective: Given a scenario where a data-cloud company is deciding whether to name a new category around AI-native data workloads, use the lesson's 10-part POV structure to draft the core sections of a category manifesto and sequence the sales conversation that would open it.
You're on the positioning team at Snowflake. Engineering shipped a new capability for running AI model workloads directly against warehoused data without exporting it. Leadership is deciding whether this deserves its own category or should ship as a feature inside the existing Data Cloud story.
Draft the Context, Problem, Villain, and Why Now sections of a POV brief, then sequence how the first sales conversation should open if this becomes a real category launch.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, comment-friendly, and matches how a real positioning brief circulates for review
The process
2 steps
Step 01 of 02
A strong category manifesto opens with four sections in order: Context (sets the scene), Problem (names the pain), Villain (the old way), and Why Now (the timing argument), before it ever mentions the solution.
What is the actual problem, not the feature, that justifies a new category here, and why does it have to be named now rather than in two years?
Procedure
- Write one paragraph of Context: what changed in how companies build with data in the last 18 months
- Write one paragraph of Problem: name the specific pain, not the feature (data leaving the warehouse to reach an AI model is slow, insecure, and creates duplicate copies)
- Write one paragraph naming the Villain: the old way companies are forced to work (exporting data to a separate ML platform)
- Write one paragraph of Why Now: the timing argument that makes this urgent instead of optional
CONTEXT: Every data team now has an AI initiative, and every AI initiative needs the company's own data, not a public model's training set. PROBLEM: Getting a company's real data in front of an AI model still means exporting it to a separate ML platform, copying it, losing governance, and waiting days. VILLAIN: The 'export-and-hope' workflow, where sensitive data leaves the warehouse's security perimeter just to be usable by an AI model. WHY NOW: Every AI vendor is racing to plug into enterprise data; the company that lets AI work where the data already lives, instead of the other way around, sets the default architecture before anyone else does.
Healthy
Problem section names a pain with no feature name in it at all.
Unhealthy
Problem section reads 'the problem is we don't have Feature X yet', which just restates the roadmap.
What this means
If you can't write a Problem paragraph without naming your own feature, you have a feature, not a category, and the launch should stay inside the existing Data Cloud story.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Problem paragraph mentions the feature name | Rewrite until it names only the pain, then re-check whether a feature name crept back in | 30 min |
Step 02 of 02
In a category-design motion, roughly the first 60% of a sales conversation is spent getting the prospect to agree the old category is broken, before a single product screen shows.
If a sales rep opens a call about this new capability, what should the first three minutes of the conversation cover before the product ever comes up?
Procedure
- Write the first question a rep should ask to surface the export-and-hope pain in the prospect's own words
- Write one follow-up question that gets the prospect to state the cost of that pain out loud
- Write the one sentence that transitions from problem agreement to naming the new approach
- Mark the point in the sequence where the product demo is allowed to start
OPEN: "Walk me through what happens today when your data science team needs data from the warehouse for a model." FOLLOW-UP: "How many separate copies of that data exist right now, and who signs off on each one leaving the warehouse?" TRANSITION: "That export-and-hope step is exactly what we built this to remove." DEMO STARTS: Only after the prospect has named their own copy-and-export pain unprompted, never before.
Healthy
The product name doesn't appear until the fourth line of the sequence.
Unhealthy
The rep's opening question already contains the product name or feature name.
What this means
A sales sequence that leads with the product name is a feature pitch wearing a category costume; the problem has to land first or the category framing never actually happens in the room.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Reps keep opening calls with a product demo | Rewrite the call script's first three lines around the problem questions above, hold the demo until the prospect names the pain | 30 min |
Final deliverable
A POV brief draft covering Context, Problem, Villain, and Why Now, plus a four-line sales-opening sequence that delays the product name until the prospect has named their own pain.
See a reference example
Qualtrics XM POV Brief, Draft 1 (excerpt) CONTEXT: Every company collects customer feedback, but almost none of it changes a decision. PROBLEM: Operational data (what happened) and experience data (how people felt about it) live in separate systems that never talk to each other. VILLAIN: The quarterly survey, filed and forgotten before the next board meeting. WHY NOW: Churn is now visible in real time on every dashboard except the one that would explain why it's happening. OPENING SEQUENCE: "Walk me through what happens after your last NPS survey closed." -> "Who acted on it, and what changed?" -> "That gap between feedback and action is what we built Experience Management to close." -> demo starts.
Success criteria
You're done when you can:
- Problem paragraph names a pain with zero feature or product names in it
- Sales-opening sequence delays the product name to the final line