Resultado de ejemplo
Creado el 27 octubre 2026
Objective 1: Make the product reliably available and trustworthy
KR 1.1
Reduce customer-impacting downtime to ≤45 minutes for the quarter, with no single incident exceeding 20 minutes.
- How to measure: Production monitoring and incident records; exclude scheduled maintenance announced at least 48 hours in advance.
- Gaming risk: Reclassifying incidents as maintenance or splitting one incident into several.
- Guard: Use customer-visible impact as the classification standard; require post-incident review for every outage over 5 minutes.
- Task-list flag: No.
KR 1.2
Reduce the rate of production requests ending in server-side errors by 50% from the previous quarter’s baseline, while keeping p95 latency at or below 500 ms.
- How to measure: APM telemetry using a fixed definition of eligible production requests and server-side errors.
- Gaming risk: Excluding problematic endpoints or reducing errors by adding retries that worsen latency.
- Guard: Track a fixed endpoint set covering ≥95% of traffic; pair the error target with the latency constraint.
- Task-list flag: No.
KR 1.3
Resolve 90% of severity-1 and severity-2 incidents within 60 minutes, and keep repeat incidents from the same root cause below 10%.
- How to measure: Incident-management timestamps and root-cause tags, audited during weekly reliability review.
- Gaming risk: Downgrading severity or labeling recurring failures as unrelated.
- Guard: Define severity using customer-impact thresholds; require cross-review of severity and root-cause classification.
- Task-list flag: No.
Objective 2: Launch a mobile app customers can adopt with confidence
KR 2.1
Release the mobile app to general availability on iOS and Android by quarter-end, with ≥99.5% crash-free user sessions during the first 30 days.
- How to measure: Store release status plus mobile observability data from production sessions.
- Gaming risk: Calling a limited bet