Transparent inside, sealed outside: where your company strategy should live
What the Anthropic and Figma fallout teaches about trusting software with your strategy, and four questions to ask before you put your OKRs anywhere.
Read the articleBlog
Practical notes on cycles, coverage, scoring, and the method — in our own words. One shared clock. Missing stays loud. Keep your tools.
What the Anthropic and Figma fallout teaches about trusting software with your strategy, and four questions to ask before you put your OKRs anywhere.
Read the articleWhy 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.
Read the articleWhy committed OKRs are graded against 1.0 and aspirational ones against ~0.7 — and why a single blended mean makes both numbers meaningless.
Read the articleWhy 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.
Read the articleHow 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.
Read the articleFree forever for company OKRs. No card, no seats. Optional AI credits only if you choose to run it.