{"id":989454,"date":"2026-10-01T10:22:49","date_gmt":"2026-10-01T10:22:49","guid":{"rendered":"https:\/\/dizitalconnect.com\/?p=989454"},"modified":"2026-10-05T08:54:07","modified_gmt":"2026-10-05T08:54:07","slug":"website-rebuild-discovery-sprint","status":"publish","type":"post","link":"https:\/\/dizitalconnect.com\/?p=989454","title":{"rendered":"Website rebuild discovery sprint"},"content":{"rendered":"
\n

The discovery process that prevents a rebuild from being an expensive change of appearance.<\/p>\n\n\n\n

Written for<\/strong> Anyone about to commission a website rebuild, or anyone who has just finished one that changed nothing.<\/p>\n\n\n\n

The bottleneck<\/h3>\n\n\n\n

Rebuilds are commissioned because the site looks dated and delivered against that brief. Six months later traffic is the same, enquiries are the same, and the only measurable change is the invoice. The brief was the problem.<\/p>\n\n\n\n

A rebuild is worth its cost only when it removes a specific constraint. Discovery exists to identify that constraint before anyone opens a design tool.<\/p>\n\n\n\n

Why it happens, five levels down<\/h3>\n\n\n\n
    \n
  1. The new site performs like the old one.<\/strong>Why? It fixed appearance, not the constraint.<\/li>\n\n\n\n
  2. Nobody identified the constraint.<\/strong>Why? The brief was written as a design brief.<\/li>\n\n\n\n
  3. It was scoped by people focused on how it looks.<\/strong>Why? Discovery was compressed into a kickoff call.<\/li>\n\n\n\n
  4. Discovery was treated as overhead.<\/strong>Why? It has no visible output the client can see.<\/li>\n\n\n\n
  5. Discovery is not valued because it produces no artefact.<\/strong>Root cause. Make discovery produce a written roadmap and it stops being cut.<\/li>\n<\/ol>\n\n\n\n

    The diagnostic<\/h3>\n\n\n\n

    Run this before planning any work. It tells you whether this is your constraint or whether something else is.<\/p>\n\n\n\n