TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Improving OKRs

63 点作者 wioota大约 1 年前

13 条评论

extr大约 1 年前
The real problem is setting "hard but not so hard as to be impossible" goals at any level is really more of an art than a science. If leadership has a strong vision and their finger on the pulse - OKRs will work great, as will any other framework (eg. simply sending an email to everyone stating that the goal is X by Y date). If nobody has any clue what they're trying to accomplish and no shared vision - following the OKR method won't save you.
评论 #39787746 未加载
评论 #39787838 未加载
评论 #39788263 未加载
seanhunter大约 1 年前
This article feels very &quot;business book of the week&quot; to me. It&#x27;s a laundry list of changes you can make so you as a manager can feel like you&#x27;re doing something but there&#x27;s absolutely no evidence whatsoever that any of them will improve anything. It&#x27;s just &quot;here&#x27;s what the leading thinkers on OKRs are doing&quot;. What makes them the leading thinkers? Why is this good? What&#x27;s the evidence that works?<p>Here&#x27;s the number one thing I&#x27;ve seen at every institution that I&#x27;ve been at that uses OKRs (or V2MOMs which is salesforces method which I&#x27;m even less of a fan of for various reasons). You do a bunch of work planning, getting everyone on the same page on the OKRs for the quarter and within a week or two something comes along and changes everything deus ex machina and your plan is basically irrelevant and you&#x27;re doing the new thing working on the hoof with no real plan. Mike Tyson&#x27;s famous words &quot;Everyone has a plan until they get punched in the mouth&quot; really resonate with anyone who&#x27;s worked in a startup.<p>Then you get to your quarterly retro and you&#x27;ve done at least one maybe two reorgs&#x2F;pivots since the OKRs and you look back on them and they all fall into three buckets:<p>- About a third &quot;yeah we did that&quot;<p>- About a third &quot;everything changed so that wasn&#x27;t relevant any more&quot;<p>- About a third &quot;what on earth were we thinking?&quot;<p>The reason for this is you aren&#x27;t doing something where the scope of effort and the domain are really well understood. You&#x27;re not digging a trench or making plastic spoons. You&#x27;re trying to build a software business in response to a shifting marketplace and an ambiguous and often hard problem.<p>The activity of planning is useful for getting everyone on the same page, taking some time to think about what&#x27;s important etc, but the plan itself ends up victim to circumstances every single time. It&#x27;s just an example of the Eisenhower maxim that plans are worthless but planning is everything.[1] As such it just seems pretty pointless to focus on optimising the OKRs themselves in any meaningful way. The process is the valuable part.<p>[1] <a href="https:&#x2F;&#x2F;quoteinvestigator.com&#x2F;2017&#x2F;11&#x2F;18&#x2F;planning&#x2F;" rel="nofollow">https:&#x2F;&#x2F;quoteinvestigator.com&#x2F;2017&#x2F;11&#x2F;18&#x2F;planning&#x2F;</a>
评论 #39788320 未加载
hunvreus大约 1 年前
I haven&#x27;t yet seen an organization that benefited from OKRs. I&#x27;m not saying they don&#x27;t work, I&#x27;ve just never witnessed them working.<p>My main gripes with them:<p>- They focus on output, and I believe most organization (especially startups) should focus on input. In that regard, I&#x27;d spend more time figuring out your internal playbook rather than measuring the (invariably too many) goals you&#x27;ve set for yourself and your team at the beginning of the quarter.<p>- The don&#x27;t reflect reality. As soon as you set measurable outcomes for anything beyond the hard success metrics (e.g. revenue, profit, churn, CAC...), expect people to try and game the system. This leads to either people hitting the numbers but missing the mark, or simply failing to report accurately.<p>- They&#x27;re mostly useful for underperformers. I have the same feeling about 1:1s. Your top performers usually don&#x27;t need OKRs to know what needs to be done or how well they&#x27;re performing. This ends up being a lot of busywork, especially for those who want to get sh*t done.<p>I wouldn&#x27;t &quot;improve&quot; OKRs. I&#x27;d drop them:<p>- Set high level goals for the company (e.g. revenue, customer acquisition and employee retention).<p>- Have leadership set TODOs for the company and teams, BUT use this mostly as a way to foster debate and alignment on what needs to be done. Expect them to change often.<p>- Focus on your inputs. And on that topic, I would invest in building a culture of documenting what you do and how you do it (for example through a playbook). You can&#x27;t build on quicksand.
评论 #39787461 未加载
评论 #39792947 未加载
评论 #39788342 未加载
评论 #39787490 未加载
评论 #39787024 未加载
评论 #39791851 未加载
nitwit005大约 1 年前
I&#x27;ve experienced several variations of this at different companies. It&#x27;s never mattered as far as I can tell.<p>Managers get required to look at it as part of a some process, and inevitably find a set of goals that make no sense, as priorities have completely shifted. They then ignore it.
评论 #39788390 未加载
boxed大约 1 年前
OKR: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Objectives_and_key_results" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Objectives_and_key_results</a> for us who don&#x27;t have it top of mind.
FridgeSeal大约 1 年前
Almost every experience with OKR’s has been an unmitigated dumpster fire.<p>Leadership sets some goal, usually something insane and physically unachievable. Some inane key result -usually no closer to reality- gets set. Management and PM’s spend inordinate amounts of time and effort faffing over the metrics and relentlessly asking “why hasn’t the number gone up by 2% today????????” No attempt is made at doing any actual work, or god forbid, actually contributing.<p>End of quarter comes and lots of numbers and reasons are thrown around. Leadership either celebrates nothing because “if you hit it, we weren’t trying hard enough” or berates you for not hitting the objective. Another, equally improbable goal is set for the next round. Beatings continue until morale improves.
评论 #39788305 未加载
mkl95大约 1 年前
You can do things the hard way and build a good product, or take shortcuts and build a not-so-good product. Most OKRs encourage leadership to take shortcuts and be cheaper (AKA more efficient). You can improve OKRs as much as you want, but most companies benefit more from problem solving than number chasing.
charlie0大约 1 年前
Our startup recently started using OKRs and gotta say, I&#x27;m not a fan. OKRs were set to be quarterly objects, but things move fast and priorities change. What once was important 2 months ago is now irrelevant.<p>The other difficult things about OKRs is attempting to assign metrics. Most of the stuff worked at in a startup are new and exploratory. That means there isn&#x27;t a sense of what a good number for success even looks like. What happens is arbitrary, and thus meaningless, numbers are assigned to OKRs just for the sake of adding metrics.<p>It seems to me OKRs are over-engineered for the purposes of achieving short-term goals. There&#x27;s probably a better framework for this.
评论 #39796079 未加载
raywu大约 1 年前
Can someone explain the leading and lagging indicator in this paragraph?<p>&gt; OKRs, given they typically focus on change are usually leading indicators focused on shorter time windows and KPIs, which represent the health of what the organisation seeks to sustain, are usually lagging indicators focused on longer timeframes.
评论 #39787463 未加载
评论 #39787472 未加载
numbsafari大约 1 年前
Curious if anyone else has had success using “4DX”[1] over OKRs?<p>[1] <a href="https:&#x2F;&#x2F;www.amazon.com&#x2F;Disciplines-Execution-Achieving-Wildly-Important&#x2F;dp&#x2F;1491517751" rel="nofollow">https:&#x2F;&#x2F;www.amazon.com&#x2F;Disciplines-Execution-Achieving-Wildl...</a>
mtremsal大约 1 年前
This is very interesting. This is similar to how Big Tech runs tech projects in a vastly different way than the “good practices” for agile&#x2F;scrum commonly adopted by the industry at large.<p>e.g. <a href="https:&#x2F;&#x2F;blog.pragmaticengineer.com&#x2F;project-management-at-big-tech&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.pragmaticengineer.com&#x2F;project-management-at-big...</a><p>Similarly the article on OKRs describes small but critical adjustments from the OKRs cannon (Measure What Matters) that only scale-ups and Big Tech seem to know about. Everyone else too often tries to:<p>1. Cascade OKRs down from the top, sometimes outside Product &amp; Engineering (in teams that are more process- than project-based like sales), killing team-level autonomy in the process.<p>2. Write Objectives for time consuming activities, rather than having a non-OKR work &#x2F; BAU section that captures it. This makes it much harder for other teams to rely on OKRs to understand the context of what’s changing and to have key cross-team alignment conversations.<p>3. Focus on OKR tracking and scoring, possibly through a dedicated tool. This misses the point that the primary value of a plan is in the planning, not the deliverable, and risks making OKRs a performance management tool (at which point teams discuss KRs endlessly to sandbag rather than setting stretch goals and moving on).<p>But when you say the local implementation looks both overkill and misguided compared to what works at other tech shops, people point to the OKR book as what drives their own implementation. :)
maytc大约 1 年前
IMHO, cascading is OKRs&#x27; real power. It forces the organization to say no to most things, which sharpens its focus on what needs to be done.<p>Throw that away, setting aligned SMART goals would achieve a similar effect as aligned OKRs.
评论 #39787008 未加载
评论 #39786734 未加载
评论 #39787598 未加载
评论 #39787268 未加载
rickydroll大约 1 年前
While reading the article, I was bothered by the tone-deaf MBA speak, which reminded me of two alternative perspectives to the OKR article.<p><a href="https:&#x2F;&#x2F;longform.asmartbear.com&#x2F;survivor-bias" rel="nofollow">https:&#x2F;&#x2F;longform.asmartbear.com&#x2F;survivor-bias</a> <a href="https:&#x2F;&#x2F;ludic.mataroa.blog&#x2F;blog&#x2F;leadership-is-a-hell-of-a-drug&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ludic.mataroa.blog&#x2F;blog&#x2F;leadership-is-a-hell-of-a-dr...</a>