Before you redesign a landing page, write the decision brief

A landing page can be visually polished and still leave the customer doing too much work. They may not know whether the service is suitable, what happens after an enquiry or why the business is credible. Before moving components around, make the decision the page should support explicit.

Write the arrival context

Record where the person is coming from, what they are looking for and what they have been promised. A highly specific paid-search ad creates a different expectation from an early research article. The page opening should help the visitor recognise that they have reached a relevant place, without making them reconstruct the connection.

Name the next decision

“Convert more visitors” is an outcome, not a useful page brief. A more practical question might be: can an operations manager tell whether this service fits their multi-site business and understand the next conversation? That example gives content, design and development a shared problem to solve.

Put the information in decision order

List the questions a suitable customer needs answered: what the service does, who it suits, what the work includes, what evidence supports it and what happens next. Order the page around those questions. A long list of capabilities at the top can delay the information someone needs to decide whether to keep reading.

Give evidence a specific role

Choose proof that answers an objection. A case study can show relevant experience; a named specialist can clarify who will do the work; a description of the engagement can explain responsibilities. Keep the source and scope of any result close to it. A decorative client logo cannot carry all of those jobs on its own.

Review the small-screen journey

Check the page on a narrow screen with ordinary text lengths and real validation messages. Can the visitor read the offer, compare the options and reach the next step without losing their place? Test form labels, required fields, keyboard focus and recovery from mistakes. The quality of the error state is part of the experience.

Treat speed as part of the job

Core Web Vitals cover loading, responsiveness and visual stability. They are useful technical signals, rather than a substitute for reviewing whether the page answers the customer’s question. Prioritise heavy media, unstable layouts or delayed interaction when those issues interfere with the journey. Verify improvements with suitable measurements instead of assuming a smaller image solved the whole problem.

Define the action and how it will be checked

Agree the completed action that matters and how the team will validate its recording. Keep the journey review and the reporting definitions connected. Attribution assigns credit within a measurement model; a change in attributed conversions alone does not prove that the redesign caused the difference. Note other changes to campaigns, offers or demand.

Choose an evaluation method the situation supports

Where traffic and conditions support a well-designed experiment, agree the question and method before launch. Where they do not, use usability findings, customer feedback and a documented comparison with its limits. The useful output is a prioritised brief, ownership and a way to learn—not an unsupported promise of a conversion uplift.