I get the difference but still find it hard to think of leading indicators when lagging are so easy. Lagging for the step before is my best rule to start with at the moment.
It is challenging! Depending on your work, behaviour and experience shifts are generally a leading indicator, so we can start by measuring that. The process I follow is: 1. Get clear what problem I'm solving (eg customers frustrated by support ticket turn around time) 2. Understand how I can measure the problem being solved (eg Average ticket closure time) 3. Come up with leading indicator ideas that might move the needle (eg Number of tickets per support person, time respond to a ticket, number of responses per ticket) 4. Choose the ones you like most for your OKR, change them if they turn out to be wrong! Jump over to our slack community and we can go through your actual situation: join.slack.com/t/quickokr/shared_invite/zt-1yqburr2f-XNIaZB_fyJYNsiIIO7Bjig
Sorry, I thought I answered this! Yes, you want to have metrics you can quickly influence. The shorter the time from when you take action to when it shows up in the metrics, the better!
Hey Thiago, check out this video. It has a few examples on how you might apply OKR with Scrum incl product goals: th-cam.com/video/4h3B7wiNMas/w-d-xo.html Let me know what you think!
I finally found a simple explanation to leading vs lagging indicators, thank you
Really glad you liked it!
Great video
Thanks Arash!
I get the difference but still find it hard to think of leading indicators when lagging are so easy. Lagging for the step before is my best rule to start with at the moment.
It is challenging! Depending on your work, behaviour and experience shifts are generally a leading indicator, so we can start by measuring that. The process I follow is:
1. Get clear what problem I'm solving (eg customers frustrated by support ticket turn around time)
2. Understand how I can measure the problem being solved (eg Average ticket closure time)
3. Come up with leading indicator ideas that might move the needle (eg Number of tickets per support person, time respond to a ticket, number of responses per ticket)
4. Choose the ones you like most for your OKR, change them if they turn out to be wrong!
Jump over to our slack community and we can go through your actual situation: join.slack.com/t/quickokr/shared_invite/zt-1yqburr2f-XNIaZB_fyJYNsiIIO7Bjig
Should lagging indicators be for the most part avoided in OKRs?
Sorry, I thought I answered this! Yes, you want to have metrics you can quickly influence. The shorter the time from when you take action to when it shows up in the metrics, the better!
I'd like to see how to use okr with product goal and sprint goal
Hey Thiago, check out this video. It has a few examples on how you might apply OKR with Scrum incl product goals: th-cam.com/video/4h3B7wiNMas/w-d-xo.html
Let me know what you think!