{ "schemaVersion": "1.0", "item": { "slug": "afrexai-okr-engine", "name": "OKR & Strategy Execution Engine", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/1kalin/afrexai-okr-engine", "canonicalUrl": "https://clawhub.ai/1kalin/afrexai-okr-engine", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/afrexai-okr-engine", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-okr-engine", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/afrexai-okr-engine" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/afrexai-okr-engine", "agentPageUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "OKR & Strategy Execution Engine", "body": "Set bold objectives. Measure what matters. Execute with discipline. Review ruthlessly." }, { "title": "Quick Health Check (/8)", "body": "Before building anything, score your current goal system:\n\nSignal✅ Healthy❌ BrokenWritten goals existDocumented, sharedIn someone's headGoals have metricsEvery goal is measurable\"Improve customer experience\"Cascade is clearTeam goals → company goalsDisconnected silosReview cadence existsWeekly check-ins happenGoals set then forgottenScoring is honestRed/yellow/green with dataEverything is \"on track\"Goals are ambitious70% hit rate = healthy100% hit rate = sandbaggingResource allocation matchesTop goals get most timeUrgent eats importantRetros happenQuarterly learning cyclesSame mistakes repeat\n\nScore: /8 → ≤3 = rebuild from scratch, 4-5 = fix gaps, 6+ = optimize" }, { "title": "Vision Statement (Revisit Annually)", "body": "Your vision is a direction, not a destination. 1-2 sentences max.\n\nFormula: We exist to [verb] [who] by [how], creating a world where [outcome].\n\nQuality test:\n\nInspiring (makes people want to show up)\n Directional (eliminates options that don't fit)\n Timeless (wouldn't change if product/market shifts)\n Memorable (can recite without reading)" }, { "title": "Mission Statement", "body": "Mission = how you pursue the vision right now. Changes every 2-5 years.\n\nFormula: We [what we do] for [who] by [unique approach], delivering [measurable impact]." }, { "title": "North Star Metric", "body": "One metric that captures the core value you deliver. Everything else is a supporting metric.\n\nSelection criteria:\n\nReflects customer value delivered (not vanity)\nLeading indicator of revenue (not lagging)\nMeasurable weekly (not annually)\nEvery team can influence it (not one department)\n\nBy business type:\n\nBusiness TypeNorth Star MetricWhySaaSWeekly Active Users or NRRUsage = value = retentionMarketplaceTransactions per weekLiquidity = value for both sidesE-commerceRevenue per visitorCombines traffic quality + conversion + AOVServicesMonthly recurring revenuePredictable value deliveryMedia/ContentEngaged time per userAttention = ad/subscription valueB2B EnterpriseExpansion revenue %Proves ongoing value post-sale" }, { "title": "Strategic Pillars (3-5 Max)", "body": "Pillars are the 3-5 themes that your goals cluster around. They persist for 1-3 years.\n\nstrategic_pillars:\n - name: \"Product-Led Growth\"\n description: \"Make the product the primary acquisition and expansion engine\"\n north_star_contribution: \"Drives WAU through self-serve onboarding\"\n \n - name: \"Enterprise Readiness\"\n description: \"Build features and processes that enterprise buyers require\"\n north_star_contribution: \"Drives NRR through larger deal sizes\"\n \n - name: \"Operational Excellence\"\n description: \"Reduce cost-to-serve and increase team velocity\"\n north_star_contribution: \"Enables more output per headcount\"\n\nRule: If a goal doesn't map to a pillar, it doesn't get resourced." }, { "title": "Annual Goal Template", "body": "Set 3-5 annual goals. Each must connect to a strategic pillar.\n\nannual_goal:\n id: \"AG-2026-01\"\n statement: \"Reach $1M ARR through product-led acquisition\"\n pillar: \"Product-Led Growth\"\n why_now: \"Market window closing, competitors raising Series A\"\n success_metric: \"ARR ≥ $1M by Dec 31\"\n current_baseline: \"$120K ARR\"\n milestones:\n q1: \"$250K ARR\"\n q2: \"$450K ARR\"\n q3: \"$700K ARR\"\n q4: \"$1M ARR\"\n dependencies:\n - \"Hire 2 engineers by Feb\"\n - \"Launch self-serve by March\"\n risk_factors:\n - \"Churn > 5% monthly kills growth math\"\n - \"Engineering capacity if hiring delayed\"\n owner: \"CEO + CRO\"" }, { "title": "Annual Planning Ritual (1-2 Days)", "body": "Pre-work (1 week before):\n\nEach leader submits: top 3 wins, top 3 misses, top 3 opportunities for next year\nFinance provides: revenue forecast, budget constraints, headcount plan\nProduct provides: competitive landscape, customer feedback themes\n\nDay 1: Review & Align\n\nScore last year's goals honestly (30 min)\nExternal landscape review — market, competitors, macro (45 min)\nInternal capability review — what are we great at? where do we suck? (30 min)\nConfirm/update vision, mission, pillars (30 min)\nBrainstorm annual goal candidates — aim for 10-15 (60 min)\n\nDay 2: Prioritize & Commit\n\nScore candidates on Impact × Feasibility matrix (45 min)\nSelect top 3-5 — kill the rest explicitly (30 min)\nDefine success metrics and quarterly milestones (60 min)\nAssign owners — one person per goal (15 min)\nIdentify top 3 risks and mitigations (30 min)\nWrite up and share within 48 hours" }, { "title": "The OKR Formula", "body": "OBJECTIVE: [Qualitative, inspiring, time-bound statement]\n KR1: [Metric] from [baseline] to [target] by [date]\n KR2: [Metric] from [baseline] to [target] by [date]\n KR3: [Metric] from [baseline] to [target] by [date]" }, { "title": "Objective Quality Rules", "body": "RuleGoodBadQualitative\"Become the fastest way to onboard\"\"Increase onboarding by 30%\"Inspiring\"Delight enterprise buyers\"\"Complete enterprise features\"Time-bound\"This quarter\" (implicit)No deadlineAchievable-ish70% confidence of hitting100% or 10% confidenceVerb-forward\"Launch\", \"Build\", \"Dominate\"\"Continue\", \"Maintain\"No metrics in objectiveDescribed in key results\"Achieve 50% growth\"" }, { "title": "Key Result Quality Checklist", "body": "Every KR must pass ALL of these:\n\nMeasurable — a number, not a judgment (\"increase NPS from 32 to 50\" not \"improve satisfaction\")\n Has a baseline — you know where you are today\n Has a target — specific number, not directional (\"to 50\" not \"higher\")\n Outcome-based — measures the result, not the activity (\"reduce churn to 3%\" not \"launch retention emails\")\n Within your control — your team can actually influence this\n Verifiable — someone else can confirm if it was hit\n Not a task — tasks go in your project plan, not your OKRs" }, { "title": "KR Scoring (0.0 — 1.0)", "body": "ScoreMeaningSignal0.0 - 0.3Failed to make progressWrong goal or wrong approach0.4 - 0.6Made progress but fell shortDecent goal, execution gap0.7Hit target (this is the goal!)Sweet spot — ambitious but achievable0.8 - 1.0Exceeded targetEither amazing execution or goal was too easy\n\nHealthy OKR program: average score across all KRs = 0.6-0.7\n\nAverage > 0.8 = goals are too safe (sandbagging)\nAverage < 0.4 = goals are too aggressive or execution is broken" }, { "title": "OKR Anti-Patterns", "body": "Anti-PatternExampleFixTask masquerading as KR\"Launch new onboarding flow\"\"Reduce time-to-first-value from 7 days to 2 days\"Vanity metric\"Reach 10K Twitter followers\"\"Generate 50 qualified leads from social\"Binary KR\"Ship enterprise SSO\"\"Enterprise accounts using SSO: 0 → 15\"SandbaggingTarget you'll hit by week 3Stretch to what you'd hit with exceptional executionToo many OKRs8 objectives, 24 KRsMax 3-5 objectives, 2-4 KRs eachNo owner\"The team\" owns itOne person accountable per OKRMoving goalpostsChange target mid-quarterLock targets; add context in scoringActivity KR\"Send 500 outreach emails\"\"Book 30 discovery calls from outbound\"" }, { "title": "OKR YAML Template", "body": "okr:\n quarter: \"Q1 2026\"\n team: \"Growth\"\n parent_annual_goal: \"AG-2026-01\"\n \n objective: \"Make self-serve onboarding so good that word-of-mouth becomes our #1 channel\"\n \n key_results:\n - id: \"KR1\"\n metric: \"Time to first value (TTFV)\"\n baseline: \"7 days\"\n target: \"< 2 days\"\n measurement: \"Median from signup to first meaningful action\"\n owner: \"Sarah\"\n confidence: 0.6 # at start of quarter\n \n - id: \"KR2\"\n metric: \"Self-serve conversion rate\"\n baseline: \"8%\"\n target: \"18%\"\n measurement: \"Free trial → paid within 14 days\"\n owner: \"Mike\"\n confidence: 0.5\n \n - id: \"KR3\"\n metric: \"Organic referral signups\"\n baseline: \"12/month\"\n target: \"50/month\"\n measurement: \"Signups attributed to referral/word-of-mouth\"\n owner: \"Sarah\"\n confidence: 0.4\n\n initiatives: # HOW you'll hit the KRs (not OKRs themselves)\n - \"Rebuild onboarding wizard with progressive disclosure\"\n - \"Add in-app referral program with credits\"\n - \"Weekly onboarding funnel analysis\"" }, { "title": "Cascade Architecture", "body": "COMPANY OKRs (CEO + leadership)\n ↓ aligns to\nTEAM/DEPARTMENT OKRs (team leads)\n ↓ aligns to\nINDIVIDUAL OKRs or COMMITMENTS (ICs)" }, { "title": "Alignment Rules", "body": "Every team OKR must support at least one company OKR — if it doesn't, why are you doing it?\nNot everything cascades down literally — team interprets company goals through their lens\nBottom-up input is mandatory — teams propose OKRs, leadership adjusts, not top-down dictation\nCross-team dependencies are explicit — if your KR depends on another team, write it down\nMax 60% of capacity on OKRs — leave 40% for operational work, fires, and innovation" }, { "title": "Alignment Map Template", "body": "alignment_map:\n company_objective: \"Become the fastest way to onboard\"\n \n team_contributions:\n - team: \"Product\"\n objective: \"Rebuild onboarding to be self-serve\"\n key_results: [\"TTFV < 2 days\", \"Self-serve conversion 18%\"]\n \n - team: \"Marketing\"\n objective: \"Make onboarding quality a core brand message\"\n key_results: [\"Case studies published: 5\", \"Onboarding-focused content: 40% of output\"]\n \n - team: \"Success\"\n objective: \"Eliminate onboarding as a churn driver\"\n key_results: [\"30-day churn from onboarding issues: < 2%\", \"Onboarding CSAT: > 4.5\"]\n \n cross_dependencies:\n - from: \"Marketing\"\n to: \"Product\"\n need: \"New onboarding screenshots and demo environment by week 3\"\n - from: \"Success\"\n to: \"Product\"\n need: \"In-app feedback widget for onboarding flows\"" }, { "title": "Individual Commitments (For ICs)", "body": "Not everyone needs formal OKRs. For individual contributors:\n\nindividual_commitment:\n name: \"Alex\"\n quarter: \"Q1 2026\"\n role: \"Senior Engineer\"\n \n commitments:\n - description: \"Ship onboarding wizard v2\"\n supports_kr: \"TTFV < 2 days\"\n milestones:\n - \"Design complete by Jan 15\"\n - \"MVP in staging by Feb 1\"\n - \"GA with telemetry by Feb 15\"\n \n - description: \"Reduce p95 API latency to < 200ms\"\n supports_kr: \"Self-serve conversion 18%\"\n milestone: \"Completed by March 15\"\n \n growth_goal: \"Lead first architecture design review\"" }, { "title": "KPI Selection Framework", "body": "KPIs are always-on metrics. OKRs are quarterly focus areas. They complement each other.\n\nKPI categories:\n\nCategoryPurposeExamplesHealthIs the business alive?MRR, burn rate, runwayGrowthAre we getting bigger?MoM growth, new customers, expansionEfficiencyAre we getting better?CAC, LTV/CAC, magic numberQualityAre customers happy?NPS, CSAT, churn rateVelocityAre we moving fast?Cycle time, deployment frequency" }, { "title": "KPI Dashboard YAML", "body": "kpi_dashboard:\n cadence: \"weekly\"\n \n health_metrics:\n - name: \"MRR\"\n current: \"$85K\"\n target: \"$100K\"\n trend: \"up\" # up/down/flat\n status: \"yellow\" # green/yellow/red\n \n - name: \"Gross Burn\"\n current: \"$45K/mo\"\n target: \"< $50K/mo\"\n trend: \"flat\"\n status: \"green\"\n \n - name: \"Runway\"\n current: \"18 months\"\n target: \"> 12 months\"\n trend: \"flat\"\n status: \"green\"\n \n growth_metrics:\n - name: \"New Customers (Monthly)\"\n current: 12\n target: 20\n trend: \"up\"\n status: \"yellow\"\n \n - name: \"Net Revenue Retention\"\n current: \"108%\"\n target: \"> 110%\"\n trend: \"up\"\n status: \"yellow\"\n \n quality_metrics:\n - name: \"Monthly Churn Rate\"\n current: \"4.2%\"\n target: \"< 3%\"\n trend: \"down\" # down is good for churn\n status: \"red\"\n \n - name: \"NPS\"\n current: 42\n target: \"> 50\"\n trend: \"up\"\n status: \"yellow\"" }, { "title": "Metric Hygiene Rules", "body": "Every metric has an owner — one person updates it weekly\nEvery metric has a source of truth — where does the number come from?\nEvery metric has thresholds — green/yellow/red defined in advance\nReview weekly, act on red — yellow is a watch, red is an action item\nLimit to 10-15 KPIs — more = nobody reads the dashboard\nSeparate leading from lagging — leading indicators predict; lagging confirms\nNever game a metric — if behavior changes to hit the number without delivering value, the metric is wrong" }, { "title": "Weekly Check-In (30 min)", "body": "Purpose: Are we on track this week? Any blockers?\n\nFormat:\n\n1. KPI dashboard review (5 min)\n - Any metric turn red since last week?\n - Action owner for each red metric\n\n2. OKR confidence update (10 min)\n - Each KR owner: confidence score (0.0-1.0) + one sentence why\n - Flag anything that dropped > 0.2 since last week\n\n3. Top 3 priorities this week (10 min)\n - Each team member: what are you working on?\n - Does it connect to an OKR? If not, why?\n\n4. Blockers & asks (5 min)\n - What's stuck? Who can unblock it?\n\nRules:\n\nNo status presentations — update a shared doc BEFORE the meeting\nMeeting is for discussion, not information transfer\nIf everything is green and no blockers, cancel the meeting (seriously)" }, { "title": "Monthly Review (60 min)", "body": "Purpose: Are we on track this quarter? Should we adjust?\n\n1. KPI trend review (15 min)\n - Month-over-month trends for all KPIs\n - 3 metrics that improved most, 3 that degraded most\n\n2. OKR mid-quarter assessment (20 min)\n - Score each KR honestly\n - Identify at-risk KRs — what's the rescue plan?\n - Any KR that's clearly going to miss 0.3 → discuss kill or pivot\n\n3. Resource check (10 min)\n - Are the right people working on the right things?\n - Any reallocation needed?\n\n4. Learnings & adjustments (15 min)\n - What surprised us this month?\n - What would we do differently?\n - Document decisions in meeting notes" }, { "title": "Quarterly Planning & Retrospective (Half Day)", "body": "Morning: Retrospective (2 hours)\n\n1. Score all KRs (30 min)\n - Final 0.0-1.0 score for each KR\n - Brief narrative: what happened and why\n\n2. Objective-level scoring (15 min)\n - Average KR scores per objective\n - Did we achieve the spirit of the objective?\n\n3. What worked? (20 min)\n - Practices, decisions, approaches that drove results\n - Capture for repetition\n\n4. What didn't? (20 min)\n - What failed, was abandoned, or underperformed?\n - Root cause: wrong goal? wrong approach? wrong timing? under-resourced?\n\n5. Lessons learned (15 min)\n - 3 things we'll do differently next quarter\n - 3 things we'll keep doing\n - 1 thing we'll stop doing\n\nAfternoon: Next Quarter Planning (2 hours)\n\n1. Annual goal progress check (15 min)\n - Are quarterly milestones on track?\n - Any annual goal that needs re-scoping?\n\n2. Context update (15 min)\n - Market changes, competitive moves, customer feedback\n - Any new constraints or opportunities?\n\n3. Draft OKRs (45 min)\n - Each team proposes 2-3 objectives with KRs\n - Stress-test: does this connect to annual goals?\n\n4. Alignment review (30 min)\n - Map team OKRs to company OKRs\n - Identify cross-team dependencies\n - Resolve conflicts\n\n5. Commit & communicate (15 min)\n - Lock objectives and key results\n - Set initial confidence scores\n - Assign owners\n - Share company-wide within 48 hours" }, { "title": "OKR Scoring Template", "body": "okr_score:\n quarter: \"Q1 2026\"\n team: \"Growth\"\n \n objective: \"Make self-serve onboarding so good that word-of-mouth becomes our #1 channel\"\n objective_score: 0.6 # weighted average of KRs + qualitative judgment\n \n key_results:\n - id: \"KR1\"\n metric: \"TTFV\"\n baseline: \"7 days\"\n target: \"< 2 days\"\n actual: \"3.2 days\"\n score: 0.5\n narrative: \"Rebuilt wizard but edge cases with enterprise SSO added 2 days for 30% of users\"\n \n - id: \"KR2\"\n metric: \"Self-serve conversion\"\n baseline: \"8%\"\n target: \"18%\"\n actual: \"14%\"\n score: 0.6\n narrative: \"Improved significantly but pricing page redesign delayed to Q2\"\n \n - id: \"KR3\"\n metric: \"Organic referral signups\"\n baseline: \"12/month\"\n target: \"50/month\"\n actual: \"38/month\"\n score: 0.7\n narrative: \"Referral program launched week 4, ramped well. On trajectory for 50+ in Q2\"\n \n lessons:\n - \"SSO complexity was underestimated — involve security team in planning\"\n - \"Referral program should have launched week 1, not week 4\"\n - \"Pricing page has massive impact on conversion — prioritize in Q2\"\n \n carry_forward:\n - \"Enterprise SSO onboarding optimization\"\n - \"Pricing page redesign\"" }, { "title": "Grading Culture", "body": "Healthy scoring culture:\n\n0.7 is a WIN — it means you set ambitious targets and mostly hit them\nConsistent 1.0 across the board = goals are too easy, push harder\nConsistent 0.3 = goals are disconnected from reality, recalibrate\nMisses are learning opportunities, not punishment\nSandbagging (setting easy goals to look good) is worse than failing on ambitious ones\n\nRed flags in scoring:\n\nEvery team scores 0.8+ every quarter → sandbagging epidemic\nScores are always exactly 0.7 → people are gaming the target\nTeams argue about scoring definitions after the quarter → define measurement upfront\nNo one cares about the scores → OKRs aren't connected to actual work" }, { "title": "Accountability Without Bureaucracy", "body": "For small teams (< 15 people):\n\nCompany OKRs only (no team-level)\nWeekly standup covers OKR progress\nQuarterly retrospective + planning = one afternoon\nIndividual commitments instead of individual OKRs\n\nFor medium teams (15-50 people):\n\nCompany + team OKRs\nWeekly team check-ins + monthly leadership review\nQuarterly planning = half day per team + half day cross-team\n\nFor larger organizations (50+ people):\n\nCompany + department + team OKRs\nDedicated OKR champion/program manager\nSoftware tool for tracking (Lattice, Weekdone, Perdoo, etc.)\nQuarterly cycle with 2-week drafting period" }, { "title": "Scenario 1: First Time Setting OKRs", "body": "Start simple:\n\nSet 2 company objectives with 3 KRs each (that's it)\nReview weekly for one quarter\nScore honestly at end of quarter\nAdd team-level OKRs in Q2 if Q1 worked\n\nCommon first-timer mistakes:\n\nSetting 8 objectives → pick 2-3\nMaking KRs into task lists → focus on outcomes\nNot reviewing weekly → put it on the calendar NOW\nChanging goals mid-quarter → lock them, learn from the miss" }, { "title": "Scenario 2: OKRs for a Solo Founder / Solopreneur", "body": "solo_okr:\n quarter: \"Q1 2026\"\n \n objective_1: \"Build a revenue engine that doesn't depend on my time\"\n key_results:\n - \"Monthly recurring revenue from $2K to $8K\"\n - \"Percentage of revenue from productized offers: 0% to 60%\"\n - \"Hours worked per $1K revenue: 40 to 15\"\n \n objective_2: \"Establish market authority in [niche]\"\n key_results:\n - \"Email list from 200 to 1,000 subscribers\"\n - \"Inbound leads per month from 3 to 15\"\n - \"Published content pieces: 0 to 12\"\n \n weekly_ritual: \"Friday 30 min — update KR numbers, plan next week's top 3\"\n monthly_ritual: \"Last Friday — full review, adjust tactics (not goals)\"" }, { "title": "Scenario 3: Pivoting Mid-Quarter", "body": "Sometimes the world changes and your OKRs become irrelevant.\n\nDecision framework:\n\nIs this a temporary disruption or a fundamental shift? → Temporary = stay the course\nWould continuing the OKR waste more than 20% of remaining quarter capacity? → Yes = pivot\nCan you modify KRs without changing the objective? → Try this first\n\nIf you pivot:\n\nScore original OKRs as-is with narrative explaining the pivot\nSet new OKRs for remaining time with appropriately scaled targets\nDon't pretend the pivot didn't happen — document the learning" }, { "title": "Scenario 4: OKRs Across Remote/Async Teams", "body": "Written over verbal — all OKR updates in shared doc, not meetings\nAsync weekly updates — each person posts by Friday EOD\nSync monthly — video call for the monthly review only\nTime zone equity — rotate meeting times if team spans > 6 hours\nOvercommunicate confidence — in person you can read body language; async you can't" }, { "title": "Scenario 5: Connecting OKRs to Performance Reviews", "body": "Caution: Tying OKR scores directly to compensation creates sandbagging.\n\nBetter approach:\n\nEvaluate EFFORT and LEARNING, not just score\nSomeone who scores 0.5 on an ambitious OKR and learns from it > someone who scores 1.0 on a safe one\nUse OKRs as INPUT to performance conversations, not the grade itself\nAssess: Did they set good goals? Did they execute with discipline? Did they learn from misses?" }, { "title": "Phase 9: Goal Quality Scoring Rubric (0-100)", "body": "DimensionWeight0-25 (Poor)50 (Okay)75-100 (Excellent)Ambition15%Obviously achievableModerate stretch60-70% confidence, would be proud to hitMeasurability20%Vague, subjectiveHas a metric but fuzzy measurementSpecific number, clear source, baseline documentedAlignment15%Doesn't connect to strategyLoosely relatedDirectly supports a pillar + annual goalOutcome Focus20%List of tasks/activitiesMix of outputs and outcomesPure outcome — measures the result, not the workOwnership10%\"The team\" or unassignedTeam-level but no individualOne person accountable, they wrote the OKRTime-Bound10%No deadline\"This quarter\"Specific milestones within the quarterIndependence10%Entirely dependent on other teamsSome dependency, documentedPrimarily within your control\n\nScoring guide:\n\n80-100: Ship it — this is a well-crafted OKR\n60-79: Good foundation, tighten weak dimensions\n40-59: Needs significant rework before committing\nBelow 40: Start over — this isn't an OKR yet" }, { "title": "Quarterly OKR One-Pager", "body": "# Q[X] 20XX OKRs — [Team Name]\n\n## Context\n- Annual goal this supports: [reference]\n- Key assumption: [what must be true for these to matter]\n- Biggest risk: [what could derail us]\n\n## Objective 1: [Inspiring statement]\n| KR | Baseline | Target | Owner | Confidence |\n|----|----------|--------|-------|------------|\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n\n**Key initiatives:** [2-3 bullet points of HOW]\n\n## Objective 2: [Inspiring statement]\n[same format]\n\n## Dependencies\n- Need from [team]: [what] by [when]\n\n## What we're NOT doing this quarter\n- [Explicit list of things we're deprioritizing]" }, { "title": "Weekly Update Template", "body": "# Weekly OKR Update — [Date]\n\n## KPI Status\n| Metric | Last Week | This Week | Status |\n|--------|-----------|-----------|--------|\n| [metric] | [value] | [value] | 🟢/🟡/🔴 |\n\n## OKR Confidence\n| KR | Last | Now | Δ | Note |\n|----|------|-----|---|------|\n| [KR1] | 0.6 | 0.5 | ↓ | [why it dropped] |\n\n## Top 3 This Week\n1. [priority] → supports [KR]\n2. [priority] → supports [KR]\n3. [priority] → operational\n\n## Blockers\n- [blocker] → need [action] from [person]" }, { "title": "Retrospective Template", "body": "retrospective:\n quarter: \"Q1 2026\"\n date: \"2026-04-01\"\n \n scores:\n - objective: \"[text]\"\n score: 0.65\n key_results:\n - kr: \"[text]\"\n score: 0.7\n - kr: \"[text]\"\n score: 0.5\n - kr: \"[text]\"\n score: 0.75\n \n overall_average: 0.65\n \n wins:\n - \"[what worked and why]\"\n - \"[what worked and why]\"\n \n misses:\n - \"[what failed and root cause]\"\n - \"[what failed and root cause]\"\n \n keep_doing:\n - \"[practice to continue]\"\n \n start_doing:\n - \"[new practice]\"\n \n stop_doing:\n - \"[practice to eliminate]\"\n \n carry_forward_to_next_quarter:\n - \"[unfinished work worth continuing]\"" }, { "title": "OKRs + Agile Integration", "body": "Sprint planning connection:\n\nEach sprint should advance at least one KR\nSprint goals reference which KR they support\nSprint retro includes: \"did this sprint move our OKRs?\"\nIf 3+ sprints pass without OKR progress, something is misaligned" }, { "title": "Stretch Goals vs Committed Goals", "body": "Google-style two-tier approach:\n\nCommitted OKRs (expect 1.0): must-hit goals with consequences for missing\nAspirational OKRs (expect 0.7): ambitious stretch goals where 0.7 is success\n\nWhen to use which:\n\nRevenue targets customers depend on → Committed\nInnovation or market expansion → Aspirational\nOperational SLAs → Committed\nCulture/employer brand → Aspirational" }, { "title": "Leading vs Lagging Indicator Design", "body": "Every KR should ideally have a leading indicator you track weekly:\n\nLagging KR (quarterly)Leading Indicator (weekly)Revenue from $X to $YPipeline generated this weekChurn from 5% to 3%Health score distribution changesNPS from 32 to 50Support ticket resolution timeConversion from 8% to 18%Onboarding completion rateNew hires: 5Candidates in pipeline by stage" }, { "title": "Multi-Team OKR Dependencies", "body": "dependency_contract:\n provider_team: \"Platform\"\n consumer_team: \"Growth\"\n deliverable: \"Self-serve SSO integration\"\n needed_by: \"2026-02-15\"\n provider_kr: \"Ship 3 enterprise features\"\n consumer_kr: \"Enterprise onboarding TTFV < 3 days\"\n escalation_date: \"2026-02-01\" # if not on track by this date, escalate\n status: \"on_track\"" }, { "title": "OKRs for Non-Typical Roles", "body": "Support/Ops teams:\n\nObjective: \"Deliver world-class support that turns users into advocates\"\nKRs: First response time, CSAT, escalation rate, knowledge base deflection %\n\nHR/People teams:\n\nObjective: \"Build a hiring engine that attracts top talent faster\"\nKRs: Time-to-fill, offer acceptance rate, 90-day retention, hiring manager satisfaction\n\nFinance teams:\n\nObjective: \"Give leadership real-time financial visibility\"\nKRs: Monthly close time (days), forecast accuracy (%), board deck delivery (days before meeting)" }, { "title": "Phase 12: 10 OKR Commandments", "body": "Less is more — 3 objectives × 3 KRs = plenty. More = dilution.\nOutcomes over outputs — Measure what changed, not what you did.\nHonest scoring or don't bother — A dishonest 0.7 is worse than an honest 0.3.\nWeekly rhythm or it dies — OKRs without regular check-ins are decoration.\nOne owner per OKR — Shared ownership = no ownership.\nLock goals, iterate tactics — Don't change the OKR mid-quarter; change how you pursue it.\nAmbitious is calibrated — 70% hit rate is the target. Not 100%, not 30%.\nAlignment ≠ top-down dictation — Teams propose, leadership aligns.\nSay what you're NOT doing — Every yes requires explicit nos.\nOKRs ≠ performance reviews — Use them as input, not the grade." }, { "title": "10 Common Mistakes", "body": "#MistakeFix1Too many OKRsMax 3-5 objectives company-wide2KRs are tasksRewrite as measurable outcomes3No baselineYou can't improve what you haven't measured4Set and forgetWeekly reviews are non-negotiable5100% hit rateYou're sandbagging — aim higher6Changing goals mid-quarterLock them; learn from the miss7OKRs in a spreadsheet nobody opensPut them where daily work happens8No retrospectiveWithout learning, cycles are just calendars9Top-down onlyBottom-up input creates buy-in and better goals10Conflating KPIs and OKRsKPIs = always-on health; OKRs = quarterly focus" }, { "title": "Natural Language Commands", "body": "\"Set OKRs for Q[X]\" → Phase 3 template + scoring\n\"Score our OKRs\" → Phase 7 scoring template\n\"Run quarterly planning\" → Phase 6 full retrospective + planning ritual\n\"Create KPI dashboard\" → Phase 5 dashboard YAML\n\"Check OKR alignment\" → Phase 4 alignment map\n\"Write annual goals\" → Phase 2 annual goal template\n\"Weekly OKR update\" → Phase 6 weekly template\n\"Grade this OKR\" → Phase 9 rubric (0-100)\n\"Plan our retro\" → Phase 6 retrospective template\n\"Help me write a key result\" → Phase 3 quality checklist\n\"What's our north star?\" → Phase 1 north star selection\n\"OKRs for solo founder\" → Phase 8 Scenario 2" } ], "body": "OKR & Strategy Execution Engine\n\nSet bold objectives. Measure what matters. Execute with discipline. Review ruthlessly.\n\nQuick Health Check (/8)\n\nBefore building anything, score your current goal system:\n\nSignal\t✅ Healthy\t❌ Broken\nWritten goals exist\tDocumented, shared\tIn someone's head\nGoals have metrics\tEvery goal is measurable\t\"Improve customer experience\"\nCascade is clear\tTeam goals → company goals\tDisconnected silos\nReview cadence exists\tWeekly check-ins happen\tGoals set then forgotten\nScoring is honest\tRed/yellow/green with data\tEverything is \"on track\"\nGoals are ambitious\t70% hit rate = healthy\t100% hit rate = sandbagging\nResource allocation matches\tTop goals get most time\tUrgent eats important\nRetros happen\tQuarterly learning cycles\tSame mistakes repeat\n\nScore: /8 → ≤3 = rebuild from scratch, 4-5 = fix gaps, 6+ = optimize\n\nPhase 1: Strategic Foundation\nVision Statement (Revisit Annually)\n\nYour vision is a direction, not a destination. 1-2 sentences max.\n\nFormula: We exist to [verb] [who] by [how], creating a world where [outcome].\n\nQuality test:\n\n Inspiring (makes people want to show up)\n Directional (eliminates options that don't fit)\n Timeless (wouldn't change if product/market shifts)\n Memorable (can recite without reading)\nMission Statement\n\nMission = how you pursue the vision right now. Changes every 2-5 years.\n\nFormula: We [what we do] for [who] by [unique approach], delivering [measurable impact].\n\nNorth Star Metric\n\nOne metric that captures the core value you deliver. Everything else is a supporting metric.\n\nSelection criteria:\n\nReflects customer value delivered (not vanity)\nLeading indicator of revenue (not lagging)\nMeasurable weekly (not annually)\nEvery team can influence it (not one department)\n\nBy business type:\n\nBusiness Type\tNorth Star Metric\tWhy\nSaaS\tWeekly Active Users or NRR\tUsage = value = retention\nMarketplace\tTransactions per week\tLiquidity = value for both sides\nE-commerce\tRevenue per visitor\tCombines traffic quality + conversion + AOV\nServices\tMonthly recurring revenue\tPredictable value delivery\nMedia/Content\tEngaged time per user\tAttention = ad/subscription value\nB2B Enterprise\tExpansion revenue %\tProves ongoing value post-sale\nStrategic Pillars (3-5 Max)\n\nPillars are the 3-5 themes that your goals cluster around. They persist for 1-3 years.\n\nstrategic_pillars:\n - name: \"Product-Led Growth\"\n description: \"Make the product the primary acquisition and expansion engine\"\n north_star_contribution: \"Drives WAU through self-serve onboarding\"\n \n - name: \"Enterprise Readiness\"\n description: \"Build features and processes that enterprise buyers require\"\n north_star_contribution: \"Drives NRR through larger deal sizes\"\n \n - name: \"Operational Excellence\"\n description: \"Reduce cost-to-serve and increase team velocity\"\n north_star_contribution: \"Enables more output per headcount\"\n\n\nRule: If a goal doesn't map to a pillar, it doesn't get resourced.\n\nPhase 2: Annual Planning\nAnnual Goal Template\n\nSet 3-5 annual goals. Each must connect to a strategic pillar.\n\nannual_goal:\n id: \"AG-2026-01\"\n statement: \"Reach $1M ARR through product-led acquisition\"\n pillar: \"Product-Led Growth\"\n why_now: \"Market window closing, competitors raising Series A\"\n success_metric: \"ARR ≥ $1M by Dec 31\"\n current_baseline: \"$120K ARR\"\n milestones:\n q1: \"$250K ARR\"\n q2: \"$450K ARR\"\n q3: \"$700K ARR\"\n q4: \"$1M ARR\"\n dependencies:\n - \"Hire 2 engineers by Feb\"\n - \"Launch self-serve by March\"\n risk_factors:\n - \"Churn > 5% monthly kills growth math\"\n - \"Engineering capacity if hiring delayed\"\n owner: \"CEO + CRO\"\n\nAnnual Planning Ritual (1-2 Days)\n\nPre-work (1 week before):\n\nEach leader submits: top 3 wins, top 3 misses, top 3 opportunities for next year\nFinance provides: revenue forecast, budget constraints, headcount plan\nProduct provides: competitive landscape, customer feedback themes\n\nDay 1: Review & Align\n\nScore last year's goals honestly (30 min)\nExternal landscape review — market, competitors, macro (45 min)\nInternal capability review — what are we great at? where do we suck? (30 min)\nConfirm/update vision, mission, pillars (30 min)\nBrainstorm annual goal candidates — aim for 10-15 (60 min)\n\nDay 2: Prioritize & Commit\n\nScore candidates on Impact × Feasibility matrix (45 min)\nSelect top 3-5 — kill the rest explicitly (30 min)\nDefine success metrics and quarterly milestones (60 min)\nAssign owners — one person per goal (15 min)\nIdentify top 3 risks and mitigations (30 min)\nWrite up and share within 48 hours\nPhase 3: OKR Writing Methodology\nThe OKR Formula\nOBJECTIVE: [Qualitative, inspiring, time-bound statement]\n KR1: [Metric] from [baseline] to [target] by [date]\n KR2: [Metric] from [baseline] to [target] by [date]\n KR3: [Metric] from [baseline] to [target] by [date]\n\nObjective Quality Rules\nRule\tGood\tBad\nQualitative\t\"Become the fastest way to onboard\"\t\"Increase onboarding by 30%\"\nInspiring\t\"Delight enterprise buyers\"\t\"Complete enterprise features\"\nTime-bound\t\"This quarter\" (implicit)\tNo deadline\nAchievable-ish\t70% confidence of hitting\t100% or 10% confidence\nVerb-forward\t\"Launch\", \"Build\", \"Dominate\"\t\"Continue\", \"Maintain\"\nNo metrics in objective\tDescribed in key results\t\"Achieve 50% growth\"\nKey Result Quality Checklist\n\nEvery KR must pass ALL of these:\n\n Measurable — a number, not a judgment (\"increase NPS from 32 to 50\" not \"improve satisfaction\")\n Has a baseline — you know where you are today\n Has a target — specific number, not directional (\"to 50\" not \"higher\")\n Outcome-based — measures the result, not the activity (\"reduce churn to 3%\" not \"launch retention emails\")\n Within your control — your team can actually influence this\n Verifiable — someone else can confirm if it was hit\n Not a task — tasks go in your project plan, not your OKRs\nKR Scoring (0.0 — 1.0)\nScore\tMeaning\tSignal\n0.0 - 0.3\tFailed to make progress\tWrong goal or wrong approach\n0.4 - 0.6\tMade progress but fell short\tDecent goal, execution gap\n0.7\tHit target (this is the goal!)\tSweet spot — ambitious but achievable\n0.8 - 1.0\tExceeded target\tEither amazing execution or goal was too easy\n\nHealthy OKR program: average score across all KRs = 0.6-0.7\n\nAverage > 0.8 = goals are too safe (sandbagging)\nAverage < 0.4 = goals are too aggressive or execution is broken\nOKR Anti-Patterns\nAnti-Pattern\tExample\tFix\nTask masquerading as KR\t\"Launch new onboarding flow\"\t\"Reduce time-to-first-value from 7 days to 2 days\"\nVanity metric\t\"Reach 10K Twitter followers\"\t\"Generate 50 qualified leads from social\"\nBinary KR\t\"Ship enterprise SSO\"\t\"Enterprise accounts using SSO: 0 → 15\"\nSandbagging\tTarget you'll hit by week 3\tStretch to what you'd hit with exceptional execution\nToo many OKRs\t8 objectives, 24 KRs\tMax 3-5 objectives, 2-4 KRs each\nNo owner\t\"The team\" owns it\tOne person accountable per OKR\nMoving goalposts\tChange target mid-quarter\tLock targets; add context in scoring\nActivity KR\t\"Send 500 outreach emails\"\t\"Book 30 discovery calls from outbound\"\nOKR YAML Template\nokr:\n quarter: \"Q1 2026\"\n team: \"Growth\"\n parent_annual_goal: \"AG-2026-01\"\n \n objective: \"Make self-serve onboarding so good that word-of-mouth becomes our #1 channel\"\n \n key_results:\n - id: \"KR1\"\n metric: \"Time to first value (TTFV)\"\n baseline: \"7 days\"\n target: \"< 2 days\"\n measurement: \"Median from signup to first meaningful action\"\n owner: \"Sarah\"\n confidence: 0.6 # at start of quarter\n \n - id: \"KR2\"\n metric: \"Self-serve conversion rate\"\n baseline: \"8%\"\n target: \"18%\"\n measurement: \"Free trial → paid within 14 days\"\n owner: \"Mike\"\n confidence: 0.5\n \n - id: \"KR3\"\n metric: \"Organic referral signups\"\n baseline: \"12/month\"\n target: \"50/month\"\n measurement: \"Signups attributed to referral/word-of-mouth\"\n owner: \"Sarah\"\n confidence: 0.4\n\n initiatives: # HOW you'll hit the KRs (not OKRs themselves)\n - \"Rebuild onboarding wizard with progressive disclosure\"\n - \"Add in-app referral program with credits\"\n - \"Weekly onboarding funnel analysis\"\n\nPhase 4: Alignment & Cascading\nCascade Architecture\nCOMPANY OKRs (CEO + leadership)\n ↓ aligns to\nTEAM/DEPARTMENT OKRs (team leads)\n ↓ aligns to\nINDIVIDUAL OKRs or COMMITMENTS (ICs)\n\nAlignment Rules\nEvery team OKR must support at least one company OKR — if it doesn't, why are you doing it?\nNot everything cascades down literally — team interprets company goals through their lens\nBottom-up input is mandatory — teams propose OKRs, leadership adjusts, not top-down dictation\nCross-team dependencies are explicit — if your KR depends on another team, write it down\nMax 60% of capacity on OKRs — leave 40% for operational work, fires, and innovation\nAlignment Map Template\nalignment_map:\n company_objective: \"Become the fastest way to onboard\"\n \n team_contributions:\n - team: \"Product\"\n objective: \"Rebuild onboarding to be self-serve\"\n key_results: [\"TTFV < 2 days\", \"Self-serve conversion 18%\"]\n \n - team: \"Marketing\"\n objective: \"Make onboarding quality a core brand message\"\n key_results: [\"Case studies published: 5\", \"Onboarding-focused content: 40% of output\"]\n \n - team: \"Success\"\n objective: \"Eliminate onboarding as a churn driver\"\n key_results: [\"30-day churn from onboarding issues: < 2%\", \"Onboarding CSAT: > 4.5\"]\n \n cross_dependencies:\n - from: \"Marketing\"\n to: \"Product\"\n need: \"New onboarding screenshots and demo environment by week 3\"\n - from: \"Success\"\n to: \"Product\"\n need: \"In-app feedback widget for onboarding flows\"\n\nIndividual Commitments (For ICs)\n\nNot everyone needs formal OKRs. For individual contributors:\n\nindividual_commitment:\n name: \"Alex\"\n quarter: \"Q1 2026\"\n role: \"Senior Engineer\"\n \n commitments:\n - description: \"Ship onboarding wizard v2\"\n supports_kr: \"TTFV < 2 days\"\n milestones:\n - \"Design complete by Jan 15\"\n - \"MVP in staging by Feb 1\"\n - \"GA with telemetry by Feb 15\"\n \n - description: \"Reduce p95 API latency to < 200ms\"\n supports_kr: \"Self-serve conversion 18%\"\n milestone: \"Completed by March 15\"\n \n growth_goal: \"Lead first architecture design review\"\n\nPhase 5: KPI Dashboard\nKPI Selection Framework\n\nKPIs are always-on metrics. OKRs are quarterly focus areas. They complement each other.\n\nKPI categories:\n\nCategory\tPurpose\tExamples\nHealth\tIs the business alive?\tMRR, burn rate, runway\nGrowth\tAre we getting bigger?\tMoM growth, new customers, expansion\nEfficiency\tAre we getting better?\tCAC, LTV/CAC, magic number\nQuality\tAre customers happy?\tNPS, CSAT, churn rate\nVelocity\tAre we moving fast?\tCycle time, deployment frequency\nKPI Dashboard YAML\nkpi_dashboard:\n cadence: \"weekly\"\n \n health_metrics:\n - name: \"MRR\"\n current: \"$85K\"\n target: \"$100K\"\n trend: \"up\" # up/down/flat\n status: \"yellow\" # green/yellow/red\n \n - name: \"Gross Burn\"\n current: \"$45K/mo\"\n target: \"< $50K/mo\"\n trend: \"flat\"\n status: \"green\"\n \n - name: \"Runway\"\n current: \"18 months\"\n target: \"> 12 months\"\n trend: \"flat\"\n status: \"green\"\n \n growth_metrics:\n - name: \"New Customers (Monthly)\"\n current: 12\n target: 20\n trend: \"up\"\n status: \"yellow\"\n \n - name: \"Net Revenue Retention\"\n current: \"108%\"\n target: \"> 110%\"\n trend: \"up\"\n status: \"yellow\"\n \n quality_metrics:\n - name: \"Monthly Churn Rate\"\n current: \"4.2%\"\n target: \"< 3%\"\n trend: \"down\" # down is good for churn\n status: \"red\"\n \n - name: \"NPS\"\n current: 42\n target: \"> 50\"\n trend: \"up\"\n status: \"yellow\"\n\nMetric Hygiene Rules\nEvery metric has an owner — one person updates it weekly\nEvery metric has a source of truth — where does the number come from?\nEvery metric has thresholds — green/yellow/red defined in advance\nReview weekly, act on red — yellow is a watch, red is an action item\nLimit to 10-15 KPIs — more = nobody reads the dashboard\nSeparate leading from lagging — leading indicators predict; lagging confirms\nNever game a metric — if behavior changes to hit the number without delivering value, the metric is wrong\nPhase 6: Review Cadences\nWeekly Check-In (30 min)\n\nPurpose: Are we on track this week? Any blockers?\n\nFormat:\n\n1. KPI dashboard review (5 min)\n - Any metric turn red since last week?\n - Action owner for each red metric\n\n2. OKR confidence update (10 min)\n - Each KR owner: confidence score (0.0-1.0) + one sentence why\n - Flag anything that dropped > 0.2 since last week\n\n3. Top 3 priorities this week (10 min)\n - Each team member: what are you working on?\n - Does it connect to an OKR? If not, why?\n\n4. Blockers & asks (5 min)\n - What's stuck? Who can unblock it?\n\n\nRules:\n\nNo status presentations — update a shared doc BEFORE the meeting\nMeeting is for discussion, not information transfer\nIf everything is green and no blockers, cancel the meeting (seriously)\nMonthly Review (60 min)\n\nPurpose: Are we on track this quarter? Should we adjust?\n\n1. KPI trend review (15 min)\n - Month-over-month trends for all KPIs\n - 3 metrics that improved most, 3 that degraded most\n\n2. OKR mid-quarter assessment (20 min)\n - Score each KR honestly\n - Identify at-risk KRs — what's the rescue plan?\n - Any KR that's clearly going to miss 0.3 → discuss kill or pivot\n\n3. Resource check (10 min)\n - Are the right people working on the right things?\n - Any reallocation needed?\n\n4. Learnings & adjustments (15 min)\n - What surprised us this month?\n - What would we do differently?\n - Document decisions in meeting notes\n\nQuarterly Planning & Retrospective (Half Day)\n\nMorning: Retrospective (2 hours)\n\n1. Score all KRs (30 min)\n - Final 0.0-1.0 score for each KR\n - Brief narrative: what happened and why\n\n2. Objective-level scoring (15 min)\n - Average KR scores per objective\n - Did we achieve the spirit of the objective?\n\n3. What worked? (20 min)\n - Practices, decisions, approaches that drove results\n - Capture for repetition\n\n4. What didn't? (20 min)\n - What failed, was abandoned, or underperformed?\n - Root cause: wrong goal? wrong approach? wrong timing? under-resourced?\n\n5. Lessons learned (15 min)\n - 3 things we'll do differently next quarter\n - 3 things we'll keep doing\n - 1 thing we'll stop doing\n\n\nAfternoon: Next Quarter Planning (2 hours)\n\n1. Annual goal progress check (15 min)\n - Are quarterly milestones on track?\n - Any annual goal that needs re-scoping?\n\n2. Context update (15 min)\n - Market changes, competitive moves, customer feedback\n - Any new constraints or opportunities?\n\n3. Draft OKRs (45 min)\n - Each team proposes 2-3 objectives with KRs\n - Stress-test: does this connect to annual goals?\n\n4. Alignment review (30 min)\n - Map team OKRs to company OKRs\n - Identify cross-team dependencies\n - Resolve conflicts\n\n5. Commit & communicate (15 min)\n - Lock objectives and key results\n - Set initial confidence scores\n - Assign owners\n - Share company-wide within 48 hours\n\nPhase 7: Accountability & Scoring\nOKR Scoring Template\nokr_score:\n quarter: \"Q1 2026\"\n team: \"Growth\"\n \n objective: \"Make self-serve onboarding so good that word-of-mouth becomes our #1 channel\"\n objective_score: 0.6 # weighted average of KRs + qualitative judgment\n \n key_results:\n - id: \"KR1\"\n metric: \"TTFV\"\n baseline: \"7 days\"\n target: \"< 2 days\"\n actual: \"3.2 days\"\n score: 0.5\n narrative: \"Rebuilt wizard but edge cases with enterprise SSO added 2 days for 30% of users\"\n \n - id: \"KR2\"\n metric: \"Self-serve conversion\"\n baseline: \"8%\"\n target: \"18%\"\n actual: \"14%\"\n score: 0.6\n narrative: \"Improved significantly but pricing page redesign delayed to Q2\"\n \n - id: \"KR3\"\n metric: \"Organic referral signups\"\n baseline: \"12/month\"\n target: \"50/month\"\n actual: \"38/month\"\n score: 0.7\n narrative: \"Referral program launched week 4, ramped well. On trajectory for 50+ in Q2\"\n \n lessons:\n - \"SSO complexity was underestimated — involve security team in planning\"\n - \"Referral program should have launched week 1, not week 4\"\n - \"Pricing page has massive impact on conversion — prioritize in Q2\"\n \n carry_forward:\n - \"Enterprise SSO onboarding optimization\"\n - \"Pricing page redesign\"\n\nGrading Culture\n\nHealthy scoring culture:\n\n0.7 is a WIN — it means you set ambitious targets and mostly hit them\nConsistent 1.0 across the board = goals are too easy, push harder\nConsistent 0.3 = goals are disconnected from reality, recalibrate\nMisses are learning opportunities, not punishment\nSandbagging (setting easy goals to look good) is worse than failing on ambitious ones\n\nRed flags in scoring:\n\nEvery team scores 0.8+ every quarter → sandbagging epidemic\nScores are always exactly 0.7 → people are gaming the target\nTeams argue about scoring definitions after the quarter → define measurement upfront\nNo one cares about the scores → OKRs aren't connected to actual work\nAccountability Without Bureaucracy\n\nFor small teams (< 15 people):\n\nCompany OKRs only (no team-level)\nWeekly standup covers OKR progress\nQuarterly retrospective + planning = one afternoon\nIndividual commitments instead of individual OKRs\n\nFor medium teams (15-50 people):\n\nCompany + team OKRs\nWeekly team check-ins + monthly leadership review\nQuarterly planning = half day per team + half day cross-team\n\nFor larger organizations (50+ people):\n\nCompany + department + team OKRs\nDedicated OKR champion/program manager\nSoftware tool for tracking (Lattice, Weekdone, Perdoo, etc.)\nQuarterly cycle with 2-week drafting period\nPhase 8: Common Scenarios\nScenario 1: First Time Setting OKRs\n\nStart simple:\n\nSet 2 company objectives with 3 KRs each (that's it)\nReview weekly for one quarter\nScore honestly at end of quarter\nAdd team-level OKRs in Q2 if Q1 worked\n\nCommon first-timer mistakes:\n\nSetting 8 objectives → pick 2-3\nMaking KRs into task lists → focus on outcomes\nNot reviewing weekly → put it on the calendar NOW\nChanging goals mid-quarter → lock them, learn from the miss\nScenario 2: OKRs for a Solo Founder / Solopreneur\nsolo_okr:\n quarter: \"Q1 2026\"\n \n objective_1: \"Build a revenue engine that doesn't depend on my time\"\n key_results:\n - \"Monthly recurring revenue from $2K to $8K\"\n - \"Percentage of revenue from productized offers: 0% to 60%\"\n - \"Hours worked per $1K revenue: 40 to 15\"\n \n objective_2: \"Establish market authority in [niche]\"\n key_results:\n - \"Email list from 200 to 1,000 subscribers\"\n - \"Inbound leads per month from 3 to 15\"\n - \"Published content pieces: 0 to 12\"\n \n weekly_ritual: \"Friday 30 min — update KR numbers, plan next week's top 3\"\n monthly_ritual: \"Last Friday — full review, adjust tactics (not goals)\"\n\nScenario 3: Pivoting Mid-Quarter\n\nSometimes the world changes and your OKRs become irrelevant.\n\nDecision framework:\n\nIs this a temporary disruption or a fundamental shift? → Temporary = stay the course\nWould continuing the OKR waste more than 20% of remaining quarter capacity? → Yes = pivot\nCan you modify KRs without changing the objective? → Try this first\n\nIf you pivot:\n\nScore original OKRs as-is with narrative explaining the pivot\nSet new OKRs for remaining time with appropriately scaled targets\nDon't pretend the pivot didn't happen — document the learning\nScenario 4: OKRs Across Remote/Async Teams\nWritten over verbal — all OKR updates in shared doc, not meetings\nAsync weekly updates — each person posts by Friday EOD\nSync monthly — video call for the monthly review only\nTime zone equity — rotate meeting times if team spans > 6 hours\nOvercommunicate confidence — in person you can read body language; async you can't\nScenario 5: Connecting OKRs to Performance Reviews\n\nCaution: Tying OKR scores directly to compensation creates sandbagging.\n\nBetter approach:\n\nEvaluate EFFORT and LEARNING, not just score\nSomeone who scores 0.5 on an ambitious OKR and learns from it > someone who scores 1.0 on a safe one\nUse OKRs as INPUT to performance conversations, not the grade itself\nAssess: Did they set good goals? Did they execute with discipline? Did they learn from misses?\nPhase 9: Goal Quality Scoring Rubric (0-100)\nDimension\tWeight\t0-25 (Poor)\t50 (Okay)\t75-100 (Excellent)\nAmbition\t15%\tObviously achievable\tModerate stretch\t60-70% confidence, would be proud to hit\nMeasurability\t20%\tVague, subjective\tHas a metric but fuzzy measurement\tSpecific number, clear source, baseline documented\nAlignment\t15%\tDoesn't connect to strategy\tLoosely related\tDirectly supports a pillar + annual goal\nOutcome Focus\t20%\tList of tasks/activities\tMix of outputs and outcomes\tPure outcome — measures the result, not the work\nOwnership\t10%\t\"The team\" or unassigned\tTeam-level but no individual\tOne person accountable, they wrote the OKR\nTime-Bound\t10%\tNo deadline\t\"This quarter\"\tSpecific milestones within the quarter\nIndependence\t10%\tEntirely dependent on other teams\tSome dependency, documented\tPrimarily within your control\n\nScoring guide:\n\n80-100: Ship it — this is a well-crafted OKR\n60-79: Good foundation, tighten weak dimensions\n40-59: Needs significant rework before committing\nBelow 40: Start over — this isn't an OKR yet\nPhase 10: Tools & Templates\nQuarterly OKR One-Pager\n# Q[X] 20XX OKRs — [Team Name]\n\n## Context\n- Annual goal this supports: [reference]\n- Key assumption: [what must be true for these to matter]\n- Biggest risk: [what could derail us]\n\n## Objective 1: [Inspiring statement]\n| KR | Baseline | Target | Owner | Confidence |\n|----|----------|--------|-------|------------|\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n| [metric] | [current] | [target] | [name] | [0.0-1.0] |\n\n**Key initiatives:** [2-3 bullet points of HOW]\n\n## Objective 2: [Inspiring statement]\n[same format]\n\n## Dependencies\n- Need from [team]: [what] by [when]\n\n## What we're NOT doing this quarter\n- [Explicit list of things we're deprioritizing]\n\nWeekly Update Template\n# Weekly OKR Update — [Date]\n\n## KPI Status\n| Metric | Last Week | This Week | Status |\n|--------|-----------|-----------|--------|\n| [metric] | [value] | [value] | 🟢/🟡/🔴 |\n\n## OKR Confidence\n| KR | Last | Now | Δ | Note |\n|----|------|-----|---|------|\n| [KR1] | 0.6 | 0.5 | ↓ | [why it dropped] |\n\n## Top 3 This Week\n1. [priority] → supports [KR]\n2. [priority] → supports [KR]\n3. [priority] → operational\n\n## Blockers\n- [blocker] → need [action] from [person]\n\nRetrospective Template\nretrospective:\n quarter: \"Q1 2026\"\n date: \"2026-04-01\"\n \n scores:\n - objective: \"[text]\"\n score: 0.65\n key_results:\n - kr: \"[text]\"\n score: 0.7\n - kr: \"[text]\"\n score: 0.5\n - kr: \"[text]\"\n score: 0.75\n \n overall_average: 0.65\n \n wins:\n - \"[what worked and why]\"\n - \"[what worked and why]\"\n \n misses:\n - \"[what failed and root cause]\"\n - \"[what failed and root cause]\"\n \n keep_doing:\n - \"[practice to continue]\"\n \n start_doing:\n - \"[new practice]\"\n \n stop_doing:\n - \"[practice to eliminate]\"\n \n carry_forward_to_next_quarter:\n - \"[unfinished work worth continuing]\"\n\nPhase 11: Advanced Patterns\nOKRs + Agile Integration\n\nSprint planning connection:\n\nEach sprint should advance at least one KR\nSprint goals reference which KR they support\nSprint retro includes: \"did this sprint move our OKRs?\"\nIf 3+ sprints pass without OKR progress, something is misaligned\nStretch Goals vs Committed Goals\n\nGoogle-style two-tier approach:\n\nCommitted OKRs (expect 1.0): must-hit goals with consequences for missing\nAspirational OKRs (expect 0.7): ambitious stretch goals where 0.7 is success\n\nWhen to use which:\n\nRevenue targets customers depend on → Committed\nInnovation or market expansion → Aspirational\nOperational SLAs → Committed\nCulture/employer brand → Aspirational\nLeading vs Lagging Indicator Design\n\nEvery KR should ideally have a leading indicator you track weekly:\n\nLagging KR (quarterly)\tLeading Indicator (weekly)\nRevenue from $X to $Y\tPipeline generated this week\nChurn from 5% to 3%\tHealth score distribution changes\nNPS from 32 to 50\tSupport ticket resolution time\nConversion from 8% to 18%\tOnboarding completion rate\nNew hires: 5\tCandidates in pipeline by stage\nMulti-Team OKR Dependencies\ndependency_contract:\n provider_team: \"Platform\"\n consumer_team: \"Growth\"\n deliverable: \"Self-serve SSO integration\"\n needed_by: \"2026-02-15\"\n provider_kr: \"Ship 3 enterprise features\"\n consumer_kr: \"Enterprise onboarding TTFV < 3 days\"\n escalation_date: \"2026-02-01\" # if not on track by this date, escalate\n status: \"on_track\"\n\nOKRs for Non-Typical Roles\n\nSupport/Ops teams:\n\nObjective: \"Deliver world-class support that turns users into advocates\"\nKRs: First response time, CSAT, escalation rate, knowledge base deflection %\n\nHR/People teams:\n\nObjective: \"Build a hiring engine that attracts top talent faster\"\nKRs: Time-to-fill, offer acceptance rate, 90-day retention, hiring manager satisfaction\n\nFinance teams:\n\nObjective: \"Give leadership real-time financial visibility\"\nKRs: Monthly close time (days), forecast accuracy (%), board deck delivery (days before meeting)\nPhase 12: 10 OKR Commandments\nLess is more — 3 objectives × 3 KRs = plenty. More = dilution.\nOutcomes over outputs — Measure what changed, not what you did.\nHonest scoring or don't bother — A dishonest 0.7 is worse than an honest 0.3.\nWeekly rhythm or it dies — OKRs without regular check-ins are decoration.\nOne owner per OKR — Shared ownership = no ownership.\nLock goals, iterate tactics — Don't change the OKR mid-quarter; change how you pursue it.\nAmbitious is calibrated — 70% hit rate is the target. Not 100%, not 30%.\nAlignment ≠ top-down dictation — Teams propose, leadership aligns.\nSay what you're NOT doing — Every yes requires explicit nos.\nOKRs ≠ performance reviews — Use them as input, not the grade.\n10 Common Mistakes\n#\tMistake\tFix\n1\tToo many OKRs\tMax 3-5 objectives company-wide\n2\tKRs are tasks\tRewrite as measurable outcomes\n3\tNo baseline\tYou can't improve what you haven't measured\n4\tSet and forget\tWeekly reviews are non-negotiable\n5\t100% hit rate\tYou're sandbagging — aim higher\n6\tChanging goals mid-quarter\tLock them; learn from the miss\n7\tOKRs in a spreadsheet nobody opens\tPut them where daily work happens\n8\tNo retrospective\tWithout learning, cycles are just calendars\n9\tTop-down only\tBottom-up input creates buy-in and better goals\n10\tConflating KPIs and OKRs\tKPIs = always-on health; OKRs = quarterly focus\nNatural Language Commands\n\"Set OKRs for Q[X]\" → Phase 3 template + scoring\n\"Score our OKRs\" → Phase 7 scoring template\n\"Run quarterly planning\" → Phase 6 full retrospective + planning ritual\n\"Create KPI dashboard\" → Phase 5 dashboard YAML\n\"Check OKR alignment\" → Phase 4 alignment map\n\"Write annual goals\" → Phase 2 annual goal template\n\"Weekly OKR update\" → Phase 6 weekly template\n\"Grade this OKR\" → Phase 9 rubric (0-100)\n\"Plan our retro\" → Phase 6 retrospective template\n\"Help me write a key result\" → Phase 3 quality checklist\n\"What's our north star?\" → Phase 1 north star selection\n\"OKRs for solo founder\" → Phase 8 Scenario 2" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/1kalin/afrexai-okr-engine", "publisherUrl": "https://clawhub.ai/1kalin/afrexai-okr-engine", "owner": "1kalin", "version": "2.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/afrexai-okr-engine", "downloadUrl": "https://openagent3.xyz/downloads/afrexai-okr-engine", "agentUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-okr-engine/agent.md" } }