MODULE "Goal setting and priority management"

​

Team Goal Setting Case Studies

by departments

IT

OKR/SMART

🎧 OKR Road Map

General goal of IT:�

Ensure a reliable, secure, and scalable technology platform that supports the company's strategic growth.

​

​

🎧 OKR Road Map

Level 1. Strategic Results

​

• Reliability (failure-free operation of services).
• Speed of development (time to introduce new features).
• Security (data protection, anti-fraud , compliance).
• Scalability (can handle growth in users/transactions).
• Efficiency (low cost per transaction, operating leverage).

Level 2. Key Business Metrics

​

• Uptime (99.9%+ availability) — how long the system is running.
• MTTR ( mean time to recovery) is the speed of response to a failure.
• Deployment Frequency — the frequency of releases into production .
• Time-to-Market of a new feature – from idea to launch.
• Number of critical security incidents.
• Cost per Transaction — operational cost of IT per transaction.
• Technical debt (% legacy in code).

🎧 OKR Road Map

Level 3. Operational Indicators

​

• Number of critical bugs per release.
• Percentage of code covered by automated tests (%).
• Percentage of releases without rollbacks.
• SLA for tickets (time to first response).
• % of infrastructure in the cloud ( vs on-prem).
• Number of regressions after release.
• % process automation ( CI/CD).

🎧 OKR Road Map

Level 4. Action Metrics. (Daily Indicators)

• Average developer response time to a ticket .
• Number of pull requests that passed code review in ≤24 hours.
• Number of automated tests added to the sprint.
• Number of deploys per week.
• The share of tasks completed in a sprint without being carried over.
• Deployment time .
• The number of incidents detected by monitoring before users.
• % of users with 2FA enabled .

🎧 OKR Road Map

IT

​

CASE STUDIES

O: To ensure stability and scalability of the platform.

​

KR:

○ Reduce average page response time to <1.5 sec.

​

○ Reduce the number of critical bugs (P1) by 40% by the end of the quarter.

​

○ Complete the migration of 80% of services to cloud architecture.

1

OKR

O: Improve the quality of internal tools for product teams.

​

KR:

○ Implement a CI/CD pipeline with automated tests for 90% of projects.

​

○ Reduce deployment time from 2 days to 2 hours.

​

○ Conduct 3 training sessions for developers on new tools.

2

OKR

O: Improve information security.

​

KR:

○ Conduct a security audit of all services by the end of the quarter.

​

○ Close 100% of identified critical vulnerabilities.

​

○ Implement 2FA for all internal systems.

3

OKR

SMART

1. Reduce the proportion of unclosed bugs older than 30 days from 25% to 10% by the end of Q4

​

2. Set up a monitoring and alert system for all APIs by November 15th.

​

3. Increase test automation from 50% to 80% by the end of the quarter.

Ineffective wording

●“Make the platform better” → not specific, no metrics.

​

●“Reduce bugs” → it is unclear to what extent and by what deadline.

​

●“Work on security” → too general, not SMART/OKR.

OKR Libraries for I T

1. Library 1
2. Library 2