ktg-plugin-marketplace/plugins/okr/README.md
Kjell Tore Guttormsen b8e362fe57 docs(okr): rewrite README for engagement — problem-first landing page
Replace dry documentation-style README with problem-first structure:
lead with public sector pain points, show realistic interaction example,
add "when not to use" section, move badges to bottom.

132 lines (down from 280). Hook within 10 seconds.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-08 15:22:45 +02:00

5.9 KiB

OKR for Public Sector

Expert OKR guidance tailored for Norwegian public sector organizations.

Solo project — bug reports welcome, PRs not accepted.

The Problem

OKR sounds simple until you try it in public sector. Your organization gets a tildelingsbrev with 47 requirements, and someone asks you to turn it into "3-5 inspiring Objectives." Teams write KRs 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.

Most OKR tools assume you're a startup with quarterly goals and stock options. 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.

This plugin understands that context.

What You Get

  • Guided OKR writing that turns vague ambitions into outcome-focused Objectives with measurable Key Results — including baseline, target, and data source
  • Quality scoring against a rubric that catches the 19 most common OKR mistakes (activity masquerading as outcome, sandbagging, missing baselines, too many KRs)
  • Tildelingsbrev translation that separates what's actually an OKR candidate from what's a KPI, a compliance requirement, or a reporting routine
  • Cascade visualization from organization strategy down to team OKR, with alignment gap detection
  • Meeting materials for check-ins, reviews, workshops, and 1:1 conversations using the CFR framework

See It In Action

> /okr:skriv We want to improve our digital services for driver's license renewals

Which team is this for, and what cycle?
> Digital avdeling, T2-2026

What's the current state — do you have baseline numbers?
> About 45% do it digitally. Average processing takes 14 business days.
> User satisfaction is 3.4 out of 5.

───────────────────────────────────────────────────

OKR for Digital avdeling — T2-2026

Objective: Make driver's license renewal a frictionless experience

Key Results:
1. Increase fully digital renewals from 45% to 75%
   Measurement: Monthly report from case system
   Type: Aspirational (target score: 0.7)

2. Reduce average processing time from 14 to 5 business days
   Measurement: Case management system
   Type: Committed (target score: 1.0)

3. Achieve user satisfaction of 4.2/5.0 (baseline: 3.4)
   Measurement: Citizen survey, quarterly
   Type: Aspirational (target score: 0.7)

───────────────────────────────────────────────────

Shall I run a quality check on this? (/okr:kvalitet)
Or cascade it from an organization-level objective? (/okr:kaskade)

Quick Start

Add the marketplace:

claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git

Or enable directly in ~/.claude/settings.json:

{
  "enabledPlugins": {
    "okr@ktg-plugin-marketplace": true
  }
}

Then start with /okr:oppsett to configure your organization and cycle.

Commands

Command What it does
/okr:skriv Write new OKR — guided from vague idea to scored output
/okr:kvalitet Score existing OKR against rubric, detect antipatterns, suggest rewrites
/okr:kaskade Cascade from organization to team, visualize alignment
/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:innføring Plan OKR rollout, handle resistance, assess maturity
/okr:governance Translate tildelingsbrev to OKR, Riksrevisjon-ready documentation
/okr:oppsett Configure organization, cycle, and Linear integration

How It Works

Under the hood, the plugin uses 5 specialized agents, 3 context-aware hooks, and a knowledge base of 15 reference documents covering methodology, governance, antipatterns, meeting formats, and sector-specific metrics.

Configuration is stored in .claude/okr.local.md in your project directory (gitignored). A hook automatically injects your org context into every conversation, so the plugin remembers your organization, cycle, and team structure across sessions.

Linear integration is optional — enable it through /okr:oppsett to track OKR progress as issues with score updates.

Public Sector Features

Framework What the plugin does
Tildelingsbrev Parse requirements, separate OKR candidates from KPIs and compliance items
Riksrevisjonen Generate documentation with baseline, target, data source, and audit trail
Political steering Handle mid-cycle priority changes with documented rationale
NTP / Stortingsmelding Cascade from national policy down to team-level OKR

When Not to Use This

  • Private sector — the governance model, examples, and cycle structure are built for Norwegian public sector
  • Individual performance reviews — OKR is a team tool; this plugin explicitly discourages individual OKR
  • Project management — OKR sets direction, it doesn't replace your backlog or Gantt chart
  • First week of OKR — start with a workshop and post-its, not a plugin; come back when you have your first draft

Limitations

  • Not tested in a real OKR cycle beyond the author's organization
  • No automated tests
  • Norwegian public sector context only
  • Linear is the only supported tracking integration
  • Windows: not tested

Version Commands Agents License

See CHANGELOG.md for version history. MIT License.