"Measure What Matters" by John Doerr

Get Started. It's Free
or sign up with your email address
Rocket clouds
"Measure What Matters" by John Doerr by Mind Map: "Measure What Matters" by John Doerr

1. What makes a good O?

1.1. Alignment.

1.2. Identify your key stakeholders/key players. (may be derivative from their Os, but not directly cascading)

1.3. "Roof-shots" (Google) - smaller than a moonshot, still allows you to feel/see progress.

1.4. Should be qualitative

1.5. Defined scope (quarterly? for the year?)

2. What makes a good KR?

2.1. Tangible.

2.2. Measurable - on a spectrum, not just binary.

2.3. Something you personally have control over.

2.4. KRs can be checks and balances against each other (quality v quantity)

2.5. Should feel like a moonshot (hard to do, but possible). Something you have to push towards. (at FB they say if you achieved 70% that's a success they need to be a stretch)

3. Problems we're hoping to solve with OKRs

3.1. Create focus for the individual contributor

3.2. Organizational alignment (runway and direction to move faster)

3.2.1. One idea: in a quarter or a month, two or more departments works on the same O with different KRs (e.g. MAU in CX and Product)

3.3. OKRs as a contract. Freeing up management to be more strategic and not tactical.

3.4. Defining what measures success. (The process of selecting OKRs)

4. Examples of companies that use them well or not-so-well & lessons learned

4.1. LinkedIn - implemented OKRs well

4.1.1. Did it well because there was a lot of honest and hard discussion (OKRs wouldn't have gone well otherwise). e.g. if there were hard blockers (if something is achievable)

4.2. Google

4.3. Facebook

4.4. CX @ Degreed

4.4.1. Need to start early (a couple weeks before the quarter starts); start the conversation 1 month before the quarter starts

4.4.2. Os must be balanced with KRs. (If you meet the KRs, the O has been achieved.)

4.4.3. Takes a few quarters to get into the flow

4.5. Nuna

4.5.1. Iterate when you don't succeed

4.5.2. Review OKRs for success or failure and adjust accordingly. don't expect to get it right the first time.

4.5.3. Be persistent in encouraging employees to create their OKRs

4.6. Remind

4.7. Ford

4.7.1. Pinto: OKRs led them to make easily-explodable gas tanks

4.8. Wells Fargo

4.8.1. Many unnecessary bank accounts created because account creation was a metric

5. Challenges with setting OKRs

5.1. Institutionalizing OKRs across culture (everyone has to be all-in)

5.2. How to write good OKRs (especially framing KRs)

5.3. Sizing (quarterly v monthly v weekly)

5.4. How cascading works effectively. (Ideally, higher up KRs become your Os? Or their Os become your Os?)

5.5. How do OKRs tie to one another? (dependencies - how to reference/track?)

5.6. If OKRs are tied to the current implementation (e.g. # of clicks v # of new users)

5.7. Competing OKRs between departments

5.8. When OKRs are used for performance management/metrics

5.9. Balance between top-down and bottom-up

5.10. Goals that work for a startup can be too nebulous for a larger company

5.10.1. MAU

6. Effects of OKRs

6.1. Clarity on what's important. Focus.

6.2. How my work matters.

6.3. How my work connects to that of others'

6.4. Allows you to say no easier to unaligned requests

7. Open questions

7.1. How have CX's OKRs evolved over time?

7.2. What does management need to define in terms of OKRs?

7.2.1. Paired results for balance (quantity vs quality)

7.2.2. Clarity around how KRs support Objectives support company strategy

7.3. What's the deliberation process?

7.4. How do you coordinate inter-dependent goals/cross-department work on the same objective?

8. Setting OKRs

8.1. Quarterly cadence (even monthly - MBOs)

8.2. Forum/discussions about how each person's work ties into objectives

9. Degreed Product Os & KR ideas

9.1. Increase our ability to embed in the HCM suite

9.1.1. (Skills?)

9.1.2. GAT - maximize revenue by connecting users

9.2. Increase the quality of our monthly releases

9.2.1. # of VSTS bugs created

9.2.2. # of customer reported bugs

9.3. Better understand the behavior of our most engaged users

9.3.1. Launch Amplitude

9.3.2. User test with 15 clients

9.4. Make our releases more data informed

9.4.1. Launch Amplitude