FY23 Planning and FY22 Theme Lookback -for PLT Offsite
I wanted to get your take on how we will end FY22. This is also a great prep for our upcoming PLT offsite in November. Jan 2021 offsite notes here
We will cover the FY23 goals quarter by quarter in the offsite. The rest will be a pre-read.
My request is for each PM to think about
- What were we planning to execute and accomplish when we started planning for FY22?
- Category Maturity Goals
- GMAU/SMAU Goals
- Key JTBD's we planned to execute on
- Tech debt
- How did we do against it so far and where will we end up by end of FY22?
- What new things did we do instead (e.g instrumentation, error budgets, reliability, usability etc)
- What is our plan for FY23? Lay it out Quarter by Quarter
- Category Maturity Goals
- GMAU/SMAU Goals
- Key JTBDs we plan to execute on
- How will we measure our success each quarter.
- One thing I want from my leadership for FY23 to help me execute better.
If a PM wasn't in the current role -that is OK -they can still lookback at what the plans were originally based on how our direction pages looked at the beginning of FY22 and how our category maturity plans looked at that time.
Additionally we also need a look-back on
-
Adoption through Usability (@clenneville @vkarnes, @david, @kencjohnston, @joshlambert)
-
GitLab Hosted First (@joshlambert )
Ops Section
I've been a big fan of the "Letter from the Editor" format that Tim has been using in Package (Tim's community is also a big fan). So my proposal is that each PM publishes a letter to the editor style annual group update in their group/stage direction page, with the following content covered in prose over no more than five paragraphs:
- Summary - Provide a TL;DR of the following four paragraphs
- State of Play - Say thanks to your team and your community, outline group size and capacity, briefly outline the current state.
- Looking Back - Outline what we set out to do via our category maturity, SMAU goals, and any key JTBD you had aimed to improve. Outline your progress against those goals (and a projection of where you think we will end up) as well as any new initiatives that you prioritized over initial goals.
- Looking Forward - Outline your plan for FY23 along those same axis (maturity, usage, and JTBD goals) including how your group's focus and goals will change throughout the year. It might be helpful to communicate this in quarter-by-quarter boundaries.
- How we can accelerate - Outline your preferred option to accelerate your FY23 plan in the form of an investment case or other leadership asks.
A few notes:
- This will be an exercise in prose writing, please write it like it is a letter written to your community (he writes in bullet form
😄 , yes I get the irony) - This will also be an exercise in brevity, keep your points succinct and use links when needed
Publish Letter from the Editor for Your Group
-
Pipeline Execution - @jheimbuck_gl - Add here, MR -
Pipeline Authoring - @dhershkovitch - Add here -
Runner - @DarrenEastman - Add here -
Testing - @rkenney2 - Add here -
Package - @trizzi www-gitlab-com!94919 (merged) -
Release - @cbalane - MR -
Configure - @nagyv-gitlab -
Monitor - @abellucci, www-gitlab-com!94572 (merged)
Publish Letter from the Editor for Your Stage/Section
Do this after the group Letters are completed and use them as summaries of group content.
-
Ops Section - @kencjohnston - www-gitlab-com!94959 (merged)
Enablement section
FY22 Lookback and FY23 plans: https://docs.google.com/document/d/1HlgpOPUb20REbBzXSPMLKmMXR4-pv2a2bMNXl5QqaHY/edit#
Planning issue: #3501 (closed)