Digital UX Checklist
-
Ó: An Roinn Caiteachais Phoiblí, Seachadta ar an bPlean Forbartha Náisiúnta, agus Athchóirithe
- Foilsithe: 16 Nollaig 2022
- An t-eolas is déanaí: 12 Aibreán 2025
- Step one: Learn from others
- Step two: Research the users
- Step three: Create user stories
- Step four: Build a prototype
- Step five: Content review
- Step six: User-test your prototype
- Step seven: Success metrics
- Step eight: Accessibility audit
| Step | Completed |
| 1. Competitor research | ✓/ x |
| 2. User research | ✓/ x |
| 3. User stories | ✓/ x |
| 4. Prototypes | ✓/ x |
| 5. Content audit | ✓/ x |
| 6. Prototype testing | ✓/ x |
| 7. Success metrics | ✓/ x |
| 8. Accessibility audit | ✓/ x |
Step one: Learn from others
Look at similar digital products to see how others approach them. This is also known as 'competitor analysis'. Digital products by the governments of the UK, USA (18f), New Zealand, Australia and Estonia are good starting points. Make a record of your competitor research.
Step two: Research the users
It is important to research the site’s users before developers begin writing code.
User research helps you find out:
- who your users are (both internal and external)
- what they are trying to do (this will reveal user needs)
- the easiest way to help users to achieve their goals
It is a good idea to involve developers in the early stages of the design process. In this way, everyone can gain an understanding of the goals and requirements of the project.
User research methods include:
- user interviews
- surveys/questionnaires
- data analysis (patterns in feedback, Google analytics, system analytics, Semrush and so on …)
Use any one — or a combination — of user research methods.
Make a record of your user research feedback.
Step three: Create user stories
User stories
Look at the most popular pages and services on your current application and create 'user stories' for each one. A user story is a simple description of a goal or need, from the point of view of the person who will use the final product.
For example:
- As a farmer
- I want to be notified when the Basic Payment Scheme deadline is approaching
- So that I get paid on time
Creating user stories ensures the focus stays on the user, not on the technical details. This allows you to research and test the best way to meet your users’ needs.
Each user story follows the same three-point format. The story is complete when you have addressed each point.
User story format:
- As someone who…
- I want to …
- So that I can …
Another example:
- As a wheelchair user
- I want to apply for a parking permit online
- So that I can park my car in designated parking spaces
Make a record of each user story that you create.
Step four: Build a prototype
A prototype is a mock-up of your site. It can save time and money by detecting design problems early.
Paper prototypes
Sketch out a prototype of the design on paper first. Include the user journey - what people need to do to achieve a goal. Paper prototypes let you explore ideas before advanced design work begins.
The government design system
The Office of the Government Chief Information Officer (OGCIO) has developed a design system that should be applied to all government digital products.
Creators of digital products can access a library of agreed styles and functions for headers, footers, fonts, buttons, tables and so on. Consistent use of this design system will help to ensure a high degree of accessibility and foster a sense of trust and familiarity for the user, while also saving on developer time.
Wireframes
A wireframe is a diagram (or collection of diagrams) showing the structure of a site and its user interface (UI).
You can create wireframes on platforms such as Figma.
Once you have created detailed wireframes, you can begin to test the new designs. At this stage, draw on feedback recorded thus far and adapt your design to better suit its users.
More information on creating a basic wireframe can be found here
Step five: Content review
Carry out a quality and clarity check on your content, and rework it where necessary. Remove all out-of-date content and use analytics tools to see which pages are highly trafficked and which pages get no traffic. Apply the principles of plain English and make use of online readability tools.
Gather feedback on your improved content and make further changes where necessary.
Step six: User-test your prototype
Test the prototype on the people who will use the system. Ask them to carry out some of the most popular tasks based on the user needs and user journeys you have already identified. You should employ a variety of tests, including ease-of-use tests, talk-aloud tests, timed-task tests and satisfaction surveys.
Make a record of these tests and of user feedback and where necessary, change your design and content according to this feedback.
Step seven: Success metrics
Create a list of things that will prove that the site is doing its job.
Some examples of success:
- user stories can be successfully completed
- costs-per-transaction are reduced
- user satisfaction ratings improve
- phone calls to helplines are reduced
- conversion rates are improved (for example, more people completing a form)
Step eight: Accessibility audit
Public bodies in Ireland must ensure their websites and apps are accessible to all, including people with disabilities, to follow the EU Web Accessibility Directive. Under this directive, you must conduct an accessibility audit.
Make changes to your design based on this audit and any feedback from users.