What to expect from a website design process.

The process starts before visual design

A studio first needs to understand what the website must change for the business. Discovery should cover the offer, audiences, important customer questions, primary conversion, current performance, technical constraints, stakeholders, budget, and launch deadline. For a redesign, it should also review the existing pages, analytics, search visibility, integrations, and content worth keeping.

The useful output is a shared definition of the problem and the boundaries of the project. You should know what is included, what your team must supply, who approves work, and what would count as an extra request. If those basics are still vague, moving into polished screens usually creates expensive revisions later.

Structure and content come before decoration

The studio should translate the brief into a page map and the main journey through the site. Each page needs a purpose, audience, important proof, and next action. Wireframes or content outlines can then establish hierarchy without asking colour and typography to solve a messaging problem.

Agree who writes, edits, approves, and enters the content. Content is not a final layer to pour into finished layouts: its length, evidence, imagery, and calls to action shape the design. Use the guide to planning the right number of pages to challenge an inflated or incomplete scope.

Design decisions should be reviewed in stages

A sensible design sequence establishes the visual direction and a representative page before expanding the system across every template. Reviews should test whether the design makes the offer understandable, supports mobile use, presents evidence clearly, and gives important actions the right emphasis. Consolidated feedback from one decision-maker keeps the work moving.

During development, approved layouts become responsive pages and working components. Forms, CMS needs, analytics, structured data, integrations, accessibility, performance, and browser behaviour are implemented and checked. Ask whether you will review a staging site and what content must be final before that review.

Testing, launch, and handover are part of the project

Before launch, check the complete website on relevant screen sizes and browsers. Test navigation, forms, validation, confirmation messages, links, metadata, analytics, cookie behaviour where applicable, and any third-party connections. A redesign also needs a URL and redirect plan so valuable pages do not disappear by accident.

The launch plan should name who controls DNS and hosting, who makes the release, how the current site is backed up, and what happens if a critical fault appears. Handover should include the agreed accounts, ownership, documentation, training, and a defined period for correcting defects. Ongoing improvement or maintenance is a separate responsibility unless the proposal says otherwise.

Evaluate the process by its decisions and outputs

• Every stage has an outcome: a brief, page map, approved design, working build, or launch record.
• Responsibilities are visible: content, feedback, access, integrations, and approval all have owners.
• Reviews happen at the right time: strategy is settled before detail and working behaviour is tested before release.
• Changes are controlled: new requests have a clear effect on scope, cost, and timing.
• The finish is defined: acceptance, launch support, ownership, and handover are written down.