Performance & Execution · Service

Agile performance management, installed without losing rigour

Move from annual appraisals to continuous, agile performance management — check-in cadence, goal architecture and rating philosophy designed for your organisation, piloted on real teams, and scaled with managers who can actually run it.

1–2 quartersPilot → scaleWorks with your HRMSMeasured at both ends

19+ years · 600+ organisations · 23 sectors · Mumbai, Bengaluru, Delhi NCR and the GCC

Annual → continuous

What the redesign changes

How it works
From one annual appraisal to a weekly check-in rhythm A flat line with a single annual spike becomes a steady weekly pulse; the new rhythm is piloted on one team and rolled out across the organisation, built on check-in cadence, goal architecture and rating philosophy. ONCE A YEAR EVERY WEEK Same managers, a new rhythm the organisation can keep PILOT, THEN SCALE One real team first Then every team, quarter by quarter Check-in cadenceGoal architectureRating philosophy
Designed, piloted, then scaled. Cadence is a design property, not a personality trait.
01 · The definition

What is agile performance management?

Agile performance management is the practice of running goals, feedback and development in short, continuous cycles — weekly check-ins, quarterly goal resets, evidence gathered as work happens — instead of compressing a year of performance into one annual appraisal event.

The name borrows from agile software delivery deliberately: shorter loops, faster correction, decisions made on current evidence rather than ten-month-old memory. Harvard Business Review’s account of the performance management revolution traces how large employers abandoned the annual verdict for exactly this reason. Applied well, the same logic replaces the year-end event with a working rhythm — and the appraisal stops being something anyone dreads, because nothing in it is news.

Continuous cadence

Performance is managed weekly and reset quarterly — the rhythm is the system, not the paperwork.

Evidence over recency

Decisions draw on a running record of check-ins and outcomes, not on whatever happened in the last six weeks before the review.

Manager as coach

The manager’s job shifts from year-end judge to weekly enabler — which is why enablement, not software, decides whether agile performance management works.

02 · Who this is for

Three situations that bring organisations to this service

The distrusted annual cycle

Your appraisal runs on time and everyone — HR included — privately agrees the ratings measure recency and rapport, not contribution.

The stalled software rollout

A continuous performance management platform was bought eighteen months ago; check-in adoption peaked in month two and managers quietly reverted to the old rhythm.

The scaling organisation

Headcount doubled, the annual cycle can’t keep pace with role changes, and goals set in April are fiction by August.

03 · The comparison

Agile versus traditional: what actually changes

The shift is not paperwork moving online — it is seven design decisions made differently. This is the honest comparison we walk boards through.

Design decision
Traditional annual cycle
Agile performance management
Goal setting
Annual cascade, fixed for the year — obsolete by the first re-org.
Quarterly reset against current strategy; goals track the business, not the calendar.
Feedback
Saved up for the year-end conversation; delivered as verdict.
Weekly or fortnightly check-ins; feedback lands while the work can still change.
Ratings
Forced distribution against a bell curve; calibrated by advocacy.
Kept, simplified or retired by design — and calibrated on a year of check-in evidence.
Manager’s role
Judge, once a year, on memory.
Coach, every week, on record — the load-bearing wall of the system.
Evidence
Recency and impression; the last quarter outweighs the first three.
Continuous telemetry: check-in adherence, goal movement, capability baselines.
Course correction
Discovered in month ten, fixed next year.
Surfaced the week it happens; the cadence is the early-warning system.
Admin load
A season-long crush of forms for HR and managers alike.
Distributed into the rhythm of work; the year-end event shrinks to a summary.

Every row is a decision made explicitly in the Design phase — nothing changes by default.

04 · What's included

Six deliverables, one working system

Design blueprint

Goal architecture, check-in cadence and rating philosophy — the agile PMS framework documented for your context, not a template.

Pilot cohort

Two to four real teams run the new rhythm for a full cycle before anything scales.

Manager enablement sprints

Working sessions on continuous feedback and check-in quality — the conversations that make continuous feedback performance management real.

HRMS configuration guidance

We design; your platform team configures — with our specification, whichever system you run.

Rollout & communication kit

Phased rollout plan, leader talking points and the FAQ your workforce will actually ask.

Baseline & re-measure

Check-in adherence, goal alignment and manager capability (DNA-25 where in scope) — before and after, reported honestly.

05 · How it works

Annual to agile in four phases

Weeks 1–3

Diagnose

Current-cycle audit, manager capability baseline and cadence data — we find where the existing system actually fails before designing its replacement.

Weeks 4–7

Design

Goal architecture, check-in rhythm and the rating question every agile performance appraisal system must answer: keep ratings, change them, or retire them — decided with evidence.

Weeks 8–16

Pilot

Real teams, full cycle, weekly telemetry. The pilot’s job is to break the design cheaply — what survives it scales with credibility no memo can buy.

Weeks 17–24

Scale & sustain

Phased rollout with manager enablement ahead of each wave, then re-measurement against the baseline — and a handover your HR team can run without us.

06 · Who benefits

What changes for the business, the leaders, the employees — and your customers

A performance system touches everyone; a redesign should be able to say what each of them gets. This is what the shift to agile performance management looks like from four seats.

The businessStrategy that survives contact with the quarter

Quarterly goal resets keep execution pointed at current strategy, misses surface in weeks instead of months, and resource reallocation happens while it still matters. The performance system becomes an execution instrument, not an HR ritual.

Watch: goal–strategy alignment, time-to-correction
Leaders & managersA coaching rhythm instead of a year-end reckoning

Fifteen-minute check-ins replace the dreaded annual marathon; the running record replaces memory in calibration; and the manager walks into every rating conversation with evidence instead of advocacy. Managing performance becomes part of managing, not an event beside it.

Watch: check-in adherence, calibration disputes
EmployeesClarity now, fairness on record, no year-end surprises

Everyone knows what this quarter asks of them, feedback arrives while it can still help, and the appraisal — where kept — summarises a year both sides watched happen. Perceived fairness rises for the least glamorous reason: the evidence exists.

Watch: rating-acceptance, regrettable attrition
CustomersThe seat everyone forgets — and the one that pays for it all

Teams aligned to outcomes and correcting weekly respond to customer signals in days, not review cycles. Service quality stops depending on which quarter it is, because the system managing the people who serve customers no longer runs on an annual clock.

Watch: complaint-to-fix time, delivery consistency
07 · Proof, on the record

What this work has delivered for clients

Agile performance management is accountable to adherence, alignment and manager confidence — measured at both ends of every engagement. Until the first measured case is published, here is the scale of the performance-system work already on the record.

430roles given key result areas and measures, so every appraisal had a written standard to rate againstBajaj Finance
~350employees moved onto one continuous performance and execution system, company-wideBrowserStack
2senior grades trained in appraisal skills, so the framework was used in the conversation rather than filedBajaj Finance

Evidence standard: delivered at scale. Business figures are the client’s own; our work ran alongside them, and we say so. The full write-ups, with situation, what we did and why it worked, are on the case studies page.

Where we work: an agile performance system for teams in Mumbai and Pune, continuous performance reviews India-wide, agile appraisals Mumbai and Delhi NCR organisations can run inside the HRMS they already own, weekly performance check-ins built into the rhythm, and continuous PM Bengaluru and Hyderabad capability centres can keep even when the parent company’s cycle stays annual. Continuous performance management India can trust is designed on site and runs wherever your managers are.

At a glance

Duration1–2 quarters
FormatDesign → pilot → scale
Delivered bySenior practitioners
PlatformWorks with your HRMS
MeasurementBaseline + re-measure
← Part of the Performance & Execution practice

Enquire about this service

Tell us where performance is slipping — a senior practitioner replies within one working day. No sales sequence, no juniors.

We use these details only to respond to your enquiry. We don't share them or add you to a mailing list. See our Privacy Policy.

08 · Practical questions

Agile performance management, asked the way buyers ask it

Do we have to give up ratings and the bell curve?

No — that's a design decision, not a precondition. Some organisations keep simplified ratings fed by continuous check-in evidence; others move to calibrated narratives. The design phase puts real data behind the choice, and whichever you pick, the forced bell curve almost never survives contact with the evidence.

How does this work with our existing HRMS or performance platform?

We design the system; your platform carries it. The blueprint ships as a configuration specification your HRMS team or vendor implements — whether you run an enterprise suite or an India-market platform. If the diagnostic shows the platform itself is the constraint, we say so before you spend on redesign.

What's the realistic timeline, and how big should the pilot be?

One to two quarters end to end: design inside seven weeks, a full pilot cycle by week sixteen, scaled rollout by week twenty-four. Pilots run best with two to four intact teams — enough variety to break the design where it's weak, small enough to fix it fast.

What does agile performance management actually ask of our managers, week to week?

One structured check-in per direct report per cycle — typically 15 to 20 minutes weekly or fortnightly — plus a short quarterly conversation replacing the annual marathon. The enablement sprints exist because the constraint is never the calendar; it's whether managers can hold a useful check-in. We build that.

Can we run the annual cycle and continuous check-ins in parallel while we transition?

Yes, and for one cycle you probably should — the pilot runs the continuous rhythm inside the pilot teams while the rest of the organisation completes the existing cycle. What we don't recommend is a permanent hybrid: two systems of record for performance is how both lose credibility.

How is the engagement priced?

Fixed-fee by phase, scoped after the diagnostic — so you're never funding an open-ended transformation. Mid-market economics with senior practitioners on every engagement; the diagnostic itself tells you the scope before you commit to the whole journey.

Ready to retire the annual appraisal?

Start with the diagnostic — it tells you whether agile performance management is your constraint, or whether the honest answer is somewhere else in the system.