bar-test-positioning
The Bar Test Positioning Framework
Overview
A role-play exercise to ensure positioning statements sound like human conversation rather than corporate jargon. If you can't explain what you do to a friend at a bar, you have a positioning problem.
Core principle: Positioning must be colloquial enough to say to a friend.
The Process
┌─────────────────────────────────────────────────────────────────┐
│ STEP 1: SET THE SCENE │
│ Imagine you're at a bar with your target persona │
├─────────────────────────────────────────────────────────────────┤
│ STEP 2: THE TRIGGER │
│ "Hey, I just started using [Product]..." │
├─────────────────────────────────────────────────────────────────┤
│ STEP 3: THE EXPLANATION │
│ Speak the Benefit + Category naturally │
│ Structure: What is it + Benefit + Differentiator │
├─────────────────────────────────────────────────────────────────┤
│ STEP 4: THE VALIDATION │
│ Does the friend nod, or ask "What do you mean?" │
│ If they ask for clarification → Test FAILED │
└─────────────────────────────────────────────────────────────────┘
Examples
| ✓ Human (Pass) | ✗ Corporate (Fail) |
|---|---|
| "Turns your iPad into a cash register" | "Leverages tablet hardware for merchant transactions" |
| "Notes that write themselves" | "AI-powered documentation solution" |
| "Your company's search engine" | "Enterprise knowledge management platform" |
Banned Words
Words people don't speak aloud:
- "Leverages" → "Uses"
- "Empowers" → "Helps"
- "Solution" → [the actual thing]
- "Platform" → [be specific]
Common Mistakes
- Trying to sound "smart" or "corporate"
- Using words you'd never say in conversation
- Assuming jargon makes you sound legitimate
Source: Arielle Jackson (First Round Capital) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
13