When introducing or improving OKRs in an engineering organisation.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Tech Communication & Leadership - Use case: Engineering OKR Framework - Source task: - Build an engineering OKR framework for {{describe_organisation_company_stage_engineering_team_size_key_bu}}. - Step 1: align engineering OKRs to the top 3 business OKRs : show the linkage explicitly. - Step 2: write 3 engineering Objectives with 3 Key Results each. - Step 3: design the OKR review cadence (check-in frequency, scoring criteria, communication of progress). - Step 4: identify the 3 most common OKR mistakes in engineering teams and how to avoid them. - Step 5: design how OKRs connect to individual performance reviews. # Goal Business OKR alignment, 3 engineering OKRs with 9 KRs, review cadence, 3 common mistakes to avoid, and performance review connection. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Business OKR alignment, 3 engineering OKRs with 9 KRs, review cadence, 3 common mistakes to avoid, and performance review connection.
{{double-curly}} with your real context.When introducing or improving OKRs in an engineering organisation.
Engineering OKRs fail when they measure activity (shipped features) rather than outcomes (user retention, system reliability, developer velocity) — insist on outcome metrics.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.