OKR Consulting for Indian MSMEs: Why Less Is More

A mid-sized manufacturer in Pune came to me with a detailed OKR spreadsheet. Forty-seven objectives across six departments. Each had three to five key results, nested sub-goals, and a weekly review cadence that required two hours every Monday morning. The system had been running for eight months.

Revenue had barely moved.

OKR consulting in India has grown rapidly — and so has a particular kind of implementation mistake. Founders read about OKRs at Google, Spotify, Intel. They buy the book, hire a consultant who gives them a 60-slide deck, and end up with a goal system so complex it becomes a second job. This post makes a simple argument: the OKR framework that works for Indian MSMEs is radically different from the one Silicon Valley exports. Less structure. Fewer goals. More ruthless prioritisation.

Why OKRs Were Built for a Different Kind of Business

OKR stands for Objectives and Key Results. Andy Grove developed it at Intel in the 1970s. John Doerr brought it to Google in 1999. In Measure What Matters (2018), Doerr catalogued its success: Google grew from 40 to 60,000 employees partly on the back of this system. That origin story is important — and almost nobody mentions it when they sell OKRs to a 50-person business in India.

Google in 1999 had $220 million in Series A funding, world-class engineers, and a product already winning. The OKR system helped it coordinate at scale. An MSME with ₹15 crore in revenue, a team of 40, and a founder who still handles customer escalations personally has a fundamentally different problem. It doesn't need coordination machinery. It needs clarity on the three things that matter most right now — and a way to make sure the team is actually working on them.

The mistake is not adopting OKRs. The mistake is adopting the architecture of OKRs without adjusting for the operating context.

Why Complex OKR Systems Fail in Founder-Led Indian Businesses

There is a predictable pattern in how OKR implementations unravel in Indian MSMEs. It goes like this:

Month 1: High energy. The team sets objectives for every function — sales, operations, HR, finance. Each objective gets multiple key results. The CEO has eight objectives personally.

Month 2: Reviews start slipping. Updating the system takes longer than the actual work it was meant to track.

Month 3: The OKR spreadsheet becomes a compliance exercise. People fill it in after the fact to show progress.

Month 4: It quietly dies.

The failure is not motivational or cultural — it's structural. Complex OKR systems assume three things that are rarely true in a 50-person Indian MSME: that the team has bandwidth for meta-work (thinking about work, not just doing it), that roles are clear enough that individuals can own objectives independently, and that the business has stable enough operating conditions that quarterly goals survive contact with the market.

In most Indian MSMEs, none of these are reliably true. The OKR consultant who doesn't account for this is selling a system the business cannot absorb.

As an OKR consultant working with Indian MSMEs, I've seen this pattern across manufacturing, retail, SaaS, and professional services. The problem is almost never goal-setting ability. It's goal system design.

The OKR Framework for MSME That Actually Works

The right OKR framework for a small business in India is not a simplified version of the Google system. It's a different system that shares the vocabulary.

Here is what it looks like in practice:

One company objective. Not five. Not eight. One. The question is: what is the single most important thing this business needs to achieve in the next 90 days? Everything else is either an input to that goal or a distraction from it. Forcing this choice is uncomfortable — founders resist it because it means saying no to things that matter. That discomfort is the point.

Three key results. Not seven. Three measurable outcomes that would prove the objective was achieved. They should be specific, time-bound, and owned by named individuals — not departments. "Increase revenue" is not a key result. "Close ₹40 lakh in new B2B contracts by September 30, led by Rajesh" is.

Fortnightly check-ins, not weekly reviews. Weekly OKR reviews kill momentum in small teams. A 90-minute Monday meeting dedicated to updating a spreadsheet is ₹15,000 of salary walking out the door before the week starts. Fortnightly 30-minute check-ins — focused entirely on blockers, not status — work better for Indian MSME teams.

No cascading until you've run the system for two cycles. The allure of OKR consulting is often the cascade: company OKRs flowing down to team OKRs, then to individual OKRs. For a 50-person business in its first OKR cycle, it's also a great way to create three months of alignment theatre and zero execution. Start with company-level OKRs only. Let the team see how it works. Add the next layer after you know the system holds.

For more on how Simpleworks approaches OKR implementation and accountability design, visit the Simpleworks Consulting homepage.

What OKR Consulting in India Should Actually Deliver

An OKR consultant is not a software vendor, a workshop facilitator, or a strategy auditor. The job is to do three things: help the founder identify the right single objective, design the key results with enough rigour that they can't be gamed, and build the review rhythm the team will actually sustain.

That's it. Done well, it takes about six weeks for the first cycle — two weeks of diagnostic and design, one cycle of 90-day execution, and a retrospective.

What it does not require: a dedicated OKR platform (Google Sheets works fine for teams under 200), a weekly all-hands, or a training programme that runs longer than the first OKR cycle itself.

The Indian MSME founders I work with through Simpleworks Consulting consistently report the same two outcomes from a well-run first OKR cycle: the team finally understands what the business is trying to do this quarter, and the founder stops firefighting as much because people make better decisions independently. Neither of these outcomes requires forty-seven objectives.

The metric that matters most in a first OKR implementation is not objective completion rate. It's whether the team can articulate the company's one objective unprompted, without looking at the spreadsheet. If they can, the system is working. If they can't, you've built a documentation system, not a goal system.

But Doesn't Simplification Mean Leaving Goals Out?

The strongest objection to this approach goes like this: "If we only have one objective and three key results, what happens to everything else? We have sales targets, quality metrics, customer satisfaction scores, HR processes — are we supposed to ignore all of that?"

It's a legitimate concern. The answer is the distinction between OKRs and BAU — business as usual. OKRs are not a replacement for operational metrics. A manufacturing plant still needs to track defect rates, throughput, and on-time delivery. A retail business still needs daily sales numbers and inventory turns. These belong in a management dashboard, not in an OKR.

OKRs are for the things that represent strategic change — the outcomes the business needs to achieve that won't happen through routine operations alone. "Keep defect rates below 2%" is not an OKR; it's a BAU target that belongs in your weekly ops review. "Launch the new B2B channel and win five accounts by end of Q3" — that's an OKR.

Once founders understand this separation, the anxiety about simplification dissolves. The business is not ignoring its operational metrics. It's just not trying to manage everything through one goal system.

The genuine limit of this argument: some businesses have multiple real strategic priorities that cannot be sequenced. A startup going through simultaneous product build and fundraising may legitimately need two parallel objectives. In those cases, two objectives with three key results each is still a system. Eleven objectives with forty-seven key results is a wish list.

The Discipline Is in What You Cut

The most valuable thing an OKR consultant can tell an Indian MSME founder is what to remove.

The OKR framework for small business success is not less rigorous than what Google uses — it's more rigorous, in a different dimension. Where Google's OKR system needs depth and cascade, an MSME's needs selectivity and clarity. The discipline is not in building more goals. It's in building fewer, better ones and then actually holding the line on them.

A 50-person business that executes brilliantly on one objective per quarter will outperform a 50-person business with a sophisticated ten-objective OKR system every time. Not because the goals are simpler — but because execution beats architecture.

The first question to ask when your OKR implementation is not working is not "how do we improve adoption?" It's "how many objectives do we have?" If the answer is more than three, you already know what to do.

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.

Ready to build OKRs your team will actually use?

Book a free first conversation with Prem Menon →