OKR Blog
The 4-Day Design Sprint: A Step-by-Step Guide That Actually Works When I was at ANZ, we tried doing workshops to get alignment and move fast. We had the post-its, the energy, the walls full of ideas. But the truth is, we weren’t really talking to real users, and most of the time we’d finish the week still debating what to build. It wasn’t until I started using Design Sprints properly
I’ve lost count of how many OKRs I’ve read that go something like: Objective: Launch the app Key Result 1: Release the app Key Result 2: Get some feedback Key Result 3: Improve the app It’s a to-do list dressed up in strategy clothes. It looks neat, but it doesn’t move the needle. It doesn’t spark action or build alignment. The truth is, a well-written OKR is less about polish
I hate being late. I hate it even more when my projects are late. I follow the mantra from the great film Glengarry Glen Ross, starring Al Pacino no less! Instead of Always Be Closing (ABC), I follow ACD. Always Be Delivering. You can’t be late when you’re early. It seems my opinion is by far the exception. Instead, most executives roll with “Go big or go home”. They go
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
Understand essential OKR ideas quickly
Use in OKR workshop to keep everyone on track
Gives you the confidence to talk OKR
We respect your privacy. Your information is safe and will never be shared.