4 Comments
Jun 20Liked by Felipe Castro

Felipe, I like the article, good food for thought, I will keep an open mind how I might use is when my own approach hits a wall.

I see the 2nd bucket as KPIs for the Key Results.

At google, OKRs where shared across teams/groups, so one team helping another team is in support of their common OKR & outcome.

Security, compliance, risk, and regulatory work fall into the investment bucket of KTLO with its own set of OKRs.

Expand full comment
author

Thanks, I'm glad you liked it.

A few comments/questions:

- Shared OKRs are extremely important, but you can't use them every time you have a small dependency with another team. Otherwise, teams may end up with too many OKRs. I need to clarify that in the article.

- My point about compliance work is that most of the metrics measure the amount of work done and not the outcome of the work (what I call project metrics). And if you are simply measuring the work, it doesn't make sense to use the outcomes approach.

Outcomes imply doing discovery to figure out a solution that will work for the customer and the business. If the list of projects/tasks you need to do is fixed, you are not focusing on a outcome.

- What do you mean the 2nd bucket as KPIs for the Key Results? Do you mean additional metrics to help you diagnose what's going on with your KR?

Expand full comment
Jun 20Liked by Felipe Castro

Yes... "Do you mean additional metrics to help you diagnose what's going on with your KR? "

Expand full comment
author

Thanks!

Expand full comment