# Weekly Plan > [!note] Important Information > This is a **live** work in progress issue. The description will get updated as we work through each of the weeks. Future weeks are planned, but may be changed in the future to align with our findings/deliverables from previous weeks. <details> <summary><strong>02.16. Week 1 {+Done+}</strong></summary> - [x] Create detailed annual plan (this issue) - [x] Begin module audit, discuss with SSCs/product area leads - https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/31 - https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/32 - [x] [RFC issue ](https://gitlab.com/gitlab-com/support/support-team-meta/-/work_items/7465#top)open - [x] [Maintainer status check](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/31) complete — a lot of modules have no active maintainer - [x] [Skills analysis report](https://support-team-skills-analysis-25ffbb.gitlab.io/) reviewed and updated last year - [x] Issue open for missing training feedback from team (https://gitlab.com/gitlab-com/support/support-team-meta/-/work_items/7465#top) </details> <details> <summary><strong>02.23. Week 2 {+Done+}</strong></summary> - [x] Draft Handbook maintainer role definition - [MR](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18615) - [x] Review the module template - [MR](https://gitlab.com/gitlab-com/support/support-training/-/merge_requests/1706) - We could add it to the skeleton that you need to pair with someone who has that topic as expertise in the skills list - [x] Discussion on use one LLMs to create basic trainings then those would be the ones to be updated by the engineers - [x] Resume module audit, discuss with SSCs/product area leads - After checking with **Kirsty Allen** on the outcome of her chats. - [x] Maintain RFC from week 1 (**[RFC: What new or improved training modules would you like to see?](https://gitlab.com/gitlab-com/support/support-team-meta/-/work_items/7465#top)**) - We need to advertise this again </details> <details> <summary><strong>03.02. Week 3 {+Done+}</strong></summary> - [x] Finalize and publish Handbook maintainer role definition - [MR](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18615) - [x] Depending on RFC from last week we might need to target seniors for input based on skills page — maybe a form/survey? - We have also [advertised this to the entire team ](https://gitlab.com/gitlab-com/support/support-team-meta/-/work_items/7465#note_3126633030) - [x] Open volunteer recruitment issue — be explicit about time commitment and responsibilities - Dependency on `Finalize and publish Handbook maintainer role definition` - [Issue created](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/37), ~~but not yet advertised until the analysis is done on the Training ideas RFC~~ Advertised in Week 4 in team calls and SWIR. - [x] Duo Training Agent Pilot - https://gitlab.com/gitlab-com/support/support-training/-/automate/agents/1004177/ - Thanks to @kategrechishkina for the idea!! :) - We had discussed this with Kate, and initially thought to create an agent for each module, but in the end opted for a single agent for all modules. - Pending process to add to gitlab-com namespace - [x] Investigate training lab exercises more - @tloughlin working on a DAST lab exercise with authentication problems - https://gitlab.com/tloughlin_ultimate_group/public/support-tools/broken-dast-scenario </details> <details> <summary><strong>03.09. Week 4 {+Done+}</strong></summary> - [x] Analyse data from RFC - https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/33 ✅ - [x] Identify specialized domain track areas (AI, Geo, etc.) - [Issue](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/40) - Reach out to EMs or SSCs to see if anything beneficial could be added to these track areas - [x] Thomas will investigate training lab exercises more - SM broken labs/instances. Fork of https://gitlab.com/tloughlin_ultimate_group/public/support-tools/gcp-ansible-sm-provisioner - [x] [Tanuki Tutor](https://gitlab.com/components/agents-and-flows/support-tanuki-tutor#) is now published and available anywhere in the `gitlab-com` namespace! </details> <details> <summary><strong>03.16. Week 5 {+Done+}</strong></summary> - [x] Advertise maintainer volunteer issue once again - [x] Finalise the [identified specialised domain track areas](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/40) - Plan new potential modules needed based on team feedback in RFC - [Note](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/40#note_3185905555) - Plan modules that need TLC based on module inventory analysis - [Note](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/32#note_3185971163) - [x] Tanuki Tutor screen recording/demo - [GitLab Unfiltered](https://www.youtube.com/watch?v=mI0OFbpDIyA) </details> <details> <summary><strong>03.23. Week 6 {+Done+}</strong></summary> - [x] Advertise Tanuki Tutor screen recording - [x] Potentially define beginner → intermediate → advanced structure for specialized domain tracks - Case-by-case basis - @tloughlin created and added recommended ordering for the pathways in this [issue](https://gitlab.com/gitlab-com/support/support-experience-strategy/-/work_items/40) - Also added to the handbook [MR](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/19088) - [x] Set up automatic ping system for module reviews - @tloughlin created - [MR](https://gitlab.com/gitlab-com/support/support-training/-/merge_requests/1733) - Scheduled pipeline created: - {width=256} - [x] Using AI in Support module - @tloughlin - https://gitlab.com/gitlab-com/support/support-training/-/blob/main/.gitlab/issue_templates/Using%20AI%20in%20Support.md?ref_type=heads - [x] Created [SadLab](https://gitlab.com/tloughlin_ultimate_group/public/experimental/sadlab) as an experimental tool - {width=256} </details> <details> <summary><strong>03.30. Week 7 {-In Progress-}</strong></summary> - [ ] Review pre-existing modules flagged as needing updates - prioritise by ticket volume/data from audit - [x] Close recruitment issue / compile volunteer responses - closing 2nd April - [ ] Identify potential maintainers for modules with no maintainer based on product area (SSCs etc.) for modules that have no maintainer - Will reach out after the issue is closed - [ ] Further SadLab work, including more scenarios - [ ] Begin work on `Compile full list of external trainings (LinkedIn Learning, etc.) GitLab already pays for` in prep for Week 8 </details> <details> <summary><strong>04.06. Week 8</strong></summary> - [ ] Compile full list of external trainings (LinkedIn Learning, etc.) GitLab already pays for - Make team aware of personal development/learning fund - [ ] Cross-reference with domain track gaps identified in Week 6 </details> <details> <summary><strong>04.13. Week 9</strong></summary> - [ ] Buffer week — follow up on volunteer recruitment if uptake was low - [ ] Begin mapping Q2 content creation priorities based on everything gathered </details> <details> <summary><strong>04.20. Week 10</strong></summary> - [ ] Finalize Q2 plan: which modules get created, by whom, in what order </details> <details> <summary><strong>04.27. Week 11</strong></summary> - [ ] Deliver: detailed annual plan broken down by quarter + full current module inventory </details> --- | Quarter | Focus | |---------|-------| | **Q2 - Q3** | Create modules / Content creation | | **Q4** | More focus on aspiring leaders and checking if we covered everything |