Make sure your future is (mostly) in your hands.
You might be obfuscating risks if you're tracking OKRs by replacing values in a cell. Being green does not always mean being on track.
There's a simple way to explain the difference between outcomes and activities in OKRs.
It can take a few quarters to get OKRs right. Here are some practical tips that many had to learn the hard way.
How can you adjust your plan when the world economy hits the breaks overnight?
Over the past 8 years, I've worked as a brand designer for several different tech companies, on different levels of involvement. I've worked with teams like Color Genomics, Cloudflare as an outside consultant
There's a heated debate about microservices vs. monoliths and I'm here to introduce my answer:
Stop asking your team to be customer-driven. Instead you should be blending outcome-driven practices as part of your weekly rituals.
Every company would benefit from working like a remote team, even if people are sitting next to each other.
How can you stay confident about future outcomes if your project takes 6 months to ship? (A: use success proxies)
OKR tools optimize for leadership, and forgot about the rest of the organization needs. Managers love you, but users hate the tool. This needs to change. We are focused on making your team happy first.
Fundraising, interacting with investors, pitching your product are all parts of a startup that no one who's starting a startup wants to do. We're designers, developers, product people; we want to focus on
Are we working on the right things? Make sure that your work is having the right impact by keeping track of progress.
The best way to reduce the costs of mistakes is to catch them early.
Stop getting projects and OKRs mixed up with a simple set of questions inspired by Simon Sinek's "Start with Why".
Cascading OKRs gives you a comforting view of your business. It feels like everything is under control — but this sentiment comes with a high price tag.
Here's a simple approach to help you define success metrics and plan your roadmap while keeping things flexible.
See how you can take a step back and run a quick retro with your team before planning the quarter.
"Eat your own dog food!" — Using Tability is about much more than testing our own product. It's what keeps us focused and flexible.
OKRs are great but a simpler language might be best for your team. See 5 questions that can help you build your own goal-setting framework.
We stopped using Intercom for announcements, but it's still the best way to scale customer success — the right tool for the right job.
Designing solutions too early can be harmful. See how we let go of our initial approach to replace Intercom announcements with a bit of code.
Slow execution puts a huge pressure on a team to get their bets right. Competition that can move faster will catch up even if they had a false start.
Visionary leaders can be powerful drivers during early days, but they'll become bottlenecks unless they switch from giving answers to providing questions.
Throwing more people at a problem is not a sustainable solution. You need to look for better ways to work as well as finding the best people to help