<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Community on </title>
    <link>/tags/community/</link>
    <description>Recent content in Community on </description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 May 2025 13:39:40 +0000</lastBuildDate>
    <atom:link href="/tags/community/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an OKR Community</title>
      <link>/blog/building-an-okr-community/</link>
      <pubDate>Mon, 05 May 2025 13:39:40 +0000</pubDate>
      <guid>/blog/building-an-okr-community/</guid>
      <description>&lt;h2 id=&#34;better-together&#34;&gt;Better together&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;/okrs&#34;&gt;OKRs&lt;/a&gt; often fail not because the framework is flawed but because implementation is inconsistent.&lt;/p&gt;&#xA;&lt;p&gt;Getting started with OKRs takes &lt;a href=&#34;/blog/study-reflection-and-practice/&#34;&gt;study, reflection, and practice&lt;/a&gt;. Successfully scaling the practice takes encouragement, sharing, and support across the organisation to achieve broad consistency, experience, and skill.&lt;/p&gt;&#xA;&lt;p&gt;Creating internal OKR communities of practice (CoPs) is my favourite way to help OKRs succeed. I try to do this in every coaching engagement I take on.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
