<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Journal on OKRs.chat</title><link>https://okrs.chat/blog/</link><description>Recent content in Journal on OKRs.chat</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://okrs.chat/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>What Makes an Objective Good</title><link>https://okrs.chat/blog/what-makes-an-objective-good/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://okrs.chat/blog/what-makes-an-objective-good/</guid><description>&lt;p&gt;An Objective gives a team direction. It describes a meaningful change that matters to the strategy and helps people decide where to put their effort.&lt;/p&gt;
&lt;p&gt;The wording matters, but it comes last. First, the team needs to agree on the change it wants to create.&lt;/p&gt;
&lt;h2 id="are-we-naming-the-change-or-prescribing-the-solution"&gt;Are we naming the change or prescribing the solution?&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;Migrate the legacy platform&amp;rdquo; may be important work. It is not automatically an Objective.&lt;/p&gt;
&lt;p&gt;Ask what problem the migration should solve. What would become possible if it succeeded?&lt;/p&gt;</description></item></channel></rss>