At some point, most teams don’t struggle with ideas, they struggle with execution. Not because people aren’t working hard, but because how work is structured creates noise instead of progress.

There’s a common perception that OKRs are complex. They’re often associated with heavy frameworks, scoring systems, long planning sessions, and documents that feel harder to maintain than the work itself. For many teams, this creates the impression that OKRs are something only large organizations can fully implement. That perception is understandable. But it’s also the reason many teams miss the real value of OKRs.

In many organizations, transparency is often misunderstood. When leaders talk about creating “full transparency,” they sometimes imagine a system where everything is visible to everyone, documents, emails, calendars, tasks, and more. On paper, this might sound like the ultimate form of alignment. But in practice, it often has the opposite effect. Instead of clarity, it creates noise. And when there is too much noise, focus disappears.

SMART goals have been around for decades. And every now and then, the question comes up: Are they outdated?

How often should you change your goals? It’s a simple question, but one that many teams and organizations struggle to answer. And more often than not, the confusion comes from leaning too far into one of two extremes.

Setting goals is something every organization does, but surprisingly few do it effectively. At first glance, it seems simple: decide what you want to achieve, write it down, and track progress. But in practice, most organizations struggle to translate goals into meaningful action.

Setting goals is one of the most common strategies leaders use to align their teams and drive growth. And yet, so many organizations fall into the same trap: focusing solely on high-level numeric targets, like revenue, without connecting them to the behaviors that actually make those targets achievable.

Writing down your ambitions is not the same as achieving them. Setting goals is not even half the battle.

Many organizations proudly say: “We already do OKRs.” But when we start working with them, we often discover something interesting: The framework is in place, the terminology is there, yet very little has actually changed.

One of the biggest reasons organizations struggle with OKRs has nothing to do with strategy. It’s hesitation.