Case study · Kerala · 2023 to present
From People-Dependent Management to a Process-Driven Performance Culture
How a 150-employee furniture manufacturing and retail organisation in Kerala built role clarity, performance discipline and management visibility — and why the work began with a board-level question rather than an appraisal form.
At a glance
| Industry | Furniture manufacturing and trading |
| Operations | Manufacturing unit plus multiple retail outlets |
| Geography | Cochin and Kerala |
| Ownership | Family-run, with the second generation taking greater responsibility |
| Engagement | Began 2023, continuing |
| Scope | Process architecture, role clarity, KRA and KPI design, performance management, reporting discipline, learning systems, pay for performance, management dashboards |
The client's identity and confidential operational information are withheld.
The situation
The organisation had successfully built a substantial manufacturing and retail operation. Its growing scale was creating a different problem: the business was becoming increasingly dependent on individual people, personal experience and informal process.
The promoters were dealing with customer satisfaction concerns, process gaps, appraisal disputes, inconsistent performance measurement, uneven role clarity, dependence on key individuals, and difficulty connecting what people did each day to what the organisation was trying to achieve.
That is a larger problem than a new appraisal format. What the organisation needed was an operating framework in which people knew what to do, managers knew what to review, leadership knew what was happening, performance could be measured, problems surfaced earlier, and organisational goals reached every level of the business.
The board-level question
How does the organisation move to the next level of professional and process-oriented management?
That was the assignment as it arrived — not a request for software, and not a request for an HR system. So the engagement started with observation and diagnosis: existing processes were studied, gaps identified, and the organisation's people, processes and management practices analysed before anything was recommended.
The diagnostic pointed to a missing chain of alignment:
Business goals → processes → roles → KRAs → KPIs → performance → review → reward.
Each link existed somewhere in the organisation. They were not connected to each other. That became the foundation of the programme.
The stakes of getting that chain right are not specific to this one organisation. Gallup's 2012 research on Indian workplaces found that only 1% of employees who felt unclear about how their performance was evaluated were engaged at work, against 66% of those who felt the criteria were clear — the largest single engagement gap the study measured. (Source: Gallup) A broken chain from business goal to individual KRA is exactly the kind of ambiguity that produces that gap.
What was built
Process observation and remapping
Existing workflows were studied for process, responsibility, communication and reporting gaps, dependencies on individuals, and opportunities to standardise. Processes were then remapped so ownership and execution were unambiguous.
Job description to KRA to KPI
A structured performance architecture across roughly 20 role categories, so that people were not simply given a designation and a list of duties but understood the result expected of the role.
Goal and role clarity, top to bottom
Organisational goals cascaded into departmental and individual responsibility. The management question shifted from what work did you do to what result were you responsible for, what was planned, what was achieved, and what happens next.
A six-level reporting architecture
Daily through yearly reporting designed to work in tandem rather than as separate documents, so daily activity feeds weekly, monthly, quarterly and annual visibility.
A fixed review rhythm
Teams meet on scheduled days to review activity, progress, issues and priorities. Monthly review widens to department and organisation level; quarterly and above consolidate for leadership planning. Event-driven management gave way to calendar-driven discipline.
Performance management and pay for performance
A structured performance management system connecting role, goal, performance, review, recognition and reward — giving appraisal conversations a documented basis and addressing the disputes that had prompted the engagement.
Learning management system
An LMS introduced as part of the performance ecosystem rather than as an isolated training platform, giving structure to capability development and letting learning activity be tracked.
Power BI management dashboards
Dashboards for the managing director, directors and department heads, giving leadership a common information layer instead of separate reports arriving from separate departments.
The reporting architecture
Six horizons, designed to feed each other. The daily report is where the discipline actually lives; everything above it is consolidation.
| Level | Report | What it answers |
|---|---|---|
| DWR | Daily Working Report | What was planned, what was completed, what is pending, what are today's priorities |
| WWR | Weekly Working Report | What moved this week, what is blocked, what needs a decision |
| MWR | Monthly Working Report | How the department performed against plan |
| QWR | Quarterly Working Report | Whether the quarter's commitments were met, and what needs correcting |
| HWR | Half-Yearly Working Report | Whether the year is on track, and where intervention is required |
| YWR | Yearly Working Report | Annual performance, as a summary of recorded evidence |
The daily report captures what was planned, what was completed, progress made, planned versus unplanned work, supporting evidence, pending items and the next day's priorities. The underlying loop is deliberately simple: plan, execute, record, review, improve. Digital platforms were later built to submit and consolidate these reports.
Anything that is not documented is not discussed.
The intention was never bureaucracy. It was to ensure management conversations rested on facts, records, activities, results and defined responsibilities rather than on competing recollections. Alongside it ran a second principle: appreciate publicly, correct privately — accountability without cost to anyone's dignity.
What changed
| Before | After |
|---|---|
| People-dependent execution | Process-oriented execution |
| Variable role clarity | Defined role responsibilities |
| Informal performance discussions | Structured performance management system |
| Appraisal disputes | KRA and KPI-based review with a documented basis |
| Fragmented reporting | A connected daily-to-yearly architecture |
| Verbal communication | Documented communication |
| Reactive follow-up | Scheduled weekly reviews |
| Periodic appraisal focus | Continuous performance management |
| Individual interpretations | A common performance framework |
| Manual and fragmented information | Digital reporting |
| Limited management visibility | Dashboards for MD, directors and department heads |
| Informal learning | LMS-supported capability development |
The most significant change was not any single system. It was the emergence of a common organisational performance language — employees, managers, department heads and leadership operating around the same framework: goal, activity, result, review, improvement.
What is measured, and what is observed
This distinction matters, so it is worth stating plainly rather than blurring it.
Countable
Around 150 employees covered. Roughly 20 distinct role categories mapped to result areas and indicators. A six-level reporting architecture in operation. Three supporting technologies — performance management, learning management and Power BI. An engagement running continuously since 2023.
Observed, not measured
The organisational changes described above are reported as observed rather than measured, because the historical baseline was not consistently captured against every metric before the work began. Presenting them as precise percentage improvements would overstate what the evidence supports.
That is a common situation in organisations at this stage, and it is itself part of the argument for the work: an organisation that cannot describe its own baseline cannot tell whether anything it does is helping. One outcome of an engagement like this is that the next change becomes measurable.
Why this was broader than an HR assignment
The organisation was not given a new appraisal form. The intervention addressed the management operating system itself, connecting eight things that had previously been handled separately.
- 1 Strategy — what does the organisation want to achieve?
- 2 Process — how should the organisation work?
- 3 Role — who is responsible?
- 4 KRA and KPI — what result is expected, and how is it evidenced?
- 5 Reporting — what actually happened?
- 6 Review — what needs attention?
- 7 Performance — how did the individual and the team perform?
- 8 Reward — how should performance be recognised?
Connecting those eight is what made this a management transformation rather than a conventional HR consulting assignment.
What transfers to other organisations
Process comes before technology
Digital systems work only when the underlying process is clear. Software laid over an undefined process automates the confusion at greater expense.
Role clarity is the foundation
People cannot deliver results consistently when the expectation was never defined. Most appraisal disputes are role-definition failures surfacing late.
Annual review alone is not enough
For a growing organisation, performance has to be visible continuously. The annual conversation should summarise something already tracked.
Documentation changes the conversation
What happened becomes answerable when activity and results are recorded. That single shift removes most of the heat from review meetings.
Dashboards must support decisions
Power BI earned its place because it was connected to the wider performance architecture, not because it displayed data attractively.
Culture follows the management system
When goals, reporting, review and recognition become consistent, professional working habits become easier to sustain than to avoid.
The consultant's view
The objective was never to make the organisation dependent on the consultant. The objective was to build a management system that the organisation could continue to operate by itself.
A growing organisation cannot remain permanently dependent on the memory, intervention and personal supervision of a few key people. At a certain point it has to move from people-dependent to process-dependent, from informal to documented, from activity-focused to result-focused, from periodic appraisal to continuous performance management, and from management by perception to management by information.
This engagement was about enabling that transition. — Dr. Babu Balakrishnan
Frequently Asked Questions
What kind of organisation was this?
A family-run furniture manufacturing and retail business in Kerala with around 150 employees, operating a manufacturing unit alongside multiple retail outlets. Roughly 20 distinct role categories were mapped during the engagement. The client's identity is withheld.
Why did they engage a consultant rather than buy software?
The presenting question was a board-level one: how does the organisation move to the next level of professional, process-oriented management? Software administers a process; it does not decide what a role should be accountable for. The engagement began with observation and diagnosis rather than a product recommendation.
How long has the engagement run?
It began in 2023 and is ongoing. What started as a board-level diagnostic grew into a transformation covering process architecture, role clarity, KRA and KPI design, performance management, reporting discipline, learning systems, pay for performance and management dashboards.
What is the DWR to YWR architecture?
A connected reporting rhythm across six horizons - daily, weekly, monthly, quarterly, half-yearly and yearly. The point is that these are not independent reports. Daily activity feeds weekly review, which consolidates upward, so annual performance is a summary of recorded evidence rather than a recollection.
Were the results measured?
Partly, and this page is explicit about the difference. Implementation facts are countable - around 150 employees, roughly 20 role categories, a six-level reporting architecture, three supporting technologies. The organisational changes are described as observed rather than measured, because the historical baseline was not consistently captured before the work began.
Would this approach suit a smaller organisation?
The architecture would be lighter but the sequence is the same. Below roughly thirty people a full system is usually heavier than the organisation needs; a simpler goal-setting and review structure is more honest. The judgement about which applies is part of the initial diagnostic.
If your organisation is at the same transition
The signal is usually recognisable: the business has outgrown the point where the promoter can assess everyone personally, and appraisal season has started producing arguments rather than decisions. A short conversation is enough to tell whether a full system is warranted or something lighter would serve better.
More on performance management
Case Study: 150-Employee Furniture Manufacturer
From people-dependent management to role clarity, KRA-based review and dashboard visibility. Kerala, 2023 to present.
Performance Management Consulting in Kerala
How a performance system is designed and implemented for a growing organisation, and what an engagement actually involves.
Kochi and Ernakulam
Multi-location retail, logistics, seafood export, IT services and manufacturing - where the measure should sit in each.
KRA and KPI Design
The difference between result areas and indicators, with worked examples for production, quality, sales, finance and HR roles.
Free KRA and KPI Template
An eight-sheet Excel workbook with worked result areas for six common roles, plus a blank template. No email required.