Discovery starts by framing the problem with you: who your users are, what tasks they need to complete, and the current environment. We map the stakeholders, constraints, and success metrics so everyone is aligned before any design or build begins. We gather evidence through user research, prototype testing, and technical reviews of existing systems to surface real pain points and opportunities. We also outline content structures, integrations, governance, and accessibility needs to ensure the future portal fits your tech context and policy requirements, and we emphasise discovery-first, evidence-driven, and iterative delivery. The output is a plan for incremental delivery, including user journeys, information architecture, and a design-system approach aligned with Drupal patterns. We factor in multilingual and accessibility considerations from the start, so the project supports inclusive, accessible experiences and practical, evidence-based scoping rather than guesswork.
Public Q&A
What does the discovery phase look like for a Web Apps & Portals 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 visual examples
Web Applications & Customer PortalsA customer using a secure modern self-service portal across laptop and smartphone while a product te…
Visual exampleLaptop screen showing Australian Government Health Workforce Locator webpage
Visual exampleLaptop screen showing map search results for a specific address
Customer Portal Service ActionA user completing a practical task in a secure customer portal—such as updating details or managing …
