Product Positioning

April Dunford's "Obviously Awesome" framework is the most rigorous and practical positioning methodology for SaaS companies. It follows five steps: identify your competitive alternatives (what would customers do if your product didn't exist? — this is their true alternative, often not a competitive product but a spreadsheet or manual process); isolate the features and capabilities you have that alternatives lack (your "unique attributes"); translate those attributes into customer value (what capabilities do your unique attributes enable?); identify who cares most intensely about that value (the customer segments that feel the pain your product resolves most acutely); and determine the best market frame (the category or comparison set that makes your unique value most obvious). The output is a positioning statement: "For [best-fit customers] who are struggling with [compelling problem], [product name] is a [market category] that [unique value proposition], unlike [primary alternative]." Product Ops facilitates the positioning workshop and documents the output, ensuring it cascades into sales decks, website copy, and customer-facing messaging.

Positioning and messaging are frequently confused, but they serve distinct purposes and live in different artifacts. Positioning is internal — a strategic document that is the source of truth from which all customer-facing communication is derived. It answers: what category are we in, who are we for, what is our unique value, and why should they believe us? Messaging is external — the words, phrases, and story structures used on the website, in sales calls, in email campaigns, and in support documentation to communicate the positioning to customers. Messaging is derived from positioning but translated into the language, metaphors, and formats appropriate for each audience and channel. The failure mode occurs when messaging teams write copy without a clear positioning foundation — resulting in messaging that is inconsistent across channels, unconvincing to customers, and impossible to coordinate across the sales and marketing functions. Product Ops maintains the positioning document as a living artifact, ensuring it is updated when the ICP evolves or the product's competitive context changes, and facilitating the cascade of positioning updates into all downstream messaging artifacts.

Positioning drift is a common challenge in scaling SaaS companies: sales reps develop their own pitch variations, marketing creates campaign messaging based on current trends, and support agents describe the product differently based on customer context. Over time, customers receive inconsistent messages about what the product is and who it is for. Product Ops prevents positioning drift by: maintaining a single canonical Positioning Document (linked from the sales enablement wiki, the marketing brief template, and the product spec template — every customer-facing communication starts here); facilitating a quarterly Messaging Audit where examples of sales call transcripts, website copy, and marketing emails are reviewed against the positioning document for consistency; and conducting an annual positioning refresh workshop (triggered by ICP evolution, major competitive entries, or significant product capability expansion). In each workshop, the output is an updated positioning document circulated to all functions with explicit notice of what has changed and how to update existing customer-facing materials.