# OKRs

Published articles for OKRs.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Performative Leadership: From Cargo Cults to OKRs

DevFeed: [Performative Leadership: From Cargo Cults to OKRs](<https://devfeed.tech/articles/performative-leadership-from-cargo-cults-to-okrs-38735.md>)

Original publisher: [Read original article](<https://codecapsule.com/2023/09/25/performative-leadership-from-cargo-cults-to-okrs/>)

Author: Emmanuel Goossaert

Published: 2023-09-25T20:47:50Z

Content type: opinion

Language: en

Sources: [Code Capsule](<https://devfeed.tech/sources/code-capsule.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [context](<https://devfeed.tech/topics/context.md>), [Google](<https://devfeed.tech/topics/google.md>), [intel](<https://devfeed.tech/topics/intel.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [andy-grove](<https://devfeed.tech/tags/andy-grove.md>), [business-processes](<https://devfeed.tech/tags/business-processes.md>), [cargo-cults](<https://devfeed.tech/tags/cargo-cults.md>), [conformity](<https://devfeed.tech/tags/conformity.md>), [consulting](<https://devfeed.tech/tags/consulting.md>), [corporate](<https://devfeed.tech/tags/corporate.md>), [corporate-culture](<https://devfeed.tech/tags/corporate-culture.md>), [corporate-identity](<https://devfeed.tech/tags/corporate-identity.md>), [corporate-rituals](<https://devfeed.tech/tags/corporate-rituals.md>), [critical-thinking](<https://devfeed.tech/tags/critical-thinking.md>), [culture](<https://devfeed.tech/tags/culture.md>), [executive-leadership](<https://devfeed.tech/tags/executive-leadership.md>), [human-psychology](<https://devfeed.tech/tags/human-psychology.md>), [industry-standards](<https://devfeed.tech/tags/industry-standards.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [leadership-and-management](<https://devfeed.tech/tags/leadership-and-management.md>), [leadership-and-management-business-processes-cargo-cults-conformity-corporate-culture-corporate](<https://devfeed.tech/tags/leadership-and-management-business-processes-cargo-cults-conformity-corporate-culture-corporate.md>), [management-practices](<https://devfeed.tech/tags/management-practices.md>), [okrs](<https://devfeed.tech/tags/okrs.md>), [organization](<https://devfeed.tech/tags/organization.md>), [organizational-behavior](<https://devfeed.tech/tags/organizational-behavior.md>), [performative](<https://devfeed.tech/tags/performative.md>), [processes](<https://devfeed.tech/tags/processes.md>), [rituals](<https://devfeed.tech/tags/rituals.md>), [workplace-dynamics](<https://devfeed.tech/tags/workplace-dynamics.md>)

### AI overview

The article argues that leadership tools and organizational practices are often transferred from the local contexts where they worked into other companies through consulting and training, where their original purpose can be lost. It uses OKRs as a central example and states that the author found no empirical evidence that OKRs improve cost efficiency, profits, or stock price, while citing reported difficulties and potential harms from implementation.

### Source excerpt

Unveiling the corporate cargo cult and how industry standards shape a homogenized leadership culture. The post Performative Leadership: From Cargo Cults to OKRs first appeared on Code Capsule.

## Better OKRs Through Threat Modeling

DevFeed: [Better OKRs Through Threat Modeling](<https://devfeed.tech/articles/better-okrs-through-threat-modeling-36697.md>)

Original publisher: [Read original article](<https://shostack.org/blog/better-oks-through-threat-modeling/>)

Author: Adam

Published: 2021-02-15T00:00:00Z

Content type: opinion

Language: en

Sources: [Shostack & Friends Blog](<https://devfeed.tech/sources/shostack-friends-blog.md>)

Topics: [Application Security](<https://devfeed.tech/topics/application-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>)

Tags: [appsec](<https://devfeed.tech/tags/appsec.md>), [okrs](<https://devfeed.tech/tags/okrs.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

This commentary argues that effective threat modeling can improve application security OKRs and help define a strategic AppSec roadmap. It proposes sample objectives involving current threat-model documents, system resilience, security testing, and reducing security debt.

### Source excerpt

Effective Threat Modeling by itself can ensure that your OKRs and AppSec Program are not only in great tactical shape, but also help define a strategic roadmap for your AppSec Program.

## OKRs aren't going to fix your communication issues

DevFeed: [OKRs aren't going to fix your communication issues](<https://devfeed.tech/articles/okrs-aren-t-going-to-fix-your-communication-issues-41215.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2019/03/30/OKRs-arent-going-to-fix-your-communication-issues/>)

Author: Map

Published: 2019-03-30T20:55:56Z

Content type: opinion

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [meetings](<https://devfeed.tech/topics/meetings.md>)

Tags: [behavior](<https://devfeed.tech/tags/behavior.md>), [change](<https://devfeed.tech/tags/change.md>), [communication](<https://devfeed.tech/tags/communication.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [early-stage](<https://devfeed.tech/tags/early-stage.md>), [founders](<https://devfeed.tech/tags/founders.md>), [management](<https://devfeed.tech/tags/management.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [notes](<https://devfeed.tech/tags/notes.md>), [okrs](<https://devfeed.tech/tags/okrs.md>), [philosophies](<https://devfeed.tech/tags/philosophies.md>), [priority](<https://devfeed.tech/tags/priority.md>), [recap](<https://devfeed.tech/tags/recap.md>), [results](<https://devfeed.tech/tags/results.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

The article argues that OKRs do not by themselves resolve startup communication problems. Teams must first identify the problem they are trying to solve and explicitly communicate agreed goals, especially as organizations grow and people miss meetings.

### Source excerpt

Talking with a startup a few days ago they asked for my opinions on OKRs. I have slightly mixed opinions on them overall and started to disclose some of those. Though in sharing some of this I had a few immediate realizations that might be broadly applicable. The crux of his question was, at what stage should we put them in place. I've seen a few companies try to put in some form of OKR, and most were met with pretty mixed results. The reason is that OKRs need to change something about your behavior otherwise why put them in place... either change something about the goals you would otherwise have or the methods at which you went about achieving them. Stepping back a bit, my first question and a very focusing question on almost any situation to ask is "What problem are we trying to solve?" In our conversation he actually paused a bit. As he paused a bit longer it was clear that question had not been fully asked or answered. The first and most common case I see with startups trying to put in place OKRs, v2moms, management by objectives is that the team is not aligned and focused on the same goals. But my follow-on question is consistently, have you communicated what you decided you goals were. Startups tend to go through some distinct growing phases. The early stages all the founders are in a room together building out the product. When you get the first few engineers you expand out a little, but still in a single co-working conference room easily. Eventually you need a real office. At the real office stage you start to have an all hands where, this is probably gathered around a large lunch table at first. At all hands no one takes meeting minutes and sends out a recap, instead people take some notes and you assume everyone was present. But, at about 20 people you have at least one person that misses the weekly team meeting and misses something key. In a 1:1 you catch it that it was talked about as a priority... but they weren't there. This very subtle change I've seen l