Fix positioning before you redesign the website

The expensive way to find out your positioning is unclear

The first homepage designs come back, and the review does not go the way anyone planned. The founder wants the hero to speak to enterprise buyers. Sales asks why the main industry they close is missing. Product wants all six modules above the fold. Marketing says the whole thing should feel more innovative. Nobody is commenting on the design. Everyone is arguing about the company.

That is a common way to discover a positioning problem, and an expensive one. Each round of design turns an open strategic question into pixels, and each new direction encodes a different answer. The team ends up choosing its market by choosing between layouts.

This post is about finding that problem before the design sprint. It covers how to tell a positioning problem from the other reasons a website underperforms, three tests to run before you brief a designer, what has to be settled before visual design and what can stay open, and when it is reasonable to redesign before positioning is fully resolved.

Positioning and design are not rivals here. The point is sequence: settle enough of the strategy that design has something specific to make clear.

Positioning, messaging and design answer different questions

A lot of redesign trouble starts with treating several different decisions as one. They connect, but each answers its own question.

Positioning answers why this product is the right choice for a defined buyer, compared with what they would otherwise do. April Dunford, whose framework is widely used in B2B software, builds it from the competitive alternatives buyers would use without you, the attributes only you have, the value those attributes create, the customers who care most about that value, and the market category that makes it easy to understand.

The value proposition is the core promise that follows from that position. Messaging is how the promise is expressed to buyers in words. Information architecture decides where each piece of information lives and how people move between pages. Conversion strategy defines the action a qualified visitor should take next and why they would take it. UX design determines how easily they can find what they need and act. Visual design expresses hierarchy, identity and quality. Technical implementation determines whether the site is fast, accessible, indexable and measurable.

Design is not cosmetic in this list. Gitte Lindgaard and colleagues found that people form judgments of a web page's visual appeal within a fraction of a second, that those judgments are stable, and that they colour later judgments of usability and credibility. A 2012 study by Alexandre Tuch and colleagues, run with Google researchers, found that sites with low visual complexity and familiar layouts for their category were rated more appealing within 17 to 50 milliseconds.

So design changes how a message is received. What it cannot do on its own is decide what the message should be. A beautiful page with an unresolved position gets a fast, favourable first impression, followed by a visitor who still cannot tell whether the product is for them.

What breaks when positioning is unclear

Unclear positioning rarely announces itself. It shows up as a set of symptoms that look like design, copy or process problems. The ones below are common observations from redesign projects rather than findings from controlled studies, but they recur often enough to be worth checking for.

Design reviews turn into strategy meetings. Feedback arrives in visual vocabulary, such as make it more enterprise, add more industries, it does not feel premium, but the disagreement underneath is about the buyer, the category or the reason to choose. Translating feedback back into the decision behind it is the fastest way to see this.

The homepage becomes broad. When the team cannot agree on one buyer, the copy is written to offend none of them, and the result describes a platform for everyone. Proof stops supporting the claim, because the case studies and logos the company has were won in one segment while the homepage now speaks to three.

Sales and marketing tell different stories. Sales wins deals by describing one painful workflow; the website leads with the all-in-one platform. Buyers notice the gap between what they read and what they hear.

Paid traffic lands on a page that never establishes relevance, so campaign performance is judged on a homepage that was not written for the audience the campaign targeted.

Agencies and designers receive briefs that change during the project. The Project Management Institute's 2014 Pulse of the Profession study found that 47 percent of unsuccessful projects missed their goals because of inaccurate requirements management. That research covers projects in general rather than website redesigns, but the mechanism is the same: decisions not made at the start get made, expensively, in the middle.

Finally, nobody can evaluate the result. If the team never agreed what the website was meant to achieve and for whom, there is no fair way to say whether the redesign worked.

Why a polished website can still underperform

A website can look excellent and still fail at its job, because visual quality is one of several things a buying decision depends on.

The visitor has to understand what the product is and who it is for. They have to see that it is relevant to a problem they have now. They have to believe the claim, which depends on proof as much as polish. They have to be able to find what they need and act, on a phone as well as a desktop, on a page that loads quickly. The traffic itself has to be the right audience, the offer has to be worth the effort, and the call to action has to match how ready they are to buy.

Nielsen Norman Group's analysis of page dwell times found that the first 10 seconds on a page are critical for whether people leave, and that visitors who stay past roughly 30 seconds tend to stay considerably longer. That is a reason to make relevance obvious early. It is not evidence that every homepage has to explain everything in ten seconds.

Good design improves several of these at once: trust, comprehension and usability. It cannot fix a weak offer, the wrong traffic or a claim the company cannot prove. A redesign that improves the look while leaving those untouched will usually produce a better-looking version of the same results.

Diagnose the symptom before choosing the fix

Before deciding that the answer is a redesign, a positioning project or both, name the symptom you are trying to fix. Different symptoms point to different layers, and each has a cheap first test.

Leads that arrive but do not fit point at the audience, the positioning or the channel; segment them by source and fit before changing a page. Visitors who cannot explain what the product does point at the message or its hierarchy; a comprehension test will show where understanding breaks. Visitors who understand but do not act point at proof, the offer, the call to action or perceived risk; funnel data and sales objections will narrow it down.

People who cannot find information point at navigation and UX, and a task-based usability test is the right tool. A site that is clear but not trusted points at proof, visual quality or security signals. Organic traffic that falls after a launch usually points at the migration itself; Google's guidance on site moves expects temporary ranking changes and recommends making one major change at a time.

Only the first two rows start with positioning. That is the useful lesson: a redesign is the right fix for several of these symptoms, and the wrong one for others. If you are still deciding whether the website is the bottleneck at all, the five-layer diagnostic for SaaS redesigns covers that question.

Test one: the team alignment test

The objective is to find out whether the people who shape the website describe the same company. Send the same questions separately to the founder, the heads of sales, product and marketing, and anyone else who will sign off the design. Ask them not to compare notes.

1. Who is the priority buyer, and in what situation do they start looking?
2. What problem makes them evaluate a product like ours?
3. What kind of product should they understand us to be?
4. What would they do instead if we did not exist?
5. Why are we meaningfully better for that situation?
6. What evidence makes that believable?
7. What should a qualified visitor do next on the website?

Compare the answers for meaning, not wording. Two people can describe the same buyer in different words, and that is harmless. Two people naming different buyers, different alternatives or different reasons to choose is a strategic disagreement, and it will resurface in every design review until it is settled.

The output is a short document listing each disagreement and who decides it. Warning signs are answers that list every possible customer, alternatives nobody has seen in a real deal, and differentiation that is a feature list. The common mistake is editing answers into agreement before comparing them, which hides exactly what the test exists to find.

The limitation is important: a team can agree on a weak position. Alignment shows the company is telling one story. The next two tests check whether that story matches what buyers understand and value.

Test two: the stranger test

The objective is to see whether someone outside the company understands the homepage without the knowledge everyone inside it takes for granted. Recruit five or so people who resemble your buyers but do not know your product. For early qualitative checks like this, a handful of sessions usually surfaces the obvious problems, which is the same logic behind testing usability with small groups.

Run it in two stages. First show the top of the homepage briefly and ask what kind of company this is and who it seems to be for, to capture the first impression. Then let them scroll and read as they normally would, and ask them to explain, in their own words, what the company offers, who it serves, what problem it solves and why someone might choose it over an alternative. Ask what they would do next.

Avoid reading the page's own phrases back to them, because people repeat the words they are given. Score each answer against what you intended them to understand, and note what they got wrong, what they could not answer and how confident they were.

The output is a list of the gaps between the intended message and the understood one. Warning signs are visitors who name the wrong category, cannot say who the product is for or describe a different product entirely. The limitation is that five people show you problems, not proportions. Treat this as a diagnostic, not a conversion forecast, and do not turn the brief first exposure into a pass or fail rule.

Test three: the sales-call audit

The objective is to compare the website's story with the one that actually wins and loses deals. Pull recordings, transcripts or detailed notes from around ten recent discovery calls, mixing wins, losses and deals that ended without a decision. Ten is a practical starting batch, not a representative sample.

For each call, note the trigger that started the search, the alternatives the buyer was considering, the outcome they wanted, their main concerns, the criteria they used to decide, the phrases they used to describe the problem, the proof they asked for and why they chose or rejected the product.

Then lay the patterns beside the homepage. Does the site name the trigger buyers mention? Does it address the alternative they actually compare against? Does it answer the objections that keep coming up? Does it offer the proof they ask for, in the order they ask for it?

The output is a gap list between the sales story and the website story. A warning sign is a homepage that leads with capabilities buyers never mention. The common mistake is copying buyer quotes straight into headlines. Buyers often describe symptoms rather than value, and use inconsistent terms, so look for patterns and synthesise them. Where you can, confirm what you find against won and lost deal data, support conversations and product analytics.

The homepage is not the sales conversation

A homepage does not have to explain the whole product. It has to make the right visitor think this is for a problem I have, explain the value in terms they recognise, show enough evidence to be believed, and point to a sensible next step. Product pages, solution pages, comparisons, documentation and the sales conversation carry the rest.

Many buyers never see the homepage first. They arrive on a product, pricing, comparison or campaign page from search, an ad or a colleague's link, so those pages need to establish relevance on their own too.

How much the homepage carries depends on the business. Enterprise products sold to buying groups need pages for different roles, because Nielsen Norman Group's B2B research shows that the people who choose a product and the people who use it look for different information. Developer tools usually earn trust with documentation and working examples rather than claims. Products with several distinct audiences often do better with dedicated landing pages than with a homepage that tries to address everyone at once.

What has to be clear before visual design begins

Before high-fidelity design starts, write the core positioning decisions on one or two pages. Not a long brand deck: a working contract the team can point at when feedback drifts.

The non-negotiables are one primary buyer and the situation that makes their problem urgent, the competitive alternative they would otherwise choose, the trigger that makes the old way unacceptable now, the value that is genuinely different, the proof you can legally and honestly publish, the category frame you want buyers to use, and the single claim the homepage has to make. Naming an incumbent as the alternative is its own decision with its own risks.

Alongside those, the brief needs the main objections to answer, the conversion goal, the journeys the site must support and how success will be measured. Some of these can be explored during design rather than settled first: page structure, the exact wording of headlines and the order of proof. The test is whether a decision changes who the site is for or what it claims. If it does, settle it first. If it only changes how the claim is expressed, design can help find the answer.

A positioning-first redesign in eight steps

Each step produces something the next one depends on, and each has a point at which the team is ready to move on. The sequence is not rigid: steps four to six often loop as testing reveals better answers.

1. Diagnose the actual problem. Decide the website's job first, because it may be qualified leads, sales enablement, self-serve sign-ups or recruiting rather than raw conversion. Then use analytics, lead quality and the symptom table above to find where it fails. The output is a problem statement and baseline metrics. Move on when the team agrees what the redesign must fix.
2. Research the audience. Run the sales-call audit and talk to recent customers. The output is a summary of triggers, alternatives, outcomes and objections. Move on when patterns repeat across sources.
3. Clarify positioning. Work through the seven decisions with the people who own them. The output is the one- or two-page positioning document. Move on when the team alignment test produces one story.
4. Validate the messaging. Draft the core message and run the stranger test on it, in a simple wireframe or a plain document. Move on when outsiders can explain the product and buyer correctly.
5. Define conversion goals and journeys. Decide what each audience should do next and which pages get them there. The output is a set of journeys and goals per page.
6. Set the content hierarchy and information architecture. Decide what each page must say, in what order, and where proof sits. The output is a sitemap and content outlines.
7. Start visual design. Now design can do its job: making a specific story easy to understand and believe.
8. Test, launch and measure. Usability-test the prototype, launch with redirects and tracking in place, and compare results with the baseline from step one.

Measure the redesign as several hypotheses rather than one. Does the audience understand the promise? Does it match a problem they care about? Is the reason to choose credible? Does the proof reduce risk? Can visitors find what they need and act? Does the presentation support trust? Does the site perform on every device and in search? Measured separately, one disappointing number points at one layer instead of condemning the whole project.

Readiness gates: green, amber or red

Before committing to high-fidelity design and build, rate six areas: audience, positioning, messaging, proof, conversion goals and decision ownership. This is a practical heuristic, not a validated scoring model. Ready means testable, not final: a clear hypothesis, the evidence behind it, the open questions written down and a plan to test them.

Green means the evidence and alignment are good enough to proceed, while remaining assumptions are tested along the way. Amber means there is a clear hypothesis but real uncertainty, so prototype and test before paying for production. Red means something important is unresolved, and expensive design work should wait for focused discovery.

A red rating on audience, the core claim, the website's job or who makes the final decision should block expensive implementation. A red rating on proof or messaging can often be resolved in parallel, as long as the team knows it is open.

When to redesign before positioning is settled

There are good reasons not to wait. Design exploration can surface positioning options the team had not articulated, because seeing two directions side by side often makes the strategic choice obvious. An early-stage startup may not have enough customers to settle its positioning, and should ship something cheap to change rather than nothing. If the main problem is usability, performance or accessibility, fixing it should not wait for a strategy exercise.

A limited redesign can also work as a controlled experiment: a new landing page for one segment teaches more than another month of internal debate. Products with genuinely different audiences can write separate messaging for each instead of forcing one homepage to resolve everything.

What keeps these cases disciplined is writing the open questions down. If the team knows it is designing to test a positioning hypothesis, design work generates evidence. If it does not, the same work generates rework.

The point

A website redesign is too expensive a place to discover what company you are. Diagnose the symptom first, check that the team tells one story, confirm outsiders understand it and buyers recognise it, and then give designers a position worth making clear.

Positioning is not a document you finish. It is a hypothesis specific enough to design against and test. Fix enough of it to stop the design sprint from becoming a strategy meeting, and design can do what it does best, which is making the truth easier to see.