スキル一覧に戻る
mguttmann

okr-setting

by mguttmann

Autonomous Organization Framework - A complete system for AI-assisted software development with Claude Code

0🍴 0📅 2026年1月25日
GitHubで見るManusで実行

SKILL.md


name: okr-setting description: Setting effective Objectives and Key Results (OKRs)

OKR Setting

Anleitung zum Setzen effektiver Objectives and Key Results (OKRs).

Was sind OKRs?

OKR = Objective (Qualitativ: Was wollen wir erreichen?)
    + Key Results (Quantitativ: Woran messen wir Erfolg?)

OKR Structure

## Objective: [Inspirierendes, qualitatives Ziel]

| Key Result | Baseline | Target | Current | Status |
|------------|----------|--------|---------|--------|
| KR1: [Messbar] | [Start] | [Ziel] | [Jetzt] | [%] |
| KR2: [Messbar] | [Start] | [Ziel] | [Jetzt] | [%] |
| KR3: [Messbar] | [Start] | [Ziel] | [Jetzt] | [%] |

**Overall Progress:** [X]%

Eigenschaften

Gute Objectives

EigenschaftBeschreibungBeispiel
QualitativBeschreibt gewünschten Zustand"Kunden lieben unser Produkt"
InspirierendMotiviert das Team"Wir sind die #1 Wahl"
ActionableTeam kann es beeinflussen"Developer Experience verbessern"
Time-boundKlar abgegrenzt (Quartal)Implizit durch OKR-Zyklus

Gute Key Results

EigenschaftBeschreibungBeispiel
QuantitativMit Zahl messbar"NPS von 30 auf 50"
OutcomeErgebnis, nicht Output"Conversion +20%" (nicht "5 Features")
AmbitiousStretch Goal (70% = gut)Über dem was sicher erreichbar ist
3-5 pro ObjectiveFokussiertMax 5 Key Results

OKR Levels

┌─────────────────────────────────────────────────────────────┐
│                    COMPANY OKRs                              │
│                    (Annual/Strategic)                        │
└─────────────────────────────────────────────────────────────┘
                            │
                            ▼
┌─────────────────────────────────────────────────────────────┐
│                    DEPARTMENT OKRs                           │
│                    (Quarterly)                               │
└─────────────────────────────────────────────────────────────┘
                            │
                            ▼
┌─────────────────────────────────────────────────────────────┐
│                    TEAM OKRs                                 │
│                    (Quarterly)                               │
└─────────────────────────────────────────────────────────────┘

OKR Setting Process

Phase 1: Preparation (Week 1)

## OKR Input Gathering

### Review Previous Quarter
| OKR | Final Score | Learnings |
|-----|-------------|-----------|
| [Previous O1] | [%] | [Was haben wir gelernt?] |

### Strategic Priorities
- [Priority 1 from leadership]
- [Priority 2 from leadership]

### Team Input
- [Idea 1 from team]
- [Idea 2 from team]

### Dependencies
- [What do we need from other teams?]

Phase 2: Drafting (Week 2)

## OKR Draft: Q[X] [Year]

### Objective 1: [Draft]
| Key Result | How to Measure | Baseline | Target |
|------------|----------------|----------|--------|
| KR1 | [Metric/Tool] | [Current] | [Goal] |
| KR2 | [Metric/Tool] | [Current] | [Goal] |
| KR3 | [Metric/Tool] | [Current] | [Goal] |

### Alignment Check
- [ ] Supports company OKR: [Which one?]
- [ ] Team has capacity
- [ ] Dependencies identified

Phase 3: Review & Commit (Week 3)

## OKR Review

| Objective | Feedback | Revision |
|-----------|----------|----------|
| O1 | [Feedback from leadership] | [Changes made] |

### Final OKRs
[Finalized OKRs hier]

### Committed: [Date]
### Owner: [Name]

OKR Template

# OKRs Q[X] [Year]
**Team:** [Team Name]
**Owner:** [Name]
**Period:** [Start Date] - [End Date]

---

## Objective 1: [Inspirierendes Ziel]

> [Optional: Kontext warum dieses Objective wichtig ist]

| # | Key Result | Baseline | Target | Week 4 | Week 8 | Week 12 | Final |
|---|------------|----------|--------|--------|--------|---------|-------|
| 1 | [KR1] | [X] | [Y] | | | | |
| 2 | [KR2] | [X] | [Y] | | | | |
| 3 | [KR3] | [X] | [Y] | | | | |

**Initiatives:**
- [Initiative 1 die zu KRs beiträgt]
- [Initiative 2 die zu KRs beiträgt]

**Risks:**
- [Risk 1]: [Mitigation]

---

## Objective 2: [Zweites Ziel]

[Repeat structure]

---

## Dependencies

| We Need | From Team | Status |
|---------|-----------|--------|
| [What] | [Team] | [Confirmed/Pending] |

---

## Check-in Schedule

| Date | Type | Attendees |
|------|------|-----------|
| [Week 2] | Weekly Update | Team |
| [Week 6] | Mid-Quarter Review | Team + Leadership |
| [Week 12] | End-of-Quarter Scoring | Team |

Scoring OKRs

Scoring Scale

ScoreMeaningInterpretation
0.0No progressDidn't start or complete fail
0.3Some progressBelow expectations
0.5HalfwayModerate progress
0.7Target zoneGood stretch goal achievement
1.0CompleteFully achieved (was target too easy?)

Scoring Formula

KR Score = (Current - Baseline) / (Target - Baseline)
Objective Score = Average of all KR scores

Scoring Template

## Q[X] OKR Scoring

### Objective 1: [Title]
| KR | Target | Actual | Score | Notes |
|----|--------|--------|-------|-------|
| KR1 | [X] | [Y] | [0.X] | [What happened?] |
| KR2 | [X] | [Y] | [0.X] | [What happened?] |
| KR3 | [X] | [Y] | [0.X] | [What happened?] |

**Objective Score:** [0.X]

### Learnings
- [What worked?]
- [What didn't?]
- [What will we do differently?]

Common Mistakes

MistakeProblemFix
Output statt Outcome"Ship 5 features""Increase activation 20%"
Zu viele OKRsKein FokusMax 3 Objectives
Zu einfachKein Stretch70% = Erfolg
Nicht messbarKeine AccountabilityKlare Metriken definieren
SandbagSicheres ZielAmbitionierte Ziele setzen
Set & ForgetKeine TrackingWeekly Check-ins

OKR Check-in Template

## Weekly OKR Check-in: [Date]

### Progress Update
| Objective | Last Week | This Week | Confidence |
|-----------|-----------|-----------|------------|
| O1 | [Score] | [Score] | [High/Medium/Low] |
| O2 | [Score] | [Score] | [High/Medium/Low] |

### Key Updates
- [What changed this week?]

### Blockers
- [Blocker 1]: [Action needed]

### Focus Next Week
- [Priority 1]
- [Priority 2]

Beispiele

Engineering Team

## Objective: Developer Experience ist erstklassig

| Key Result | Baseline | Target |
|------------|----------|--------|
| Build time | 5 min | < 1 min |
| Developer NPS | 20 | 50 |
| Time to first PR (new devs) | 5 days | 1 day |

Product Team

## Objective: Nutzer lieben unser Onboarding

| Key Result | Baseline | Target |
|------------|----------|--------|
| Activation Rate (7 day) | 30% | 50% |
| Time to Value | 10 min | 3 min |
| Onboarding NPS | 25 | 45 |

スコア

総合スコア

70/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です