OKRs and Team Performance
OKRs fail in Malaysian organisations for a consistent reason: the existing KPIs get renamed as key results, everything stays exactly as it was, and within two quarters the process is abandoned as another management fashion. The difference between OKRs and KPIs is not the format, it is that a key result describes an outcome you are trying to change rather than an activity you were always going to do. This day is spent on writing them properly and running the cycle that makes them matter.
Programme Agenda
What OKRs Are For
Focus and alignment, not performance appraisal. Why coupling OKRs to bonuses reliably destroys them, and the difference between an OKR and the operational KPIs you still need to run the business.
Objectives Worth Pursuing
Writing an objective that is directional, meaningful and finite. Why three matter more than eight, and how to say no to a fourth that a senior stakeholder wants.
Key Results That Measure Outcomes
The central skill. Turning "launch the new portal" into a result describing what changes because the portal exists. Avoiding key results that are task lists with a checkbox at the end.
Making Them Measurable but Not Gameable
Baselines, targets and the metric that improves while the underlying situation worsens. Pairing a metric with a counter-metric so a team cannot hit one by damaging the other.
Alignment Without Mechanical Cascading
Connecting team OKRs to company direction without each level simply restating the level above. Horizontal alignment between teams that depend on each other, and negotiating a shared key result.
Ambition, Scoring and Honesty
Committed against aspirational OKRs, what a score of 0.7 should mean, and building a culture where reporting a missed key result is safe. What happens to the process the first time someone is punished for a low score.
The Quarterly Cycle
Setting, weekly or fortnightly check-ins that take fifteen minutes, mid-quarter correction, and a closing review that produces learning rather than a scorecard. Keeping the overhead low enough to survive.
Writing Your Own
Participants draft a set for their own team, then have them challenged: is this an outcome, is it gameable, is it too many, and what would you stop doing to achieve it.
Learning Outcomes:
Explain what OKRs do that KPIs do not, and keep them out of appraisal
Write objectives that are directional, meaningful and few
Convert an activity into a key result that measures an outcome
Set baselines and pair metrics with counter-metrics against gaming
Align team OKRs to company direction without mechanical cascading
Use scoring honestly, including reporting a miss
Run a low-overhead quarterly cycle with short check-ins
Leave with a drafted and challenged OKR set for your team
Duration: 1 Day (8 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: All levels
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included
Frequently Asked Questions
More in Leadership and Management
- Stakeholder and Vendor Management · All levels, 1 day
- Scrum Master and Agile Fundamentals · Beginner, 2 days
- Leadership Skills for New and First-Time Managers · New managers, 2 days
- People Management and Team Leadership · Managers and supervisors, 2 days
- Working Manager and First-Line Supervisor · All levels, 1 day