<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by YC Lian on Medium]]></title>
        <description><![CDATA[Stories by YC Lian on Medium]]></description>
        <link>https://medium.com/@yclian?source=rss-c39f98f7fe46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*4Lrp6kdKfjlEzzuw41d9ew.jpeg</url>
            <title>Stories by YC Lian on Medium</title>
            <link>https://medium.com/@yclian?source=rss-c39f98f7fe46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:23:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yclian/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[RE: Product Tonic Lab Cohort 1 @ 2021]]></title>
            <link>https://yclian.medium.com/re-product-tonic-lab-cohort-1-2021-ede50b83b18a?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/ede50b83b18a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Fri, 19 Nov 2021 07:08:56 GMT</pubDate>
            <atom:updated>2021-11-19T07:09:08.878Z</atom:updated>
            <content:encoded><![CDATA[<p>I spent the last 6 month with the Product Tonic Lab community led by <a href="https://medium.com/u/65117a315e0d">Michael Ong</a>, <a href="https://medium.com/u/ba22ed267d7f">Mulyadi Oey</a>, et al. It was my third time joining the retreat since 2018, with the intention to gratify my curiosity, connect with people, and build new relationships. This year however, we didn’t travel to a remote island due to the new way of life. I signed up as a mentor instead, in hope to make some impacts to some people, and discover and develop my mentorship skills.</p><p>I have learned that <em>deliberateness</em> is my biggest enemy during this journey. 2 years (and more, actually, given the nature of my work) of intense Zoom calls, which are often outcome driven, gave me a rough start going into this program with some mentees. It was also a point in time I was coached by Dave Osh (of Varlinx) and hence introduced to many interesting tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67Vr2pp-S9Lm1DjdaVPXNw.jpeg" /></figure><p>As I sipped my Martinez the other day, seated at a bar half filled with couples, I wrote: “be a tortoise&quot;. A realization, a good advice and reminder to my future self: go slow, connect deeply, listen openly, be vulnerable, be in the moment.</p><p>Thanks to my mentees — Azri, Cloud, Dominic, and Jocelyn — and other participants who have contributed to my positive learning experience. See you around in the <a href="https://medium.com/product-team-tonic/">next events</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ede50b83b18a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gotcha: pyenv-win shims messing with global packages]]></title>
            <link>https://yclian.medium.com/gotcha-pyenv-win-shims-messing-with-global-packages-6bfe96cbdb6e?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bfe96cbdb6e</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[git-remote]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Sun, 12 Sep 2021 12:02:47 GMT</pubDate>
            <atom:updated>2021-09-12T12:07:13.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Cleaned up my Python set-up recently with <a href="https://github.com/pypa/pipx">pipx</a> and <a href="https://github.com/pyenv-win/pyenv-win">pyenv-win</a> recently and unknowingly broke git-remote-codecommit.</p><p>This is the error you may see:</p><pre>% git clone codecommit::us-west-2://some-project<br>Cloning into &#39;some-project&#39;…<br>&#39;Scripts&#39; is not recognized as an internal or external command,<br>operable program or batch file.</pre><p>Initially, I thought I messed up my %PATH% as I also happened to clean up my environment variables, profiles and RC files. Turned out the culprit was a local git-remote-codecommit in one of the Python installations:</p><pre>$ find pyenv-win/versions -name &quot;git*remote*codecommit&quot;<br>pyenv-win/versions/3.9.2/Lib/site-packages/git_remote_codecommit</pre><p>The installation would cause pyenv-winto place a few shims whenever rehashis called, and therefore throwing the aforementioned error whenever Git process accesses git-remote-codecommit outside of — in this case — the 3.9.2 shell.</p><p>The fix is easy: get rid of all git-remote-codecommit packages from all Python installations maintained by pyenv-win and ensure that there’s a global installation that no shims can supersede, pipx or not.</p><p>The prevention? Be careful whenever you install a package that’s meant for global.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bfe96cbdb6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On getting things done — it all starts from an investment mindset]]></title>
            <link>https://yclian.medium.com/on-getting-things-done-it-all-starts-from-an-investment-mindset-16047fb48a5?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/16047fb48a5</guid>
            <category><![CDATA[jim-collins]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[getting-things-done]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Wed, 03 Mar 2021 07:36:56 GMT</pubDate>
            <atom:updated>2021-03-03T07:36:56.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13AvHmTirTb3-5-L3FgaSA.png" /><figcaption>Some Jim Collins’ concepts from <a href="https://www.jimcollins.com/concepts.html">his site</a>.</figcaption></figure><h4>On getting things done — it all starts from an investment mindset</h4><p>Today I had a good conversation with one of our Tech leaders on “getting things done”. Be it in ServiceRocket or not, is not an overnight process but an investment.</p><p>It requires investment on communication and relationship, it requires constant conversation on vision and reshaping it, it requires developing enough evidence to gain the trust to take on bigger things, it requires methodical attention on execution and measurement to display and generate progress, etc.</p><p>An investment decision can be disruptive, but often that requires power which very few people in an organization have, and it doesn’t remove one from the accountability of poor results either way. Now, knowing those, if you have to invest in a new team to solve problem X, what do you need in order to achieve that? A business case usually already exists but it isn’t sufficient to get you the resources.</p><p>As soon as I stepped out from the call, I asked myself “how can we build more leaders with such investment mindset?”. Then I recalled some important concepts that I assume most readers here appreciate: <a href="https://www.jimcollins.com/concepts/twenty-mile-march.html">the 20-mile march</a>, <a href="https://www.jimcollins.com/concepts/the-flywheel.html">the flywheel</a>, <a href="https://www.jimcollins.com/concepts/fire-bullets-then-cannonballs.html">the bullets &amp; cannonball</a>.</p><p>I hope what I wrote resonates with you, and I look forward to some of your stories in the comments section.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16047fb48a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RE: Manager README]]></title>
            <link>https://yclian.medium.com/re-manager-readme-4f5a651d2557?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f5a651d2557</guid>
            <category><![CDATA[group-dynamics]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Mon, 28 Dec 2020 02:20:12 GMT</pubDate>
            <atom:updated>2020-12-28T05:54:26.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WaPFCgTAOvO9EDFgOvcOew.png" /><figcaption><strong>Source: </strong>Screen grab of managerreadme.com</figcaption></figure><p>Unpolished notes extracted from my reply to a friend who asked me for my view on Manager README within a group chat. It was not a familiar concept to me although I have seen (very few) people within my organization practiced it.</p><ol><li>It’s a good piece of introspective &amp; retrospective document to maintain. Personally, I exercise that by penning down lessons of the week and share to very few in our conversations. I think having a way to maintain an ever-changing <em>to-be</em> but having a few more mechanisms to verify the constantly evolving <em>as-is</em>, is an important duty to anyone who’s serious about working effectively with people.</li><li>It however shouldn’t substitute interactions with individuals through day-to-day instances or under a group setting. Because assimilation is simply most effective through interactions vs. reading README files.</li><li>A Manager README is not the same as a Manager’s playbook or an Engineering handbook. If I have to choose where I should spend my time, it will be the latter as it serves a greater purpose. My objective to spend 2–5 years in a team is not to instill personal values and expectations but to align, learn, and discover the best ways we all can play well together.</li></ol><p><strong>Further reading</strong></p><ul><li><a href="https://tdevroome.medium.com/the-manager-readme-is-dead-b1807397a2c5">The manager README is dead</a> (Vroome, 2019)</li><li><a href="https://www.businessballs.com/organisational-culture/likerts-management-systems/">Likert’s management system</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f5a651d2557" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Free Course: Introduction to FinOps by edX & The Linux Foundation]]></title>
            <link>https://yclian.medium.com/free-course-introduction-to-finops-by-edx-the-linux-foundation-9201a9fd9375?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/9201a9fd9375</guid>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[cost-management]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[financial-management]]></category>
            <category><![CDATA[free]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Mon, 06 Jul 2020 07:41:40 GMT</pubDate>
            <atom:updated>2020-07-06T07:56:31.733Z</atom:updated>
            <content:encoded><![CDATA[<p>Financial management, in the cloud economy with predominantly variable cost, has a fancy name called #FinOps. Here’s a free edX course starting end of this month to introduce you to the framework.</p><p>Within my circle, cost management has been a recurring topic in the past few quarters, and it cannot be more timely due to the situation many firms are now in.</p><p>I also find people with a *BA or investment background better practitioners in managing money (duh), but technologists often aren’t trained and equipped with such skills. Therefore, at work, I am focusing on developing 2 competencies: 1) managing P&amp;L at different levels (finest at the product level) #ZBx, 2) decision making &amp; execution through closed-loop control which observability is a key part of it.</p><p><a href="https://www.edx.org/course/introduction-to-finops">https://www.edx.org/course/introduction-to-finops</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9201a9fd9375" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Presentation: Control Chart by Balaji Reddie]]></title>
            <link>https://yclian.medium.com/presentation-control-chart-by-balaji-reddie-9b18c77d05b6?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b18c77d05b6</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[control-chart]]></category>
            <category><![CDATA[deming]]></category>
            <category><![CDATA[process-improvement]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Thu, 11 Jun 2020 06:23:37 GMT</pubDate>
            <atom:updated>2020-06-15T03:01:18.906Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PR185bPpVy0V290RjGJPFA.png" /></figure><p>As some of you may know, I am a strong advocate of Control Chart and I speak often about it, internally at work and externally with the community, and you can find the slides to a <a href="https://www.facebook.com/events/926817480727427/permalink/938796599529515/?__cft__[0]=AZVJFiJe2Nolmlc0p69MvjR2U85JKeq_MXGKO1HczGi7Mjzn-nZc-DUF73oihVcPSn5UsEzXfyggc9Qh5JVskAY5k2r_A-ONVOb01b5k19bfH9z-Zmli3HaF_d9SkJCZrWQ&amp;__tn__=%2CO%2CP-R">public presentation</a> I did years back.</p><p>Invented by Shewhart, and popularized by Deming. He called it <strong>“the communicable operation definition” of when to act and which way to act</strong>.</p><p>In this video, Balaji, who is the founder of Deming Forum in India, explains its concepts and application. During the pandemic, which we are still in, he worked directly with the Association of Healthcare Providers of India to look at data differently to draw new conclusions. You can <a href="https://www.youtube.com/watch?v=sFmvt0X0bpU">watch the <strong>full video here</strong></a>.</p><p>I’m recommending this video because I haven’t seen a good one for a while, and Balaji presented it in a clear and concise manner. If you are new to the tool or would like a refresher, here are a few things to take note of:</p><ul><li>Control Chart uses a 3-sigma approach to define upper &amp; lower control limits.</li><li>You don’t rush into making a <strong>prediction</strong>, you work towards getting things under <strong>control</strong> first.</li><li>As the upper and lower control limits narrow down, through process improvement, making prediction becomes easier.</li></ul><p>I have found success using it to drive process improvement at work, <a href="https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/">through Jira</a>. Although there’s a lack of extreme homogeneity in the data which represents our work, it is still helpful to use it to understand the software development process or the performance of a service desk.</p><p>If you have found success with its application, leave me a comment and tell me your story!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b18c77d05b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gotchas: API access to Google Admin SDK]]></title>
            <link>https://yclian.medium.com/gotchas-api-access-to-google-admin-sdk-4cf5ed49540?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cf5ed49540</guid>
            <category><![CDATA[google-api]]></category>
            <category><![CDATA[gotchas]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Mon, 24 Feb 2020 05:32:04 GMT</pubDate>
            <atom:updated>2021-09-12T11:27:11.329Z</atom:updated>
            <content:encoded><![CDATA[<h3>Gotcha: API access to <a href="https://developers.google.com/admin-sdk/directory/v1/quickstart/python">Google Admin SDK</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqn44HPQVqPOTeznLsvKxw.png" /></figure><p>Sharing a gotcha that took almost a day off from my weekend to deal with —</p><ol><li>If you are building a local script or server-to-server app, access the admin SDK with a <a href="https://l.workplace.com/l.php?u=https%3A%2F%2Fcloud.google.com%2Fdocs%2Fauthentication%23applications&amp;h=AT06nehdT0cEPcdDL7uMLz5Vwf4rZxaFg4BFiMJiwjnQs2_h6jwkAphlBpz954tp36DNmIrxxjkmocP6IFcPo4e0kMeEogR_edP6xkGMIIDuA8wdCh40chDSiaqL-mrdFBU0lWUL3rl4t7FvUiRPE1mk50G6Ir2gWf9R57sa5UmoRQ">service account</a>.</li><li>If you are accessing the Admin SDK with a service account, you <a href="https://stackoverflow.com/a/26469289/36397">must delegate to a domain admin</a>.</li><li>If you are delegating, you must <a href="https://developers.google.com/admin-sdk/directory/v1/guides/delegation">Enable G Suite Domain-wide Delegation</a>.</li><li>After you have delegated, you must grant access to the client with at least the scopes your app requests for, via the G Suite domain’s <a href="https://developers.google.com/admin-sdk/directory/v1/guides/delegation#delegate_domain-wide_authority_to_your_service_account">Admin console &gt; Security &gt; Advanced Settings</a>.</li></ol><p>— it was painful and stupid to realize I overlooked #4 while doing steps on the same page of #3.</p><p>If you are stuck with #1, this is the error you most likely would be seeing:</p><pre>googleapiclient.errors.HttpError: &lt;HttpError 403 when requesting https://www.googleapis.com/admin/directory/v1/customers/Cxxxxxxxx?alt=json returned “Not Authorized to access this resource/api”&gt;</pre><p>Otherwise, you would be seeing:</p><pre>google.auth.exceptions.RefreshError: (&#39;unauthorized_client: Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested.&#39;, &#39;{\n  &quot;error&quot;: &quot;unauthorized_client&quot;,\n  &quot;error_description&quot;: &quot;Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested.&quot;\n}&#39;)</pre><p>Thanks to <a href="https://medium.com/u/fa47a2e2f9b8">Sami Lunnamo</a>’s comment in <a href="https://github.com/googleapis/google-auth-library-ruby/issues/123#issuecomment-371745457">this GitHub thread</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cf5ed49540" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frameworks and their unlimited abusability]]></title>
            <link>https://yclian.medium.com/frameworks-and-their-unlimited-abusability-7aab5317e513?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aab5317e513</guid>
            <category><![CDATA[six-sigma]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 05:14:40 GMT</pubDate>
            <atom:updated>2019-09-10T05:14:40.368Z</atom:updated>
            <content:encoded><![CDATA[<p>There has been an article circulating around on “<a href="https://qz.com/work/1635960/whatever-happened-to-six-sigma/">whatever happened to Six Sigma</a>” written by <a href="https://medium.com/u/35f509dc1bc9">Oliver Staley</a>, which speaks about how things eroded over time in General Electric and the world of Six Sigma due to gamed reward systems, consultants, etc.</p><blockquote>You take the tools that help you manage uncertainty and you get rid of the underlying thinking, and you’re left with just the tools.</blockquote><p>There’s nothing fundamentally broken with TQM, Six Sigma, Lean, Scrum, etc. What’s broken is when people from both sides, for and against a bandwagon, try to oversell or fight against it <strong>without knowledge</strong>.</p><p>And it makes matters worse when one is <strong>resistant to change</strong>: be it defending a status quo (due to habit and security), or being open to embracing the new philosophy (driven by adaptability due to survival needs).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aab5317e513" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the prime factor to great innovation]]></title>
            <link>https://yclian.medium.com/on-the-prime-factor-to-great-innovation-130a6909044f?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/130a6909044f</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Sat, 18 May 2019 09:59:30 GMT</pubDate>
            <atom:updated>2019-05-18T17:27:48.196Z</atom:updated>
            <content:encoded><![CDATA[<p>About 2 months ago I tried to formulate the structure of salary adjustment, I created a formula that takes long- and short-term effort into consideration. About few weeks ago, I was introduced to <a href="https://twitter.com/safibahcall">Safi Bahcall</a>, then I went through a few of his interviews, with a16z, Tim Ferriss, etc.) and decided to read his latest book <a href="https://www.amazon.com/Loonshots-Nurture-Diseases-Transform-Industries/dp/1250185963">Loonshots</a>.</p><p>Safi speaks a lot on “mind the systems, not projects”. And that includes how to manage the system to incentivize innovation. One of the ingredients comes from understanding the Magic Number and 4 of its control parameters:</p><pre>M = (E x S^2 x F) / G</pre><p>e.g. when equity stake is low, people will rather invest time for politics.</p><p>On innovation, he shares one same message with Alex Osterwalder: “It’s not about culture.”</p><p>Alex Osterwalder spoke about defining the right structure to shape innovation culture (who C-Innovation-O should be reporting to, vs. CEO/COO). Safi too, is a disbeliever of culture as the <em>prime cause </em>(think Aristotle’s <a href="https://en.wikipedia.org/wiki/Unmoved_mover#Aristotle&#39;s_theology"><em>prime mover</em></a> concept).</p><p>Read more about it in <a href="https://hbr.org/2019/03/the-innovation-equation">this HBR entry</a>, and hopefully I can come back to write more on what I eventually formulated based on his idea.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=130a6909044f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On OKR: Managing challenges and successes]]></title>
            <link>https://medium.com/sgem/on-okr-managing-challenges-and-successes-49079725966?source=rss-c39f98f7fe46------2</link>
            <guid isPermaLink="false">https://medium.com/p/49079725966</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[goal-setting]]></category>
            <dc:creator><![CDATA[YC Lian]]></dc:creator>
            <pubDate>Sat, 24 Nov 2018 09:18:23 GMT</pubDate>
            <atom:updated>2018-11-24T10:01:18.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhiH0gM3030mOpUEsvir8Q.png" /></figure><p>SGEM is a small group of Engineering management professionals who meet up on a regular cadence. to learn from one another. On the 3rd of July ’18, the SGEM people met up to discuss about the challenges and successes of OKR adoption in Engineering team (and beyond).</p><p>This entry captures some dialogues we had and provides some afterthoughts from the author (<a href="https://medium.com/u/c39f98f7fe46">Yuen-Chi Lian</a>, YC) after more than a quarter since the meeting. The attendees were <a href="https://medium.com/u/8e8e15694d1f">Chew Chee Ming</a> (CM), <a href="https://medium.com/u/bd70a254fc29">Ping</a> (CP), Sunny (SS), <a href="https://medium.com/u/4ca94360f97d">Swayam Narain</a> (SN).</p><p>These topics were proposed for a deep dive: Getting buy-ins (CP), trickling down OKR to individuals (SS, CM).</p><h4>On getting buy-ins</h4><p>Perhaps, during early implementation, OKR could stop at engineering managers’ level, shielding engineers from unclear implementation, esp. for a fatigued team that is demotivated by firefighting and performance issues.</p><p>This view is only supported by half of the group, esp. from SS: “the whole ship needs to follow a single direction”. Managers should work on improving the clarity of objectives and use that to create alignment, rather than avoiding the responsibility. Other tools such as creation of dashboard to visualize numbers (e.g. revenue), or to use personas to build empathy for customers, will help engineers to understand their role and impacts to the business.</p><p><strong>After thoughts:</strong> The purpose of OKR is to create focus and be very committed to it, as a team. Shielding the engineers from OKR doesn’t protect but actually jeopardize the business. It will take many iterations to sharpen your implementation, so starting small (by being selective on the smaller teams to engage with) and scale adoption incrementally with results (e.g. with <a href="https://www.kotterinc.com/8-steps-process-for-leading-change/">Kotter’s 8-step process</a>) may be a good way to go about it.</p><h4>On trickling down to individuals</h4><p>An objective could be a creation with the higher objective (from the top) in mind, or simply a copy of the higher objective with set of key results specifically supported by the function (Engineering in this case).</p><p>An EM could approach individuals with an objective, and leave the formation of key results to them. These objectives could be improvement or roadmap items, which will eventually be placed in the backlog, but they have to be aspiring and not to be confused with key results.</p><p>There was a conflicting view on whether it is valuable to have individuals owning OKR vs. the team. Some thought the XP value of <a href="http://www.extremeprogramming.org/rules/collective.html">collective ownership</a> conflicts with individually-owned OKR.</p><p><strong>After thoughts:</strong> One main job of EM is to build tooling (SS). So, testing and figuring out the right tools to make the communication and tracking (one of the 5 superpowers John mentioned) easy will help to cut it for the engineers. As mentioned earlier, it takes iterations to improve your implementation, So, turning a top-down framework with strong bottom-up participation (which John said, a 60% of bottom-up is a success) is a matter of time by sticking to and refining it.</p><h4>Resources</h4><ul><li><a href="https://www.commonwealthclub.org/events/archive/video/venture-capitalist-john-doerr-measure-what-matters">Commonwealth Club: Interview with John Doerr (by Sal Khan, Oct ‘18)</a></li><li><a href="https://hbr.org/2018/05/how-vc-john-doerr-sets-and-achieves-goals">HBR: How John Doeer sets goals (May, 2018)</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49079725966" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sgem/on-okr-managing-challenges-and-successes-49079725966">On OKR: Managing challenges and successes</a> was originally published in <a href="https://medium.com/sgem">SGEM</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>