How do you rebuild a website in sprints and measure it from day one?
By Nicola Sirchia. Published . 3 minute read.
The short answer
Run a website rebuild as a loop, not a line. Work from one backlog, plan a sprint, design it with the stakeholders, build it with demos, launch, and feed what you learned into the next plan. And decide how you will measure success before the first sprint starts, because analytics added after launch can only tell you what you already missed.
Why does a straight line fail?
Because the business changes while you build. A plan signed off in January describes a company that no longer exists in September. The traditional route also hides the work for months, so the first time leaders see the site is the week before launch, when every change is expensive.
What does the loop look like?
Two moments make the difference. Design reviews, where the stakeholders see the work while it can still change easily. And demos at the end of each build sprint, where they see something that works. Both feed a short list of learnings that goes straight into the next sprint plan.
Why measure before you build?
Because the site will produce data from its first day, and the only question is whether it is the data you need. Before the first sprint I want five answers on the table.
Brands and regions matter more than people expect. A global team may want one dashboard, while each market needs to see its own leads, its own products and its own campaigns. Agree that early, or every market will build its own reporting on the side.
What should the platform and the content get right?
A checklist I use before launch. If a line is not true, it goes into the backlog with an owner.
| The platform | The content |
|---|---|
| People in marketing can publish without IT | Audited before migration: keep, rewrite or retire |
| Components work for every brand and language | Written for the reader, not the org chart |
| Pages load fast on a phone | Built to last, not tied to one campaign |
| Accessible to everyone, to WCAG AA | Adapted for each market, not only translated |
| Stable and secure, with a clear owner | Tagged, so every asset can be found and reused |
| Clear enough for an AI assistant to read and quote |
Where would I start?
- Put every request into one backlog, with the business reason next to it.
- Agree the five measurement answers before the first sprint.
- Book the design reviews and demos in the calendars of the people who matter, for the whole project.
- After launch, keep the loop running. A site that stops changing starts ageing.
Sources
This piece comes from my own work running website and platform projects. It uses no outside data.