Positioning Statement: Name the Alternative
A team can fill every blank in a positioning template and still disagree about its product. Sales describes it as a replacement for the customer’s current process. Marketing puts it in a broad software category. The product team talks about its most unusual feature. All three descriptions may be grammatically sound, yet each asks a different buyer to make a different comparison. If you searched for a positioning statement because your homepage, sales deck, and product description seem to tell separate stories, another polished sentence will not settle the disagreement. A decision about whom the product serves and what that buyer would otherwise use will.
A positioning statement is a compact record of that decision. It names a target customer, the need that matters to that customer, the category in which the product should be understood, the benefit it offers, the main alternative, and the difference that makes the benefit plausible. The familiar two-sentence structure appears in Stanford University’s positioning template. The template is useful because it makes missing choices visible. It cannot tell you whether the choices you enter are true for a particular product and market.
I would therefore write the statement late in the positioning work, even if the assignment asks for one now. First decide what customers actually compare, which of those customers care most about your advantage, and what you can responsibly say they get from it. Then compress those decisions into language a colleague can use. The cost is that you may have to reject a broad, flattering description and narrow the immediate audience. That constraint is also what gives the finished statement its value.
A good sentence records the market choice
The word positioning often gets applied to any short description of a product. That blurs an important distinction. A positioning statement is primarily an internal choice about where the product belongs in a buyer’s mind. A homepage headline or advertisement is a message made for a particular moment and audience. The message can draw on the positioning, but it need not reproduce the internal sentence. Product Marketing Alliance describes positioning as an input to customer-facing messaging. That division gives the team room to write clear customer language without changing its market choice every time it changes a campaign.
The statement should answer a concrete question: why would this particular buyer choose this offer instead of the option available to them now? A phrase such as “an innovative platform for modern businesses” answers none of it. “Businesses” hides who would decide; “modern” hides the need; “innovative” makes no comparison. Even a precise category and a real product capability are insufficient if the capability has no consequence the buyer values. A statement becomes useful when each part limits the next: the buyer has a need, the alternative leaves some part of that need unmet, and the product has a relevant difference.
This is why a filled template can conceal unfinished work. April Dunford’s positioning sequence begins with competitive alternatives, then moves through differentiated capabilities, customer value, best-fit segments, and market category. A completed sentence alone cannot carry that reasoning. Two people can use the same six fields while assuming entirely different alternatives. Their final drafts may sound similar until a buyer asks, “Why would I switch from what I already use?”
I would keep a short account of the choices behind the sentence: the customer situation, the alternative considered, the relevant product difference, and the reason the proposed benefit follows. That account is not extra language for the public statement. It is how the team avoids treating elegant wording as a substitute for a defensible choice. If nobody can explain why one audience and alternative were selected over another, rewriting the sentence is premature.
Find the alternative before naming the advantage
Start with the buyer’s available choice. Ask what the target customer would do if your product did not exist. The answer could be another product, a spreadsheet, a manual process, or simply continuing the current arrangement. Dunford explicitly starts with that question in her guide to positioning. It is more useful than assembling a list of every company in a nominal category, because a possible competitor is not necessarily the option this buyer is weighing.
This changes how you describe a difference. If a customer currently uses a spreadsheet and text messages, an advantage might be that one job record stays attached to its updates. If the customer instead uses a specialist application with the same record, that advantage disappears. The product has not changed; the comparison has. Writing “unlike competitors” without identifying the relevant alternative lets a team claim a distinction that may not exist in the decision the buyer is making.
The alternative also tells you what the buyer has already accepted. A manual method may cost staff time but require no new subscription or training. An established product may already cover most needs and have a known purchase process. Either can be hard to displace. If the current way is good enough for the customer, a statement promising to be “better” cannot create a compelling reason to change. The positioning has to address a need that makes the difference matter now, or the team should admit that this segment may not be its best first choice.
I would write the alternative in ordinary language before attaching a brand or category label. “The dispatcher texts assignments and copies updates into a shared spreadsheet” tells a product team what behavior must change. “Legacy workflow tools” does not. If customers use several alternatives, do not blend them into one imaginary opponent. Choose the alternative that defines the decision for the audience in this statement; a materially different decision may call for a separate position or message.
There is a trade-off here. A statement aimed at the status quo can be immediately recognizable to people using that process, but it may not explain why an established software buyer should switch products. A statement aimed at a specialist competitor can make a sharper feature comparison, but it may miss customers who have never bought that category. Choose according to the buyer you intend to win, rather than which comparison makes your product look easiest to praise.
Separate the customer from the need
The target customer and the customer’s need occupy different fields in Stanford’s template for a reason. “Small companies” is a customer description, albeit a broad one. “Need to keep field job records usable when a connection drops” is a situation. The same small company may never face that situation; a larger company might face it every day. If you fuse customer type and need into a vague phrase such as “busy teams,” you lose the condition that makes the product relevant.
Define the customer narrowly enough that someone can recognize whether they are in the intended group. Industry and company size may help, but the decisive characteristic is often the circumstance that makes the benefit valuable. The useful target might be a person responsible for a workflow rather than every employee who touches the product. Specify who makes or strongly influences the purchase if that affects the story. A technician may use an application while an operations manager decides whether it is worth buying; their questions will not be identical.
Then state the need as a task, obstacle, or desired outcome in the customer’s terms. “Needs digital transformation” is too far from a decision. “Needs completed job details available for invoicing even when technicians cannot stay online” identifies the work and the friction. The wording still has to be checked against the actual customer; a plausible need invented in a meeting is only a hypothesis. The distinction matters because a feature can appeal to users without being important enough to change the buyer’s budget or process.
The Harvard Business School Institute for Strategy and Competitiveness frames a value proposition around choices about which customers to serve, which needs to meet, and what relative price offers value to customers while supporting the business. These choices constrain each other. If you select a segment that needs extensive service, a low-price promise may conflict with what serving it requires. If you choose a narrow need, a broad claim that the product solves every related problem weakens the choice. A positioning statement should reflect the part of the market the company is prepared to serve, not the largest collection of people who could theoretically use the product.
Narrowing a target does not mean declaring everyone else unwelcome. It means choosing the buyer whose problem the product can explain most clearly. The cost is leaving some potential uses out of the lead sentence. That can feel uncomfortable when a product has many capabilities, but a sentence that tries to serve all buyers usually gives none of them a clear reason to pay attention. If another segment later proves to value a different capability, revisit the position rather than quietly expanding every field until it says little.
Turn a product difference into a buyer benefit
Once the alternative and customer need are clear, compare capabilities. What can this product do that the alternative cannot do, or cannot do as well under the conditions that matter? Describe an observable difference before selecting an adjective. “Can save a job report without a live connection and synchronize it later” is a capability. “Seamless” is a judgment without an object. The capability matters only if it changes something the buyer cares about.
Move from capability to benefit by following the consequence through the customer’s work. If a report remains available offline, a technician can finish the record at the site even when a connection is unavailable. If the record synchronizes later, the office can receive the completed details without asking the technician to re-enter them. Whether that saves enough time, reduces errors, or changes revenue is a separate factual question. Without product and customer data, write the directly supported operational benefit and leave the bigger outcome unclaimed.
This distinction keeps a positioning statement from making a leap that sales cannot explain. “Offline reports” by itself describes the product. “Eliminates billing delays” may overstate what the feature accomplishes, because billing can also depend on approval, pricing, and office practices. “Lets technicians capture completed work at the site despite a lost connection” is narrower and easier to connect to the capability. A buyer may value that strongly, weakly, or not at all. The real customer decision determines whether it belongs at the center of the position.
The strongest difference is not necessarily the rarest feature. An obscure capability can be unique and still irrelevant. Conversely, a capability shared by several products cannot support a claim that only yours delivers it. Dunford’s sequence joins differentiation to value and then to the customers who care most about that value; the steps are connected rather than independent blanks in a form. Her guide explains that relationship. I would reject a proposed “key differentiator” if the team cannot finish the sentence “which matters to this buyer because…” with a specific consequence.
If several benefits are credible, choose the one that best explains the buying decision. A statement loaded with speed, control, simplicity, savings, and confidence may sound complete but gives no priority to any of them. Secondary benefits can appear in later messaging. The internal statement needs a primary value that connects the target customer’s need to the product’s difference. That choice also makes it easier to see what would overturn the position: a different customer need, a competitor matching the capability, or a product change that removes the advantage.
Choose a category that creates the right comparison
The market category tells a buyer what kind of thing the product is. It sets expectations before the rest of the sentence has finished. A familiar category can help the buyer understand the product quickly, but it also invites comparisons with products already in that category. A broad label may attract more searches or conversations while forcing the team to explain why its focused product lacks features buyers expect from a full suite. A narrow label may clarify fit but exclude some buyers who would benefit. Category selection is therefore a judgment about the comparison you want, not a hunt for the most fashionable term.
I would choose the narrowest familiar category that accurately describes the product and gives the selected buyer a fair basis for comparison. A team should be able to say what customers will expect after hearing the label and whether the product meets those expectations. If the category requires apologizing for many absent features, consider a different frame. If the category is so novel that every conversation begins with a definition, weigh the time and expense of teaching it before adopting it. Dunford places category after alternatives, differentiation, value, and customers for this reason: the label should make an established value easier to understand, not decide the value in advance. Her sequence puts market category last.
Price also belongs in the reasoning, even if the statement itself does not include a number. The Harvard value-proposition framework asks what relative price makes sense alongside customers and needs. Its discussion of relative price distinguishes buyers who want enough of a product at a lower price from those willing to pay more for needs that are underserved. That does not establish the right price for your product. It means a promise of premium service, a low-cost comparison, and the chosen buyer’s willingness to pay cannot be considered separately.
Suppose the position emphasizes a focused tool that replaces a manual process. The buyer may compare the subscription with the effort of changing habits, rather than with another subscription. Suppose instead the position claims a more capable alternative to specialist software. The buyer may ask which existing features would be lost and what the difference costs. In each case, price and switching effort can change whether the claimed benefit feels worthwhile. If those facts are unknown, keep the statement from promising savings or a premium return. The missing commercial information should remain an open decision, not be disguised by an attractive sentence.
Write the statement after making those choices
The classic form remains a useful compression device. In paraphrase, it says: for a defined customer with a defined need, the product is a category offering a key benefit; unlike the main alternative, it has the difference that enables that benefit. That is the structure in Stanford’s two-sentence template. You can change the grammar if it reads awkwardly. Keep the causal links.
Before drafting, put each answer on its own line in your working notes: buyer, need, current alternative, relevant difference, resulting benefit, and category. Read across the answers once. If the buyer named in the first line would never consider the alternative in the third, the choices do not fit together. If the difference cannot produce the benefit, the sentence will overpromise. If the category suggests a product much broader than the one described, the buyer may expect the wrong thing. Fix the choice before polishing the wording.
Then write a sentence a colleague could repeat without adding caveats. Prefer concrete nouns and verbs to superlatives. “For every business” is usually a warning that no target has been selected. “The only,” “best,” and “most advanced” require support that a framework does not supply. A named alternative is useful when that alternative genuinely defines the buyer’s decision; otherwise a specific process may be more accurate than a brand. A comparison against “traditional solutions” rarely tells a reader what is being replaced.
Concise does not mean stripping away the mechanism. “For repair teams, our software improves operations” is short but gives little direction. A somewhat longer statement that identifies the responsible buyer, the job, the current process, and the product’s operational difference can guide a sales conversation or a product decision. Brevity becomes useful after the choice is clear. It cannot make an unclear choice clear.
An illustrative statement, built from its assumptions
Consider an entirely illustrative product, not a claim about an existing company or market. Assume a field-service application lets technicians record completed work without a live connection and synchronizes those records when connectivity returns. Assume the intended buyer is the operations manager of a residential repair company whose technicians sometimes work where mobile service is unreliable. Assume the company’s current alternative is a mix of text messages and a shared spreadsheet, and that those tools do not reliably preserve a complete, site-level record. These assumptions are visible because a real positioning decision would need them checked with the product and the customers.
The initial temptation might be to write, “For service businesses, our innovative field-service platform makes work easier.” That sentence hides the actual situation. “Service businesses” could include many buyers with different processes. “Work easier” says nothing about the record that matters. “Innovative” offers no relevant difference from the spreadsheet or from another application. The sentence gives a writer several attractive words but almost no guidance about which customer story to tell.
The alternative in this illustration is the spreadsheet-and-text process. The distinctive capability, by assumption, is that a technician can save a completed job record at the site while offline and send it when connected. The immediate benefit is a usable record created where the work was done despite an interrupted connection. The buyer is the operations manager who needs those records; the technician is an important user. The category could be “field-service job software,” provided the imagined application meets the basic expectations that label creates. The need is more precise than a general wish to “streamline operations.”
A defensible illustrative statement would read: “For operations managers at residential repair companies whose crews work with unreliable mobile service, the product is field-service job software that lets technicians record completed work at the site and synchronize it later. Unlike a process built from texts and shared spreadsheets, it preserves one job record through the offline-to-online handoff.” That wording is longer than a slogan because it is doing a different job. It specifies the buyer’s situation, the alternative, the capability, and the operational consequence. It does not claim a measured reduction in missed jobs, billing time, or cost.
The assumptions also show how the statement could fail. If buyers already use an application with reliable offline records, the spreadsheet comparison is the wrong one. If connectivity is rarely a problem, the selected benefit may be too small to influence a purchase. If the product only saves drafts offline but cannot preserve attachments needed by the office, “one job record” may be too strong. If the application lacks what buyers expect of field-service job software, the category may set the wrong expectations. Each of these is a reason to revise a specific choice, rather than to add more enthusiastic adjectives.
Now change one condition. Suppose the same imagined product is sold to firms whose technicians are always connected but whose office needs a better approval flow. The offline capability no longer explains why that segment would buy. It may still be a feature, but it should not anchor their position. The team would need to identify the relevant alternative, the approval need, and a genuine capability that meets it. If those facts are unavailable, the honest answer is that there is no support yet for a strong statement about that segment.
The example illustrates the price question as well. A buyer using texts and a spreadsheet may regard the existing tools as inexpensive even if they take effort. The new subscription and change in routine are costs to weigh against a clearer job record. Without information about the product’s price, the time currently spent, and the value of a better record, the statement cannot promise a financial return. It can still articulate a product difference and a plausible operational benefit. A useful position can be specific without pretending to know a result it has not measured.
Let the statement guide messages without becoming the message
Once the statement is sound, use it as a check on customer-facing language. A homepage could lead with the problem of recording work at sites with poor connectivity. A product page could explain how offline capture and later synchronization work. A sales conversation could start by asking how the prospect currently records completed jobs. Those are different messages drawn from the same illustrative position; they should not all paste the internal two-sentence statement verbatim. Product Marketing Alliance distinguishes the internal position from the messaging built from it.
This separation also stops the statement from trying to carry every proof point and objection. A customer-facing claim about saved time would need product and customer support that the internal sentence does not create. A demo would need to show the offline record and the later handoff. A pricing discussion would need to address what the buyer spends or gives up to switch. The statement tells the team which story it has chosen; the messages and materials must do the work of explaining that story in the buyer’s context.
I would ask people who will use the position to explain it in their own words. Can they identify the intended buyer and say when the position does not apply? Can they name the alternative and show the difference without reaching for an unsupported claim? Can they explain why the feature produces the stated benefit? Disagreement on any of these points usually means the choice behind the sentence is still unsettled. Agreement on the words alone is less useful than agreement on the situation those words describe.
The position should change when the decision it represents changes. A product may gain or lose a relevant capability. The buyers who care most may turn out to be different from the initial target. The alternative a buyer uses may change. A category label may start suggesting expectations the product cannot meet. In each case, reopen the affected choice and trace its effect through the buyer, benefit, and comparison. Changing a headline for a new campaign, by itself, is not such a change; it is a different expression of the same position.
The practical standard is simple. A positioning statement earns its place when it helps someone choose a buyer, explain a benefit, and understand the alternative in the same breath. If the sentence can be attached to almost any product, return to the customer’s situation. If it depends on a result nobody can substantiate, reduce the claim to the mechanism you can explain. If the team cannot agree which current option the buyer would give up, begin there. Once those decisions are made, the wording becomes the easy part.