Engineering OKR example

Meet our reliability targets

Hit agreed service levels on the services that matter most.

Suggested timeframe: Set with your team1 objective · 3 key results

YOUR STARTING POINTEngineering OKRs

OBJECTIVE

Hit agreed SLOs on our most critical services

KR 1
Raise API availability from 99.5% to 99.9%
KR 2
Bring p95 response time on core endpoints from 900ms to 400ms
KR 3
Define and publish SLOs for all 8 tier-1 services, up from 2

Example targets. Adapt to your baseline before you start.

USE THIS WHEN

Reliability is discussed in general terms with no shared targets. Works for platform and SRE teams.

Make it work for your team

Set your baseline. Check where you are today, then choose targets that stretch your team.

Agree on ownership. Give each key result a clear owner and a source of data.

Check in every week. Review the numbers, share confidence, and decide what needs attention.

FROM PLAN TO PROGRESS

Give these goals
a weekly rhythm.

Track your results, spot what needs attention, and keep everyone in the loop with Tability.

Make it your own. Then move it forward.

Your weekly check-in

Start with your team's baseline.

Clear objectivesMeasurable resultsAgreed owners

A clear owner for every result
Simple weekly check-ins
Progress reports, ready to share

Get this template as YAML

A machine-readable version of this example for a script or AI assistant.

title: Meet our reliability targets
objectives:
  - title: Hit agreed SLOs on our most critical services
    outcomes:
      - title: Raise API availability from 99.5% to 99.9%
        initiatives: []
      - title: Bring p95 response time on core endpoints from 900ms to 400ms
        initiatives: []
      - title: Define and publish SLOs for all 8 tier-1 services, up from 2
        initiatives: []

KEEP EXPLORING

More examples to explore.

Explore the collection

Reliability

Cut production incidents

Make the product something customers can rely on.

Objective

Make our product something customers can rely on

Reduce customer-facing incidents from 12 to 5 per quarter
Cut mean time to recovery from 3 hours to 45 minutes
Complete post-incident actions for 100% of major incidents within 2 weeks, up from 50%

View template

Delivery