Having a website designed, one stage at a time
A website comes together in a natural order. First you work out what it is for, then you try rough versions. A few people use it before everyone does, and once it is live you keep improving it.
The GOV.UK Service Manual, which government digital teams follow, gives those stages names: discovery, alpha, beta and live. A small business having a site made can follow the same order on a much smaller scale.
Discovery: the problem the site solves
The Service Manual starts before anything is built, with the problem that needs solving.
A team may be handed a ready-made answer, and the manual asks them to turn it back into a question. In its own example, a team is asked to build an interactive map showing where its contact centres are. Underneath is a simpler question. How can people find the centre closest to them, for an appointment in person?
The same turn works for a shop or a trade. A request for "a gallery page" might become a question about how a customer can see your past work before they phone you.
Discovery then looks at the people who will use the site. That means what they are trying to get done, and how they go about it today.
Alpha: rough versions, tried out
In alpha, the team tries out different answers by building prototypes and testing ideas.
A prototype might be a sketch with a pen on paper. It might also be working code that behaves like a full, interactive website. Sketches suit a first talk about ideas. The Service Manual finds prototypes built in code better for testing with users, because they are more realistic.
The manual expects most of this work to be thrown away at the end of alpha. It suggests starting with the parts you think will be hardest, so the riskiest ideas get tested first.
Beta: a few people first
Beta takes the best idea from alpha and builds it for real.
It starts as a private beta, with a limited number of invited people using the new site. Their feedback shapes the improvements before it opens to everyone.
Where the new site replaces an old one, the manual keeps the old one running until the new one is live.
Live: still improving
In live, the work turns to running the site and improving it.
The manual asks for each change to be tested with different browsers and devices. Before launch, it also asks for measures in place that show how well the site is doing.
People who use the site, at every stage
The W3C's Web Accessibility Initiative asks projects to involve disabled people and older people early, and all the way through.
It explains that designers and developers who see how people use the web with assistive technology find better ways to make a site work. Its guidance says the result works better for more people, with or without a disability.
Useful links
- How the discovery phase works (GOV.UK Service Manual)
- How the alpha phase works (GOV.UK Service Manual)
- How the beta phase works (GOV.UK Service Manual)
- How the live phase works (GOV.UK Service Manual)
- Making prototypes (GOV.UK Service Manual)
- Involving users in web projects (W3C Web Accessibility Initiative)