Whew! 😅
Q1 was full of change. We re-organized squads. We “Built the Nest.” We started bi-weekly syncs and product forums. We switched from GitHub Projects to Linear. We even rebranded the app!
All of these changes were invisible to customers, except for the rebrand. So why did we do them? The end-of-year vision is that they’ll greatly reduce incidents, bugs, and other interrupts so that we can ship new value to customers faster than ever.
So what will Q2 be about?
Q2 is the first turn of our quarterly planning cadence. We’ll use it to align squads and EPD Leadership on the roadmap for the quarter, not just the next couple weeks. It’ll work like this:
- Squad leads* review EPD’s quarterly Objectives and Key Results (OKRs) below, as well as their squad’s intent section.
- Squad leads map Linear projects to our Key Results and make roadmap prioritization changes, if needed.
- Key Result owners meet with leads contributing to their KRs, and calibrate KR goal numbers.
- Squad leads summarize Q2 roadmap changes (or lack thereof) in their #epd-leads channels.
- EPD Leadership shares feedback in #epd-leads channels or in the next bi-weekly leads sync.
** Product Manager, Engineering Manager, Product Designer, Site Reliability Engineer, and Product Marketing Manager. These folks must be aligned on all quarterly planning decisions.*
Q2 Engineering, Product, and Design OKRs
- Maintain Platform Operational Health
- Reduce database-related incidents from X% (Q1) to Y% of total Q2 incidents
- Squads maintain work on the highest priority breached nest layer for 80% of the quarter
- Reduce our Google Cloud Platform costs from X% to Y% of MRR
- Advance our Multi-Product Strategy
- Increase New-Product-X Pilot Accounts from 0 to X
- Increase the accounts active in both Product A and Product B from X% to Y%
Squad Intents
Expand your squad’s toggle to read how your squad is intended to fit into the OKRs above.
- Squad Pipelines
- Squad Profiles
- Squad Content
- Squad Enablement