skills/product-positioning/SKILL.md
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.
npx skillsauth add assimovt/productskills product-positioningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
These steps are sequential. Do NOT skip ahead or rearrange.
What would your best customers do if you didn't exist? List real alternatives:
Be honest. If "do nothing" is the primary alternative, that tells you a lot about urgency.
What do you have that the alternatives don't? List concrete, verifiable capabilities — not marketing spin.
What do those unique attributes ENABLE for the customer? Translate features into outcomes.
Who cares MOST about the value you deliver? Define them tightly:
Best-fit customers have: the problem acutely, tried alternatives, have budget/authority, and get the most value from your unique attributes.
What market do you position in so that your value is obvious? This is the LAST decision, not the first.
Options:
Built on Obviously Awesome by April Dunford. Skills from productskills.
development
Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.
documentation
Write product strategy documents with real tradeoffs and clear choices. Use when asked to write a product strategy, define strategic direction, create a strategy doc, or articulate where to play and how to win. Built on Playing to Win and Rumelt's Strategy Kernel.
tools
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
development
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.