diff --git a/plugins/okr/README.md b/plugins/okr/README.md index 46ccc08..e7b6f5a 100644 --- a/plugins/okr/README.md +++ b/plugins/okr/README.md @@ -6,11 +6,11 @@ ## The Problem -OKR sounds simple until you try it in public sector. Your tildelingsbrev has 47 requirements and someone asks you to turn it into "3-5 inspiring Objectives." Teams write Key Results that are just task lists. Tertial cycles don't match the quarterly model from Google. And when Riksrevisjonen asks for documentation, nobody can trace which OKR delivered which mandate requirement. +Your organization has a strategy. Turning it into OKR that actually drive change is where it gets hard. Teams write Key Results that are just task lists. "Gjennomføre 5 kurs" is not a result — it's an activity. Tertial cycles don't match the quarterly model from Google. And nobody can trace the line from strategic intent through OKR down to what teams actually deliver. -Most OKR resources assume you're a startup. You're not. You have political steering, budget cycles tied to Stortinget, and mid-cycle priority changes from a minister who read something in Aftenposten. +Most OKR resources assume you're a startup. You're not. You have political steering, budget cycles tied to Stortinget, governance requirements from Riksrevisjonen, and mid-cycle priority changes from a minister who read something in Aftenposten. -**This plugin gives you an OKR expert that knows Norwegian public sector governance, learns your organization's context, and works alongside you through the entire OKR process** — from translating your tildelingsbrev into OKR candidates, through iterative quality improvement, to check-in meetings and cycle reviews. +**This plugin gives you an OKR expert that knows Norwegian public sector governance, learns your organization's context, and works alongside you through the entire OKR process** — from turning strategy into OKR candidates, through iterative quality improvement, to check-in meetings and cycle reviews. ## How It Works: Onboarding First @@ -21,16 +21,18 @@ The plugin starts by learning your context. This is the most important step — - **Your organization** — which agency, which sector, which ministry - **Your OKR maturity** — first attempt, pilot phase, or scaling across teams - **Your cycle** — tertial or quarterly, current phase, team count -- **Your strategic documents** — tildelingsbrev goals, virksomhetsplan priorities +- **Your strategy** — virksomhetsplan, strategic priorities, tildelingsbrev goals - **Your tools** — Linear integration, meeting tools, delivery methodology -This context is saved locally and automatically injected into every conversation. You do it once. After that, the plugin knows who you are, what cycle you're in, and what your strategic goals are. +This context is saved locally and automatically injected into every conversation. You do it once. After that, the plugin knows who you are, what cycle you're in, and what your strategic priorities are. ## Bring What You Have You don't need to start from scratch. The plugin meets you where you are: -**Have a tildelingsbrev?** The plugin parses it, separates what's actually an OKR candidate from what's a KPI, a compliance requirement, or a reporting routine — and drafts aligned OKR directly: +**Have a strategy or virksomhetsplan?** The plugin analyzes your strategic priorities and suggests OKR candidates that are outcome-focused, measurable, and scoped to a cycle. + +**Have a tildelingsbrev?** Leaders can use it as an early analysis tool — the plugin separates what's actually an OKR candidate from what's a KPI, a compliance requirement, or a reporting routine. It's a way to build awareness of where OKR can add value: ``` > /okr:governance @@ -84,7 +86,7 @@ KR2: "Answer 90% of calls within 3 minutes" — Score: 6/10 Overall: 4/10 — rewrite recommended. Shall I draft improved versions? ``` -**Starting from a vague idea?** The plugin guides you through structured questioning and suggests OKR aligned with your strategic context — because it already knows your tildelingsbrev goals and organizational priorities from onboarding. +**Starting from a vague idea?** The plugin guides you through structured questioning and suggests OKR aligned with your strategic context — because it already knows your organization's priorities from onboarding. ## The Development Process @@ -134,7 +136,7 @@ Then run `/okr:oppsett` — it takes 5–15 minutes and unlocks everything else. | `/okr:kaskade` | Cascade from organization to team, visualize alignment gaps | | `/okr:sporing` | Track progress scores (0.0-1.0), generate check-in reports | | `/okr:møter` | Generate agendas for workshops, check-ins, reviews, and 1:1s | -| `/okr:governance` | Translate tildelingsbrev to OKR, Riksrevisjon-ready documentation | +| `/okr:governance` | Analyze tildelingsbrev, ensure Riksrevisjon-ready documentation | | `/okr:innføring` | Plan OKR rollout, handle resistance, assess maturity | ## Public Sector Governance @@ -150,7 +152,7 @@ Then run `/okr:oppsett` — it takes 5–15 minutes and unlocks everything else. 5 specialized agents, 3 context-aware hooks, and a knowledge base of 15 reference documents covering methodology, antipatterns, governance, meeting formats, and sector-specific metrics. The plugin remembers your organization context across sessions via local configuration and automatic context injection. -Linear integration is optional — enable through `/okr:oppsett` for OKR tracking with score updates. +Tracking integration is optional. The plugin has built-in support for Linear, and the approach works with any issue tracker your organization already uses — Azure Boards, Jira, or similar. Configure through `/okr:oppsett`. ## When Not to Use This @@ -163,7 +165,7 @@ Linear integration is optional — enable through `/okr:oppsett` for OKR trackin - Not tested in a real OKR cycle beyond the author's organization - Norwegian public sector context only -- Linear is the only supported tracking integration +- Linear has built-in MCP integration; Azure Boards and Jira work but require their own MCP setup ---