Turn an outdated website into a clearer digital experience

A redesign is more than replacing colours or choosing a newer typeface. It examines how the site presents information, guides visitors and supports important actions, then reshapes those elements into a coherent experience. Work may include hierarchy, calls to action, reusable components and clearer content.

Redesign and redevelopment are related but different. Redesign focuses on visual language, interaction and user experience; redevelopment may change the CMS, templates, integrations, data structure or code. Defining that boundary prevents a visual refresh being mistaken for a technical rebuild when the foundations are limiting the site.

• Visual direction
• UX and information structure
• Clear scope between design and code

Redesign is useful when a site is difficult to navigate, visually inconsistent, out of step with the organisation, or unclear about what visitors should do next. It can also help when services have accumulated without structure, content has become repetitive, or the website no longer fits its audience.

The starting point is an understanding of users, priorities and friction in the existing experience. Reviewing representative pages and journeys helps separate symptoms from causes. Some sites need focused improvements; others need a broader restructure first.

• Navigation and content audits
• Audience and task clarity
• Focused or site-wide scope

A redesign may cover the visual system, page templates, responsive layouts, navigation, forms, calls to action and content grouping. It can establish practical rules for typography, colour, spacing, imagery, buttons and reusable sections. For a portfolio-website category, for example, that may mean a clear way for visitors to explore work, background and contact information.

The structure depends on the website rather than a fixed package. Work may focus on a page family, a new homepage and navigation model, or templates for a wider refresh. Content guidance can be included; extensive copywriting, photography, illustration or migration should be scoped separately.

• Responsive page templates
• Design-system foundations
• Content and conversion pathways

Good redesign helps people recognise where they are, understand a page and choose a sensible next action. That means meaningful headings, readable text, visible focus states, useful error messages and consistent navigation. Accessibility belongs alongside aesthetics, including contrast, keyboard interaction, semantics and layouts that remain understandable when text size changes.

Usability decisions should be grounded in the real content the site carries. A polished screen can still fail if labels are vague, menus are crowded or important information is buried. Content hierarchy and representative journeys test whether the interface communicates clearly rather than acting as decorative screens.

• Accessible interaction patterns
• Readable hierarchy
• Journey-focused design decisions

A redesign must account for its implementation environment. We consider the platform, CMS, hosting, analytics, forms, search, third-party services and integrations. If those foundations make the experience difficult to maintain, redevelopment can address relevant templates, components or code.

Mobile layouts are planned as a core experience, not a late adjustment. Performance is also distinct from aesthetic improvement: image handling, scripts, caching, fonts and page weight may need technical attention. Faster delivery and cleaner design are separate decisions.

• Mobile-first considerations
• CMS and integration awareness
• Separate performance decisions

An existing website contains more than visible pages. It may have useful URLs, search visibility, structured content, forms, editorial routines and integrations. Before rebuilding, we can identify what should move, what needs redirecting and where the system creates avoidable work.

Maintenance is different from a full rebuild. Maintenance keeps an existing site functioning through updates, fixes and small improvements; a rebuild changes its implementation or structure more deeply. Some projects need front-end changes; others need a new platform, data model or publishing workflow.

• URL and content continuity
• Migration considerations
• Maintenance versus rebuilding

A typical project begins with goals, constraints and a review of the current website. It can then move through information architecture, content priorities, visual direction, key page designs, responsive states and implementation planning. The sequence can adapt while decisions limit avoidable rework.

Before implementation, we clarify included pages, templates, content tasks, integrations, environments and approvals. During build, designs are checked against live content and technical behaviour. Launch preparation can cover quality checks and handover, while maintenance or performance optimisation can be discussed as separate needs.

• Discovery and prioritisation
• Design-to-build collaboration
• Explicit deliverables and responsibilities