Difference between revisions of "March 20, 2024 - Updates, priorities of the week"

From wiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
[[FR: 20 mars 2024 - Mises à jour, les priorités de la semaine]]
 
Back to [[GC Web Priorities Meetings - Réunions des Priorités Web du GC]]
 
Back to [[GC Web Priorities Meetings - Réunions des Priorités Web du GC]]
 
==Meeting information==
 
==Meeting information==

Revision as of 10:27, 17 April 2024

Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC

Meeting information

Agenda

1. Updates

2. Roundtable

Notes and action items

Updates

PCO

  • We’re getting questions about budget, no info yet, will share when we know
  • Budget is April 17
  • Adobe Analytics monthly meeting this morning, check the GCPEDIA page if you’re interested in joining up for next month

Roundtable

CRA

  • If you have migrated your Intranet to Sharepoint, please contact gabriel.portillo@cra-arc.gc.ca
  • Also looking for anyone who can share training experience for Drupal

Public Safety

  • Get Prepared - We anticipate publishing updated content from the first set of 10 hazards that were developed with partner departments in the coming weeks in advance of EP Week (May 5th)

Health Canada - Recalls and Safety Alerts - Updated UX test

  • Website about recalls and safety alerts
  • Goals and objectives, to determine if changes made were helping users
  • Users had to complete 14 tasks
  • Old study: Moderated
    • All tasks were in random order
  • New study:
    • Unmoderated
  • We used UserZoom
  • Findings:
    • We scored users scored from 1-5
    • Found this system better than pass/fail
  • Task performance Old vs. New
    • User success increased roughly by 22%
    • Users got frustrated with task 7, they said it was not user friendly
    • Comparing task 7 and 14, the Transport Canada system, users preferred the TC search system
    • Task 1, find if there’s issues with Primidone drug, there seems to be a problem with metadata so that GOC results appeared low on the page
    • Users saw filters as an obstacle rather than a tool
  • Filtering issues
    • We are asking users to filter based on categories they didn’t know
    • Additionally, on mobile, users had to scroll through several screens to navigate through all the filters
  • Search issues:
    • The search was collecting too many results based on irrelevant search terms
    • Users are more willing to wait when they see a loading animation
    • If nothing is happening, they don’t know if the search has stopped working
    • Users didn’t know when to stop searching
    • Action items were at the bottom of the page
  • Mobile design issues:
    • We had to make sure that users on mobile didn’t have to scroll horizontally
    • Have to take into account how users hold their phones
  • Lessons learned:
    • A bad system can make a user lose faith after just one bad experience, they will use a different system like Google
    • We have made a prototype which is available for testing
    • Users don’t know if they’re searching for something that exists or not
      • If the result does show up right away, they will assume there’s no recall

QUESTIONS

Q: The responsive table on Canada.ca was designed so that you don’t have to scroll sideways, but it’s stayed in Beta.

A: Transport Canada has a good internal search, but not really accessible from google. The Health Canada data has been accessible in Google. We are based on a Drupal platform and haven’t to date been able to implement the responsive table, but we are working on it right now.

Q: Really great presentation. Two points: It seemed that the alerts looked permanent, but they should be temporary. The health icon was not easily identifiable.

A: Thank you.

Q: How did you like UserZoomGo?

A: Actually the company has been bought out, so stay tuned to hear about other products.

DTO:

  • This is a good issue for everyone to share their experiences in Slack, because companies change rapidly, so the landscape is constantly evolving rapidly

Comments on research tools:

  • Participants mentioned it would be helpful to assemble a list of approved tools and the justifications teams used to get approval
  • A user mentioned it could be a good idea if Principle Publisher had a license for a research tool similar to Adobe Analytics, for use by the whole community