• Adopt an agile methodology
    • Use a multi-disciplinary team: Consider tools and techniques based on agile values and principles. Engage a multidisciplinary team to understand the whole problem and create an effective solution. Monitor time and effort expended to understand and refine whole-of-life investment costs from the outset. 
    Off
  • Guidance to have a clear intent

  • Understand the problems your service will solve

    Understand your current digital landscape and the problems or gaps your service will solve: 

    • Conduct needs assessments and collect qualitative and quantitative data through surveys, interviews and focus groups to understand user experiences and challenges.
    • Clarify the problem that needs to be addressed by creating user journey maps to visualise the user experience. Include pain points, problems that slow or halt progress and areas of confusion. 
    • Gather insights into challenges by engaging with a diverse range of stakeholders, including users, staff and community organisations.
    • Periodically review and analyse trends in user behaviour and service performance to identify recurring problems and new challenges. 
    Off
  • Understand government initiatives that address the problem

    Research and identify existing programs or initiatives that address the problem. Leverage these initiatives to enhance service delivery or fill the gaps. Use methods or tools such as:

    • Review government policies and existing initiatives and map the problem to relevant strategic objectives and priorities.
    • Collaborate with other government agencies and departments with similar issues to facilitate resource sharing, knowledge exchange and coordinate efforts. 
    • Engage with stakeholders involved in related government initiatives to gain insights into government approaches and successes. 
    • Periodically review and update strategic objectives, ensure plans are flexible in response to new information, the changing landscape and user needs.
    Off
  • Document your findings

    Document your findings and recommendations to apply criterion 1:

    • Develop clear problem statements that articulate the issues identified. This will communicate the problem to stakeholders and set a focused direction for efforts.
    • Make sure the data is collected and documented in a centralised knowledge repository. 
    Off
  • The supporting standards

  • Understand the users of the service
    • Listen carefully for implicit and explicit needs: During user research, discuss their daily lives and observe their real-world actions to contextualise their needs. Use a discussion guide to capture all aspects of their experience. While some needs or pain points will be stated explicitly, pay attention to small or superfluous details to recognise the implicit ones. Use at least 2 methods of user research to make sure what they say matches what they do. For example, open-ended interviews and observing users completing relevant tasks.
    • Begin with pain points: Identify and address the most common pain points that the service should address. Prioritise them by most impactful; this isn’t necessarily the number of users affected. Adopt continuous improvement to address pain points that emerge after launch or upgrades.
    • Observe usage patterns: Use various data sources to identify how often different users use the service. Stress test any solutions for pain points along task journeys and assess load-bearing capacity during peak periods.
    • Map experiences: Use visual aids to make sure the breadth of user interactions are captured and that the team works from a shared understanding. Build, test and refine journey maps and job stories. This will help to understand the end-to-end user journeys and behind-the-scenes processes. It will also reduce unintentional duplication and support agencies to communicate findings.
    Off
  • Conduct user research
    • Test any assumptions: Validate assumptions made in Criterion 1 (‘Have a clear intent’). Qualitative user research conducted directly with people who may be impacted by the service will provide agencies with either confirmation that they are on the right track, or that they are solving the wrong problem and need to adapt their approach.
    • Gather different perspectives: Undertake ethical and inclusive user research to capture a breadth of needs and capabilities. Zoom out and consider how the digital service interacts with the agency’s wider methods of service delivery. It is helpful to zoom in and out of the problem space to observe the different perspectives and impacts of the service being designed, and to explore how the problem may manifest at macro and micro levels.
    Off
  • Test and validate designs
    • Embed co-design: Where appropriate, use co-design to involve users and stakeholders and demonstrate transparent, equitable decision making. Avoid tokenism by meeting people’s physical, cultural and psychological safety needs in consultations. Maintain ongoing user engagement to keep the service fit for purpose and address changing needs over the course of people’s lives.
    • Engage designers: Make sure the team has the expertise to capture and interpret useful information from users’ personal experiences. Use service designers and user experience (UX) designers to conduct user research, map experiences and design the service to meet and surpass the needs of all users.
    Off
  • Guidance to know your user

  • Understand who uses your service

    Understand who uses your service and establish what their needs are. Use methods or tools such as:

    • Regularly collect qualitative and quantitative data and user feedback from user research surveys, usability testing, interviews and focus groups. 
    • Use web analytics and user data to verify current users, including demographics, behaviours and usage patterns.
    • Create user personas representing different segments of the user base to  visualise the user and understand their needs.
    Off
  • Address pain points and negative feedback

    Draw on feedback, data and insights to highlight the needs and challenges of users. Use methods or tools such as:

    • Conduct a thorough analysis of any identified pain points or negative feedback to understand the root cause.
    • Use an iterative design process, make incremental changes based on feedback and test these changes with users to assess their effectiveness.
    • Prioritise pain points that have the most significant impact on user experience and ensure resources are allocated effectively.
    Off
  • Identify patterns and trends in usage

    Identify usage patterns and trends to paint a picture of the users of the service. Use methods or tools such as:

    • Use analytics to identify usage patterns, such as peak usage times, common user paths and drop-off points.
    • Prioritise features that align with identified usage patterns and user needs to ensure that resources are focused on what users value most.
    • Continuously monitor usage data after implementing changes and adjust strategies as necessary. This will make sure improvements meet user needs.
    • Combine user research efforts across the DX Policy and its standards to reduce duplication and the cost of research.
    Off
  • Document your findings

    Document findings and recommendations to apply criterion 2:

    • Collect qualitative and quantitative data through surveys, interviews and focus groups to understand user needs and experiences.
    • Regularly collect feedback and analyse pain points to identify root causes, use an iterative design process to implement and test incremental changes.
    • Prioritise the pain points that have the most significant impact on user experience and allocate resources effectively.  Make sure the data is collected and documented in a centralised knowledge repository. 
    Off
  • Understand the diversity of users
    • Conduct segmented user research: Go broad and deep on the learnings from Criterion 2 (‘Know your user’) by conducting targeted and ethical user research. Make sure the service captures and responds to unique circumstances and needs.
    • Use data-driven insights: Collect and analyse information about different users to understand the different barriers they might experience when using the service. Eliminate these barriers through design and validate the effectiveness of solutions with real-world users.
    • Include non-digital users: Test how easily users can access the service to understand the impact of the digital divide. Make sure those users have a voice in decisions affecting them. Design omni-channel pathways that cater to non-digital access and experiences that some users rely on to access government services.
    • Form partnerships: Some types of users are under-represented in research, may be difficult to reach or require different or tailored engagement approaches. If this is the case, collaborate with other agencies, community groups or the private and not-for-profit sector to reach them.
    Off
  • Comply with legislation and standards
    • Use existing standards as a baseline: Comply with legislation and standards to make sure the service uses best practice and meets the expectations for government services. Consider any specific legislation or policies relevant to the service as well as the Disability Discrimination Act 1992, the Disability Services and Inclusion Act 2023, the latest version of the Web Content Accessibility Guidelines (WCAG) and the Australian Government Style Manual.
    • Offer content in alternate formats: Offer content in different mediums, such as text, images and audio and segment long documents or tutorials into chunks. Provide human-validated multilingual support for critical information. Evaluate the service with users who depend on assistive technology, integrate their feedback and resolve pain points through design.
    • Consider different platforms: Comprehensively test the service across devices and platforms users may access it through prior to launch. Anticipate how content will appear on different devices in designs and assess whether platform-specific interfaces support or fail to meet accessibility standards.
    • Design for affordability and connectivity: Design and develop the service to use as little bandwidth and data as possible. Where it suits the service, make it cache for offline access or offer downloadable, print-friendly versions of critical content.
    • Use accessible language: Use plain language in both the content and user interface to make sure the service is usable by all. Replace niche terminology or jargon with widely understood terms. Always adhere to the Australian Government Style Manual and plain language guidance.
    Off
  • Implement a feedback mechanism
    • Incorporate feedback: Give users the ability to provide feedback, report issues and suggest service improvements. Act promptly on feedback and provide timely, transparent responses describing how it’s being actioned.
    • Raise awareness of the service: Plan an ongoing awareness campaign and deploy it across a variety of channels to reach users. Consider training frontline staff so they can inform, suggest or demonstrate the service to people.
    Off
  • Guidance to leave no one behind

Connect with the digital community

Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.