# How we run OKRs

> How-to notes from Gahmbit on OKR cycles, coverage gaps, committed vs aspirational scoring, and why OKRs are a town square — not another work OS.

Agent index: https://gahmbit.com/llms.txt
HTML page: https://gahmbit.com/blog

Practical notes on cycles, coverage, scoring, and the method — in our own words. One shared clock. Missing stays loud. Keep your tools.

- [Transparent inside, sealed outside: where your company strategy should live](https://gahmbit.com/blog/okr-data-privacy-ai.md) (2026-11-10): What the Anthropic and Figma fallout teaches about trusting software with your strategy, and four questions to ask before you put your OKRs anywhere.
- [How to run OKRs without migrating your tools](https://gahmbit.com/blog/okrs-without-migrating-tools.md) (2026-10-08): Why OKRs should live in a company town square — not another work OS — and how to keep Jira, docs, and personal task lists while still sharing commitments.
- [How to score committed vs aspirational OKRs](https://gahmbit.com/blog/committed-vs-aspirational-okrs.md) (2026-09-15): Why committed OKRs are graded against 1.0 and aspirational ones against ~0.7 — and why a single blended mean makes both numbers meaningless.
- [How to see who hasn’t written OKRs](https://gahmbit.com/blog/missing-okr-coverage.md) (2026-08-27): Why empty OKR coverage should stay loud — and how to run a directory that shows Has, Missing, Draft, and Pending instead of hiding people with nothing written.
- [Should different teams have different OKR cycles?](https://gahmbit.com/blog/one-okr-cycle.md) (2026-07-16): How to run one company OKR cycle when some teams want yearly goals and others want weekly check-ins — and why parallel department calendars break alignment.
