Discovery phase
The discovery phase is the initial research and strategy stage of a project, where goals, user needs, the competitive landscape, and technical constraints are defined before any design work begins. Its outcome is a clearly defined project direction based on data, not assumptions. Without it, a team designs a solution to a problem it doesn’t understand.
Projects that skip the discovery phase have a demonstrably higher failure rate. Data from several independent studies confirms it:
- Discovery reduces the risk of failure by 75%: a Nielsen Norman Group survey of 436 UX professionals showed that projects with a discovery phase had only 4 failures compared with 16 for projects without one. Yet only 20% of organizations run discovery on every project (NNGroup – How Well Discovery Phases Are Performed, 2019)
- Projects without preparation run 45% over budget: McKinsey, together with the University of Oxford, analyzed more than 5,400 IT projects and found that large projects run 45% over budget and 7% over schedule on average, while delivering 56% less value than predicted (McKinsey – Delivering Large-Scale IT Projects, 2012)
- Only 31% of projects succeed: in its CHAOS Report 2020, the Standish Group found that 50% of projects exceed their budget or schedule and 19% fail outright (Standish Group – CHAOS Report, 2020)
- Fixing errors after launch costs up to 100× more: a NIST study estimates that software errors cost the US economy $59.5 billion a year, and about a third of that could be eliminated by catching them earlier (NIST – Economic Impacts of Inadequate Software Testing, 2002)
FAQ
What does the discovery phase deliver?
Typical deliverables include personas, a user journey map, a competitive analysis, defined project goals, and a prioritized feature list. NNGroup recommends a discovery team of ideally 3–7 people, including a UX researcher who leads qualitative research into users’ needs and motivations (NNGroup – Discovery Phase Definition).
How long does the discovery phase take?
It depends on the scope of the project, from one week for a smaller website to several weeks for complex products. What matters isn’t the duration but covering every area: user research, business analysis, and technical research. McKinsey points out that every additional year spent on a project increases cost overruns by 15% (McKinsey, 2012).
Do I need discovery for a small website, too?
Yes, just on a smaller scale. Even on simpler projects, discovery helps define who the website is for, what problems it solves, and how it will stand out from the competition. Standish Group data shows that clear requirements are a key success factor regardless of project size.
Sources:
- NNGroup – How Well Discovery Phases Are Performed (2019) – survey of 436 UX professionals on the quality and impact of discovery phases
- McKinsey / University of Oxford – Delivering Large-Scale IT Projects (2012) – analysis of more than 5,400 IT projects
- Standish Group – CHAOS Report (2020) – ongoing study of IT project success
- NIST – Economic Impacts of Inadequate Software Testing (2002) – economic study of the cost of software errors
%201.webp)