Difference between revisions of "February 28, 2024 - Updates, priorities of the week"

From wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
 +
[[FR: 28 février 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]]
 
==Agenda==
 
==Agenda==

Latest revision as of 15:28, 18 March 2024

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

Agenda

1.Updates

2.Roundtable

Notes and action items

Updates

Principal Publisher

  • We have been updating Institutional Landing pages, specifically the “Follow us” page
  • We anticipate a few weeks of work on GCWEB to update the Twitter/X logo on pages and soon after in AEM
  • For AEM it will be released automatically
  • When it’s released, we will contact the community with more details and specifications, either through Slack or this meeting

PCO

  • Presentation at CSPS on prototyping reinforced the need to demonstrate issues rather than just talking about them
  • March is just around the corner
    • If you have any new campaigns, please share them with us so we can promote them
  • Shout-out to ECCC team that ran some A/B tests that made improvements to their content

Roundtable

IRCC - presentation - Explore Immigration Programs  

  • Task Success Survey highlighted some issues users had finding information
  • Our tool Come to Canada limits general exploring, but users wanted to “program shop” to compare immigration stream
  • Our objective was to make it easier for users to find information, so we
    • Changed the tool to ask simple questions
    • Supplied overview based on user answers
    • Used Simple interface

Approach:

  • Used an iterative approach
  • Robust monitoring
  • Implement improvements quickly
  • User centric design principles
    • 50% of users on mobile
    • We removed images to look better on mobile
    • Put in spacing and padding
  • Iterative design
    • Determined nice to haves
    • Only implemented what we could to be ready for launch

Usability testing

  • 8 sessions mix of mobile and desktop
  • Positive feedback on navigation
  • Users unclear on the first question, so we knew we had to change before launch
  • The filters weren’t being used very well, so we removed them
  • For the controls, users weren't using “start over” button, so we made the colour more noticeable

Launch

  • We introduced the changes gradually starting with just a few pages
  • Monitoring:
    • We used a Validated UX survey, we were happy with the score of 3.7/5
    • Also used Page Feedback tool data
    • Adobe Analytics
  • 163,691 users, 69% of visitors clicked on the start tool at least once

Next Steps

  • Looking back to the “nice to have” to see how to make improvements
  • We used simplicity which helped us be successful
  • We continue to make updates
  • One update at a time, then push it live, then monitor

QUESTIONS

Q: How did you get to be an empowered team?

A: Support from management.

Manager: We built the team, and the team had demonstrated success with past projects. The team also had buy-in from upper management for user-centric design.

Comment:

IRCC has a culture of answers not information, due the nature of their work and the amount of questions that they get. Therefore there’s a focus on providing service to users. This design follows that culture.

Q: Is this developing into a new overall system replacing C2C? How did you find the approval process?

A: The approval process was long due to delays, but not hard.

To replace C2C would be very complicated, as it ties into many accounts and systems. But eventually, yes we hope this system will replace C2C.

Q: Did you specifically make this new tool look different from C2C?

A: Yes, we wanted to differentiate it for users, that it was a place to get quick help, and not so filled with long informational content.

Q: Did you check the code to make sure the html specifications are proper for accessibility? I ran it through a checker and found some errors.

A: Yes we did run some checkers, we have seen some small errors to fix.

Reply: Yes it would be great to connect to discuss how to fix these kind of problems, as my team has encountered them as well

General updates:

WAGE

IRCC

  • Launched the new Sudan PR pathway yesterday and working with GAC to update the Canada’s response to the crisis page on their side
  • Going to start chats in the coming weeks about how we can ensure we’ve got clear cross linked info for these crises across departments
  • Waiting on a major announcement tomorrow that will have large impacts to the web content around visit

NRCan

  • Removing some Ukraine content

RCMP

NRCAN

  • We’re adopting Power BI for data visualization
  • We’re having accessibility issues.
  • Has any other department used it and mitigated the problems?
  • Hoping to see if anyone has the issue and interested in working on it.

Discussion about PowerBI

  • ISC -We’ve also been having issues, would be interested to work on this
  • Issues with judging if content is WCAG compliant, who really decides if content actually is compliant
  • DTO: if a team is pushing to have content labeled compliant…they have to accept that they will take responsibility for any risk or consequences
  • ISC: We have been using the system that groups have to have content approve for accessibility compliance at the ADM
  • There's a PowerBI Community of Practice (On teams/ GCExchange) that might be helpful
  • It was resolved that the participants interested in this issue would connect for meeting and possibly to setup a working group

Canadian Heritage

Sharepoint

ISED

Theme-wise we have identified a couple of places to add FPM content on Canada.ca, mainly:

We are already planning to post a feature to Doing business with government - Canada.ca for PSPC

Retrieved from "https://wiki.gccollab.ca/index.php?title=February_28,_2024_-_Updates,_priorities_of_the_week&oldid=117220"