Engineering OKR Framework

Design an engineering OKR framework for [Team/Organization]. Include: 1) Engineering-specific OKR philosophy — balance feature delivery, technical health, team growth, and operational excellence. Avoid vanity metrics. 2) Company-to-team cascade — how engineering OKRs connect to company objectives, bidirectional alignment (top-down strategy + bottom-up expertise). 3) Sample OKRs by category — Feature delivery (user-facing outcomes, not output), Quality (bug rates, test coverage, incident reduction), Performance (latency, reliability, scalability), Developer experience (build times, deploy frequency, onboarding time), Team health (retention, engagement, skill growth). 4) Anti-patterns — avoid counting shipped features, story points, or lines of code. Focus on customer and business outcomes. 5) Scoring methodology — 0.0-1.0 scale, target 0.7 as success, stretch goals vs committed goals, binary vs progressive key results. 6) Cadence — quarterly setting process, weekly check-ins, mid-quarter adjustments, end-of-quarter retrospective. 7) Cross-team dependencies — shared OKRs, dependency tracking, commitment negotiation process. 8) Tool recommendations — OKR tracking integration with project management, visibility dashboards, automated progress updates.