The Case Against Treating Outcomes as the Only Good Key Results

This story was originally published on HackerNoon at: https://hackernoon.com/the-case-against-treating-outcomes-as-the-only-good-key-results. Should key results measure outcomes or outputs? This essay argues that outcome-only OKRs can hide the work, weaken learning, and reduce shared understanding. Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #okr, #okr-management, #management-by-objectives, #writing-effective-okrs, #outcome-based-key-results, #goal-setting-frameworks, #responsible-management, #hackernoon-top-story, and more. This story was written by: @taboca. Learn more about this writer by checking @taboca's about page, and for more stories, please visit hackernoon.com. When the stakes are high, our objectives all of the sudden are serious. We set great key results that look like wishes. And we keep on pushing our teams to "just solve the problem". The real problem is that we keep on hiding what we do, how we do, and why we do, we keep on forcing our culture to look professional, pushing us towards learning in retrospect and oriented to trial and error. Let's call the fathers of OKR to rescue the essence of it: Key Results are meant to start the conversation about how to close the gap.