In practice, discovery for a government digital services project starts by clarifying who the users are, what problem they face, and what constraints — governance, accessibility, security, and publishing workflows — shape the solution. We map current services and data flows, review how content would be published and updated, and identify key dependencies and risks. We then test ideas through small, iterative design and technical exploration, focusing on an evidence-led approach and user-centered outcomes. The team considers the technology landscape (for example GovCMS, Drupal, or other platforms) and plans incremental delivery to reduce risk and move toward a usable public service.
Public Q&A
What does a typical discovery phase look like for a government digital project?
Useful next steps
Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.
Related Topics
