How to Set Up OKRs for Your Startup
Implement OKRs (Objectives and Key Results) to align your team around measurable goals. Learn how to write effective objectives, set ambitious key results, and run the quarterly review cycle.
Before You Start
- 1
A team of at least 2-3 people
- 2
A clear company mission or north star metric
- 3
Willingness to commit to a quarterly planning cadence
Step-by-Step Guide
Set 2-3 company-level objectives for the quarter
Objectives should be qualitative, ambitious, and inspiring. They answer 'what do we want to achieve?' Good objectives: 'Become the go-to analytics platform for seed-stage startups,' 'Deliver a product experience that users love and recommend,' 'Build a repeatable sales engine.' Bad objectives: 'Increase revenue by 20%' (that is a key result, not an objective). Limit to 2-3 objectives per quarter. More than that fragments focus.
Your objectives should feel slightly uncomfortable. If you are 100% confident you will hit every one, they are not ambitious enough. Aim for 70% achievement as the sweet spot.
Define 2-4 measurable key results per objective
Key results are quantitative outcomes that prove you achieved the objective. Each key result needs a specific number and deadline. Example: Objective: 'Deliver a product experience users love.' Key Results: (1) Increase NPS from 32 to 50, (2) Reduce time-to-activation from 3 days to 1 day, (3) Achieve 40% weekly active user rate. Key results should be outcomes, not outputs. 'Ship 5 features' is an output. 'Reduce churn to 3%' is an outcome.
Use the 'Will this key result move the objective forward even if nothing else changes?' test. If yes, it is a good key result. If it is just activity that might not matter, rethink it.
Set up your OKR tracking tool
Use Notion for a simple, flexible OKR database with custom views by team and status. Linear works well if your OKRs are primarily product and engineering focused, with cycle goals mapping to key results. Asana offers dedicated goal tracking features with progress roll-ups. Create a central dashboard where all OKRs are visible to everyone. Transparency is core to OKRs working.
Do not over-engineer the tooling. A shared Notion page beats a complex OKR platform for teams under 20 people. The process matters more than the software.
Run weekly check-ins and monthly scoring
Every Monday, each key result owner updates the confidence level (on track, at risk, off track) and adds a brief note on progress or blockers. Monthly, score each key result on a 0.0-1.0 scale based on progress toward the target. Discuss off-track key results in your team meeting and decide on corrective actions. Keep check-ins under 15 minutes. The goal is visibility, not lengthy discussion.
Color-code your OKRs: green (on track, 0.7-1.0), yellow (needs attention, 0.4-0.6), red (at risk, 0.0-0.3). This makes your weekly review a quick visual scan instead of a deep dive.
Run the quarterly review and planning cycle
At quarter end, score all key results and calculate the average per objective. Reflect: What worked? What did we learn? What will we do differently? Share results with the full team. Then begin planning the next quarter: review your annual goals, identify the most impactful areas to focus on, draft new objectives, and cascade them into team and individual key results. Allow 1-2 weeks for this planning cycle.
Scoring 0.6-0.7 on average means you set the right level of ambition. Consistent 1.0 scores mean your targets are too easy. Consistent 0.3 scores mean they are disconnected from reality. Calibrate over 2-3 quarters.
