Cascading vs. aligning OKRs: why cascading OKRs might be harmful to your org culture - Deepstash

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

There are 3 main reasons why a cascading model doesn’t work in agile markets:

  • It assumes your strategy is perfect.
  • It’s expensive and slow to move.
  • It leaves many teams on the sideline.

1

3 reads

Cascading OKRs means that teams at a level N can only write their OKRs if OKRs at the level N-1 are written. That means a lot of waiting around.

And, once again, it means having to rebuild the entire OKRs tree if one of the top-level Key Results is changed (this will happen, trust me).

1

1 read

A common question we get during onboarding calls at Tability is about cascading OKRs, and our answer is always the same: don’t do it .

But we’re not the only ones saying that. It’s an opinion shared by OKRs experts like Christina Wodtke or Felipe Castro . This post will show why cascading OKRs is dangerous, and how a simple change can make the whole thing easier.

1

1 read

IDEAS CURATED BY

edmarmiyake

Entrepreneur and angel investor

Edmar Miyake's ideas are part of this journey:

Making Remote Work, Work

Learn more about leadershipandmanagement with this collection

How to create a productive workspace at home

How to balance work and personal life while working remotely

How to maintain focus and motivation while working remotely

Related collections

Similar ideas

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

100+ Learning Journeys

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates