Product OKR Template — With Industry Examples
Template · 8 min read
The Core Philosophy: Outcomes over Outputs
The most common mistake Indian startups make during quarterly planning is confusing "Outputs" with "Outcomes".
- Output (Bad): "Ship the new UPI AutoPay integration by May 1st." This is a task. The user doesn't care about your code; they care if it solves their problem.
- Outcome (Good): "Increase the successful recurring subscription rate from 65% to 85%." This is a metric. If you ship the UPI integration and the metric doesn't move, you failed the OKR, even though you shipped the code.
The Standard OKR Structure
Every Product Pod (e.g., The "Activation" pod or the "Retention" pod) should own a maximum of 1 or 2 Objectives per quarter. Under each Objective, there should be a maximum of 3-5 Key Results. Below the OKRs sit the Initiatives (the actual features you will build to try and hit the KRs).
[The Objective]
A qualitative, ambitious statement of what you want to achieve. It should inspire the team.
- 📈 [Key Result 1]: A quantitative metric measuring success (Metric X from A to B).
- 📈 [Key Result 2]: A secondary quantitative metric measuring success.
- 🛡️ [Key Result 3 (Counter-measure)]: A quantitative metric to ensure quality doesn't drop while chasing KR1.
Initiatives (The Backlog): The actual epics, features, or UI changes you will experiment with to hit these numbers.
A Complete Q1 Example: Indian Fintech Startup (PayTech)
Context: A hypothetical Indian fintech startup that processes B2B payments. They're at 150 enterprise customers and need to grow to 400 by Q2 to hit their Series B targets. Here's their Q1 OKR plan.
Objective 1: Own the B2B Payments Wedge for Indian Tier-2 Companies
- 📈 KR 1: Increase Monthly Recurring Revenue (MRR) from ₹45 lakhs to ₹75 lakhs (+66%).
- 📈 KR 2: Achieve Net Revenue Retention (NRR) of 110% (currently 95%, meaning existing customers are growing their usage).
- 🛡️ KR 3 (Counter-Measure): Keep customer churn rate below 3% per month (currently 4%).
Why this OKR? MRR growth is the North Star. But if we only chase MRR and ignore NRR, we're acquiring low-quality customers who'll churn fast. The counter-measure KR forces us to improve retention alongside growth.
Proposed Initiatives:
1. Launch a new "Batch Payment Processing" feature (currently, users must upload files one by one; can we auto-batch?)
2. Build a dedicated Customer Success program for customers >₹5 lakhs ARR (quarterly check-ins, quarterly business reviews).
3. Launch a referral program: ₹50k credit to each existing customer who brings 1 paid customer.
Objective 2: Become the Easiest-to-Integrate Payment Platform in India
- 📈 KR 1: Reduce Time-to-Live (time from signup to first transaction) from 6 days to 2 days.
- 📈 KR 2: Increase the percentage of trial signups that complete a test transaction from 35% to 70%.
- 🛡️ KR 3 (Counter-Measure): Maintain a Net Promoter Score (NPS) of >50 in the "Ease of Integration" category.
Why this OKR? Our biggest competitor has a complex API that takes 2 weeks to integrate. Our core advantage is ease-of-use. This OKR forces us to make integration actually fast and simple, not just claim it in marketing.
Proposed Initiatives:
1. Rebuild the API documentation (Postman collections, cURL examples, code samples in Python / Node.js).
2. Launch a "Sandbox Mode" that works instantly without email verification.
3. Create a step-by-step video series (12 videos, 2 mins each) showing integration in different tech stacks.
Objective 3: Build Enterprise Trust (Compliance & Security)
- 📈 KR 1: Achieve ISO 27001 certification (Binary: Yes/No by end of Q1).
- 📈 KR 2: Pass a formal penetration test with 0 critical/high vulnerabilities (Binary: Pass/Fail).
- 🛡️ KR 3: Increase the % of Enterprise trial users (>₹50 lakhs ARR) who upgrade to paid from 25% to 45%.
Why this OKR? Tier-1 customers don't care about features; they care about safety. RBI compliance + ISO 27001 are table stakes for any payment company in 2026. The third KR measures if our compliance investments actually move the needle on conversions.
Proposed Initiatives:
1. Hire an external ISO audit firm (₹25 lakhs investment, 8-week process).
2. Engage HackerOne / YesWeHack to run a bug bounty program.
3. Publish a formal Data Privacy Policy and SOC2 Trust Center on the website.
Filled Examples by Industry
Example 1: Fintech (Wealthtech & Investing)
Context: An Indian mutual fund platform struggling with top-of-funnel drop-offs due to regulatory friction.
Objective: Become the most trusted, frictionless platform for first-time mutual fund investors in Tier-2 India.
- KR1: Increase Day-1 KYC completion rate from 35% to 55%.
- KR2: Reduce customer support tickets related to "money not reflecting in account" by 40%.
- KR3 (Counter-measure): Maintain an average initial SIP size of ₹1,500 (Ensure we aren't just acquiring low-intent users to inflate KR1).
Proposed Initiatives:
1. Implement the Setu / Digilocker auto-fetch API to bypass manual document uploads.
2. Build a new, highly visible "Payment Processing - Estimated Time 4 hrs" UI state to reduce user anxiety.
3. Launch vernacular (Hindi/Tamil) video tooltips inside the onboarding flow.
Example 2: B2B SaaS (HR Tech or CRM)
Context: A fast-growing Indian SaaS company trying to move upmarket to close Enterprise deals in the US.
Objective: Prove enterprise readiness and eliminate the "your software is too small for us" sales objection.
- KR1: Achieve SOC2 Type II compliance certification by the end of Q2 (Binary: 0 or 1).
- KR2: Decrease 95th percentile dashboard load time for accounts with >5,000 employees from 4.2 seconds to under 1.5 seconds.
- KR3: Increase the percentage of Enterprise trial users completing the "SSO Setup" milestone from 10% to 40%.
Proposed Initiatives:
1. Massive database indexing refactor (Engineering tech-debt sprint).
2. Partner with Okta / Auth0 for seamless SAML integration.
3. Hire an external penetration testing firm.
Example 3: Consumer (Hyperlocal / Quick Commerce)
Context: A 10-minute grocery delivery app trying to build deeper habituation beyond weekend impulse buys.
Objective: Transform our delivery app from a "weekend luxury" into an unavoidable "daily habit."
- KR1: Increase the frequency of orders per MAU from 2.1 to 3.5 per month.
- KR2: Grow the "Morning Essentials" (Milk/Bread) category from 15% to 35% of total GMV.
- KR3: Increase Push Notification opt-in rate for new installs from 45% to 65%.
Proposed Initiatives:
1. Launch a "Subscribe & Save" recurring feature for daily milk deliveries.
2. Implement a custom Permission Priming screen before requesting OS-level push access.
3. Run an A/B test on the homepage UI, moving the "Essentials" category to the top row above "Snacks".
Example 4: EdTech Platform
Context: An upskilling platform that acquires users easily but suffers from terrible course completion rates.
Objective: Fix our leaky educational bucket and prove our students actually achieve mastery.
- KR1: Increase the Module 1 completion rate from 22% to 60%.
- KR2: Reduce the average time taken to submit the first graded assignment from 14 days to 4 days.
- KR3: Achieve an NPS of >40 for the newly launched "Live Doubt Clearing" feature.
Proposed Initiatives:
1. Gamify the first 3 lessons with instant unlocks and progress bars.
2. Build an automated WhatsApp-based assignment reminder bot via Twilio.
3. Overhaul the video player UI to include a "Raise Hand" button.
How to Grade Your OKRs: The 0.0 to 1.0 Scale
At the end of each quarter, score every Key Result on a decimal scale from 0.0 to 1.0.
- 0.0 - 0.3 (Red Alert): We achieved less than 30% of the target. This usually means either: (a) the initiative failed to ship, (b) the market assumption was wrong, or (c) we hit an external blocker we couldn't overcome. Action: Either pivot the strategy or re-estimate effort for next quarter.
- 0.4 - 0.6 (Yellow - On Track but Blocked): We achieved 40-60% of the target. We made real progress but fell short. Often caused by: (a) underestimated engineering effort, (b) external dependencies (waiting on a partner API), (c) we had to context-switch mid-quarter to a crisis. Action: Extend the timeline or simplify the goal for next quarter.
- 0.7 - 0.9 (Green - Stretch Goal Hit): We achieved 70-90% of the target. This is the sweet spot. We set an ambitious goal and we're hitting it. The 0.7-0.9 band (not 1.0) shows you set a real stretch goal. Action: This is success. Celebrate, learn, and set new goals for next quarter.
- 1.0+ (Sandbagging / Underestimation): We achieved 100% or more. This is a red flag that your OKR was not ambitious enough. You essentially set a safe task, not a stretch goal. The point of OKRs is to shoot for the moon and land on the stars. Hitting 100% means you played it safe. Action: Next quarter, increase ambition. Aim for 0.7-0.9 range.
Grading in Practice: PayTech Example
KR: Increase MRR from ₹45 lakhs to ₹75 lakhs (+66%)
End of Q1 Result: Achieved ₹70 lakhs
Grade: (70-45) / (75-45) = 0.83 (Green)
This is a solid outcome. You set a 66% growth target and achieved 55% growth. The miss was likely due to a delayed enterprise deal that closed on Day 1 of Q2, not a strategy failure. Grade: 0.83 = Success.
The 5 Common OKR Anti-Patterns (Avoid These)
- Anti-Pattern 1: Vanity Metrics. Bad KR: "Increase sign-ups from 100 to 500 per month." Good KR: "Increase Day-30 retention from 25% to 45%." Sign-ups are meaningless without retention. You're acquiring low-intent users.
- Anti-Pattern 2: More than 5 Key Results per Objective. If you have 6+ KRs, you've lost focus. You're saying "everything is equally important," which means nothing is. Max 3-5 KRs per Objective.
- Anti-Pattern 3: Output vs. Outcome Confusion. Bad KR: "Ship the new dashboard UI." Good KR: "Increase power-user daily active users from 30% to 60% using the new dashboard." The first is a task. The second is a business result.
- Anti-Pattern 4: No Counter-Measure. Bad: Just optimize for revenue. You'll churn customers. Good: Optimize for revenue AND maintain NPS >50. The second ensures quality doesn't drop while chasing quantity.
- Anti-Pattern 5: Setting OKRs in a Vacuum. Bad: The CEO writes OKRs alone. Good: The entire product team debates, questions, and commits together. Buy-in matters.
The Quarterly OKR Cadence: When to Set, Check, and Grade
OKRs aren't a "set and forget" exercise. Here's a monthly checklist:
| Timing | Activity | Owner | Duration |
|---|---|---|---|
| 6 weeks before quarter | Strategy sessions. Review previous quarter's performance. Identify market shifts. Draft new OKRs. | CEO + Product Leads | 3-4 sessions, 2 hrs each |
| 2 weeks before quarter | Finalize OKRs. Engineering estimates effort. Negotiate scope if needed. | Product + Engineering leads | 2 sessions, 1.5 hrs each |
| Day 1 of quarter | OKRs go live. Share with entire team. Make the document public/accessible. | Product Manager | 1 all-hands presentation, 30 mins |
| Every 2 weeks | OKR Check-in during Sprint Planning. Update progress. Identify blockers. Adjust if needed. | Product Manager | 30 mins in sprint planning |
| Last week of quarter | Final data collection. Grade each KR. Document what worked and what didn't. | Product Manager | 4-6 hours |
| First week of next quarter | OKR Retrospective. Share grades and learnings with team. Celebrate wins. Discuss failures. | Product Manager | 1 all-hands, 45 mins |
India-Specific: Adapting OKRs to the Indian Market Calendar
Regulatory Quarters: India's fiscal year doesn't align with the calendar. RBI policy announcements often happen in Q4 (Dec-Feb) and Q2 (Jun-Aug). If you're a fintech, your OKRs might need to flex around regulatory changes. Example: If RBI raises the Retail Direct Account limit in December, your investment app OKRs should expect a surge in activated users in Q4, not Q1.
Festival Seasons: Consumer app OKRs must account for seasonal spikes. Diwali (Oct-Nov) drives a 40-60% spike in e-commerce transactions. New Year (Dec-Jan) drives health/fitness app signups. Your OKRs should expect this surge and prepare the infrastructure. Don't set a baseline OKR in September and hope it holds through Diwali.
Tax Season (Mar-May): B2B apps that serve accountants, CFOs, and bookkeepers will see a 50% drop in usage during March-May (India's financial year-end and tax deadline crunch). Your Q1 OKRs should NOT target growth during this period. Focus on Q4 and Q2 instead.
Hiring Freezes: Many Indian startups freeze hiring in June-July due to fiscal year-end. This affects your engineering velocity. If your Q2 OKR depends on shipping 4 complex features, but your team gets 30% capacity due to hiring freeze, your OKR will fail. Adjust in advance.
The Bi-Weekly Check-In & Scoring Rubric
Are Your OKRs Just a Feature Backlog?
Transitioning from an output-driven culture to an outcome-driven culture is painful. Let our consulting team help your product org set rigorous, measurable quarterly OKRs.
Hire us →