19 Technology in Performance Management Systems

Learning Objectives

After studying this chapter, the reader should be able to:

Trace the evolution of performance management technology from paper-based instruments to integrated human capital management platforms.
Distinguish the principal categories of performance management technology and assess the conditions under which each is appropriate.
Identify what technology does well in performance management and what it cannot substitute for, however sophisticated it becomes.
Evaluate the emerging role of artificial-intelligence-adjacent capabilities in performance management workflows.
Recognise the implementation pitfalls that cause technology investments to underdeliver and design approaches that avoid them.
Apply change-management principles to the rollout of performance management technology in large organisations.
Adapt these principles to Indian operating realities, including hybrid workforces, regional language requirements, and data-residency considerations.

19.1 Introduction

Technology as Enabler and Constraint

Technology has reshaped the practice of performance management more profoundly over the past two decades than any other single factor. Paper forms have given way to digital platforms; annual cycles to continuous workflows; supervisor-only data flows to multi-source feedback architectures; manually compiled reports to real-time dashboards. The shift has been substantial, and the benefits have been real: scale that paper-based systems could never achieve, visibility that handwritten records could never provide, ritual reduction that frees managerial time for the conversations that actually matter. But technology is also a constraint. It shapes what is recorded and therefore what is attended to; it imposes workflows that fit some kinds of work better than others; it generates data whose interpretation requires care that the technology itself does not supply. The chapter that follows examines technology in performance management as both enabler and constraint, with attention to the design choices and implementation disciplines that determine which face it shows in any particular organisation (H. Aguinis, 2013).

The Stance of This Chapter

The chapter treats performance management technology not as a magic instrument that solves managerial problems but as infrastructure whose value depends on the practices, capabilities, and intent that surround it. Technology can amplify good practice; it can also amplify bad practice. A platform deployed atop a coherent performance management philosophy delivers genuine improvements in efficiency, visibility, and developmental conversation quality. The same platform deployed atop an incoherent philosophy produces faster, more visible, and better-documented dysfunction. The chapter is therefore as much about the choices that surround technology — what to deploy, when to deploy it, how to deploy it, and what to leave to humans — as about the technology itself (M. Armstrong, 2009).

19.2 The Evolution of Performance Management Technology

From Paper to Workflow

The earliest performance management technologies were not technologies at all but standardised paper forms that codified the questions managers should ask, the dimensions they should rate, and the development conversations they should hold. The shift to digital began with the simple replacement of paper forms with electronic ones, often as part of broader human resource information system deployments in the 1990s. The next stage introduced workflow capability that routed forms among the parties involved — employee, manager, skip-level reviewer, HR — and tracked completion. The stage after that integrated performance data with other people-data flows, enabling reporting that combined performance ratings with compensation, succession, and development data. Each stage added value, but each also brought the risk of amplifying the bureaucratic dimension of performance management at the expense of its developmental purpose (M. Armstrong, 2009).

The Continuous-Feedback Era

The most consequential recent shift in performance management technology has been the emergence of platforms designed around continuous feedback rather than around the annual cycle. These platforms restructure the user experience around frequent check-ins, lightweight feedback exchanges, real-time goal updates, and integrated conversation capture. Their design embodies a different theory of performance management — one anchored in ongoing conversation rather than periodic evaluation — and they have driven, as well as supported, the broader continuous-feedback movement examined in earlier chapters. Their adoption has been particularly rapid in technology-intensive industries and in organisations whose workforces expect digital interaction as a baseline (M. Buckingham & A. Goodall, 2015).

Integrated Human Capital Management Platforms

Parallel to the emergence of specialist continuous-feedback platforms, the major enterprise software vendors have built integrated human capital management suites that bring performance management together with recruitment, learning, compensation, succession, and analytics in a single architecture. The integration offers genuine advantages: data flows seamlessly between modules, reporting can combine information from across the people-data lifecycle, and the employee experience is consolidated rather than fragmented across multiple systems. The integration also imposes constraints: design choices in one module propagate across others, customisation is harder, and the integrated platform is rarely best-in-class for every function it covers. Organisations choose between integrated suites and best-of-breed combinations based on their priorities and their tolerance for integration complexity (H. Aguinis, 2013).

19.3 A Typology of Performance Management Technologies

The Major Categories

The technologies available to support performance management can usefully be grouped into several categories. Integrated HCM suites — Workday, SuccessFactors, Oracle HCM, Cornerstone — provide performance management as one module within a broader people platform. Specialist continuous-feedback platforms — Lattice, 15Five, Betterworks, Culture Amp — offer focused capability designed around modern feedback practices. Indian-origin platforms — Darwinbox, Keka, Zoho People — provide locally adapted capability that often fits Indian operating contexts more readily than global platforms. Talent and learning platforms — increasingly merged with performance capability — connect skill development directly to performance gaps. Analytics platforms — Visier, Crunchr, and analytics built into the major HCM suites — turn performance and people data into reporting and insight (T. V. Rao, 2008).

Figure 19.1: Categories of performance management technology

flowchart TB
    Org["Organisation's<br>technology choice"]

    Org --> HCM["INTEGRATED HCM<br>SUITES"]
    Org --> Spec["SPECIALIST<br>PLATFORMS"]
    Org --> Local["INDIAN-ORIGIN<br>PLATFORMS"]
    Org --> Learn["TALENT AND<br>LEARNING"]
    Org --> Anly["ANALYTICS<br>PLATFORMS"]

    HCM --> HCMex["Workday, SuccessFactors,<br>Oracle HCM, Cornerstone"]
    Spec --> SpecEx["Lattice, 15Five,<br>Betterworks, Culture Amp"]
    Local --> LocalEx["Darwinbox, Keka,<br>Zoho People"]
    Learn --> LearnEx["Coursera for Business,<br>LinkedIn Learning"]
    Anly --> AnlyEx["Visier, Crunchr,<br>built-in HCM analytics"]

    classDef org fill:#E8F0DC,stroke:#4A7A2E,stroke-width:2px,color:#2C2416
    classDef cat fill:#FAF7E8,stroke:#8B7355,stroke-width:2px,color:#2C2416
    classDef ex fill:#F4E4D4,stroke:#C95D3F,stroke-width:2px,color:#2C2416

    class Org org
    class HCM,Spec,Local,Learn,Anly cat
    class HCMex,SpecEx,LocalEx,LearnEx,AnlyEx ex

Choosing Among Categories

The choice among these categories depends on organisational scale, geographic reach, integration appetite, customisation needs, and budget. Large multinationals with global operations and existing HCM investments typically extend their HCM suite into performance management even when specialist platforms might offer better-fitting capability, because the integration value outweighs the functional gap. Mid-sized organisations with focused continuous-feedback needs often choose specialist platforms whose user experience is built around the practice they intend to embed. Indian organisations with predominantly domestic workforces frequently choose Indian-origin platforms whose handling of local payroll integration, statutory compliance, and operating context offers practical advantages. Each choice involves trade-offs, and there is no universally correct answer (S. R. Kandula, 2006).

19.4 What Technology Does Well

Scale and Visibility

Technology’s first and most obvious contribution is the scale at which it can operate. A paper-based performance management system in an organisation of fifty employees is workable; the same system in an organisation of fifty thousand is not. Technology makes the rituals of performance management — goal-setting, check-ins, reviews, ratings, calibration — practical at any scale. Alongside scale comes visibility: senior leaders can see, in near real-time, the state of goal-setting completion, review participation, and rating distributions across the entire organisation, in ways that paper-based systems could never have supported. The visibility itself changes management behaviour by exposing patterns that would otherwise have remained hidden in local practice (M. Armstrong, 2009).

Data Capture and Longitudinal Tracking

Technology captures data that human memory and paper records cannot reliably preserve. Conversation notes from one-on-ones, feedback comments from peers, goal-progress updates, calibration discussions — all of these accumulate into a longitudinal record that supports better decisions about development, promotion, and compensation than the impressionistic recall on which earlier eras depended. The longitudinal record also supports analytics that reveal patterns invisible in any single point-in-time view: the trajectory of an employee’s development over years, the consistency of a manager’s feedback practice, the comparative trajectory of cohorts hired into different roles. The data is only useful when it is captured carefully and interpreted with discipline, but its availability is the precondition for analytical work that earlier eras could not undertake (D. W. Bracken et al., 2001).

Ritual Reduction

A subtler but important contribution of technology is the reduction of low-value ritual that paper-based systems inflicted on managers. The hours spent compiling forms, transcribing comments, calculating ratings, distributing copies, filing originals — all of this consumed managerial time that produced little of developmental value. When technology eliminates these rituals, the time it frees can be redeployed to the conversations that genuinely matter. Whether organisations actually capture the freed time for higher-value use, or whether they simply absorb it into other administrative work, depends on choices the organisation makes about what to demand of managers. But the opportunity is real and substantial (H. Aguinis, 2013).

19.5 What Technology Does Poorly

The Substitution Trap

The most consequential failure of technology in performance management is the temptation to use it as a substitute for the managerial craft it was meant to support. A platform that prompts managers to enter quick comments at scheduled intervals does not produce the developmental conversation those comments are meant to capture; it produces typed text that satisfies the prompt. A goal-setting workflow that walks managers through structured prompts does not produce the strategic translation those goals should embody; it produces filled-in fields that meet the workflow’s requirements. The substitution trap is particularly seductive because it produces visible compliance — the platform reports show high engagement and complete records — while the underlying practice remains hollow. Organisations that monitor only the platform metrics and not the substantive quality of the conversations the platform supports are particularly susceptible to this pathology (M. Armstrong, 2009).

The Limits of Structured Capture

Performance management at its most valuable involves nuanced developmental conversations, judgement calls about competing considerations, and the exercise of empathy that no technology can replicate. The structured fields that technology provides — ratings, competency selections, drop-down options for performance dimensions — capture some of this work but inevitably distort it. A nuanced assessment that distinguishes a employee’s contributions across three dimensions becomes a single rating; an empathetic conversation about a personal situation becomes a coded note that risks misinterpretation when read later. Mature use of technology recognises these limits, captures structured data where it serves the organisation’s analytical needs, and protects the unstructured space within which the developmental work itself happens (J. Whitmore, 2009).

The Comparison Problem

Technology makes comparison across employees, teams, and units easy in ways that earlier systems did not. The ease of comparison is not always a benefit. Ratings displayed in calibration sessions invite the visual smoothing of distributions toward expected shapes regardless of actual performance. Dashboards that rank teams against each other invite gaming behaviours that distort the underlying activity. Public visibility of individual performance data, even within management circles, can produce defensive responses that suppress the candour required for honest assessment. The architects of performance management technology must make deliberate choices about what to make visible and to whom, and must recognise that visibility itself shapes behaviour rather than merely revealing it (A. N. Kluger & A. DeNisi, 1996).

19.6 AI-Adjacent Capabilities

The Emerging Capability Set

Performance management platforms have begun to incorporate capabilities that draw on machine learning and natural language processing techniques that have matured rapidly over the past several years. These include sentiment analysis applied to feedback text to detect tone and emotional valence, goal-drafting assistance that suggests goal language based on role and strategic context, bias detection in rating distributions and language patterns, and predictive analytics that forecast attrition risk based on engagement and performance signals. The capabilities are real, are improving rapidly, and are increasingly available in commercial platforms. Their value depends on how thoughtfully they are deployed and how candidly their limitations are acknowledged (H. Aguinis, 2013).

Where AI Capabilities Help

Several uses of these capabilities have shown genuine value. Sentiment analysis can flag feedback patterns that warrant attention — for example, a sustained negative tone in feedback to a particular employee that the manager may not have recognised — without making evaluative judgements itself. Goal-drafting assistance can give managers a starting point for goal language that they then refine, reducing the friction of the goal-setting workflow. Bias detection can surface patterns in rating distributions that suggest unconscious bias and can prompt human review. Predictive analytics can identify employees whose disengagement signals warrant a manager conversation before attrition becomes inevitable. In each case, the AI capability supports human judgement rather than replacing it (D. W. Bracken et al., 2001).

Where AI Capabilities Fail

The same capabilities, deployed badly, fail in characteristic ways. Sentiment analysis trained on one cultural context misclassifies tone in another, particularly across the linguistic and cultural diversity of Indian English usage. Goal-drafting assistance that is treated as a finished product rather than a starting point produces goals that look similar across the organisation and lose the specificity strategy requires. Bias detection that is interpreted as proof of bias rather than as a flag for inquiry can produce wrongful conclusions about individuals and undermine the credibility of the system. Predictive attrition models that are acted upon without human judgement risk creating self-fulfilling prophecies and discriminating against the patterns the model has learned to associate with attrition. The mature deployment of these capabilities pairs them consistently with human judgement and treats their outputs as inputs to decision-making rather than as decisions (A. N. Kluger & A. DeNisi, 1996).

19.7 Implementation Pitfalls

Process Automation Without Process Reform

The single most common implementation failure is the automation of an existing process whose underlying design was already broken. An organisation whose annual review process was producing rating compression, manager fatigue, and employee cynicism deploys a platform that supports the same process more efficiently and is surprised when the underlying problems persist. The technology investment was substantial; the process improvement was nil. Successful implementations begin with process design, identify what should change about the practice itself, and then deploy technology to support the new practice. Implementations that begin with technology selection and treat the practice as fixed produce automation of dysfunction (M. Armstrong, 2009).

Data Privacy and Consent

Performance management generates data that is, by its nature, sensitive: ratings, feedback, development concerns, sometimes notes on personal circumstances that affect performance. The handling of this data raises privacy questions that earlier paper-based systems addressed implicitly through limited circulation but that technology platforms must address explicitly through access controls, retention policies, and consent frameworks. The Digital Personal Data Protection Act and the global regulatory landscape impose specific obligations on personal data handling that performance management platforms must respect. Organisations that treat data privacy as a compliance afterthought rather than as a design principle expose themselves to legal, reputational, and trust-based risks that compound over time (P. Chadha, 2003).

Surveillance Anxiety

Performance management technology can produce, even when not so intended, the perception that employees are under continuous surveillance. Platforms that track keyboard activity, monitor application usage, or capture screen contents — capabilities that have become technically feasible and are sometimes marketed alongside performance management platforms — produce employee responses ranging from defensive caution to active resistance. Even platforms without these capabilities can produce surveillance anxiety when their visible scope and usage are not clearly bounded. Organisations that deploy performance management technology must be deliberate about what is monitored, transparent about it with employees, and disciplined about not creeping the scope of monitoring beyond what was originally communicated (A. C. Edmondson, 1999).

The Customisation Trap

Enterprise platforms typically offer extensive customisation capability, and large organisations often respond by customising the platform to fit existing processes in detail. The customised platform fits the organisation’s current state but creates technical debt that complicates upgrades, slows the adoption of new capability, and locks the organisation into practices that should themselves be evolving. The discipline of restrained customisation — fitting the organisation’s practice to the platform’s defaults where possible, and customising only where genuine differentiation requires it — produces a more sustainable long-term outcome than the customisation that initial deployment teams often pursue (H. Aguinis, 2013).

19.8 Change Management for Technology Rollouts

The Stakeholder Map

Performance management technology touches every employee in the organisation, but the rollout must engage specific stakeholder groups in different ways. Senior leaders need confidence that the platform supports the organisation’s strategic intent and provides the visibility they require. People managers need training in the platform’s workflows and confidence that it makes their work easier rather than harder. Employees need clear communication about what the platform does, what it does not do, and how their data is handled. HR business partners need deep capability with the platform so they can support managers and employees as questions arise. The IT function needs integration with the broader application landscape and ongoing support arrangements. Rollouts that engage these stakeholders unevenly — overinvesting in some, underinvesting in others — produce uneven adoption and lasting resistance from neglected groups (D. Ulrich, 1997).

Figure 19.2: A staged approach to technology rollout

flowchart LR
    Stage1["STAGE 1<br>Process design"] --> Stage2["STAGE 2<br>Platform selection"]
    Stage2 --> Stage3["STAGE 3<br>Configuration<br>and pilot"]
    Stage3 --> Stage4["STAGE 4<br>Training and<br>communication"]
    Stage4 --> Stage5["STAGE 5<br>Phased rollout"]
    Stage5 --> Stage6["STAGE 6<br>Monitoring and<br>refinement"]

    Stage1 -.- Note1["Decide what the<br>practice should be<br>before tooling"]
    Stage3 -.- Note2["Test with a<br>limited population<br>before scale"]
    Stage5 -.- Note3["Roll out by unit<br>or geography to<br>manage absorption"]
    Stage6 -.- Note4["Adjust configuration<br>based on observed<br>usage and feedback"]

    classDef stage fill:#E8F0DC,stroke:#4A7A2E,stroke-width:2px,color:#2C2416
    classDef note fill:#FAF7E8,stroke:#8B7355,stroke-width:1px,color:#2C2416

    class Stage1,Stage2,Stage3,Stage4,Stage5,Stage6 stage
    class Note1,Note2,Note3,Note4 note

The Pilot Discipline

Mature rollouts begin with a pilot deployment in a limited population — a single business unit, a single geography, a single function — that allows the organisation to learn what works and what does not before committing to enterprise-wide rollout. Pilots are most useful when they are run with the same rigour the full rollout will require: real training, real communication, real support, real measurement of outcomes. Token pilots that are not taken seriously produce optimistic results that do not survive the transition to scale. Honest pilots produce more sober results but ones the organisation can act on with confidence (M. Armstrong, 2009).

Sustaining Adoption Beyond Launch

The rollout phase that receives the most attention is launch, but the phase that determines long-term success is the year that follows. Adoption metrics typically peak in the months immediately after launch and then decline as the novelty wears off and as the daily friction of the platform becomes apparent. Organisations that sustain adoption do so through ongoing investment: regular communication that highlights successful use, refreshed training as the platform evolves, responsive support that resolves issues quickly, and iterative configuration changes that respond to user feedback. Organisations that treat the rollout as complete at launch see adoption decay until the platform becomes a compliance exercise rather than a working tool (S. R. Kandula, 2006).

19.9 The Indian Context

Hybrid Workforce Realities

Indian organisations frequently operate hybrid workforces that combine office-based knowledge workers, field-based sales and service teams, factory-floor operators, and increasingly distributed remote workers. Performance management technology that serves only the office-based knowledge worker — a common limitation of platforms designed for Western corporate environments — leaves substantial parts of the workforce out of the system. Successful Indian deployments typically combine a primary platform with adaptations or complementary tools that serve other workforce segments: mobile-first interfaces for field teams, simplified workflows for factory supervisors, offline capability for environments with intermittent connectivity. The integration challenge of these hybrid configurations is real but the alternative — separate systems for separate workforce segments — produces worse outcomes (T. V. Rao, 2008).

Regional Language and Accessibility

A workforce that includes employees whose primary language is not English requires performance management tooling that operates in regional languages. Major HCM platforms have added multilingual capability but the depth and quality varies, and many specialist platforms remain English-only. Indian-origin platforms typically lead on this dimension because their market demands it. Beyond language, accessibility considerations — interface design for users with limited prior computer exposure, mobile interfaces that work on basic smartphones rather than only on premium devices — affect whether the technology actually reaches the populations it is meant to serve. Decisions about technology that ignore these considerations produce systems that work well for some employees and exclude others (S. R. Kandula, 2006).

Data Residency and Regulatory Considerations

The regulatory landscape for personal data in India has evolved substantially in recent years, with the Digital Personal Data Protection Act establishing obligations on data fiduciaries that include consent management, purpose limitation, and rights of data principals. Performance management data falls within scope, and global platforms hosted outside India must address data-residency and cross-border transfer considerations. Organisations selecting performance management technology should evaluate the platform’s compliance posture with respect to current and emerging Indian regulation, and should be prepared for the regulatory environment to continue evolving. Treating regulatory considerations as a procurement-stage checklist that can be deferred is a common but increasingly risky pattern (P. Chadha, 2003).

19.10 Case Studies

Case Study: Biocon and Global HCM Platform Rollout

Biocon, India’s leading biopharmaceutical company with operations spanning research, manufacturing, and commercial functions across multiple geographies, undertook the deployment of a global integrated HCM platform through the late 2010s as part of a broader transformation of its people systems. The deployment scope included performance management alongside recruitment, learning, compensation, and analytics, and it spanned the company’s Indian operations and its international subsidiaries including Biocon Biologics and Syngene. The integration challenges were substantial: legacy systems had been deployed unevenly across business units, data quality varied, and process design had diverged across geographies in ways that the new platform’s defaults did not always accommodate. The deployment team chose a phased approach, beginning with the corporate functions and large operating units before extending to smaller and more specialised entities, and made deliberate choices to minimise customisation in favour of adapting practice to platform defaults where the differences were not strategically meaningful. Manager training was extensive, complemented by a network of platform champions in each business who provided peer support during the transition. The deployment took longer than initially projected, as such deployments typically do, and produced uneven adoption across business units in its first year before reaching steadier use as the practice embedded. The case illustrates both the genuine value of integrated HCM platforms in supporting performance management at global scale and the realistic timelines and effort that such deployments require, particularly in organisations whose pre-deployment landscape is complex.

Case Study: Zomato and Home-Grown Performance Tooling

Zomato, the food-delivery and restaurant-discovery platform, faced an unusual performance management challenge as it scaled rapidly through the late 2010s and into the 2020s. Its workforce comprises a relatively small core of corporate and engineering employees alongside a much larger gig-adjacent workforce of delivery partners whose performance management requirements differ fundamentally from those of the corporate workforce. For the corporate workforce, the company adopted modern continuous-feedback platforms that fit its young, technology-fluent employee base. For the delivery partner workforce, no off-the-shelf platform fit, and the company built proprietary tooling that combined real-time delivery metrics, customer feedback signals, location and timing data, and reliability scores into a performance signal that drove allocation, ratings, and earnings. The tooling raised questions about transparency to delivery partners, about the fairness of algorithmic allocation, about the appeal mechanisms available to partners who disputed metrics, and about the broader regulatory environment for gig-economy workforces in India. The company’s evolution of these systems through successive iterations reflects ongoing learning about what such tooling can and cannot do. The case illustrates that performance management technology in non-traditional workforce configurations may require purpose-built capability rather than adaptation of existing platforms, and that the design choices in such tooling carry significant implications not only for performance outcomes but for the broader social contract between the organisation and its workforce.

19.11 Summary

Summary

Technology is both enabler and constraint. Platforms amplify the practices they support, whether coherent or dysfunctional, and they shape what is recorded and therefore what is attended to. The craft of deployment is recognising both effects and managing them deliberately (H. Aguinis, 2013; M. Armstrong, 2009).
The evolution has been rapid and directional. Paper forms gave way to electronic forms and workflow, then to integrated HCM platforms, and most recently to specialist continuous-feedback platforms whose design embodies a different theory of what performance management is for. Each generation solves problems the last one could not and creates new ones of its own (D. W. Bracken et al., 2001; M. Buckingham & A. Goodall, 2015).
Platform categories serve different needs. Integrated HCM suites, specialist continuous-feedback platforms, Indian-origin platforms, talent and learning platforms, and analytics platforms each occupy a distinct niche. Choice depends on scale, geographic reach, integration appetite, customisation needs, and the practices the organisation intends to embed (M. Armstrong, 2009; P. Chadha, 2003).
Technology does some things very well. Scale, visibility, longitudinal data capture, workflow consistency, and ritual reduction are all genuine gains that manual systems cannot match, and organisations that ignore these benefits pay an avoidable tax in administrative overhead and missing information (H. Aguinis, 2013; S. R. Kandula, 2006).
The substitution trap is the central failure mode. When technology becomes a substitute for the managerial craft it was meant to support, when form completion substitutes for conversation and dashboard monitoring substitutes for observation, the organisation accumulates records without developing capability (M. Buckingham & A. Goodall, 2015; A. N. Kluger & A. DeNisi, 1996).
AI-adjacent capabilities cut both ways. Sentiment analysis, goal-drafting assistance, bias detection, and predictive analytics all offer genuine value when paired with human judgement and reveal characteristic failure modes when treated as substitutes for it. The discipline is knowing which is which (H. Aguinis, 2013; A. C. Edmondson, 1999).
Implementation pitfalls are predictable. Process automation without process reform, under-investment in data privacy and consent, surveillance anxiety from ambient monitoring, and the customisation trap that converts configurable platforms into unmaintainable bespoke systems are all recurring and all preventable with discipline (M. Armstrong, 2009; T. V. Rao, 2008).
Change management is the work. Technology rollouts are substantial undertakings that require stakeholder-specific engagement, honest piloting, and sustained investment beyond launch. Organisations that treat the go-live date as the finish line typically discover, months later, that the platform has settled into partial use (S. R. Kandula, 2006; J. Whitmore, 2009).
The Indian context adds its own requirements. Hybrid workforces, regional-language and accessibility needs, and the evolving regulatory landscape under the Digital Personal Data Protection Act make platform choice and configuration substantially different from what Western vendors default to (P. Chadha, 2003; T. V. Rao, 2008).
Case lessons: Biocon shows what disciplined deployment of a global integrated platform looks like in a complex biopharmaceutical organisation with scientific, manufacturing, and commercial populations. Zomato demonstrates that home-grown tooling, purpose-built for a gig-adjacent workforce, can outperform generic enterprise platforms when the workforce shape does not match what those platforms were designed for. Both affirm that performance management technology is infrastructure whose value depends on the practices, capabilities, and intent that surround it (S. R. Kandula, 2006; T. V. Rao, 2008).