Most of the businesses that come to BPro are not failing. They are growing faster than the way they manage people. This is an account of what a full performance management engagement actually looks like from the inside, written from BPro consulting practice with MSMEs in Kerala and across India. Client identities and commercially sensitive details are withheld under non-disclosure agreement, so what follows describes the work and the change in it, not a named organisation.
The situation these organisations arrive with
The pattern repeats almost word for word. A promoter-led business, somewhere between eighty and four hundred people, has grown on the strength of a founder who knew every employee by name and could judge performance by watching. Then it crossed a threshold. New locations opened. A second tier of managers came in. The founder could no longer see everything, and nothing had been built to see it in their place.
By the time BPro is called in, the symptoms are consistent:
- Appraisals happen once a year, are dreaded by both sides, and change nothing. Ratings cluster in the middle because no manager wants a difficult conversation.
- Good performers leave quietly. Exit interviews reveal they never knew where they stood or what advancement required.
- Promotions are contested. Without a defensible basis, every decision looks like favouritism, and in a family-run business that suspicion is corrosive.
- Managers describe their teams in adjectives rather than evidence. Sincere. Not proactive. Attitude problem. None of it is actionable.
- HR spends its month on payroll and leave, not on capability. There is no time left for the work that would actually compound.
- The founder is still the escalation point for decisions three levels down, and is exhausted by it.
Nobody in these organisations is lazy or ill-intentioned. What is missing is a shared, written definition of what good work looks like in each role, and a rhythm for checking against it. That is what the engagement builds.
Phase one: diagnosis before design
BPro does not begin with a system. It begins with two to three weeks of listening, because the stated problem is rarely the real one. A business that asks for an appraisal format often turns out to have a role clarity problem: two managers believe they own the same outcome, and a third believes nobody does.
The diagnostic covers the organisation structure as it exists on paper against how work actually flows; existing job descriptions, where they exist at all; the last two appraisal cycles and what happened as a result of them; attrition and its stated reasons; and unstructured conversations with a cross-section of employees, deliberately including people who are not in management.
That last group matters most. Senior teams describe the organisation they intend to run. Employees three levels down describe the one that exists. The distance between those two accounts is usually where the engagement will do its real work.
What commonly surfaces at this stage
- Job descriptions that were written for recruitment advertisements and never revisited, describing duties rather than outcomes.
- Two or three roles carrying the majority of institutional knowledge, with no succession behind them.
- Departments optimising against each other because each is measured on something the other has to sacrifice.
- A previous attempt at a performance system, abandoned within a year, which has left the workforce sceptical of the next one.
That last finding changes how the engagement is run. Where a failed system is in living memory, adoption has to be earned rather than announced, and the rollout is deliberately slower and more visible.
Phase two: defining what good actually looks like
This is the longest phase and the one that creates the value. Every role in scope gets a written set of Key Result Areas, and each KRA gets measures against which performance can be evidenced. The distinction between the two is where most in-house attempts fail, and it is worth reading our explanation of rolling out KRAs across an organisation alongside this.
The work is done with managers, not for them. A consultant drafting KRAs in isolation produces a document that is technically correct and organisationally dead. The workshops are uncomfortable by design, because they force questions that have been avoided for years: if two managers claim the same result, which one is accountable when it is missed? If a role has eleven priorities, which three actually determine whether the year was a success?
The rules that hold the framework together
- Five to seven KRAs per role. More than that is a list of activities, not a definition of the job.
- Every measure has a source. If the number cannot be produced from a system or a record that already exists, either the measure changes or the record gets built. Measures that depend on someone remembering do not survive contact with a busy quarter.
- Behavioural expectations are written and weighted, not left implicit. Otherwise the framework rewards results obtained in ways the organisation does not want repeated.
- Targets are agreed with the person who has to meet them. A target handed down is a target argued with all year.
- Nothing is measured that nobody intends to act on. Every metric that survives has a named decision attached to it.
Where BPro is also implementing the Performance Management System, this framework becomes its configuration. Where the client uses another platform, the framework is written to be portable.
Phase three: putting a system underneath the framework
A framework on paper degrades within one cycle. It needs somewhere to live. In most engagements this means implementing the HRMS so that employee records, leave, attendance and appraisal history sit in one place, and the PMS on top of it so that goal setting, mid-cycle reviews and final ratings follow a defined workflow rather than a chain of email attachments.
Organisations arriving from spreadsheets often underestimate this step, which is why we wrote separately about the point at which a business has outgrown Excel. The technical migration is rarely the hard part. The hard part is that a system makes visible what spreadsheets allowed to stay vague, and some of what becomes visible is uncomfortable.
Where repetitive back-office work is consuming disproportionate HR time, Process.ai is brought in to automate the routine transactions, on the reasoning that a system nobody has time to maintain is a system that will be abandoned.
Phase four: building the capability to use it
The most consistent finding across engagements is this: the framework is rarely what fails. The conversation is. Managers who have never been taught to give evidence-based feedback will avoid it, and a well-designed system administered by managers who dread using it produces well-formatted nothing.
So capability building runs alongside the rollout rather than after it. Manager training covers writing an observation rather than an adjective, holding a review where disagreement is allowed, separating the development conversation from the compensation conversation, and rating honestly when the organisational instinct is to cluster everyone at satisfactory.
Where the client has a Learning Management System in place, or implements one as part of the engagement, this content becomes permanent and available to managers promoted after the consultants have gone. That is deliberate. An engagement that leaves capability only in the heads of the people who attended the workshops has built something with a short half-life.
Phase five: making review a rhythm rather than an event
An annual appraisal is a poor instrument. Twelve months is long enough for a correctable problem to become a resignation, and for a manager to forget everything except the last six weeks. Engagements therefore establish a cadence: brief structured check-ins through the year, a substantive mid-cycle review where targets can legitimately be renegotiated against changed circumstances, and an annual review that should contain no surprises for either party.
Alongside it, HR data analytics gives the leadership team a view it did not previously have: where rating distributions are implausible and therefore where a manager needs support, which functions lose people and at what tenure, whether training is reaching the people whose reviews identified the gap. The point is not the dashboard. The point is that leadership acquires the habit of asking questions the organisation can now answer.
What changes, and what it feels like
BPro does not publish client performance figures, and any consultancy quoting precise percentage improvements from an engagement of this kind should be asked how the counterfactual was established. What can be described honestly is the qualitative change, which is consistent enough across engagements to be worth setting out.
| Area | Before the engagement | After a full cycle |
|---|---|---|
| Defining the job | Titles and inherited duty lists; two managers often claiming the same outcome | A written, agreed set of five to seven result areas per role, each with a measure and a source |
| The appraisal conversation | Once a year, adjective-based, dreaded, and disconnected from anything that follows | A short structured check-in each quarter and a mid-cycle review where targets can be renegotiated |
| Rating behaviour | Almost everyone rated satisfactory, because differentiation invites argument | Differentiation that managers can evidence, and are willing to defend in the room |
| Promotion decisions | Contested, read as favouritism, and difficult to explain to the person passed over | Traceable to a documented record that predates the decision |
| HR time | Consumed by payroll, leave and chasing forms | Released toward capability, succession and retention work |
| The founder | Escalation point for decisions three levels down | Reviewing the exceptions rather than adjudicating the routine |
| Evidence for decisions | Recollection, impression and whoever spoke most recently | A record the organisation can query, and increasingly does |
The change that clients themselves report first is almost never the one they engaged BPro for. They ask for an appraisal system. What they notice, a year in, is that arguments about who was responsible have largely stopped, because responsibility is written down and was agreed by the people it binds.
What made the difference
Across engagements that worked, four things were consistently present. Where an engagement struggled, at least one of them was missing.
- The promoter was visibly in it. Where the founder or managing director set their own KRAs first and had them reviewed like everyone else, adoption followed. Where performance management was delegated to HR as an administrative project, it was treated as one.
- The framework was built with managers, not delivered to them. Ownership cannot be retrofitted. Managers who argued their way through the design workshops defended the system afterwards; managers who received a finished document complied with it minimally.
- The first cycle was allowed to be imperfect. Organisations that waited for a flawless framework never launched. The ones that succeeded launched something defensible, ran it, and corrected it at the mid-cycle review with the evidence the cycle produced.
- Compensation was decoupled in year one. Where ratings drove increments from the first cycle, managers inflated them to protect their teams and the data was useless. Introducing the linkage in the second cycle, once managers trusted the process, produced ratings worth acting on.
What this kind of engagement does not do
It is worth being direct about the limits, because a consultancy that promises everything is a consultancy that will disappoint you specifically.
- It does not fix a compensation structure that is materially below market. A clear performance framework will simply tell a good employee, with evidence, that they deserve more than you are paying.
- It does not resolve a genuine strategic problem. If the business is unclear about which market it serves, cascading goals will cascade that confusion with new precision.
- It does not substitute for a manager who will not manage. The system makes avoidance visible; deciding what to do about it remains a leadership decision.
- It does not work in one cycle. The first cycle produces a baseline and exposes what was wrong with the design. The second is where the value appears. Organisations that abandon the effort after year one conclude, wrongly, that performance management does not work.
If this describes your organisation
If the symptoms at the top of this page were recognisable, the useful next step is a conversation about your specific situation rather than a proposal for a product. Our note on when an MSME actually needs an HR consultant is a reasonable place to start if you are still deciding, and why performance management matters for MSMEs sets out the underlying case.
BPro is based in Kochi, Kerala and works with organisations across India. Call +91 80869 08876, email care@bpropms.com, or use the contact form. You can also read more about BPro and Dr. Babu Balakrishnan.
A note on confidentiality. Client identities, sectors, locations, financial information and performance data are masked and withheld throughout this page under the non-disclosure arrangements BPro holds with its clients. This account is written as a composite of BPro consulting practice rather than a report on any single organisation, and no figures are attributed to any client. Where a prospective client requires verifiable references, BPro will arrange them directly and with the referring client’s consent.