Business
Vague goals produce vague results. Describe what you want to achieve and get OKRs with the clarity, ambition, and measurability that make them actually useful.
AI-generated output
Fill in the details above and click Generate to get your OKRs.
Describe the area you want to set goals in — growth, product quality, team development, customer success, or any other strategic priority. Be specific about what "winning" looks like in this area.
Provide context about your current situation and the challenges you are facing. OKRs that acknowledge real constraints produce more useful key results than aspirational statements divorced from reality.
You get one well-crafted Objective (inspiring, qualitative, directional) and three to four Key Results (specific, measurable, time-bound) — plus guidance on how ambitious each result is and how to track it.
For example, a product team focused on improving customer retention might get: Objective: "Make our product so indispensable that leaving feels like a genuine loss" — with Key Results like "Increase 90-day retention from 62% to 75%", "Reduce time-to-value for new users from 14 days to 5 days", and "Achieve a net promoter score of 45+ by end of quarter".
The guidance note might flag that the NPS target requires a baseline measurement first, and suggest establishing the baseline in Week 1 before committing to the target number publicly.
KPIs (Key Performance Indicators) measure the ongoing health of existing processes — they track whether things are working as expected. OKRs are goal-setting tools — they define where you want to go and how you will know when you have arrived. A KPI might be "monthly churn rate"; the corresponding OKR would be "Reduce monthly churn from 4% to 2.5% by end of Q3". KPIs describe the present; OKRs define the future.
Google, who popularised OKRs, targets achieving 60–70% of their key results — and considers 100% achievement a sign that the goal was not ambitious enough. The design intent is to set goals that require significant effort and some stretch, not goals that are predictably achievable with current resources. If you always hit 100% of your OKRs, make them harder.
Most practitioners recommend no more than 3–5 objectives per level, with 3–4 key results per objective. This is intentional constraint — the purpose of OKRs is to force prioritisation. A team with 10 objectives has not set priorities; it has listed everything it might do. The hard work is deciding what not to pursue, and OKRs are a tool for that decision.
For quarterly OKRs, a monthly check-in is typical, with a full review at the end of the quarter. Check-ins should be brief (30 minutes maximum) and focused on progress, blockers, and whether any key results need to be updated to reflect new information. OKRs set in stone regardless of reality become a source of pressure rather than direction — some evolution mid-cycle is healthy.
AI-generated SWOT analysis with a strategic verdict and priority action.
Structured, timed meeting agendas built from your objective and topics.
Thingy Tools