Difference between revisions of "May 22, 2024 - Updates, priorities of the week"

From wiki
Jump to navigation Jump to search
(Created page with "Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC ==Meeting information== ===Agenda=== 1. Updates 2. Roundtable =Notes and action item= ===Updates==...")
 
Line 8: Line 8:
 
===Updates===
 
===Updates===
 
'''PCO'''
 
'''PCO'''
−
*If you have any material you want to promote in the home page features, please let us know
 
−
*Thanks for the organizers of PowerBI meeting last week
 
−
*Thanks to the community for all your work
 
−
'''AAFC'''
 
−
*PowerBI meetings went well
 
−
*The Health Canada team have twenty people working on data visualization
 
−
*Discussed the coding side and analytics
 
−
*Takeaways:
 
−
**B3 is not necessarily the “magic bullet” for accessibility for data visualization
 
−
**You have to do a lot of work to make it accessible
 
−
**They get a lot of students to work on it, the skills can be learned in a couple of weeks
 
−
*Notes from the meeting: https://docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#bookmark=id.qrznm25qpjk0
 
−
'''[[:en:images/c/c0/PP-SC-GC_Web_Priorities_Updated_2024.eng_for_posting.pptx|Presentation - Tanya Gagnon - Canada.ca Re-Procurement Project]]'''
 
−
*Managed Web Service (MWS) platform is the core technology
 
−
*Three elements:
 
−
**Content management
 
−
**Cloud hosting
 
−
**Cybersecurity and content distribution network
 
−
*Currently one provider for all 3 elements, which is Adobe
 
−
*Contract will expire in six years (March 2029) with no extension years possible
 
−
*Six years is actually not that far away to put the new contract in place
 
−
*Goals for next contract:
 
−
**To continue service with no interruptions
 
−
**Providing excellent customer service
 
−
**That the next platform meets evolving digital needs
 
−
*Some steps on the roadmap to get to next contract:
 
−
**Engaging PSPC to develop procurement strategy
 
−
**Public user survey
 
−
**Request for information for industry input
 
−
*We’ve shared our work so far with Web Executive Board, GCWP and working groups as needed
 
−
*In 2021, DTO conducted a brainstorming session with Web Executive Board
 
−
*DTO also conducted a survey to see what people thought was needed for next platform
 
−
*Business capabilities
 
−
**One of the most important is being able to integrate well into broader ecosystem
 
−
**Better personalization based on user
 
−
**Better analytics
 
−
**Eligibility for program calculators
 
−
**Ability to connect with AI chatbots
 
−
**More supportive of accessibility
 
−
**Support for Indigenous languages
 
−
**Capability for hosting Protected B content
 
−
*We ran a Industry Request for Information (RFI), helps to ensure a successful bidding process, it RFI closes this Friday
 
−
We want to make sure that the new system will be able to support any future technology needs, like enhanced sign-in.
 
  
−
'''More information from the chat:'''
+
* Thanks for sending in your May promos
−
*Canada.ca currently focuses on Information as a Service which does not require authentication. We are still evaluating future state capabilities and what that represents.  We do know that ESDC through BDM is procuring a new Access Management System.  Our objective is to ensure that the new Canada.ca platform has the levers to permit future state capabilities.
+
* Thanks to the Principal Publisher analytics team that ran a learning activity on search terms today, check out the [[/www.youtube.com/@AnalyticsServices|Youtube video]]
−
'''Qː''' In the RFI, did you ask about analytics capabilities?
 
  
−
'''A:''' Yes we did, and also CDS gave us some input about analytics considerations such as AI.
+
[[Mailto:lana.stewart@cds-snc.ca|Lana Stewart]] DTO - Task Success Survey Q4 and 2023-24 Results
  
−
'''Q:''' Curious about AI capabilities.
+
* Q4 looks similar to Q3, but there were changes in the types of tasks
 +
* Going forward might be good to report a “basket of tasks” each quarter instead of changing each quarter
 +
* Top 25 taks, mostly successful, may be time to increase the success rate marker higher
 +
* Repeated tasks have the highest success rate
 +
* Lowest scoring tasks are those related to an account, where you have to sign in, this is having negative impact
 +
* Annual results
 +
** Just over 500,000 respondents
 +
** 71% said they could complete their tasks
 +
** Again, repeated tasks are the most successful
 +
* What’s next for the survey
 +
** To select core common tasks to report on each quarter
 +
** More qualitative feedback
 +
** Call out for TSS case studies, how is it working for you?
  
−
'''A:''' We asked companies how they could support AI requirements we might have. We are looking forward to what industry will tell us.
+
Q & A
  
−
'''Q:''' In terms of archiving, one of the other functions at CRA is looking at ways to be able to remove the need for single page guides (HTML and PDF) but still leverage the use of multiple web pages...so a way to build content that can be both optimized for web, but could also degrade to a simple single page (print or save as PDF friendly)....that could be an important function.
+
Q:Is there a recommended stat significance checker?
 +
 
 +
A: Yes, here’s what I use: <nowiki>https://docs.google.com/spreadsheets/d/1I-pkCshlwAmHp0YHfwHqAHDZQEvFLCBc/edit?usp=sharing&ouid=116339843045842450748&rtpof=true&sd=true</nowiki>
 +
 
 +
Life Events - ESDC - Jodi Seguin - Navigating a death
 +
 
 +
LLO GCWP Presentation.pptx (sharepoint.com)
 +
 
 +
* Pain points from employees and clients
 +
** Worries start early
 +
** No news is bad news
 +
* Where we started
 +
** For example call centres get over 300,000 calls about death benefits
 +
** The process is a challenge, how do we manage it
 +
* We studied the process through the Losing a loved one journey lab
 +
** Our mission was to improve the experience for Canadians
 +
** Our vision is a single point of access based on life events to manage events
 +
* We used an agile process to work on the Life Events design
 +
* We workshopped and worked with a variety of stakeholders to generate ideas, and through an iterative process, boiled it down to 5 processes
 +
* We gathered together a checklist of what to do online when someone dies
 +
* LLO Journey Lab MVP
 +
** Landing page
 +
** Interactive guidance
 +
** Print and share pages
 +
** Personalized checklist
 +
** Curated links
 +
* We’re working to break down silos between departments and bringing together services together
 +
 
 +
Comments:
 +
 
 +
What to do when someone dies hub prototype
 +
 
 +
* Guides the user through such as:
 +
** First steps
 +
** Notify
 +
** Apply
 +
* The prototype is built to give users as much information with in a way that it easy to consume
 +
* Also has a print function
  
−
'''A:''' Yes, we are working to ensure the platform will allow for these kinds of capabilities, but at the same time we are not building the capabilities ourselves.
 
 
===Roundtable===
 
===Roundtable===
−
Public Safety (PJE Theme)
+
 
−
*Work ongoing on updating the 1st round of hazard updates for GetPrepared.gc.ca. Emergency Preparedness Week is May 5 to 11. https://www.getprepared.gc.ca/cnt/rsrcs/ep-wk/index-en.aspx
+
 
−
'''CBSA'''
+
 
−
*The CBSA Assessment and Revenue Management (CARM) launch rescheduled to the fall
+
ISC
−
Office of the Privacy Commissioner of Canada
+
 
−
*Privacy Awareness Week
+
* We got our UX recruitment form through ATIP approvals
−
*This year’s theme is Privacy and technology: Improving transparency, accountability, and security, and the Canadian awareness campaign will run from May 6 to 10.
+
 
−
For more information: https://www.priv.gc.ca/en/about-the-opc/what-we-do/awareness-campaigns-and-events/privacy-awareness-week/
+
Principal Publisher
 +
 
 +
* Adobe Experience Manager (AEM) training material has been updated to reflect the stabilized institutional landing page template and related components. Please refer to [[/www.gcpedia.gc.ca/gcwiki/images/9/91/AEM-Documentation-6.5-Unit-3-12-Creating-an-Institutional-Landing-Page-ILP.pdf|Unit 12 – Creating an Institutional Landing Page (ILP)]] on GCpedia for step-by-step instructions.  
 +
 
 +
* GC developers and web publishers using the AEM freestyle template or not using AEM can find technical guidance in the [[/wet-boew.github.io/GCWeb/templates/institutional-landing/institutional-landing-doc-en.html#variations|GCWeb documentation]].

Revision as of 15:16, 11 June 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 item

Updates

PCO

  • Thanks for sending in your May promos
  • Thanks to the Principal Publisher analytics team that ran a learning activity on search terms today, check out the Youtube video

[Stewart] DTO - Task Success Survey Q4 and 2023-24 Results

  • Q4 looks similar to Q3, but there were changes in the types of tasks
  • Going forward might be good to report a “basket of tasks” each quarter instead of changing each quarter
  • Top 25 taks, mostly successful, may be time to increase the success rate marker higher
  • Repeated tasks have the highest success rate
  • Lowest scoring tasks are those related to an account, where you have to sign in, this is having negative impact
  • Annual results
    • Just over 500,000 respondents
    • 71% said they could complete their tasks
    • Again, repeated tasks are the most successful
  • What’s next for the survey
    • To select core common tasks to report on each quarter
    • More qualitative feedback
    • Call out for TSS case studies, how is it working for you?

Q & A

Q:Is there a recommended stat significance checker?

A: Yes, here’s what I use: https://docs.google.com/spreadsheets/d/1I-pkCshlwAmHp0YHfwHqAHDZQEvFLCBc/edit?usp=sharing&ouid=116339843045842450748&rtpof=true&sd=true

Life Events - ESDC - Jodi Seguin - Navigating a death

LLO GCWP Presentation.pptx (sharepoint.com)

  • Pain points from employees and clients
    • Worries start early
    • No news is bad news
  • Where we started
    • For example call centres get over 300,000 calls about death benefits
    • The process is a challenge, how do we manage it
  • We studied the process through the Losing a loved one journey lab
    • Our mission was to improve the experience for Canadians
    • Our vision is a single point of access based on life events to manage events
  • We used an agile process to work on the Life Events design
  • We workshopped and worked with a variety of stakeholders to generate ideas, and through an iterative process, boiled it down to 5 processes
  • We gathered together a checklist of what to do online when someone dies
  • LLO Journey Lab MVP
    • Landing page
    • Interactive guidance
    • Print and share pages
    • Personalized checklist
    • Curated links
  • We’re working to break down silos between departments and bringing together services together

Comments:

What to do when someone dies hub prototype

  • Guides the user through such as:
    • First steps
    • Notify
    • Apply
  • The prototype is built to give users as much information with in a way that it easy to consume
  • Also has a print function

Roundtable

ISC

  • We got our UX recruitment form through ATIP approvals

Principal Publisher

  • GC developers and web publishers using the AEM freestyle template or not using AEM can find technical guidance in the GCWeb documentation.
Retrieved from "https://wiki.gccollab.ca/index.php?title=May_22,_2024_-_Updates,_priorities_of_the_week&oldid=121811"