Why Most Performance Management Systems Fail Before They Start
The majority of performance management systems in Asian businesses are built to satisfy HR compliance, not to drive performance. They produce paperwork. They do not produce results.
We have seen this pattern repeatedly across portfolio companies in Sri Lanka, Indonesia, and Bangladesh. A company installs a performance review framework, runs it for two cycles, and then watches managers treat it as an administrative burden rather than a leadership tool. The system does not fail because the framework was wrong. It fails because no one treated the quality of the conversation as the variable that matters most.
If you are scaling a business in South or Southeast Asia and you want a performance management system that creates genuine accountability, this post is for you. [INTERNAL_LINK: scaling people operations in high-growth companies]
The Core Problem With Annual Performance Reviews in Asia
Annual-only performance reviews are a structural guarantee of underperformance. When the only formal feedback moment is December, employees who began drifting in March do not find out until eleven months later. By that point, the cost to the business is significant and the cost to the individual is significant. Both were preventable.
This is not a Western versus Asian problem. It is a management architecture problem. And it is acutely damaging in fast-moving sectors like fintech, logistics, and consumer technology across Sri Lanka, India, and Southeast Asia, where market conditions shift within quarters, not years.
The fix is not to add more forms. The fix is to increase the frequency and quality of feedback touchpoints so that course correction happens in weeks, not months.
OKR Implementation in Asian Companies: What Works and What Does Not
How Gojek Scaled OKRs Across 20,000 Employees
Gojek's OKR implementation is one of the most studied examples of performance architecture in Southeast Asia. As the company grew from a Jakarta-based ride-hailing service into a multi-product super-app operating across Indonesia, Vietnam, and Thailand, it needed a way to keep individual contributors aligned with company-level objectives across product, engineering, and operations simultaneously.
The mechanism was a quarterly OKR cycle linked explicitly to company-level priorities. Individual objectives were not set in isolation. They were cascaded from team objectives, which were cascaded from business-unit objectives, which connected to the company's annual goals. Every employee could draw a line between their quarterly priorities and what the company was trying to achieve. That line creates accountability in a way that a job description never can.
Critically, Gojek did not treat OKRs as a performance rating tool in the traditional sense. They treated them as a shared language for what matters right now. That distinction separates the companies that get value from OKRs from the companies that get overhead from OKRs.
The Checkbox OKR Problem
The single most common OKR failure mode we observe in South and Southeast Asian businesses is implementation without consequence. Companies introduce OKRs, train managers, and run the first quarter. Then nothing happens when objectives are missed and nothing notable happens when they are exceeded. Within two cycles, OKRs become a checkbox exercise that managers resent and employees ignore.
For OKRs to function, there must be a visible link between performance against objectives and real outcomes. Those outcomes do not have to be purely financial. They can include stretch assignments, public recognition, access to leadership, or development opportunities. But the link must exist and it must be consistent. [INTERNAL_LINK: building accountability culture in high-growth startups]
How Many OKRs Should a Team Set Each Quarter
Set fewer objectives than you think you need. Three priorities with genuine clarity will outperform ten priorities that create ambiguity about where to direct energy on a Tuesday afternoon.
In our work with a Colombo-based SaaS startup that was scaling its sales and customer success functions simultaneously, the founding team initially set seven company-level OKRs for their first quarter. Every team had seven OKRs. Every individual had five to six key results. The system collapsed under its own weight within six weeks because no one could hold that much in focus while also doing their jobs.
We worked with them to reduce to three company-level OKRs with no more than five key results total at the team level. Completion rates on key results went from below forty percent to above seventy percent in two quarters. The constraint was the intervention.
Continuous Feedback Loops: Monthly 1:1s, Quarterly Reviews, and Bi-Annual Calibration
Monthly 1:1s as the Foundation of Performance Management
Monthly one-on-one conversations between managers and direct reports are the single highest-leverage activity in a performance management system. They are also the most consistently skipped activity when calendars get busy.
A monthly 1:1 serves three functions that no review form can replicate. It gives the employee a predictable space to raise blockers before they become crises. It gives the manager early signal on trajectory before the quarter closes. And it builds the trust that makes difficult feedback land constructively rather than defensively.
In markets like Sri Lanka and Bangladesh, where hierarchical norms can make direct upward communication feel risky for junior employees, the structured regularity of a monthly 1:1 does important cultural work. It normalises the expectation that feedback flows in both directions. [INTERNAL_LINK: management practices for hierarchical workplace cultures]
Quarterly Reviews: What They Should and Should Not Cover
Quarterly reviews are for assessing progress against objectives, recalibrating priorities for the next quarter, and identifying development needs. They are not for surprises. If a quarterly review contains information the employee has never heard before, your monthly 1:1s are not working.
The quarterly review format that we have seen perform best in Asian high-growth companies is short and structured. Thirty to forty-five minutes. A review of the previous quarter's OKRs with honest scoring. A discussion of what enabled or blocked performance. And a forward look at the next quarter's objectives with clear agreement on what success looks like.
Bi-Annual Calibration Sessions Across Business Units
John Keells Holdings, one of Sri Lanka's largest conglomerates, uses a formal calibration process that runs across its business units twice a year. The structure is deliberate: group-level targets cascade to individual business unit KPIs, and then leaders across the conglomerate come together to review talent assessments and ensure that performance ratings are consistent rather than inflated or deflated by individual managers' tendencies.
This calibration step is essential and consistently underused by growing companies. Without it, performance ratings in one team become incomparable to performance ratings in another. A five-out-of-five in the finance team means something different from a five-out-of-five in engineering if no one has ever aligned on what excellent looks like. Calibration sessions solve that problem.
For companies scaling across multiple markets, including regional businesses operating in Sri Lanka, India, and Southeast Asia simultaneously, calibration becomes even more important. Cultural differences in how managers assess and communicate performance can produce systematically inconsistent talent data if calibration is not built into the cycle. [INTERNAL_LINK: managing distributed teams across Asian markets]
Cascading KPIs in Conglomerate and Multi-Business Structures
How to Design KPI Cascades That Create Accountability
Cascading KPIs are the mechanism by which strategic intent becomes individual responsibility. At the group or company level, you have three to five headline metrics that define success for the year. Those metrics break into business-unit KPIs. Business-unit KPIs break into team KPIs. Team KPIs break into individual targets.
The cascade works when every layer can articulate how their KPIs connect to the layer above. It breaks when individual KPIs are set by managers in isolation from business-unit strategy, which happens more often than it should in fast-growing organisations where strategic planning and operational management are running at different speeds.
A Sri Lankan logistics firm we worked with had a classic cascade failure. The group-level objective was to reduce cost per delivery by fifteen percent. The operations team had KPIs around on-time delivery rates. The driver teams had daily trip volume targets. None of these KPIs had been formally connected. Improving trip volume, as the drivers were incentivised to do, was actually increasing cost per delivery in certain route configurations. The cascade had not been designed. It had been assumed.
Performance Management Is a Conversation, Not a Form
The quality of your managers' feedback skills determines whether your system works. Not the platform. Not the template. Not the rating scale. The manager sitting across from the employee.
Investing in a performance management software platform before investing in manager capability is a sequencing error that costs companies real money. We have watched companies in Colombo, Jakarta, and Dhaka spend significant sums on HR technology that their managers did not have the skills to use well. The technology amplified the problem. It did not solve it.
Manager capability on feedback means three specific things. First, the ability to give specific, behavioural feedback rather than vague impressions. Second, the ability to have a difficult conversation without damaging the relationship. Third, the ability to connect an individual's development to the company's direction so that performance conversations feel meaningful rather than mechanical. [INTERNAL_LINK: manager training and development programs]
Building these skills requires deliberate investment. Workshops, coaching, modelling from senior leaders, and accountability for managers on the quality of their 1:1s. It is slower and less visible than buying software. It is also the thing that determines whether the whole system functions.
FAQ: Performance Management Systems in Asian Companies
What is the difference between OKRs and KPIs in a performance management system?
OKRs define what you are trying to achieve in a specific time period and how you will know you have achieved it. KPIs are ongoing metrics that tell you whether core business processes are healthy. Both belong in a performance management system, but they serve different functions. OKRs drive prioritisation and focus on change. KPIs maintain visibility on operational fundamentals. The mistake is treating them as interchangeable.
How often should performance reviews happen in a fast-growing company?
Fast-growing companies need at least quarterly formal reviews supplemented by monthly manager-to-employee 1:1s. Annual reviews alone are structurally inadequate because the business and the individual's role can change significantly within a quarter. The bi-annual calibration session sits above these touchpoints to ensure consistency in how performance is assessed across the organisation.
How do you implement OKRs without them becoming a checkbox exercise?
Three things prevent OKRs from becoming checkbox exercises. First, visible consequences: there must be a consistent, known link between OKR performance and outcomes that employees and managers care about. Second, genuine scoring: OKR scores must reflect reality, not aspiration. If every team scores four out of five every quarter, the system has no signal. Third, senior leader behaviour: if leadership does not publicly discuss their own OKRs and their own misses, OKRs will be seen as a tool for junior employees only and will lose legitimacy fast.
What is performance calibration and why does it matter in Asian conglomerates?
Performance calibration is a structured session in which managers across teams or business units align on how to apply performance standards consistently. It matters in conglomerates because each business unit develops its own manager culture, which creates rating inflation or deflation that makes talent data unreliable at the group level. JKH's bi-annual calibration process across its diverse business portfolio is a strong example of how to systematise this in a multi-business structure.
Building a Performance Management System That Scales
The companies in Asia that scale performance management successfully share a single characteristic: they treat it as a leadership discipline, not an HR process. The system is the scaffolding. The quality of the conversations that happen inside the system is what determines whether the business gets faster, more aligned, and more capable as it grows.
Start with fewer objectives. Build the feedback rhythm before you build the rating framework. Invest in manager capability before you invest in technology. And run calibration sessions from early enough that consistency becomes a habit rather than a correction.
The architecture matters. The execution matters more.