← Journal
Strategy4 min read

How to Write a Positioning Statement That Is Actually Useful

Most positioning statements are useless. Learn how to write one that actually guides decisions, informs product, and creates competitive differentiation.

Parker CurryFounder, Product & Design
How to Write a Positioning Statement That Is Actually Useful

Most positioning statements are useless. They sound good. They're grammatically correct. They look professional on a document. But they don't actually guide decisions. They don't actually help the business. They don't actually help teams make choices.

A useful positioning statement is different. It guides decisions. It helps teams make choices consistently. It informs what you build. It informs how you market. It informs who you hire. It actually matters.

The difference between a useless positioning statement and a useful one isn't eloquence. It's specificity. It's decisiveness. It's actually reflecting how your business operates and who you serve.

Understanding how to write a positioning statement that's actually useful transforms how your company operates.

What Makes a Positioning Statement Actually Useful

A useful positioning statement does several things.

First, it narrows down. It specifies who you serve. It specifies what problem you solve. It specifies how you're different. It doesn't try to appeal to everyone. It appeals to someone specific.

Real example: Useful positioning statement: "Figma is the collaborative design platform for product teams." This specifies who (product teams), what (design platform), how different (collaborative). Not useful positioning: "Design software for modern teams." This is too vague. It could describe many tools.

Second, it guides product decisions. When you're deciding what to build, you should be able to ask: does this serve our positioned customer? Does this align with our positioning? If not, you don't build it. If positioning doesn't guide product decisions, it's not useful.

Third, it guides marketing decisions. When you're deciding what to say about your product, you should be able to ask: does this communicate our positioning? Does this emphasize what makes us different? If not, you don't say it. If positioning doesn't guide marketing, it's not useful.

Fourth, it guides hiring decisions. When you're hiring, you should be able to ask: does this person understand and believe in our positioning? Are they excited about serving this specific customer? If not, you don't hire them. If positioning doesn't guide hiring, it's not useful.

Fifth, it's defensible. When a competitor copies you or attacks your positioning, you should be able to defend it. "Here's why we're right for this customer. Here's why we're different. Here's why we're better." If you can't defend your positioning, it's not useful.

Sixth, it's honest. The positioning should reflect reality. It should reflect what your product actually does. It should reflect who actually uses your product. If positioning isn't honest, customers discover the lie quickly and churn.

Common Mistakes in Writing Positioning Statements

Most companies make mistakes when writing positioning statements.

First mistake: Being too vague. "The tool for modern businesses." This could describe hundreds of companies. It doesn't narrow down. It's not useful.

Second mistake: Trying to appeal to too many segments. "The CRM for small businesses and enterprises and nonprofits." The multiple "ands" show you're trying to appeal to everyone. You're not narrowed. You're not useful.

Third mistake: Positioning on something temporary. "The cheapest project management tool." Competitors can copy this. It's not defensible. Better to position on something harder to copy.

Fourth mistake: Positioning on something that doesn't matter to customers. You emphasize beautiful design. Customers care about powerful features. Your positioning doesn't align with what customers value. It's not useful.

Fifth mistake: Positioning that doesn't match reality. You position as "easy to use" but the product requires technical setup and steep learning curve. Customers discover the mismatch. They churn. It's not useful.

Sixth mistake: Making it too long. A useful positioning statement is one or two sentences. If it's long, it's not positioning. It's messaging or a value proposition statement.

Real example: Not useful: "We are a comprehensive cloud-based project management solution that helps teams of all sizes collaborate more effectively, streamline workflows, improve communication, and deliver projects on time and on budget." This is too long. It's trying to communicate too much. It's not useful positioning.

Useful: "Asana is the work management platform for teams." Short. Clear. Useful.

Seventh mistake: Not testing it. You write a positioning statement without talking to customers. You don't know if it resonates. You don't know if it differentiates. You publish it and hope it works. It's not useful.

The Process for Writing a Useful Positioning Statement

Here's how to actually write a positioning statement that's useful.

Step one: Define your target customer precisely. Not "businesses." But "SaaS companies with fifty to five hundred employees." Not "teams." But "fully remote product teams." Write down who this customer is. What they do. What they care about.

Step two: Understand what this customer values. What are their top three pain points? What outcomes do they want most? What would they pay premium prices for? Talk to customers. Don't guess.

Real example: A project management tool talks to their best customers. Customers say the top pain point is context switching between tools. The outcome they want is unified work management. What they'd pay premium for is transparency across the team.

Step three: Understand your competition. Who else serves this customer? How are they positioned? What are they claiming? Where are the gaps? Where are the blind spots?

Step four: Identify your distinctive advantage. What do you do that competitors don't? What's hard for them to copy? What's based on your unique capabilities or perspective?

Real example: The project management tool realizes most competitors position on features. "More powerful," "easier to use." But all project management tools are getting more powerful and easier. The tool realizes that unified work management is harder to copy. Most competitors focus on one type of work (tasks, projects, issues). This tool unifies all work types. That's distinctive.

Step five: Identify what you do better for this customer specifically. Not what you're better at generally. What you're better at for this specific positioned customer.

Real example: For fully remote product teams, what's most important? Unified communication. Transparency across time zones. Single source of truth. The tool identifies that they're better at unified work management for remote teams specifically.

Step six: Write the positioning statement. Use this framework:

"[Product name] is the [category] for [target customer] that [differentiator]."

Real example: "Figma is the collaborative design platform for product teams."

Step seven: Test it. Does it resonate with your target customer? Show it to customers. Get feedback. Ask:

  • Do you feel like this is built for you?
  • What's the differentiator?
  • Is it believable?
  • Would this make you more likely to try it?

Get feedback. Iterate.

Step eight: Stress-test it. Ask:

  • Could a competitor claim this?
  • Is this defensible?
  • Does it guide product decisions?
  • Does it guide marketing decisions?
  • Is it honest?

If it doesn't pass these tests, refine it.

Step nine: Write it down and communicate it. Put the positioning statement somewhere accessible. Make sure your team knows it. Make sure they understand it. Make sure they can articulate it.

Examples of Useful vs Non-Useful Positioning Statements

Let's look at examples.

Not useful: "Innovative software that helps teams succeed." This is vague. It could describe hundreds of companies. It doesn't narrow down. It doesn't differentiate. It doesn't guide decisions.

Useful: "Monday.com is the work management platform for hybrid teams." This specifies category (work management platform), target customer (hybrid teams), and implicitly differentiates by focusing on hybrid work flexibility.

Not useful: "The comprehensive financial management solution." Comprehensive is vague. For what customers? What problems? It doesn't narrow down.

Useful: "QuickBooks is financial software for small business owners." Specifies target (small business owners), category (financial software). It narrows down from "any business" to "small business owners specifically."

Not useful: "Making work easier and faster for everyone." Everyone? That's not narrowed. Easier and faster are generic benefits. It doesn't differentiate.

Useful: "Slack is where work happens." This positions Slack as the center of work coordination. Not just chat. The center of work. This is specific and differentiating.

Not useful: "The platform for data analytics and business intelligence and reporting." The multiple "ands" show it's trying to appeal to multiple use cases. It's not focused.

Useful: "Mixpanel is product analytics for product teams." Specifies category (product analytics), target (product teams). It narrows from "any analytics" to "product analytics specifically."

How to Use Your Positioning Statement

Once you have a useful positioning statement, how do you use it?

First, use it to guide product decisions. When your team is deciding what feature to build, what product to launch, what to prioritize, they should ask: does this serve our positioned customer? Does this align with our positioning?

Real example: A project management tool positioned as "for fully remote teams" is deciding whether to build an in-person meeting scheduler. They ask: does this serve remote teams? Not really. Remote teams rarely meet in person. It doesn't align with positioning. They don't build it.

Second, use it to guide marketing decisions. When you're deciding what to say about your product, what benefits to emphasize, what ad to run, you should ask: does this communicate our positioning? Does this appeal to our positioned customer?

Real example: A financial tool positioned as "for freelancers" decides what to emphasize in marketing. They could emphasize powerful features. But their positioning is for freelancers. Freelancers care about simplicity and affordability. They emphasize those instead.

Third, use it to guide sales decisions. When your sales team is deciding who to target, how to position the product to prospects, what benefits to emphasize, they should use positioning.

Real example: A SaaS tool positioned for "fast-growing companies" uses this to guide sales. They don't waste time on mature, slow-growth companies. They focus on fast-growing ones. When they pitch, they emphasize how the product helps fast-growing companies scale.

Fourth, use it to guide hiring decisions. When you're hiring, you should ask: does this person understand our positioning? Are they excited about serving this customer? Do they believe in our differentiation?

Real example: A company positioned as "for creative professionals" is hiring designers. They hire a designer who loves working on tools for creatives. They don't hire a designer who wants to work on enterprise tools. The positioning guides hiring.

Fifth, use it to guide customer research. When you're talking to customers, you should ask: are these questions helping us understand our positioned customer better? Are these decisions helping us serve that customer better?

How to Communicate Your Positioning Statement

Once you have a useful positioning statement, you need to communicate it.

First, communicate it to your team. Make sure everyone knows it. Make sure they can articulate it. Make sure they understand what it means for their job.

Second, communicate it to your board and investors. Make sure they understand your positioning. Make sure they understand who you're serving and why you're different.

Third, communicate it externally through your brand and marketing. Your website should clearly communicate positioning. Your sales deck should communicate positioning. Your ads should communicate positioning.

Fourth, make sure positioning is consistent across all communications. Your website doesn't say one thing. Your ads don't say another. Your sales deck doesn't say yet another. Everything communicates the same positioning consistently.

When to Refine Your Positioning Statement

Your positioning statement isn't permanent. It can evolve. But it shouldn't change constantly.

You should refine your positioning when:

  • You learn that your target customer is different than you thought
  • The market changes significantly
  • You pivot your product
  • You acquire a company
  • You have a competitive threat

You should NOT change your positioning when:

  • You get critical feedback
  • A campaign didn't work
  • You lose a deal
  • Every time you learn something new

Positioning is strategic. It should be stable. But it should be refined based on real learnings.

Real example: A company positions as "for startups" but discovers that most customers are actually from mid-market companies. This is real learning. It's time to refine positioning. Maybe now it's "for growing companies."

Real example: A company loses a deal because the prospect wanted enterprise features. This doesn't mean the positioning is wrong. This is a single deal. Don't change positioning based on single data points.

How Embedded Design Leadership Helps

Writing a useful positioning statement requires expertise. It requires understanding markets, customers, competition, and strategy. It requires testing and iteration.

This is where embedded design leadership helps. When Rival works with companies, we help them write useful positioning statements. We do customer research. We understand the market. We identify distinctive advantages. We write positioning statements. We test them. We refine them.

We also help companies use their positioning statements. We make sure they guide decisions. We make sure they're communicated consistently. We make sure they're actually useful.

At inflection points like product launch, series A fundraising, or competitive challenges, having embedded design leadership to help clarify and refine positioning is valuable.

The Path Forward

If you're trying to write a positioning statement that's actually useful, here's what to do.

First, define your target customer precisely. Write it down. Who is this customer? What do they do? What do they care about?

Second, understand what this customer values. Talk to them. Ask what their top pain points are. Ask what outcomes they want most. Ask what they'd pay premium prices for.

Third, understand your competition. How are they positioned? What are they claiming? Where are the gaps?

Fourth, identify your distinctive advantage. What do you do that competitors don't? What's hard to copy?

Fifth, write your positioning statement. Use the framework. Make it specific. Make it narrow. Make it defensible.

Sixth, test it. Share it with customers. Get feedback. Iterate.

Seventh, communicate it. Make sure your team knows it. Make sure it guides decisions.

Eighth, use it. Let it guide product decisions, marketing decisions, sales decisions, hiring decisions.

This is what we help companies do at Rival. We help you write positioning statements that are actually useful. We help you test them. We help you refine them. We help you use them to guide your business.

Because a useful positioning statement transforms how your company operates. It guides decisions. It creates consistency. It creates focus. It creates growth.

That's why writing a positioning statement that's actually useful matters.

More from the Journal