Skip to main content
ClaudeWave
Skill1.3k repo starsupdated yesterday

obviously-awesome

The Obviously Awesome skill helps teams define product positioning by systematically mapping competitive alternatives, unique attributes, value themes, best-fit customers, and market category to create clear context for how customers evaluate the product. Use this when launching new products, repositioning existing ones, entering crowded markets, or diagnosing why prospects misunderstand your product's value proposition.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/wondelai/skills /tmp/obviously-awesome && cp -r /tmp/obviously-awesome/obviously-awesome ~/.claude/skills/obviously-awesome
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Product Positioning Framework

April Dunford's "Obviously Awesome" methodology: a structured, repeatable process for defining how your product is the best in the world at delivering something a well-defined set of customers cares a lot about. Positioning determines what customers compare you to, which features they notice, and ultimately whether they buy.

## Core Principle

**Positioning is not messaging. Positioning is context.**

Positioning defines the context within which customers evaluate your product -- what category they place you in, what alternatives they compare you against, and how they judge your value. Customers always evaluate relative to alternatives; there is no absolute product perception -- a product that seems expensive in one context seems cheap in another. Deliberately choose the context that makes your unique strengths obvious: get it right and messaging, sales, and pricing become dramatically easier; get it wrong and no amount of clever copywriting will save you.

## Scoring

**Goal: 10/10.** Rate any product's positioning 0-10 using the bands below, and always state the current score with the specific improvements needed to reach 10/10.

| Score | Description |
|-------|-------------|
| 0-2 | No clear positioning; customers can't explain what the product is or who it's for |
| 3-4 | Vague: category unclear, differentiation weak, target customer is "everyone" |
| 5-6 | Partial: some components clear, others missing; team members describe the product differently |
| 7-8 | Strong: all five components defined, team aligned, customers generally understand the value |
| 9-10 | Exceptional: every component reinforces the others; customers immediately get what it is, why it's different, and why they should care |

## The 10 Positioning Components

| Component | Description | Example |
|-----------|-------------|---------|
| Competitive Alternatives | What customers would use if you didn't exist | Spreadsheets, consultants, doing nothing |
| Unique Attributes | Capabilities only your product has | Real-time collaboration on financial models |
| Value Themes | Benefits customers get from unique attributes | Save 10 hours/week on financial reporting |
| Best-Fit Customers | Who cares most about your value | Mid-market CFOs managing 3+ business units |
| Market Category | The market you describe yourself as part of | FP&A software |
| Relevant Trends | Dynamics that make positioning resonate now | Remote finance teams need real-time collaboration |
| Positioning Statement | Internal one-line summary for team alignment | "For mid-market CFOs, the FP&A platform built for real-time collaboration" |
| Sales Narrative | Positioning as a compelling sales story | Problem -> old way -> new way -> your solution -> proof |
| Messaging | External language derived from positioning | "Financial planning that keeps up with your business" |
| Content Strategy | What content positioning tells you to create | Thought leadership on collaborative finance |

## The 5-Step Positioning Process

### Step 1: Identify Your Competitive Alternatives

**Core concept:** Understand what your best customers would do if your product vanished tomorrow -- not just direct competitors, but any way they solve the problem today: manual processes, spreadsheets, hiring someone, or doing nothing.

**Why it works:** Customers always evaluate products relative to alternatives, so "differentiated" only has meaning against the real alternatives in your customer's mind.

**Key insights:**
- Ask existing happy customers, not prospects -- they can tell you what they actually switched from
- The most common alternative is often not a product -- it's a spreadsheet, a manual process, or the status quo
- "Do nothing" is your biggest competitor in many markets
- Group similar alternatives ("general-purpose spreadsheets" rather than Excel, Sheets, Numbers)
- Different customer segments may have different alternatives

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| New product launch | Interview early adopters on what they used before | "70% used spreadsheets, 20% a generic PM tool, 10% hired contractors" |
| Repositioning | Survey churned and retained customers | Retained customers compared you to consultants, not software |
| Competitive analysis | Map alternatives by segment | Enterprise compares to Salesforce; SMBs to spreadsheets |

**Copy patterns:**
- "Unlike [competitive alternative], [product] does [unique thing]"
- "Stop using [painful alternative] for [job]"
- "You've outgrown [alternative]. Here's what comes next."

**Ethical boundary:** Base alternatives on actual customer research, never assumptions or wishful thinking.

See: [Competitive Alternatives Analysis](references/competitive-alternatives.md) for interview scripts, clustering, and "do nothing" analysis.

### Step 2: Identify Your Unique Attributes

**Core concept:** List every attribute -- feature, capability, company characteristic, or approach -- that you have and your competitive alternatives don't. They must be both unique AND true.

**Why it works:** Unique attributes are the raw material of differentiation: if it isn't unique it can't differentiate you, and if it isn't true you'll lose trust.

**Key insights:**
- Look beyond features: architecture, business model, team expertise, integrations, community
- "Better" is not unique -- "10% faster" doesn't qualify; "a fundamentally different algorithm enabling real-time processing" might
- Every attribute must survive the "only we" test: "Only we [attribute]"
- Attributes are facts about your product; benefits are what customers get from them -- don't confuse the two
- Cluster related attributes into groups (they become value themes in Step 3)

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Feature launch | Check if it creates a unique attribute | "The only PM tool with built-in time-zone-aware s
37signals-waySkill

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

blue-ocean-strategySkill

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

clean-architectureSkill

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

clean-codeSkill

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

contagiousSkill

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

continuous-discoverySkill

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

cro-methodologySkill

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

crossing-the-chasmSkill

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.