<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OKR on Panji Gautama</title><link>https://panjigautama.com/categories/okr/</link><description>Recent content in OKR on Panji Gautama</description><generator>Hugo</generator><language>en</language><copyright>Copyright © Panji Gautama</copyright><lastBuildDate>Wed, 15 Nov 2023 17:37:11 +0000</lastBuildDate><atom:link href="https://panjigautama.com/categories/okr/index.xml" rel="self" type="application/rss+xml"/><item><title>Thoughts on Developer Productivity</title><link>https://panjigautama.com/thoughts-on-developer-productivity/</link><pubDate>Wed, 15 Nov 2023 07:29:59 +0000</pubDate><guid>https://panjigautama.com/thoughts-on-developer-productivity/</guid><description>&lt;p&gt;&lt;img src="https://miro.medium.com/v2/resize:fit:512/1*nYbbM6V6ZJmlmUToZmLNTw.gif" alt="Color Cycling in Pixel Art | by Stephen Schroeder | Prototypr"&gt;&lt;/p&gt;
&lt;p&gt;I used to have a dream to work at a consulting giant until a few years ago. I worked with a bunch of them, as my parent company decided to hire one of the consulting companies, and they gave me nothing but a mess (Duh! 🙄). A while back, I stumbled upon this &lt;a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity"&gt;&amp;ldquo;Yes, you can measure software developer productivity&amp;rdquo;&lt;/a&gt; article from the consulting giant, and it sparked debate in a lot of tech blogs/newsletters.&lt;/p&gt;</description></item><item><title>Engineering Metrics</title><link>https://panjigautama.com/engineering-metrics/</link><pubDate>Tue, 06 Sep 2022 09:16:02 +0000</pubDate><guid>https://panjigautama.com/engineering-metrics/</guid><description>&lt;p&gt;&lt;a href="https://www.slideshare.net/panjigautama/metrics-that-matters-in-software-engineering"&gt;https://www.slideshare.net/panjigautama/metrics-that-matters-in-software-engineering&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;bunch of metrics are available to track and give us insights, but are they really that important?&lt;/p&gt;</description></item><item><title>Engineering Initiative, where to start?</title><link>https://panjigautama.com/engineering-initiative-where-to-start/</link><pubDate>Thu, 18 Mar 2021 11:31:04 +0000</pubDate><guid>https://panjigautama.com/engineering-initiative-where-to-start/</guid><description>&lt;p&gt;Performance improvement we must do, but where to identify it? Sometimes this kind of things might not obvious as they are, as experience and frame of reference from each of the individual engineer within your team might vary.&lt;/p&gt;
&lt;p&gt;This post intended to share questions and framework that I&amp;rsquo;ve been using (and pushing) to my team to give cue and where to start on finding room for engineering improvements.&lt;/p&gt;
&lt;p&gt;We start with very basic &lt;a href="http://www.barbaraminto.com/"&gt;Minto Pyramid&lt;/a&gt; framework to help us have clear written thoughts of problems &amp;amp; solutions.&lt;/p&gt;</description></item><item><title>Engineering North Star Metrics</title><link>https://panjigautama.com/engineering-north-star-metrics/</link><pubDate>Sat, 09 Jan 2021 12:11:10 +0000</pubDate><guid>https://panjigautama.com/engineering-north-star-metrics/</guid><description>&lt;p&gt;In the world where all of the metrics are available to be fetch and tracked, we end up on too many things being measured or worst, too little things that are being measured. It is impractical to make smart decisions based upon all available data and impossible to make any decision without data, and virtually impossible to make every metric as a priority worthy of improvement. The first challenge is deciding on what to measure, this article is intended to propose following metrics as the de jure metrics that being tracked and constantly improved going forward within tech team that I led so far.&lt;/p&gt;</description></item><item><title>Talking about OKR</title><link>https://panjigautama.com/okr/</link><pubDate>Sat, 02 Jan 2021 09:58:17 +0000</pubDate><guid>https://panjigautama.com/okr/</guid><description>&lt;p&gt;&lt;img src="https://panjigautama.com/images/67de3130-3c19-42a1-b015-f353970b4c6a.png" alt=""&gt;&lt;/p&gt;
&lt;h3 id="why-do-we-care-about-okr-"&gt;Why do we care about OKR ?&lt;/h3&gt;
&lt;p&gt;Managing a company’s performance relative to goals is important. OKRs (Objectives and Key Results) have been found by the tech industry to be a good way to do that. See &lt;a href="https://en.wikipedia.org/wiki/OKR"&gt;&lt;em&gt;https://en.wikipedia.org/wiki/OKR&lt;/em&gt;&lt;/a&gt; for a history of OKRs. See &lt;a href="https://www.amazon.com/Measure-What-Matters-Google-Foundation-ebook/dp/B078FZ9SYB/ref=tmm_kin_swatch_0?_encoding=UTF8&amp;amp;qid=1560736204&amp;amp;sr=8-1"&gt;&lt;em&gt;Measure What Matters, by John Doerr&lt;/em&gt;&lt;/a&gt; for a great read on how they started to be used at Google.&lt;/p&gt;
&lt;p&gt;By using OKRs correctly, we can align both within groups and across the company on our strategic direction and our tactical implementation of that direction. We can also chart how that direction changes during a period, and we can measure ourselves on how we did. Just like a feedback-and-performance culture is imperative to have at the individual employee level, it’s also essential to have at the team/group/org/company level.&lt;/p&gt;</description></item></channel></rss>