OKR Plan
Our objective this quarter is to:
Make providing an effortless customer experience a habit for each application engineer by consistently honoring our guiding principles and definitions of success while maintaining healthy work habits.
We will measure this via the following key results:
- Anyone on the team will be able to review all open cases and say “yes” we are honoring our guiding principles and definitions of success at least 95% of the time when measured.
- All application engineers will have a sentiment of at least a 2 in at least 60% of the technical competency areas outlined in our technical competency matrix.
- All application engineers honor their weekly focus day at least 90% of the time and have taken about 20–30 days off by the end of the quarter (about 20 for those who started in June/July; about 30 for those who started in February/March).
We will track our progress (some key results will be measured weekly, others on a more meaningful cadedence for the intention of the OKR) in our tracker.
To accomplish our OKR, we will…
TO BE FILLED IN BY .
| # | Status | Responsible | Project |
|---|---|---|---|
| 1 | In-progress | CS leadership | Case reviews |
| 2 | In-progress | CS leadership | Healthy habits |
| 3 | In-progress | Application engineers | Enablement |
Task details
1 Case reviews
- Workgroup: CS leadership
- Facilitator: Nonso
- Details: CS leadership will launch 3 types of case review practices in advance of in order to impact KR1:
- Peer reviews (similar to the idea of code reviews)
- Manager reviews (which include self-review)
- Retros on cases that take longer than 2 week to resolve (finishing what we started in Q3)
2 Healthy habits
- Workgroup: CS leadership
- Details: CS leadership will dig in with each member of the team to understand what needs to shift (mindset or practices) in order to make it easy to honor taking a focus day and taking time off as needed.
3 Enablement
-
Workgroup: All application engineers
-
Details: Each application engineer will work to complete as many enablement courses as possible and add them to our enablement page as they complete them. Our goal is to complete the following crash courses by end of December (and then more to come in January!):
- Perforce (Alex)
- RDS databases (Amber)
- GraphQL (Ben)
- Prometheus (Don)
- Scaling (Gabe)
- Code insights (Giselle)
- Docker/docker-compose migrations (Jason)
- CodeIntel (Kelvin)
- Docker/docker-compose deploy (Mariam)
- Kubernetes migrations (Michael)
- Marketplace extensions (Stompy)
- Kubernetes deploy (Warren)
A crash course is something lasting and referenced from the handbook … either a video (harder to update over time but also super useful and/or written materials) … so more like Youtube – all at the application engineer’s preference. It’s okay for folks to experiment and see what works.