Digital experiences · JNAGA perspective
When is a website problem really a service problem?
If a website looks dated or enquiries are poor, the visible page may be only one part of the difficulty.
Published 25 September 2026
Imagine a site clearly promises a consultation, but the first reply is a generic form asking the visitor to choose a technical product. The page and the service now tell different stories.
Fixing the response and handover may improve the experience more than changing the visual design. Review the entire path before commissioning a rebuild.
Look beyond the screen
Follow a visitor’s path from the question that brought them to the site through the first reply and the eventual service. Can they understand what is offered, who it is for and what happens next? Does the organisation respond in a way that matches the promise made online? A polished redesign cannot repair a broken handover on its own.
Talk to the people who receive enquiries. Their account of recurring misunderstandings can be more useful than a debate about the colour of a button.
Separate comprehension from conversion
More submissions are not always better. If the wrong people contact you because the service is vague, a clearer explanation may reduce volume while improving fit. If visitors hesitate because responsibilities or next steps are unclear, adding urgency or a form may make the experience worse.
Review the language, navigation, accessibility and evidence on the page together with the response process behind it.
Change the smallest useful part first
Sometimes a better service description and an honest contact route are enough. Sometimes the enquiry, assessment and fulfilment journey needs redesign. Define which part of the experience is failing before funding a full visual rebuild.