Note · 4 min read

A finished design can still contain an unfinished journey

The first slide looks right. The fifth still says Lorem Ipsum. Review the paths and hidden states a screenshot cannot show.

Published · Updated

In this note

Picture a testimonial carousel ready for launch: the first slide has an approved quote, a portrait and a name. The fifth still says “Lorem Ipsum”, attributed to “Profile name, CEO”. Nothing about the first slide tells a reviewer what is waiting at the end.

This is a review problem with a specific remedy. Judge the rendered journey, including the content it takes interaction to reveal. A finished-looking page is a reason to start that check, not evidence that it has passed.

Check the material asking for trust

Testimonials, team profiles and case studies ask the reader to believe something about the organisation. Check them as evidence as well as content. Is the quotation approved? Does the portrait belong to the named person? Does a case card open the case it describes? A default quote is not a weak testimonial; it provides no testimonial at all.

A card styled as a link also makes a promise. If it opens nothing, the reader cannot complete the action the design invited. Keyboard and screen-reader users need meaningful destinations too. Remove an unavailable link or explain its state instead of leaving a control that has no useful action.

Follow the button as a new visitor

Consider a sign-up journey where the homepage's “Get started” button opens a login screen with no account-creation route. Other pages may use the correct sign-up URL. The homepage can still pass a visual review: the label, colour and spacing are all right. The destination is what needs testing.

Start logged out, without the account or knowledge your team normally has. Write down the label, destination and next available step. Analytics can suggest where a journey loses people; tracing the path helps establish whether the implementation matches its promise. Neither check alone proves how much a repair will change conversion.

A release check for content and paths

Run this against the production build in preview before launch, then repeat safe checks on the live release. Use an agreed test path for actions that send messages, take payment or change records. The time needed depends on the site's size and states; record the coverage rather than assuming an afternoon is enough.

  • Search the rendered site for “Lorem Ipsum”, “Placeholder” and template default text.
  • Check link destinations, including in-page anchors; fix empty or unintended targets.
  • Follow the primary call-to-action from every landing page as a first-time visitor.
  • Open every tab and advance every carousel to its last slide.
  • Check repeated content blocks for accidental duplicates.
  • Review image alternatives for their actual purpose; remove template defaults.
  • Check confirmation and failure states, including the next action they offer.

Treat interaction as part of coverage. A tab panel, expanded menu or final slide is still published content. If a component requires interaction to reveal it, that interaction belongs in the review.

Why this survives professional rebuilds

Design approval and content approval answer different questions. So does a journey check. If late content is pasted in after sign-off, the approved screenshot no longer represents the release. Give those changes an owner and a repeatable check instead of relying on someone to remember which parts were still waiting for words.

One named person should record which routes and states were checked, which defects were repaired, and what remains outside coverage. Automated link and placeholder checks can help. They still need a person to judge whether the destination fulfils the label.

If you have not walked yours lately

Begin with the task that matters most: joining, booking, donating or making an enquiry. Follow it from its entry page through to its real next state. If you need a structured review, our fixed-fee UX audit covers agreed pages and journeys and ranks findings by severity and effort. Send us the URL and the task you want the review to examine.

Have a product decision to make?

Tell us what needs deciding and what constrains it. We can discuss whether definition, a build or a reset fits.