Notion is designed to help good teams be great. Our mission is to give teams and their leaders the insight they need to continuously improve their health, happiness, and performance. And because our work is all about our customers' work, we decided to start sharing their stories. We have shared stories from the incredible teams at Avid and Upside. Today we talk to Aaron Vernon, CTO of digital product agency, Two Bulls.
Notion is designed to help good teams be great. Our mission is to give teams and their leaders the insight they need to continuously improve their health, happiness, and performance. And because our work is all about our customers' work, we decided to start sharing their stories. We started with the incredible team at Avid, and we continue with Emily Dresner, Chief Technology Officer of Upside Travel!
Over the past few releases, we've added a handful of little features that spell big changes for building and tracking team metrics in Notion.
Most recently, with the introduction of target insights, you can now stay on top of team achievements across your dashboards and help your teams stay focused on the most important goals.
In our most recent Product Stack webinar, I was fortunate to join Dan Podsedly from Pivotal Tracker and Greg Goodman from ProductPlan to discuss some real world examples of aligning product strategy with customer feature requests—a topic that we all run across on a weekly, if not daily, basis in our jobs.
When you work in the software business, whether you're planning the roadmap, shipping product, evangelizing its value, or supporting your customers, it's easy to get lost in the details of the product itself. You spend so much time planning new features and explaining the value of existing ones that you can easily forget why the heck you're doing all this work in the first place: your customers.
In an effort to shine a brighter light on the incredible work that our customers do, we're launching a new series of articles about the teams that use Notion, the products they build and support, and the people that make it all possible.
All too often, software development dashboards focus only on quantitative data and performance metrics like velocity, escaped bugs, and ticket churn. We agree that these metrics are critical to your team's overall success, but there's another category of KPI that is vital to the long-term productivity of your team. Some people refer to this group of software development metrics as Team Health or Team Happiness. At Notion, we call this category of KPIs, Team Joy.
The tricky part with measuring Joy is that this category by definition looks at qualitative information - the feelings of team members - which is challenging to measure in any systematic fashion. After all, a common pitfall with metrics and KPIs is to track only what is easy to measure, which inevitably tells only part of the story. So we advocate using a blend of regular team polls and other team health measurements to understand not just how your team is performing, but how they feel about their work.
JIRA is an amazing ticket management platform. With its vast array of customization options, it can do just about anything you want to manage your software development process. While the data available in JIRA can be as unique and useful as your team, JIRA reporting for teams has a few shortcomings.
Last week, we cohosted a ProductStack webinar called: How Product Managers and Agile Dev Teams Can See Eye-to-Eye.
If you aren't aware, The ProductStack is a community focused on helping product teams build data driven products that customers love. We're proud to be founding partners in the community with ProductPlan and Pivotal Tracker - both companies whose products we use every day. If you're a product leader looking to learn, share, and grow with other like-minded folks, please join our growing Slack community.
Kevin Steigerwald, our co-founder and Chief Product Officer, joined product leaders from both ProductPlan and Pivotal Tracker to discuss how product managers and software development teams can stay aligned, collaborative, and focused on building exceptional products.
With over 600 attendees to the webinar, we got a ton of questions from the audience. Though we did our best to answer many of them during the session, there were some that we missed and wanted to address. As we looked through the long list of questions listeners submitted, we picked out a few prominent and recurring themes, which Kevin took the time to address below.
“Metric” is a magic word in today’s data-driven world. But while some SaaS metrics seem to cast a success spell that moves your business forward, others can curse you if not balanced carefully. This especially rings true in the world of customer support, where metrics have always been a crucial piece of employee performance evaluation and team goal setting. Also check out our recent post on the 7 essential customer success metrics you should be tracking.
A critical part of running a successful software development team is being able to properly plan for each sprint - especially knowing how many stories or points to include in order to release on schedule. Efficient sprint planning requires a thorough understanding of not just your team's productivity, but its accuracy in predicting that productivity. And because it's hard to foresee every event that might influence your dev team's efficiency, it's critical that you consistently track software development metrics that can indicate when your dev team might not deliver on time.
Go beyond burndown charts (though we certainly have a soft spot for burndowns) and discover the metrics you need to be tracking and watching to ensure you stay ahead of roadblocks in your team's way.