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

From wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
[[FR: 13 mars 2024 - Mises à jour, les priorités de le 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==
Line 14: Line 15:
 
*Thanks to the teams that supported updating the canada.ca Media contacts page. We're almost wrapped up. Next review in August.
 
*Thanks to the teams that supported updating the canada.ca Media contacts page. We're almost wrapped up. Next review in August.
  
 
+
'''PowerBI meeting - Fiona Currie - AAFC'''
 
 
PowerBI meeting - Fiona Currie - AAFC
 
  
 
* People having difficulties with clients wanting to post PowerBI content on website
 
* People having difficulties with clients wanting to post PowerBI content on website
Line 28: Line 27:
 
*** Good example, Public Health made some good Covid-19 dashboards
 
*** Good example, Public Health made some good Covid-19 dashboards
 
** Next meeting April 15
 
** Next meeting April 15
** Sign up for the meeting: [[/events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd|https://events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd]]
+
** Sign up for the meeting: https://events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd
** Google docs link: [[/docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#heading%3Dh.alxcm7d7x5d8|https://docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#heading=h.alxcm7d7x5d8]]
+
** Google docs link: https://docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#heading=h.alxcm7d7x5d8
  
Principal Publisher - UTM campaign report - Andrew Lau
+
'''Principal Publisher - UTM campaign report - Andrew Lau'''
  
 
* Concept of report is that it should be “plug and play” for everyone
 
* Concept of report is that it should be “plug and play” for everyone
Line 45: Line 44:
 
* We’ve also tried to make report user friendly by defining terms
 
* We’ve also tried to make report user friendly by defining terms
 
* If you use Page Feedback tool, this is incorporated into your Adobe Analytics data
 
* If you use Page Feedback tool, this is incorporated into your Adobe Analytics data
* You can reach us for Adobe Analytics questions at: [[Mailto:GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca|GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca]] or submit a service desk ticket ([[/requestform.portal.gc.ca/tickets.html|http://requestform.portal.gc.ca/tickets.html]])
+
* You can reach us for Adobe Analytics questions at: [Mailto:GCmailto:ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca] or submit a service desk ticket (http://requestform.portal.gc.ca/tickets.html)
  
Questions
+
'''Questions'''
  
 
Q: Are there still office hours for any questions about Adobe Analytics?
 
Q: Are there still office hours for any questions about Adobe Analytics?
  
A: Yes, you can arrange to meet with an AA expert for any questions you have. Here’s the link: [[/www.gcpedia.gc.ca/wiki/Adobe Analytics Office Hours|https://www.gcpedia.gc.ca/wiki/Adobe_Analytics_Office_Hours]]
+
A: Yes, you can arrange to meet with an AA expert for any questions you have. Here’s the link: https://www.gcpedia.gc.ca/wiki/Adobe_Analytics_Office_Hours  
  
DTO - Lisa Fast - Alerts
+
'''[[:en:images/5/53/Alert_study_report-EN_to_post.pptx|DTO - Lisa Fast - Alerts]]'''
  
 
* Study goal was to measure alert styling decisions to create clearer guidance
 
* Study goal was to measure alert styling decisions to create clearer guidance
Line 68: Line 67:
 
** Tell web advisors to warn their clients overuse of alerts have negative impact on web users
 
** Tell web advisors to warn their clients overuse of alerts have negative impact on web users
  
Comments:
+
'''Comments:'''
  
 
DTO: We should be telling comms advisers how long to keep alerts posted.  
 
DTO: We should be telling comms advisers how long to keep alerts posted.  
Line 78: Line 77:
 
Other ideas: Interactive questions are very effective.  
 
Other ideas: Interactive questions are very effective.  
  
Chat summary
+
'''Chat summary'''
  
 
* On the topic of out of date browsers: I wonder if there could be a reusable content snippet with language around browser compatibility that could be shown if certain criteria are met? We piloted this for location detection during COVID on the vaccine page, if I remember correctly.  
 
* On the topic of out of date browsers: I wonder if there could be a reusable content snippet with language around browser compatibility that could be shown if certain criteria are met? We piloted this for location detection during COVID on the vaccine page, if I remember correctly.  
Line 86: Line 85:
 
* Question to ask your clients when they want an alert: When will this be taken down? Alerts should be time sensitive to prevent overuse
 
* Question to ask your clients when they want an alert: When will this be taken down? Alerts should be time sensitive to prevent overuse
  
* Another option is to use colour for emphasis. [[/wet-boew.github.io/wet-boew-styleguide/design/colour-en.html#basic|https://wet-boew.github.io/wet-boew-styleguide/design/colour-en.html#basic]]
+
* Another option is to use colour for emphasis. https://wet-boew.github.io/wet-boew-styleguide/design/colour-en.html#basic
  
 
Anything is better than a paragraph of bolded text.  
 
Anything is better than a paragraph of bolded text.  
  
 
* Comment: “If everything is important, nothing is important”
 
* Comment: “If everything is important, nothing is important”

Latest revision as of 16:56, 18 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

Digital Transformation Office (DTO) updates

  • We have reviewed the Audit of Templates and Patterns and will be bringing it back to this table soon to review before officially decommissioning anything.

Roundtable

PCO

  • Thanks to the teams that supported updating the canada.ca Media contacts page. We're almost wrapped up. Next review in August.

PowerBI meeting - Fiona Currie - AAFC

Principal Publisher - UTM campaign report - Andrew Lau

  • Concept of report is that it should be “plug and play” for everyone
  • Access by:
    • Logging into your Adobe Analytics and go to templates
    • If you don’t have AA, go to our GCPEDIA page, and find Workspace Templates, this version is good if you want a quick overview instead of more details
  • In AA, you can find data on users broken down by criteria such as
    • geographic area
    • mobile vs desktop
    • performance of landing page
    • time users are staying on campaign pages
  • We’ve also tried to make report user friendly by defining terms
  • If you use Page Feedback tool, this is incorporated into your Adobe Analytics data
  • You can reach us for Adobe Analytics questions at: GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca or submit a service desk ticket (http://requestform.portal.gc.ca/tickets.html)

Questions

Q: Are there still office hours for any questions about Adobe Analytics?

A: Yes, you can arrange to meet with an AA expert for any questions you have. Here’s the link: https://www.gcpedia.gc.ca/wiki/Adobe_Analytics_Office_Hours

DTO - Lisa Fast - Alerts

  • Study goal was to measure alert styling decisions to create clearer guidance
  • Alert use is inconsistent across GOC websites
  • Testing shows that alerts can distract users and overuse also reduces their value
  • Looked at current guidance
  • Behavioral survey for GC Web community, which showed disagreement on how people would use alerts
  • Next steps:
    • Update alert guidance with example from study
    • Add keywords for each style
    • Add ideas for alternatives to alert styles, so that users have more options
    • Provide guidance so users can be more consistent
    • Use more A/B testing to understand impact of changes
    • Tell web advisors to warn their clients overuse of alerts have negative impact on web users

Comments:

DTO: We should be telling comms advisers how long to keep alerts posted.

Q: ESDC: Clients often ask for alerts, they think it will make content “pop”. What about using a well?

A: Lisa F: Bars are a better solution than wells - we removed the well on topic pages for Most requested, and replaced them with a bar, because eye tracking and analytics showed people weren’t looking at the well. If clients want their info to ‘pop’, it should be redesigned rather than added.  

Other ideas: Interactive questions are very effective.

Chat summary

  • On the topic of out of date browsers: I wonder if there could be a reusable content snippet with language around browser compatibility that could be shown if certain criteria are met? We piloted this for location detection during COVID on the vaccine page, if I remember correctly.
  • For a warning to display for only out of date browsers, would require custom scripting. We requested that DTO/PP create a GCWeb component that could be added to identify out of date browsers based on lacking the functions for the components needed to run them.
  • Question to ask your clients when they want an alert: When will this be taken down? Alerts should be time sensitive to prevent overuse

Anything is better than a paragraph of bolded text.  

  • Comment: “If everything is important, nothing is important”