Frequently asked questions
Discovery uncovers business goals and user needs before design or development starts, through stakeholder interviews, user research, content and technical audits, so that scope, cost and platform decisions (like GovCMS SaaS vs PaaS) are based on evidence rather than assumption. Skipping it tends to surface the same questions later, at higher cost, mid-build.
This scales with project complexity; a straightforward content site might need a short, focused discovery, while a large-scale transformation with multiple data sources and stakeholder groups (of the kind involving extensive discovery and content modelling work) can run considerably longer. The right length is set by how many unknowns genuinely exist, not a fixed template.
Typically a clear articulation of user needs and business goals, a recommended approach (platform, information architecture direction, integration requirements), and enough detail to scope the build phase with confidence — discovery should de-risk the decisions that are expensive to get wrong later, particularly platform and content-model choices.
Insights