A website can tell the story of an organisation long after that organisation has moved on. Keeping the two connected takes memory, insight and a willingness to reconsider what people actually need.
The person who knows what is wrong with your website may be the person who answers your phone. They hear the questions that should already have been answered, explain where to find information and reassure customers who have misunderstood the offer. They talk people through a process that appeared straightforward when it was drawn on a whiteboard six months earlier. Somewhere in those conversations is a brief for a better website, although it does not always reach the people responsible for one.
Meanwhile, the business carries on learning. It develops services, acquires experience and discovers things about its customers that nobody could have known at the outset. Its website can remain attached to an earlier understanding of the organisation, gradually becoming less representative of what it does and less helpful to the people it wants to reach. Eventually, someone decides it looks dated and a redesign begins, even though its appearance may be only part of the problem.
We tend to discuss websites as objects: things commissioned, built and delivered. Projects have milestones, launch dates and handovers, all necessary for getting work into the world. Yet the neatness of that process can obscure the less orderly life that follows. Once a website is live, its assumptions meet people who were absent from the planning meetings. Those people have limited time, particular intentions and little interest in the internal arrangements that determined where a piece of information ended up. Their experience depends on how well the organisation has understood the gap between what it knows and what they need to know.
Our recent work for Hannington, Carriage Works and Dogparks has brought that question into focus. A village community, a former railway works finding a contemporary purpose, and a platform connecting dog owners with secure exercise spaces have little reason to look or sound alike. Each requires its own approach to language, imagery and navigation, shaped by the circumstances in which someone is likely to visit. What connects them is the need to make the knowledge behind the website useful to someone encountering it from the outside.
For a community website such as Hannington’s, that begins with recognising how much local knowledge is taken for granted. People closely involved in village life may know which organisation handles a particular matter or where a document is likely to be filed. A resident looking for an answer may have no reason to know either. The website has to bridge that difference while also reflecting the character and activity of the place. Its value rests on making practical information accessible without reducing a living community to a collection of administrative pages.
At Carriage Works, the challenge is to explain a place whose identity encompasses several different things. Its railway history matters, as do the businesses, workspaces and events giving the buildings a contemporary life. Someone considering space there needs to understand both the atmosphere and the practical offer. Photography and editorial content can help communicate what it feels like to be part of the place, while clear routes through the information allow a prospective occupier to establish whether it could suit their organisation. The website has to accommodate curiosity and serious consideration, often within the same visit.
Dogparks takes that challenge further because the website has to serve two audiences whose needs meet within the same booking. For dog owners, the experience begins with finding somewhere suitable: understanding the setting, checking facilities and choosing a session with confidence. Behind that apparently straightforward transaction sits the work of running a park. Availability, prices, access instructions, payments and booking changes all need to make sense to the customer while remaining manageable for the operator. Designing the public-facing experience therefore means understanding the business taking place behind it, including the everyday exceptions that a simple booking form cannot anticipate.
The operator tools are a substantial part of that work. The Pro dashboard brings together booking management and practical controls for running the park, from managing closures and adding manual bookings to handling offers and customer changes. A feature-rich system earns its value when those capabilities feel understandable to the person using them, particularly someone fitting administration around the physical demands of maintaining a field and looking after customers. That creates a demanding design problem: giving operators enough control to accommodate how their business works, while keeping routine tasks clear and quick. Every additional option has to justify the attention it asks of them.
It is also a system whose requirements continue to develop as new parks join. Different operators bring different booking arrangements, working habits and customer expectations, testing decisions that seemed settled when fewer parks were involved. A useful request from one park may reveal an improvement that benefits others; a popular feature may need refining as more people use it, exposing awkward steps or unnecessary choices. The platform accumulates experience through the businesses operating within it, and that experience informs what gets built, simplified or reconsidered. Continual development involves the less visible work of absorbing complexity into the system so that owners and operators encounter a more coherent, easier experience.
Across all three projects, the initial design represents the best understanding available at the time. Questions recur, services develop and people use things in ways that were not anticipated. An organisation starts to recognise where explanations are working and where uncertainty remains. The opportunity is to carry that learning back into the website, so that experience improves the service instead of simply increasing the amount of work required to support it.
This accumulated understanding can be thought of as digital memory, although much of it begins away from a screen. It exists in customer conversations, staff experience, correspondence and previously published material. Searches and website activity can contribute, where they are collected responsibly and interpreted with care, but the most useful insight often comes from bringing those sources together. A report may identify a pattern; the person dealing with enquiries may be able to explain it. Neither should automatically be treated as a complete account of what is happening.
That matters because numbers can invite confident conclusions they do not support. Someone leaving a page may have found exactly what they wanted, while a frequently visited page may be attracting people because an answer is difficult to locate elsewhere. Understanding the circumstances takes investigation. It means asking what people were trying to achieve, what they expected to find and whether the website helped them get there. The purpose of gathering insight is to improve decisions, which sometimes requires accepting that an established assumption was wrong.
The resulting changes need not be dramatic. A recurring question might justify a clearer explanation at an earlier point. A service that has grown in importance might deserve greater prominence, while a substantial archive of useful content may need better organisation so that earlier work remains discoverable. In other cases, the learning asks for a more fundamental reconsideration of how the organisation presents itself. A business may find that customers value a different part of its offer, or that the audience it now serves has changed. Continuing to frame everything around the original brief would preserve consistency at the expense of relevance.
Continual evolution also requires restraint. Familiarity helps people use a website, and every new feature or piece of content competes for attention. An insight can justify removing something, simplifying a choice or leaving a successful part of the experience alone. The judgement lies in distinguishing useful development from activity that merely creates the appearance of progress. A website needs someone to take responsibility for those decisions, connecting what the organisation learns with what its visitors experience.
For a business, the consequences extend beyond presentation. When information is unclear, staff spend time explaining it. When an offer is poorly expressed, prospective customers struggle to judge whether it is right for them. When a process feels uncertain, people seek reassurance or postpone the decision. These are ordinary operational problems, some of which a better website can help resolve. Improvements that seem modest on an individual page can become significant when they affect hundreds of visits and the work that follows them.
A website should become more useful with experience, retaining what the organisation has learned while remaining open to a different understanding of its audience. Hannington, Carriage Works and Dogparks will each develop in their own way, and their websites need the attention to develop with them. Launch marks the point at which the work meets the public; its longer-term value depends on how closely anyone listens to what happens next. A few months after the launch email, the person answering the phone may have something worth hearing.
