Why Most Performance Management Systems Fail in Asian High-Growth Companies
The single biggest performance management failure we see across South and Southeast Asian businesses is not a framework problem. It is a timing problem. Companies run annual reviews, employees discover they have been underperforming for twelve months, and by then the damage to the team, the product, and the culture is already done.
We have worked across Sri Lanka, Indonesia, India, and the Philippines with businesses at every growth stage. The pattern is consistent. A founder builds a strong early team on trust and informality, the team scales past fifty or a hundred people, and suddenly there is no shared language for what good performance looks like. What replaces it is usually a hastily adopted annual appraisal cycle borrowed from a multinational playbook that was never designed for fast-moving, resource-constrained Asian businesses.
This post is a practitioner's guide to building performance management systems that work in the Asian context. Not because Western frameworks are wrong, but because the adaptations required for Asian market conditions, organisational structures, and manager maturity are specific enough to deserve their own treatment.
The Case for Continuous Feedback Loops Over Annual Review Cycles
Continuous feedback is not a nice-to-have. It is the core infrastructure of a functional performance system. Monthly one-on-ones, quarterly reviews, and bi-annual calibration sessions form the minimum viable rhythm for any business scaling past fifty employees.
The math is straightforward. An annual review gives you one intervention point per year. A monthly one-on-one gives you twelve. If a team member is off-track, you want to know in month two, not month eleven. The cost of a late correction is always higher than the cost of an early one, whether that cost is measured in revenue, team morale, or the departing employee's institutional knowledge.
The objection we hear most often from founders is time. Monthly one-on-ones feel like overhead when every manager is also an individual contributor. Our answer is always the same: the time you spend in a structured thirty-minute monthly conversation is a fraction of the time you will spend managing the fallout from a performance crisis that a single earlier conversation could have prevented.
[INTERNAL_LINK: building manager capability in scaling startups]
How to Structure Monthly One-on-Ones for Maximum Effectiveness
The most effective one-on-ones are employee-led, not manager-led. The employee sets the agenda, which signals that the conversation exists for their development, not for the manager's reporting needs.
A functional structure covers three things: progress against current priorities, blockers the manager can help remove, and one piece of forward-looking feedback in either direction. That is enough for thirty minutes. Anything more becomes a status meeting, which defeats the purpose.
The output of every one-on-one should be one or two documented action items. Without documentation, patterns disappear. When a quarterly review arrives and a manager cannot recall what was discussed in month one, the review becomes impressionistic rather than evidence-based.
OKR Implementation in Asian Companies: What Gojek Got Right
OKRs work when they create shared accountability across functions. They fail when they become a documentation exercise with no connection to how decisions are actually made or how people are rewarded.
Gojek's implementation across more than 20,000 employees as it scaled is one of the most instructive case studies available in Southeast Asia. The company linked individual goals to company-level objectives, which meant that an engineer in Jakarta and an operations lead in Bangalore could both trace their quarterly priorities back to the same two or three organisational bets. That shared line of sight is what OKRs are designed to create. Most implementations never get there because the cascading process is treated as a formality rather than a strategic exercise.
The failure mode we see most often in South Asian companies is OKR proliferation. A leadership team sets ten company-level objectives. Each business unit adds five of its own. Individual contributors end up with seven OKRs, none of which they can meaningfully prioritise. The system becomes noise. [INTERNAL_LINK: goal-setting frameworks for South Asian startups]
Setting Fewer OKRs: Why Three Priorities Beat Ten
Clarity on three priorities is operationally more valuable than ambiguity across ten. This is not a philosophical position. It is a practical one grounded in how attention and effort actually distribute across a team.
The discipline of choosing three objectives forces a strategic conversation that most growing companies avoid. It requires leaders to say explicitly what does not matter this quarter, which is often harder than agreeing on what does. That conversation is valuable precisely because of its difficulty.
Our standard recommendation for companies implementing OKRs for the first time is to cap company-level objectives at three, allow a maximum of three key results per objective, and require individual contributors to connect their work to at least one company-level objective. If the connection cannot be drawn, the work should be questioned.
Cascading KPIs in Conglomerate Structures: The JKH Model
Not every Asian business is a startup. Conglomerates and diversified groups operate under a fundamentally different performance management logic, and the Sri Lankan market offers a clear reference point.
John Keells Holdings operates across hospitality, transportation, retail, and financial services. Its performance management architecture uses cascading KPIs from group-level targets down to individual business unit goals, with a formal annual calibration process that runs across the entire portfolio. The calibration process matters because it creates a common standard for what high performance looks like, even when the underlying businesses are structurally different.
The lesson for other conglomerates and multi-business Sri Lankan firms is that the calibration session is not an administrative step. It is where the system develops integrity. Without cross-business calibration, you end up with a situation where a top performer in one business unit would be rated average in another, because the standards were never aligned. That inconsistency destroys the credibility of the system and, over time, the trust of your best people. [INTERNAL_LINK: HR governance for conglomerates in Sri Lanka]
Quarterly Reviews and Annual Resets: Building the Right Cadence
The OKR framework operates on a quarterly review and annual reset cycle for good reason. Quarters are short enough to stay relevant and long enough to show real progress. Annual resets allow for strategic recalibration without the disruption of constant framework changes.
In practice, the quarterly review should answer three questions: Did we achieve what we said we would? If not, why not? What does that tell us about what we should prioritise next quarter? The review is diagnostic, not punitive. The purpose is learning, not judgment.
The annual reset is where strategy and performance management connect. Leadership should use the reset to examine whether the objectives they have been pursuing still reflect the company's strategic direction. In fast-moving markets like Indonesia, Vietnam, or Sri Lanka's technology sector, a company's priorities in January can look materially different by December. The annual reset is the structured moment to acknowledge that and adjust accordingly.
Performance Management Is a Conversation, Not a Form
The quality of your managers' feedback skills determines whether your performance system works. This is the variable that most HR frameworks underweight and most HR software vendors completely ignore.
A company can implement the best-designed OKR system in the market, run quarterly reviews on schedule, and still produce no improvement in performance if its managers do not know how to have a direct, constructive feedback conversation. We have seen this pattern repeatedly across Colombo-based SaaS companies and Jakarta-based logistics firms alike. The system exists on paper. The conversations do not happen in practice.
The investment required to fix this is not large. It is targeted manager training on feedback delivery, active listening, and distinguishing between performance feedback and personal criticism. Two half-day sessions with a skilled facilitator will produce more improvement in system effectiveness than six months of OKR software configuration. [INTERNAL_LINK: manager training programmes for Asian companies]
Why Manager Capability Is the Highest-Leverage HR Investment
Managers are the transmission mechanism between your performance system and your employees. If that mechanism is weak, the signal does not get through regardless of the quality of the framework behind it.
In Asian business contexts, there is an additional cultural dimension. Direct negative feedback can feel confrontational in ways that vary significantly across Sri Lanka, India, Indonesia, and the Philippines. Effective managers learn to deliver honest assessments within the relational norms of their specific context, not by avoiding difficult feedback, but by framing and sequencing it in ways that preserve trust.
This is not about softening feedback until it loses meaning. It is about delivering it in a form the recipient can actually use. A senior manager at a Sri Lankan logistics firm once described it to us as the difference between feedback that lands and feedback that bounces. Both were delivered. Only one was received.
Consequences and Recognition: Making Your Performance System Credible
OKR implementations that have no consequence for misses and no recognition for exceptional performance will stop working within two cycles. People are not naive. They will calibrate their effort to the actual incentives in the system, not the intended ones.
Consequences do not have to mean termination. They can mean reduced scope, development plans, or simply a direct conversation about expectations. The requirement is that misses are acknowledged and addressed, not absorbed silently into the next quarter's reset.
Recognition matters equally. A high-performer who consistently delivers and receives no differentiated acknowledgment will eventually wonder why they are bothering. In competitive talent markets across Bangalore, Jakarta, and Colombo, that employee has options. Your performance system should make the case for staying, not quietly build the case for leaving.
FAQ: Performance Management Systems in Asian Businesses
What is the best performance management framework for fast-growing Asian companies?
The OKR framework, combined with a continuous feedback cadence of monthly one-on-ones and quarterly reviews, is the most widely effective structure for high-growth Asian businesses. The key is keeping objectives to three or fewer at the company level and ensuring every individual contributor can trace their priorities to a company-level goal.
How often should performance reviews happen in a scaling startup?
Minimum cadence is monthly one-on-ones, quarterly formal reviews, and a bi-annual calibration session. Annual-only reviews are not sufficient. By the time issues surface in a year-end review, the cost of the underperformance has already been absorbed by the business.
How do you implement OKRs without them becoming a checkbox exercise?
OKRs require two things to stay meaningful: genuine consequences for consistent misses and visible recognition for exceptional results. Without those, the system becomes documentation. Leadership also needs to model the process visibly, not just mandate it for individual contributors.
How does performance management work differently in conglomerates versus startups?
Conglomerates need cross-business calibration sessions to ensure performance standards are consistent across different business units. Without calibration, the same output could be rated differently depending on which business unit an employee works in. Startups need speed and simplicity, which is why OKRs with short quarterly cycles tend to outperform complex KPI systems in early-stage environments.
Building a Performance Management System That Scales
The businesses we have seen build durable performance cultures across Asia share a few common attributes. They invest in manager capability before they invest in systems. They prioritise conversation quality over process compliance. They set fewer goals with more clarity. And they treat calibration as a strategic exercise, not an administrative one.
Performance management is ultimately about closing the gap between what your organisation is capable of and what it is currently delivering. The framework matters. The cadence matters. But the thing that determines whether any of it translates into actual performance improvement is whether your managers are having honest, skilled, timely conversations with their people.
That is the work. Everything else is infrastructure.