OKR for Small Business India: Why You Probably Need KPIs First

It is week three of the quarter. The whiteboard in the founder's cabin still carries five objectives and fifteen key results, written in three colours during an offsite that everyone enjoyed. Ask the sales head whether KR 2.1 has moved and he will tell you it's progressing. Ask him by how much, and the room goes quiet.

In the businesses I work with, this is the standard failure mode of OKR for small business India has imported wholesale from Silicon Valley. It has almost nothing to do with the framework being wrong. It has to do with sequence. OKRs are an instrument for changing a business. They assume you can already measure the business. Adopt them in the opposite order and you end up with quarterly ambitions nobody can verify, which is a worse position than having no framework at all, because now the failure is documented.

Two instruments, two different jobs

A KPI is a vital sign. It tells you how the business is doing at the thing it already does: gross margin, on-time dispatch, collection days, repeat order rate. It runs continuously, it has no end date, and a good one is boring. You want it stable or slowly improving. Nobody celebrates a heartbeat.

An OKR is a change instrument. An Objective is the qualitative thing you want to be true by the end of a quarter, and the Key Results are the two to four numbers that would prove it. It is time-boxed by design. It exists to move something that isn't moving on its own.

The lineage matters here, because it's routinely skipped. Andy Grove developed OKRs at Intel in the 1970s, adapting Peter Drucker's Management by Objectives into something with sharper measurement teeth. John Doerr carried the method from Intel to Google in 1999, and later wrote Measure What Matters, which is how it reached most Indian founders.

What that story leaves out is the substrate. Intel in the 1970s was a semiconductor manufacturer already running detailed operational measurement: yields, cycle times, defect rates, cost per unit. Grove did not invent OKRs to create measurement discipline. He invented them because the measurement discipline existed, and he needed a way to point it at the things that were changing.

The scale mismatch is the second thing that gets skipped. India has crossed 7.83 crore enterprises registered on the Udyam portal, according to the Ministry of MSME, and the overwhelming majority are micro and small. A firm with 40 people and no finance function is reading a book about a company that had thousands of engineers and a controller in every division. The framework survives the translation. The assumptions underneath it do not.

Why KPI discipline has to come first

Three specific things break when a small business runs OKRs on a weak measurement base.

You cannot write a key result without a baseline

"Increase repeat order rate from 18% to 30%" is a usable key result. That 18% is a KPI. If the business does not already produce that number every month, from the same source, calculated the same way, then the key result is a wish with a decimal point attached.

The failure is quiet. The team will nod, because everyone would like more repeat orders. Nobody will notice for eight weeks that there is no way to tell whether the work is doing anything.

The tell is easy to check. Pick any key result in your current set and ask what the number was last month. If nobody can answer within a minute, that key result is decorative.

The numbers exist but they disagree

This is the more common condition in Indian MSMEs, and it is more dangerous than having no data at all. Sales reports one dispatch figure, the plant reports another, and accounts reconciles to a third at month end. All three are honest. They are counting different things, being order booked, material out of gate, and invoice raised, and nobody has ever forced the definitions to agree because until now nothing depended on it.

The moment you build an OKR on top of that, you have a quarterly review where two managers argue about whose number is right instead of what to do next. KPI consulting for MSME India, done properly, is mostly this unglamorous work: agreeing definitions, fixing the source, and getting to one number everyone accepts even when they dislike it.

There is no review rhythm to hang it on

OKRs need a weekly cadence. Not a meeting, but a rhythm, where the same short set of numbers gets looked at by the same people, and last week's commitment gets closed before this week's is made. Most small businesses have a monthly sales review that expands to fill three hours, and a lot of firefighting in between. Dropping OKRs into that produces ceremony without accountability.

Think of it this way. OKRs are physiotherapy: a deliberate, effortful programme to make a specific thing work better than it currently does. KPIs are the ability to take a pulse. No competent physiotherapist starts a rehab programme on a patient nobody can monitor. The programme might even be the right one. You would have no way of knowing.

Where OKRs earn their place

None of this is an argument against OKRs. It is an argument about placement, and there is a clear condition that makes them worth the overhead: the business faces a discontinuity.

A new channel it has never sold through. A geography it has no relationships in. A product line that has to work this financial year or be shut. A founder handing operational control to the next generation. In each case, the thing you need to happen is not on any existing KPI, because the business has never done it before. Continuous metrics are useless for discontinuous change. That is the gap OKRs fill, and it is why the good ones feel uncomfortable when you write them.

Two rules keep them from metastasising in a small firm.

One objective, three key results, one quarter. Not per department. For the company. A 50-person business has roughly one thing it can change in ninety days while continuing to trade. Everything beyond that is a list. If you have run OKRs before and found them exhausting, the volume was almost certainly the cause. I have written before about why less is more when introducing OKRs to an Indian MSME, and the arithmetic is unforgiving at small scale.

Never convert a KPI into a key result. "Maintain gross margin at 34%" is not an OKR. It is a KPI with a ribbon on it, and putting it in the quarterly set trains everyone to believe that OKRs are the old targets in new language. The reverse error is subtler: a key result that succeeds and then quietly stays on the board for four quarters. When a change lands, it stops being an OKR and becomes a KPI. Move it, and free the slot.

Running both without building a bureaucracy

The whole system fits on one page, and it should.

Six to eight KPIs, reviewed monthly, covering the health of the business as it runs today. One or two each for demand, delivery, cash, and people. Each has a named owner and a floor rather than a target. The floor is the number below which you have a problem regardless of what else is going well.

One OKR set, reviewed weekly, for the thing that has to change. Fifteen minutes. What moved, what didn't, what's blocked, who is unblocking it.

The interesting design question is what happens when the two conflict, and in a small business they will. The new channel needs credit terms that stretch your collection days past the floor. The answer is that the KPI floor wins. A business that hits its quarterly objective and breaks its cash cycle has not succeeded at anything; it has bought a change it cannot afford to keep. The floors are what make ambition survivable, and building accountability systems that hold without adding bureaucracy is largely a matter of deciding that hierarchy in advance, in calm conditions, rather than in the week it bites.

The strongest objection

Here is the fair version of the case against everything above.

You will never get to OKRs if you wait for the data to be ready, because the data is never ready. The reason OKRs work is that they force measurement into existence. You commit publicly to moving a number, and within three weeks somebody has built the report that tracks it, because the commitment made it necessary. Waiting for clean KPIs is how a business waits forever.

That objection is right often enough to deserve a real concession. In a business of fifteen people where the founder personally sees every order, every collection and every customer complaint, the founder is the measurement system. Running a single OKR there works, and it works precisely because the forcing function has a competent instrument behind it. Grove would recognise the setup.

The limit is scale, and it arrives faster than founders expect. Somewhere between forty and eighty people, the founder stops being able to hold the business in their head. The reports that the OKR was supposed to force into existence get built by four different people to four different definitions, because nobody was arbitrating. That is the point at which the forcing function stops producing measurement and starts producing arguments. It is also, usually, the exact point at which someone suggests adopting OKRs properly, with a tool.

What the choice is really about

Framing OKR versus KPI as a choice is the error. They answer different questions, and which one you need is a diagnosis rather than a preference.

If your business does roughly the right things and does them less well than it should, with margins slipping, deliveries late and collections drifting, you have a KPI problem. No amount of quarterly ambition fixes an execution baseline. If your business does the right things well and they are no longer sufficient, because the market moved or the customer changed or growth has flattened at a ceiling, you have an OKR problem. You will still need the KPIs, because that is what you steer by while you change.

Which makes the first question for any small business owner simpler and more uncomfortable than picking a framework. Name the six numbers that tell you whether this business is healthy, and say when you last looked at all six together. Whatever you answer determines where you start.

About Prem Menon

Prem Menon is the founder of Simpleworks Consulting, working with MSME founders and growth-stage businesses across India to turn strategy into execution. With experience spanning manufacturing, SaaS, retail, and professional services, Prem brings a practitioner's eye to the problems most consultants only theorise about.

Not sure whether you need better metrics or a better goal system?

Book a free first conversation with Prem Menon →