<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Okrs on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/okrs/</link>
    <description>Recent content in Okrs on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 10 Nov 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/okrs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Outcomes Over Outputs: Measuring What Matters</title>
      <link>https://www.secdev.uk/blog/leadership/3.5-outcomes-over-outputs-measuring-what-matters/</link>
      <pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.5-outcomes-over-outputs-measuring-what-matters/</guid>
      <description>&lt;p&gt;Early in my career, I inherited a team with a beautiful dashboard. Every metric was green. Velocity was up. Story points completed per sprint were trending in the right direction. Code coverage was above the target. Release frequency was on schedule. By every measure on that dashboard, the team was performing brilliantly.&lt;/p&gt;&#xA;&lt;p&gt;The product they were building had almost no users.&lt;/p&gt;&#xA;&lt;p&gt;That was my introduction to what Osmani calls the watermelon effect, metrics that look green on the surface but are red underneath. The team was producing outputs at an impressive rate. They just weren&amp;rsquo;t producing outcomes that mattered.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
