Is your website redesign stuck? Maybe the brief has grown to forty bullet points, the developer keeps asking which ones matter, and each answer from the team is “all of them”. That is a classic symptom with a boring, fixable cause: the project has no ranked list of must-haves versus nice-to-haves. We will diagnose the cause first and then go through a remedy that you can start using within days.

The symptom: everything is urgent, so nothing ships

Here is how a stalled redesign usually looks from the outside. The kick-off was energetic. A few weeks later the schedule has slipped, nobody can say precisely why, and the review meetings have turned into debates about small details such as the animation on a button. Meanwhile the pages that visitors really need, like the one explaining what you sell and the one where they can contact you, remain half-finished.

If this rings true, resist the urge to blame people. A project with a flat list of wishes will behave this way no matter how talented the team is. Every item competes with every other item, and a flashy extra can eat days that a core page needed.

The diagnosis: no one wrote down the non-negotiables

Ask three people on the project to list the five things the new site absolutely must do. If you get three different lists, you have found the root cause. Without a shared definition of “must”, everyone defends their own favourite, and the developer is left to guess. Guesses are expensive.

A second check: look at how many items are labelled “high priority”. If more than a third are, the label has stopped carrying information. Priority only means something when some things are clearly lower.

The treatment, step by step

1. Agree on what “must-have” means

Use a plain test: if this is missing at launch, would the site fail at its job or put the business at risk? A visitor who cannot find your contact details is a failure. A visitor who does not see a parallax scroll effect is not. Write the test at the top of the shared document so you can point to it when feelings run high.

2. Write the musts as outcomes

Phrase them as things a visitor or editor can do. “Visitors can request a quote in under a minute.” “Staff can update opening hours without calling a developer.” “Pages load comfortably on a mid-range phone.” Outcomes leave room for the developer to pick a sensible solution, while features lock you into a particular answer too early.

3. Check the structure against the basics

Most business sites need a similar skeleton, and it pays to confirm that your musts cover it. A thorough walkthrough of the pages a business website should have is a useful cross-check. If a page type on that list is missing from your must-have column and you cannot explain why, discuss it before moving on.

4. Park the rest in a ranked tie-breaker list

Everything that did not make the cut goes on a second list. Do not delete these ideas; they are often good. Rank them by benefit, effort and how easy they are to add after launch. Items that are cheap to add later, such as an extra gallery or a newsletter box, are perfect candidates for “after launch”. Items that are hard to retrofit, such as a major change to how content is organised, deserve a closer look now, and some of them may deserve to move up.

5. Plan before you build

Once the lists exist, they feed straight into a development plan. For a deeper look at that stage, there is a step-by-step approach to planning a site before development begins, which fits neatly after the sorting exercise. The must-have list becomes the first milestone, and the tie-breakers become a menu for later releases.

Quick checks that your list is healthy

• It fits on one screen without scrolling.
• Someone outside the project can read it and say what the site is for.
• No item is a specific tool or plugin name; those belong in the solution, not the requirement.
• Every item has a person who can explain why it is there.
• There is a date on it, and a plan to revisit it.

A quick example of the fix at work

A small training company had a redesign list of thirty-odd items. After one workshop, the musts came down to five: a clear course catalogue, an enquiry form that works on phones, a page for each course that staff can edit, fast loading, and a privacy notice. Everything else, from a video banner to a testimonial slider and a members area, moved to the tie-breaker list. The core launched in a few weeks, and two of the extras were added the next month after the team saw what visitors actually clicked. Nothing was thrown away; it was simply put in the right order.

What if the client or boss insists everything is a must?

This happens, and arguing rarely helps. A gentler move is to ask a trade-off question: “If we could only launch with three of these, which three?” Most people can answer when forced to choose, and the answer tells you what the real core is. Another option is to show the cost. Put the effort next to each item and let the group see that the animated intro costs as much as the entire contact flow. Visible costs tend to cool enthusiasm without any confrontation.

A side note on decisions outside web work

This sorting habit travels well. People arranging healthcare abroad, for example, can use it for the practical parts of the journey: dates, language support, who goes with them. An educational website called BestCardiacHospitals, an educational site for patients looking at care abroad, lays out a process of sharing needs, getting options and comparing them, and it notes on its own pages that nothing there is medical advice or intended for emergencies. The takeaway for a web project is the same: sort what you need before comparing choices, and leave specialist questions to specialists.

Mistakes that bring the problem back

Letting a nice-to-have sneak in through a side door. A well-meaning chat message that says “could we also…” can bypass the whole list. Route every request through the same sorting test.

Forgetting quality musts. Speed, accessibility and security belong on the core list. They are easy to forget because nobody asks for them in a meeting, yet visitors notice when they are missing.

Never revisiting the list. New information arrives during the build. Review the lists at each milestone, and move items in either direction, writing down why.

Letting the list grow back. A must-have list that doubles in a month is a signal that wishes are being relabelled. Return to the definition and apply the test again.

The cure in one paragraph

Write down what “must” means, list a handful of outcomes that meet it, check them against the usual structure of a good business site, rank everything else as tie-breakers, and plan from the short list. The result is not a perfect website. It is a website that actually launches, with a clear queue of improvements behind it. After that, you can spend your energy on what visitors really respond to rather than on the endless argument about what to include.