product-positioning

Included with Lifetime

$97 forever

Position a product using April Dunford's Obviously Awesome framework. Use when asked to define positioning, articulate differentiation, write a value proposition, or figure out how to position a product in the market. Follows the five-step competitive alternatives approach.

General

What this skill does

Position products by starting from what customers would do without you — not from your features or aspirations. April Dunford's Obviously Awesome framework works because it's grounded in reality: what alternatives exist, what you do differently, and who cares most about that difference.

## The Five Steps (In Order)

These steps are sequential. Do NOT skip ahead or rearrange.

### 1. Competitive Alternatives
What would your best customers do if you didn't exist? List real alternatives:
- Direct competitors
- Indirect solutions (spreadsheets, hiring someone, different tools)
- Do nothing

Be honest. If "do nothing" is the primary alternative, that tells you a lot about urgency.

### 2. Unique Attributes
What do you have that the alternatives don't? List concrete, verifiable capabilities — not marketing spin.

- "Real-time collaboration on specs" (verifiable)
- NOT "best-in-class experience" (unverifiable)

### 3. Value
What do those unique attributes ENABLE for the customer? Translate features into outcomes.

- Attribute: "Real-time cursors and inline comments on any document"
- Value: "Get feedback from your team in minutes instead of waiting for a meeting"

### 4. Best-Fit Customers
Who cares MOST about the value you deliver? Define them tightly:

- "Remote teams of 5-15 who collaborate daily but drown in Slack threads and lost Google Docs"
- NOT "product managers" (too broad)

Best-fit customers have: the problem acutely, tried alternatives, have budget/authority, and get the most value from your unique attributes.

### 5. Market Category
What market do you position in so that your value is obvious? This is the LAST decision, not the first.

Options:
- **Existing category:** "We're a [known category] that [key differentiator]." Works when the category is well-understood and your differentiator is strong.
- **Subcategory:** "We're [modifier] + [existing category]." Works when you serve a specific segment better. E.g., "async-first collaboration tool."
- **New category:** Create a new name. Only works if you have the budget and patience to educate the market. Almost always the wrong choice for startups.

## Guidelines

- CRITICAL: NEVER position in a vacuum. Always start from competitive alternatives.
- NEVER lead with the market category. It's the output of positioning, not the input.
- ALWAYS position for your best-fit customers, not for everyone. Trying to appeal to everyone means resonating with no one.
- NEVER confuse features with value. Features are what you built. Value is what the customer gets.
- ALWAYS pressure-test by asking: "If I told my best-fit customer this positioning in one sentence, would they immediately get why they should care?"
- NEVER use superlatives you can't prove ("best," "most powerful," "leading"). Use specifics.

---

*Built on Obviously Awesome by April Dunford. Skills from [productskills](https://github.com/assimovt/productskills).*

Files: 1

Size: 3.2 KB

Complexity: 8/100

Category: General

Source: https://github.com/assimovt/productskills/tree/main/skills/product-positioning

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts