Zack RossApr 14, 20212 min readWhat is a good OKR vs a bad OKR for engineering?Updated: Mar 17, 2022OKR can be used in any industry, but here are a some detailed examples of bad and good OKRs just for the engineers. Bad OKR Examples:1. Objective: Test new vendor software release for bug fixKey Result: Software release tested.2. Objective: Respond to new tickets within stated SLAKey Result: Most ticket responses met SLA.3. Objective: Albatross tool automation development workKey Result: Evolve and refine the procedures and tools for Albatross.4. Objective: Clean router air filtersKey Result: Air filters vacuumedGood OKR Examples:1. Objective: Implement fix for critical bug that turn bits blueKey Result: Create and document test plan; [Doc link here].Key Result: Execute test plan and document test results; [Doc link here].Key Result: Plan rollout of new software; plan here.Key Result: Create MOP for software rollout; MOP link here.Key Result: Rollout new software to FOA sites; PCR link here.Key Result: Rollout new software to all production sites; Status tracking report here.2. Objective: Respond to new tickets within 5 minute SLA for urgent priority tickets to minimize customer impact.Key Result: 147 tickets received this quarter with 139 (95%) addressed within 5 minutes. See report at < link >.3. Objective: Add new vendor xyz to Albatross data collection tool to identify initial configuration errors.Key Result: Automation requirements collected from cross-functional team; document here.Key Result: Code written to implement new vendor data collection; CL here.Key Result: Dashboard presentation and alerting mechanism implemented; CL here.Key Result: Identified errors assigned to engineer for resolution; Ticket summary here.4. Objective: Perform preventative maintenance cleaning of router air filters annually.KR: Air filter cleaning schedule published; plan link here.KR: 25% of air filters checked and cleaned this quarter; Work tracking results link here.KR: Pine air freshener added to each site cleaned; Tracking results here.
OKR can be used in any industry, but here are a some detailed examples of bad and good OKRs just for the engineers. Bad OKR Examples:1. Objective: Test new vendor software release for bug fixKey Result: Software release tested.2. Objective: Respond to new tickets within stated SLAKey Result: Most ticket responses met SLA.3. Objective: Albatross tool automation development workKey Result: Evolve and refine the procedures and tools for Albatross.4. Objective: Clean router air filtersKey Result: Air filters vacuumedGood OKR Examples:1. Objective: Implement fix for critical bug that turn bits blueKey Result: Create and document test plan; [Doc link here].Key Result: Execute test plan and document test results; [Doc link here].Key Result: Plan rollout of new software; plan here.Key Result: Create MOP for software rollout; MOP link here.Key Result: Rollout new software to FOA sites; PCR link here.Key Result: Rollout new software to all production sites; Status tracking report here.2. Objective: Respond to new tickets within 5 minute SLA for urgent priority tickets to minimize customer impact.Key Result: 147 tickets received this quarter with 139 (95%) addressed within 5 minutes. See report at < link >.3. Objective: Add new vendor xyz to Albatross data collection tool to identify initial configuration errors.Key Result: Automation requirements collected from cross-functional team; document here.Key Result: Code written to implement new vendor data collection; CL here.Key Result: Dashboard presentation and alerting mechanism implemented; CL here.Key Result: Identified errors assigned to engineer for resolution; Ticket summary here.4. Objective: Perform preventative maintenance cleaning of router air filters annually.KR: Air filter cleaning schedule published; plan link here.KR: 25% of air filters checked and cleaned this quarter; Work tracking results link here.KR: Pine air freshener added to each site cleaned; Tracking results here.
