Scaling Small Preparing the next quarter — part 2: planning Here's a simple approach to help you define success metrics and plan your roadmap while keeping things flexible.
Scaling Small Preparing the next quarter — part 1: retros See how you can take a step back and run a quick retro with your team before planning the quarter.
Scaling Small How we use Tability to build... Tability "Eat your own dog food!" — Using Tability is about much more than testing our own product. It's what keeps us focused and flexible.
Scaling Small 5 questions to build your own goal-setting framework 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.
Scaling Small Intercom part 2: How Intercom helps us scale customer success We stopped using Intercom for announcements, but it's still the best way to scale customer success — the right tool for the right job.
Scaling Small How we replaced (part of) Intercom with 100 lines of code 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.
Features A simpler way to tell you what's new We're making feature announcements less intrusive while keeping them easier to find.
Scaling Small Execution beats strategy 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.
Why we're not building yet another OKR tool Sometimes, you have to anchor yourself on an existing conversation to tackle a deeper problem. That's exactly what's happening to us with OKRs.
Scaling Small Why visionary leaders don't scale Visionary leaders can be powerful drivers during early days, but they'll become bottlenecks unless they switch from giving answers to providing questions.
Scaling Small Scaling Small — a Newsletter About Growing Lean 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
integrations Link goals and OKRs to your Jira issues I have a simple way to describe Tability's relationship to Jira: * Tability is where you track outcomes. * Jira is where you track outputs. There's a strong relationship between these 2 concepts. Outcome-driven teams want to see the connections between their goals, and how they're
product teams It's not just what, it's also when Sometimes we give our users all the right answers at all the wrong time. It took us a while to realize this, but we got there.
roadmap Keep your roadmap public to move faster Having a public roadmap has helped us to worry less about competition, and focus more on making our customers happy.
7 ways to see progress on your OKRs and goals in Tability See how Tability can help team leads and contributors visualize progress on their goals and OKRs.
Design Designing Tability – June Update Introducing a few new features to make goal tracking more engaging and intuitive
startups Customer interviews for startups Interviews are one of the most powerful tools for startups. It'll help you save time and money, get free consulting, and turn people into advocates.
Design We can't not judge a book (or a tech startup) by it's cover Some reasons for investing in design early in your start up, and why it has worked for us.
focus The art of not being busy We all want to be busy all the time, but is being busy really equivalent to being productive?
outcomedriven How to combine the Product Lifecycle and the AARRR funnel to map priorities The Product Lifecycle and the AARRR funnel are great tools that can be combined to help you figure out how to launch products, and when to sunset them.
goal-setting Tips and guides to improve your goals next quarter Get your goals and OKRs ready with our tips and tutorials for outcome-driven teams.
futureofwork No, burning yourself out does not make you a business athlete Let's stop guilt-tripping people into working crazy hours by pretending that it's what pro athletes do.
Design Designing for business outcomes: Great, but is it so simple? The truth to “Designing for Business Outcomes,” is that it’s exactly what we should all be doing, but we don’t have the tools, systems, or mentality in place to make an outcome-driven culture viable in an organization. So how do we solve this?
