<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Notion Data on Medium]]></title>
        <description><![CDATA[Stories by Notion Data on Medium]]></description>
        <link>https://medium.com/@UseNotion?source=rss-3f1c6f3fd94f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ykCLsVeRiBpY1taJ.png</url>
            <title>Stories by Notion Data on Medium</title>
            <link>https://medium.com/@UseNotion?source=rss-3f1c6f3fd94f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:03:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@UseNotion/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Notion Acquired by Jama Software; Expands Focus on Product Teams Transforming for the Future]]></title>
            <link>https://medium.com/data-driven/notion-acquired-by-jama-f864eb9ebddc?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f864eb9ebddc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[acquisition]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 13:06:15 GMT</pubDate>
            <atom:updated>2018-01-16T13:06:15.120Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*awePZvGIZ3CSbhfZAhl8rg.png" /></figure><p>Today we’re super excited to announce the acquisition of Notion by Jama Software, the leading-product development platform for companies building complex products and systems. Our whole team is joining Jama, and I’m thrilled to expand the work that Kevin and I began almost three years ago.</p><p>Three years ago, a product that easily helped teams focus on and measure process improvement was just a few sketches on an old-window whiteboard at Kevin’s house. Early team members and investors signed on because they believed in the potential of what we were building. In the time since, the team has relentlessly breathed life into a complete platform that taps into the tools that have some of your most important information and makes it easy to surface that information across all of your teams. Notion was always designed to go beyond simple charting — by capturing your conversations and decisions to tell the story behind your data, the path you’re on, and, ultimately, your future trajectory.</p><p>Along the way, we’ve had amazing conversations with our customers and partners that have shaped the way we look at the world, and it’s been incredibly rewarding to help you tune the processes that are driving your business forward.</p><p>We’ve discovered that there are huge shifts happening in the software and hardware product development space. There’s more pressure than ever to launch products quickly, with high quality, and exceed user expectations, but teams building those complex products are struggling to mine the information they already have to make decisions quickly. In the constant struggle to stay on task and on track, leaders are looking for better ways to both understand how their teams are doing and communicate that up and across the organization.</p><p>As we’ve grown Notion and developed the capabilities that are helping teams manage risk and improve performance everyday in their product development lifecycle, we’ve found the greatest need at organizations with the largest teams building the most complex systems. With Jama, we’re united in our belief of a smarter future for product development.. We’re thrilled to serve a larger customer base and bring the Notion capabilities to Jama customers for critical insights into their product development process.</p><p>I want to thank everyone that made the Notion journey possible, and we look forward to continuing to serve you in our next chapter at Jama.</p><p>Dave</p><p>Have a few questions about Jama’s acquisition of Notion? <a href="https://usenotion.com/jama-announcement/">Head over to our FAQ for answers</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f864eb9ebddc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/notion-acquired-by-jama-f864eb9ebddc">Notion Acquired by Jama Software; Expands Focus on Product Teams Transforming for the Future</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Your Team Better When You’re Running a Modern Stack]]></title>
            <link>https://medium.com/data-driven/running-your-team-better-when-youre-running-a-modern-stack-dc14cfd6810f?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc14cfd6810f</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 20:46:03 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:29.558Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by: </em><a href="http://usenotion.com/"><em>Notion</em></a><em> co-founder and CEO, </em><a href="https://medium.com/@dshanley"><em>Dave Shanley</em></a><em>.</em></p><p>As product managers and leads, we’re constantly trying to optimize our teams for productivity and success. It’s seriously competitive out there, and we’re all winning, right?</p><p>Before starting <a href="http://usenotion.com/">Notion</a>, <a href="https://medium.com/u/457ffb926a27">Kevin</a> <a href="https://twitter.com/dshanley">and I</a> were lucky enough to see the power of bringing a data driven framework to our teams to make decisions. But it was hard to do. We set up spreadsheets, logged in to different tools to grab data, took screenshots. All that time spent pasting stuff for the team into Hipchat and Slack meant we had to track down the conversations again when it came to monthly or quarterly reporting. There was no easy way to automate it and there was this unmistakeable missing connection between all the tools we were using.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DVLOs1DHYV-WQzxp.png" /></figure><p>Digging in, what we found surprised even us. It’s like the big bang started with the first SaaS companies (Concur, Salesforce, Netsuite, Webex) and is only just cooling off (but you’d never know it). Using the marketing tech space as an example, there are more than 5x the companies today than 2012. There are <a href="http://chiefmartec.com/2015/01/marketing-technology-landscape-supergraphic-2015/">2x the companies today than there were just last year</a>. Think back to the tools you were using three years ago — your team is likely using (and paying for) more than twice as many now. I know we were. Scott Brinker (from <a href="http://chiefmartec.com/">ChiefMarTec.com</a>) highlights that the <a href="http://chiefmartec.com/2014/10/just-martech-fintech-legaltech-hrtech-etc/">Five Revolutionary Forces of the Cloud</a> are going to continue driving the growth of this universe, and we’ll all be using more tools with the hope of being more competitive.</p><p>Our team was signing in to 10 tools just to get notifications. Now there is <a href="https://slack.com/">Slack</a>.</p><p>We were integrating with four or five APIs to send the same customer metrics and events. Now there is <a href="http://segment.com/">Segment</a>.</p><p>We were writing a lot of glue code to get our tools’ APIs to work together. Now there is <a href="http://zapier.com/">Zapier</a>.</p><p>What we love about these new layers for making our SaaS stack work better is that we buy them just like the tools we already have. Free trial, easy self signup, fast deployment, and a really fast time to initial value.</p><p>We want to deliver that same experience for all the insights into how your team is doing. It used to be called business intelligence, but that might be a dirty word given that up to 80% of those projects fail and can cost hundreds of thousands of dollars. We’re building Notion, so you get easy self signup, fast deployment, and same-day insights into the tools you’re already invested in. Your data isn’t just a byproduct — it’s your greatest asset, and we want to help you accomplish your goals in a very big way.</p><blockquote><a href="http://usenotion.com/school">Enroll in one of our School of Little Data courses and master the art and science of Team Intelligence.</a></blockquote><p>We’ve been there — asked how our team metrics were performing: it took too many people, too many tools, and too much wasted time to come up with a good enough answer. We believe, like Steve Singh, that “if we can focus on our weaknesses alongside the things we are great at, we will become impossible to beat.”</p><p>If you feel the same way and want to learn how to maximize your operational ability with the tools you already love, sign up for a free trial: <a href="http://www.usenotion.com/">usenotion.com</a></p><h4>If you enjoyed this post, please click that little green heart below. Also subscribe to our <a href="http://usenotion.com/school/newsletter">School of Little Data Newsletter</a> and get future posts delivered right to your inbox.</h4><p><em>Originally published at </em><a href="http://blog.usenotion.com/running-your-team-better"><em>blog.usenotion.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc14cfd6810f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/running-your-team-better-when-youre-running-a-modern-stack-dc14cfd6810f">Running Your Team Better When You’re Running a Modern Stack</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Little Data for Better Product]]></title>
            <link>https://medium.com/data-driven/little-data-for-better-product-254f7cf4629c?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/254f7cf4629c</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 21:27:42 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:31.416Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve heard about big data. But how are you using Little Data?</p><p>Maybe you wear a FitBit or track your spending. Seeing how many steps you take each day can help you to set incremental goals to help you to get more healthy.</p><p>In agile software development, you can learn a lot by tracking your data, too. If you don’t have a good way to measure and analyze your team metrics, you’ll get stuck in an endless cycle of guessing and speculation.</p><p>In the <a href="http://theleanstartup.com/">Lean Startup</a>, Eric Ries described an ideal process as “Build, Measure, Learn.” But a lot of teams are still relying on a process that is more like, “build, get a vague impression, guess.” That’s because, despite the many sources of data we have at our disposal, getting ongoing context, learning and then operating from a truly data driven framework can be a real challenge.</p><p>For example, you may be collecting data about your development process (ticketing &amp; bugs) in JIRA, customer feedback in a tool like Zendesk, user interaction behaviours in you own app database and engagement metrics in something like HubSpot. Awesome! You should have everything you need!</p><h4>Big data: Big headache</h4><p>If all this is so great, why don’t all companies have a great Build, Measure, Learn approach?</p><p>In the past, enterprising CEOs and agile Product Managers would create custom databases, make elaborate spreadsheets, or just eyeball different metrics in different systems. There could be a veritable flood of PDFs, powerpoints, emails but the information would still be disjointed.</p><p>Because many of our software tools measure on a short-term basis, it’s often hard to see how data trends across time. Many of the metrics that do get tracked aren’t useful, because they only tell “what happened” without giving context to make better future decisions.</p><p>There is a significant challenge of giving context to data that may be small in each segment, but can grow completely unwieldy if it’s all thrown together without that data driven framework.</p><p>You could have been tracking your steps by figuring out the distances you walked and adding it all every day, but that probably would have gotten old quickly. We designed Notion to make tracking your team’s data more intuitive and centralized in a single KPI dashboard so you can visualize it and make correlations more easily.</p><h4>Why do you need little data?</h4><p>The data that you can get about your product engineering team is crucial in planning your product process and sprints. Collecting information over time about what you can accomplish in a typical cycle lets you estimate how many features you can develop, how much time you need for QA, and what reasonable expectations look like.</p><p>Other SaaS metrics can tell you about your customer’s satisfaction with what you’re making, and about the financial indicators of your success. These are all numbers that are unique to your product, team and market. There is no giant repository of data that can replace these individual measurements and lead you to better decisions.</p><h4>Build, Measure…?</h4><p>There are a ton of things you could measure and sometimes the sheer volume can make selecting key metrics confusing. When we’ve talked to successful agile Product Owners we’ve discovered that there are some measurements that will benefit almost every company and team, and some that are more specific to your particular set of goals.</p><p>We’ve put together a guide of some of the most important metrics for each stage of your company, based on the idea of Dave McClure’s Pirate Metrics for SaaS companies. In addition, <a href="http://usenotion.com/aarrrt/">our AARRRT! Guide</a> explains some of the key Team Metrics that reflect what your engineering team can accomplish. These are the metrics that most SaaS teams will learn the most from.</p><p>At Notion, our focus on product development means that Build metrics like Throughput, <a href="http://blog.usenotion.com/little-data-dre-metric">DRE</a> and <a href="http://blog.usenotion.com/do-you-know-your-cycle-time">Cycle Time</a> can be compared with the metrics that indicate customer happiness. Team Intelligence means understanding how your developers are impacting your business.</p><blockquote><a href="http://usenotion.com/school">Want to master the art and science of Team Intelligence? Enroll in one of our School of Little Data courses.</a></blockquote><p>Most SaaS companies focus on the process of bringing on new customers in their growth stage, while retention and customer success might be more emphasized with maturity. When your product is in its early stages, your team may be putting all its energy into developing features and increasing <a href="http://blog.usenotion.com/little-data-velocity-throughput-kpi">velocity</a>, which may turn into a focus on quality and stability as you grow.</p><p>In the School of Little Data, we’ll also be covering specific metrics to track for early stage and mature products, for comparing SaaS metrics from sales, support and marketing, and for solving specific problems such as <a href="http://blog.usenotion.com/a-double-take-on-churn">Churn</a>.</p><p>You don’t need to use Notion to get started with your Measure step. Most of the recipes we include in the <a href="http://usenotion.com/aarrrt">AARRRT guide</a>, for example, could be entered into a spreadsheet and will start to give you a picture of what you can Learn after you Build and Measure.</p><h4>Taking action</h4><p>It’s helpful to see all your data in nice-looking graphs, but without acting on the information, you really can’t get anywhere. The point of Build, Measure, Learn is that learning informs your next build process.</p><p>For example, you’ve noticed that user churn has been increasing over the last few weeks. Members of your team believe that to resolve the issue the focus should be on delivering new features as fast as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*HqaEhUpo8s_weCaubt2Igg.png" /></figure><p>As the product owner, it’s your responsibility to understand if this is the best solution. And to do that, the more data you have the better.</p><p>To start, you’ll want to look at some of your dev team metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*nQ-__eyXgMKlgbJn-ZSMIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*YQ5m-TQiwgrQx49S1-Y19A.png" /></figure><p>Velocity has been pretty consistent and going up. But Team Morale — a team poll you set up to track how the team feels about the amount of work they are doing each sprint — is starting to drop, which indicates to you that you can’t push the team much harder. Meaning trying to release new features at a faster rate with the current team isn’t possible.</p><p>So you probably need another option to reduce your churn.</p><p>Next you look at Throughput. Over the past few sprints you can see that your team is already delivering more features than normal, and as a result fewer bugs are being delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*ixNd9WuKBDn3cLUcn658Jg.png" /></figure><p>While this could mean that your code quality is improving and there are simply fewer bugs to work on, it could also mean code quality is dropping because the team isn’t spending time there. Let’s look at more data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*hH_xsSOtsqlub2MtjWrd-Q.png" /></figure><p>Your Defect Removal Efficiency is dropping. This is a way to track where your bugs are being found, and in this case, more are being found in production.</p><p>And when you peek at the number of customer support requests, you see that it is increasing as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*g_al3i_aVLbZFzNbQNlHLQ.png" /></figure><p>This is all the info you need now to form the hypothesis: Code quality is decreasing, which is resulting in an increase user churn. The team is releasing features too fast already, which is taking time away from fixing existing bugs AND increasing new bugs into the system.</p><p>To track this hypothesis, you create a new dashboard and set goals around the following recipes:</p><ul><li>Bug Reaction Time</li><li>Throughput</li><li>Bug Cycle Time</li><li>User Churn</li><li>Team Morale</li></ul><h4>Communicating your results</h4><p>One of the most frustrating aspects of data that we encountered before building Notion was that individual SaaS metrics were often siloed in specific departments. Developers, the support team, marketing folks and product people didn’t have much of the data that could help them to each make more effective decisions. Despite our common goal across the organization, vital data collected in an app could get stuck and never leave the department that used that software.</p><p>We also encountered situations where we needed to communicate results with investors, clients or other stakeholders and there wasn’t a simple way to create a good-looking, meaningful KPI dashboard report to convey progress. It’s been great to be able to create custom reports anytime for people who contribute to our success.</p><p>For us, the goal of greater communication seems to be as important as collecting and visualizing data so that if you’re making decisions about the product, you’ll have the context and expertise of the whole company to inform you.</p><p>What is your experience with Little Data? What do you want to learn more about? Write to us at <a href="/service/mailto:school@usenotion.com">school@usenotion.com</a> and be sure to <a href="http://usenotion.com/school/newsletter">subscribe now</a> to the School of Little Data newsletter if you haven’t already.</p><p><em>Originally published at </em><a href="http://blog.usenotion.com/little-data-for-better-product"><em>blog.usenotion.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=254f7cf4629c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/little-data-for-better-product-254f7cf4629c">Little Data for Better Product</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A quick take on a simple support metric]]></title>
            <link>https://medium.com/data-driven/a-quick-take-on-a-simple-support-metric-87d938fc8926?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/87d938fc8926</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 21:07:32 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:29.021Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>tl;dr</strong> While customers may expect it, replying as fast as you can to support requests won’t immediately solve your problems. Find the right balance between response time and team morale and properly set expectations with your customers to achieve support success.</p><p>Providing a high level of customer care is critical to your product success, but is hard to achieve. When customers have a problem, they often want a solution instantly. Thankfully, there are a great many customer ticket support tools that help you provide fast and efficient service whether you’re a small start up or a large enterprise. The challenge is that the more power we have to respond instantly, the more the customer comes to expect instant gratification all the time.</p><p>If you are delinquent in responding to customers, then you risk negative impact on Customer Satisfaction which correlates with larger issues such as Customer Churn. Moreover, it’s not uncommon for customers to complain on social media, which can undermine marketing and acquisition efforts.</p><p>Here are a few helpful steps to create a data driven framework for ensuring your team is properly meeting customer expectations and delivering feedback in a timely fashion.</p><h4>Step One</h4><p>Find your average Time to First Response.</p><p>The formula itself is simple: the average amount of time it takes to initially respond to support requests from when they are first filed within a set period of time.</p><p>Depending on the volume of support tickets you get, you may want to track this daily or weekly in a KPI dashboard software.</p><p>Most of the support ticketing tools will track this for you, but it is important to make sure everyone on your team is aware of it, so it helps to include it on a team KPI dashboard.</p><h4>Step Two</h4><p>Setting targets around your response time as a team is critical for measuring and improving customer satisfaction.</p><p>For example, during work hours, you might want your response time to be less than 15 minutes. But after work hours, your response time can drop to less than 4 hours. Find what works for your team as a group and be committed to sticking to those targets.</p><p>Targets give you direct indicators to know how well or poorly the team is performing. It also helps you set expectations with your customers. If they know upfront that it will take approximately 15 minutes for you to respond, they are more likely to be understanding of their initial wait.</p><h4>Step Three</h4><p>Compare your response time alongside overall customer satisfaction and team morale. A stable response time, customer satisfaction score or NPS, and team morale is a good thing. Decreasing response times correlated with decreasing morale regardless of an increasing CSAT or NPS is something to watch out for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*F5kXLvhUGGwx5lidwi8B5Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*glfzjeZqcVDfOfAEzb3CUw.png" /><figcaption><a href="http://usenotion.com/">Notion</a> allows you to easily compare different metrics to get the complete picture.</figcaption></figure><p>Test and measure adjustments to your targets to find the proper balance for your customers and team. <em>(Pro tip: This is exactly what we built Notion to help with). </em>Understanding the Problem Resolution Time can help complete the picture as well, but we’ll save that for another lesson.</p><blockquote><a href="http://usenotion.com/school">Enroll in one of our School of Little Data courses and master the art and science of Team Intelligence.</a></blockquote><p>You can track all this Support metrics right in <a href="http://usenotion.com/">Notion</a> so everyone has visibility to it. We even do the calculation for you if you are using <a href="http://usenotion.com/zendesk/">Zendesk</a>.</p><p>Building great products isn’t easy, but sometimes supporting them is even harder. Your product sets high expectations all around and paying close attention to these simple company and team metrics helps you manage those expectations while keeping a finger on the pulse of your support team.</p><p>We’d love to hear any tips or tricks that work for your team as well.</p><p><em>Originally published at </em><a href="http://blog.usenotion.com/little-data-quick-take-simple-support-metric"><em>blog.usenotion.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87d938fc8926" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/a-quick-take-on-a-simple-support-metric-87d938fc8926">A quick take on a simple support metric</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Managers: How Active is Active?]]></title>
            <link>https://medium.com/data-driven/product-managers-how-active-is-active-2f34e2c22079?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f34e2c22079</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 20:35:36 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:29.463Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>tl;dr</strong> Active User rates are vanity metrics that can mislead or misrepresent your actual success. Tying user activity to the core value of your app is a better way to provide actionable insights for your team.</p><p><em>This article is the new lesson from our ongoing newsletter, the </em><a href="http://usenotion.com/school"><em>School of Little Data</em></a><em>. If you’d like to receive articles like this a week in advance, </em><a href="http://usenotion.com/school/newsletter"><em>subscribe here</em></a><em>.</em></p><p>A common metric that most agile product owners and teams track is their active user rate. Whether it’s monthly (MAU), weekly (WAU), or daily (DAU), it’s seen as a simple metric to calculate and represent how their app is doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Yo0z2CKiNCxXoX7sa5lv7Q.png" /><figcaption>Track your actionable metrics with <a href="http://usenotion.com/">Notion</a></figcaption></figure><p>Unfortunately, there are a few problems with active user rates that people often overlook.</p><p>First, as a SaaS metric, it’s easy to manipulate and difficult to compare. One company’s definition of active might be very different than another. So if your goal is to claim as many (or more) active users as one of your competitors, you could tweak your definition to increase your count. But what will you have really learned from that?</p><p>Even within your own company, the definition of active might mean different things to different departments. Without proper alignment, your marketing team and product team might have conflicting ideas of what is or isn’t working in the product — causing dissension around what to fix.</p><p>Second, it’s hard to <strong>make the data actionable</strong>. If your MAU drops from 75% to 63% in a month… do you know why? Not from just looking at MAU, you won’t. You’ll not only be left scratching your head wondering what caused the drop-off but also wondering what you can do to make sure it doesn’t happen again.</p><blockquote><a href="http://usenotion.com/school">Enroll in one of our School of Little Data courses and master the art and science of Team Intelligence.</a></blockquote><p>We recommend a better way of approaching user activity as part of your company’s data driven framework for decision-making. The first step is to define the features that provide the true value of your app. As an example, let’s say you are a photo sharing app. One of your most valuable features is users actually sharing a photo — because without photos, users won’t return.</p><p>Next, you want to set up what we call an <strong>L7 metric</strong> around that feature. That is, how many users have performed an action in the “last 7 days”. (Note: the number of days may change, over time, to meet the specific needs of your product.)</p><p>So rather than just looking at your MAU, it’s better to look at how many users uploaded a photo each week. And if no one has been uploading photos over the past few weeks, it’s now no longer a surprise to see that your MAU is dropping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*KffmBcIYC96mUVtAiabw9Q.png" /><figcaption>Track real <strong>actionable metrics</strong> in your KPI Dashboard with <a href="http://usenotion.com/">Notion</a>.</figcaption></figure><p>With this information in hand, you can focus your efforts on features that make it easier to upload photos.</p><p>And just like that, you’ve gone beyond a vanity number in your KPI dashboard software to a real, actionable SaaS metric that you can experiment with.</p><p>Of course, your app is probably a little more complicated than a single feature, so be sure to <strong>set up multiple L7 metrics</strong> to help pinpoint the areas of strength and weakness within your application.</p><p>Using <a href="http://cur.at/4rgCSUh?m=web&amp;sid=kaZNMT8">Mixpanel</a> or <a href="http://cur.at/owtjXQQ?m=web&amp;sid=kaZNMT8">Intercom</a> are both great ways to set up segments to easily get at these numbers. And <a href="http://cur.at/Qmmw1qA?m=web&amp;sid=kaZNMT8">Notion</a> makes a great home to store the data, so your team has full access to the results.</p><p><em>Originally published at </em><a href="http://blog.usenotion.com/little-data-vanity-metrics"><em>blog.usenotion.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f34e2c22079" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/product-managers-how-active-is-active-2f34e2c22079">Product Managers: How Active is Active?</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Superstars: Aaron Vernon, CTO of Two Bulls]]></title>
            <link>https://medium.com/data-driven/customer-superstars-aaron-vernon-cto-of-two-bulls-6959d764302c?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6959d764302c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[notion-case-study]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 22:07:07 GMT</pubDate>
            <atom:updated>2017-11-10T18:51:24.663Z</atom:updated>
            <content:encoded><![CDATA[<p>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 <a href="https://medium.com/shining-a-light-on-customer-superstars-meet-michelle-and-avid-technology">Avid</a> and <a href="https://medium.com/customer-superstars-emily-dresner-cto-of-upside-travel">Upside</a>. Today we talk to <a href="https://www.linkedin.com/in/avernon/">Aaron Vernon</a>, CTO of digital product agency, <a href="https://www.twobulls.com/">Two Bulls</a>.</p><figure><img alt="Screen Shot 2017-10-04 at 3.04.26 PM.png" src="https://cdn-images-1.medium.com/max/803/0*8V05fmzq57mXA-j8.png" /></figure><h4><strong>Tell us about your product.</strong> What do you spend your days building? What’s the coolest thing about it? Why do your customers love it?</h4><blockquote>At Two Bulls we build innovative digital products for our clients. This is great because it means we the have the opportunity to keep adapting to and working with the latest technology.</blockquote><blockquote>Products our teams are working on include a global telco’s smart cities infrastructure &amp; product, a multi-country industrial IoT system connecting and monitoring remote sensors over a low power, wide-area LAN (LPWAN), a smart appliance ecosystem for a partner who installs over 400,000 kitchens a year in Europe, rethinking &amp; building new technology to improve the school food ecosystem for a company that covers over half of all the children in America. For each of these platforms we connect intelligent edge devices to each other, to the cloud, and to front end interfaces on mobile, web, and custom hardware.</blockquote><blockquote>Our clients love that we do everything in house with fully-integrated teams. We also push them to embrace the latest technologies, whether that be serverless infrastructure in the cloud, modern languages like Kotlin and Swift on mobile, or edge technologies like LoRa networks, device-to-device connectivity, and distributed intelligence at the edge.</blockquote><h4><strong>Tell us about your team</strong>. Why are they amazing? What is your favorite thing in working with them? If you could do anything to help them, what would it be?</h4><blockquote>Our entire team gets excited by beautiful solutions, solving difficult problems, creating great user experiences and being at the forefront of everything that we do. I love working every day with intelligent, ambitious and product driven people. <strong>As the technical leader of the company, my goal is to always enable engineers to have the environment and context to do their best work.</strong></blockquote><h4><strong>Tell us about data, numbers, metrics.</strong> What sources do you track? How does data help your team be successful? What’s your biggest struggle in using data?</h4><blockquote>We use JIRA for our project management and are very disciplined in each team’s implementation of Agile, be it Kanban or Scrum. Usually all of the data we ever need is available in a raw format but it can sometimes be extremely difficult to transform it into a form that can be easily communicated and digested by managers and stakeholders. This has the flow on effect that metrics will often end up out of date.</blockquote><blockquote>I tend to be heavily inspired by the quote “If you can’t measure it, you can’t improve it.” This means data, numbers and metrics are obviously instrumental to any sort of improvement.</blockquote><h4><strong>Tell us about Notion.</strong> When do you review your Notion data? How have you incorporated Notion into your team workflow/processes? What problems has Notion helped you solve?</h4><blockquote>Our teams review Notion data daily and we review it with our clients at least every two weeks. The phrase “if it is not in notion, then it is not done” is something I say <strong>increasingly</strong> around the office. Notion has allowed us to completely automate the process of formatting our raw data in JIRA into a form that presents a holistic view of the project and allows us to make informed decisions. At this high level it is also not unusual to discover counterintuitive information.</blockquote><blockquote>We track things like <strong>rolling average sprint velocity</strong>, <strong>burnups</strong> for particular releases, <strong>bug counts</strong>, <strong>projected remaining time for releases</strong>. Teams also get a lot of value out of tracking the current sprint <strong>cumulative flow</strong>.</blockquote><h4><strong>What would you say is the greatest benefit to using Notion?</strong></h4><blockquote>The greatest benefit of using Notion is that after you set things up there is zero overhead in maintaining daily high quality data, numbers and metrics. A big part of this is the seamless integrations with 3rd party services such as JIRA and Github.</blockquote><h4><strong>In one sentence, tell us what would happen if we took Notion away?</strong></h4><blockquote>Our team members would have to spend more time on laborious tasks rather than working on stuff that really matters.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6959d764302c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/customer-superstars-aaron-vernon-cto-of-two-bulls-6959d764302c">Customer Superstars: Aaron Vernon, CTO of Two Bulls</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Superstars: Emily Dresner, CTO of Upside Travel]]></title>
            <link>https://medium.com/data-driven/customer-superstars-emily-dresner-cto-of-upside-travel-fe4e5acd9761?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe4e5acd9761</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[notion-case-study]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Mon, 18 Sep 2017 18:26:23 GMT</pubDate>
            <atom:updated>2017-11-10T18:51:43.394Z</atom:updated>
            <content:encoded><![CDATA[<p>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 <a href="https://www.linkedin.com/in/emilydresner/">Emily Dresner, Chief Technology Officer of Upside Travel</a>!</p><figure><img alt="Upside Logo.jpg" src="https://cdn-images-1.medium.com/max/1024/0*xy-SKUC98byCZQlQ.jpg" /></figure><h4><strong>Tell us about your product.</strong> What do you spend your days building? What’s the coolest thing about it? Why do your customers love it?</h4><blockquote>We are <a href="https://meo.upside.com/?utm_source=blog&amp;utm_medium=notion-blog&amp;utm_campaign=NotionBlog&amp;utm_content=EmilyGuestBlogNotion&amp;utm_promo=0">Upside Travel</a>! We are a new online service aimed at giving the do-it-yourself business traveler a better business trip. We’re turbo-charging business trips making it smoother to book or change your trip, get you tools to navigate your trip better, and ensuring you get home quickly and reliably.</blockquote><blockquote>We’re a lean microservices platform built on a Docker and Kubernetes infrastructure. We built our main website in React.js and charged it with an expansive node.js REST platform. We also supply iOS (Swift 3) and Android (Java and Kotlin) apps so <a href="https://meo.upside.com/?utm_source=blog&amp;utm_medium=notion-blog&amp;utm_campaign=NotionBlog&amp;utm_content=EmilyGuestBlogNotion&amp;utm_promo=0">Upside</a> is always-on. Our infrastructure is 100% AWS Cloud Native — no servers anywhere.</blockquote><blockquote>Coolest thing about <a href="https://meo.upside.com/?utm_source=blog&amp;utm_medium=notion-blog&amp;utm_campaign=NotionBlog&amp;utm_content=EmilyGuestBlogNotion&amp;utm_promo=0">Upside</a> from a purely technical perspective is how fast we ship changes to production. On a busy day, we can push 20+ microservice changes to production. Because of how we architected our system, we can move a new feature from an engineer desk to production in a few minutes. Another cool thing: because we embraced lean microservices hard, we can easily spin up new features, teams, and products in parallel with all other development without anyone stepping on toes!</blockquote><blockquote>Our customers don’t have their own in-house dedicated travel staff or support staff. They’re stuck making all their plans themselves and navigating the thin-margin leisure market. They love we can give them the customer service they deserve when they buy through <a href="https://meo.upside.com/?utm_source=blog&amp;utm_medium=notion-blog&amp;utm_campaign=NotionBlog&amp;utm_content=EmilyGuestBlogNotion&amp;utm_promo=0">Upside</a>.</blockquote><h4><strong>Tell us about your team</strong>. Why are they amazing? What is your favorite thing in working with them? If you could do anything to help them, what would it be?</h4><blockquote>Our <a href="https://resources.upside.com/team?utm_source=blog&amp;utm_medium=notion-blog&amp;utm_campaign=NotionBlog&amp;utm_content=EmilyGuestBlogNotion&amp;utm_promo=0">team</a> here at Upside is the elite of the Washington DC metro area (Maryland, Virginia, DC). We focus heavily on full stack here. We look for engineers who can walk and chew gum, produce a pixel-perfect front end while a perfectly scaling web service, who is comfortable working with a UX designer and DevOps. They’re mostly Node.JS engineers (so they tell me).</blockquote><blockquote>We have a strong “<a href="https://engineering.upside.com/top-5-reasons-why-youll-love-the-engineering-culture-at-upside-153a9f999698">no jerk</a>” policy here at Upside. No bros, no egos, none of that nonsense. We’re a high performing sports team trying to win the Super Bowl. Not the local high school team. Awesome people are on the Upside engineering team — awesome colleagues and awesome friends.</blockquote><blockquote><strong>If I could do anything for the team, it would be to get them better information to get more done, faster.</strong></blockquote><h4><strong>Tell us about data, numbers, metrics.</strong> What sources do you track? How does data help your team be successful? What’s your biggest struggle in using data?</h4><blockquote>Upside is 100% on JIRA for all epic, story, task, and bug tracking. We use it as our main source of “truth” when it comes to overall team performance. We’re mostly looking at:</blockquote><blockquote><strong>Burn Ups</strong>. How well the teams are tracking against completing all current sprint work against the mutually understood goal.</blockquote><blockquote><strong># of Story Points Resolved. </strong>How much work is engineering-complete but sitting on staging waiting for Product Manager sign-off.</blockquote><blockquote><strong>Throughput</strong>. How many “things” the team completes in a two week sliding window. This lets us understand if the team is spending their time fire fighting or fixing bugs vs working on feature work.</blockquote><blockquote><strong>Velocity.</strong> We look at a 6 week, 1 sprint back sliding window of velocity to see if the team is under-committing, over-committing, needs more engineers, and generally gelling as a group.</blockquote><blockquote>Velocity is an extremely useful metric for the teams and their Product Owners (here, Product Managers). It allows us to understand the “size of the bread box” — ie, how much the team can reasonably commit and see success. Because we don’t track velocity/engineer but by overall team metrics, we can predict how much work a team can complete, if a team will benefit from another team member or have Mythical Man Month issues, and how much they can commit to in a full release.</blockquote><blockquote>Our biggest struggle is the standard fight with of Man vs. JQL. JQL is a <em>very </em>powerful query language to derive facts, but it’s not friendly. Much of the useful queries are buried 4 or 5 levels deep on Atlassian’s documentation page. It has plenty of powerful date manipulations and custom query functions, but they’re not immediately obvious.</blockquote><h4><strong>Tell us about Notion.</strong> When do you review your Notion data? How have you incorporated Notion into your team workflow/processes? What problems has Notion helped you solve?</h4><blockquote>Frankly, we’re hooked on Notion. We review Notion data daily. It helps engineering leadership and product head off what look like slow downs, blockers, and problems. We’re a low friction/high shipping organization, so those burn ups not moving for a few days is an indicator to get in and figure out what’s going on.</blockquote><blockquote>We tried several tools to integrate with our JIRA data and workflow but they were all either too complex for our needs, woefully incomplete, or limited. None of them worked well for our team. Notion is the first tool that sits on our team’s actual daily workflow and allows us visibility across all the teams quickly and easily.</blockquote><h4><strong>What would you say is the greatest benefit to using Notion?</strong></h4><blockquote>The greatest benefit to using Notion are the quickly and easily generated reports at my fingertips right from the JQL we use every day. If Notion went away tomorrow, we’d have to rebuild it ourselves!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe4e5acd9761" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/customer-superstars-emily-dresner-cto-of-upside-travel-fe4e5acd9761">Customer Superstars: Emily Dresner, CTO of Upside Travel</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transform Your Team with Smarter Dashboards and Better Insights]]></title>
            <link>https://medium.com/data-driven/transform-your-team-with-smarter-dashboards-and-better-insights-d3610535a30e?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3610535a30e</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 23:03:12 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:29.840Z</atom:updated>
            <content:encoded><![CDATA[<p>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.</p><p>Most recently, with the introduction of <strong>target insights</strong>, you can now stay on top of team achievements across your dashboards and help your teams stay focused on the most important goals.</p><p>In this post, we’ll walk through a few of these recent updates and highlight how your team can benefit from them.</p><h4>Recommended metrics for easier dashboard setup</h4><p>If you’re new to Notion, you’ll find an Action Plan designed to help you get started quickly, customized for you based on your answers to a quick survey at signup. If you want to connect your tools to Notion, we’ll walk you through the connection process (with zero engineering support needed) and show you a few examples of metrics you can create with your data.</p><figure><img alt="Screen Shot 2017-09-14 at 9.28.00 AM.png" src="https://cdn-images-1.medium.com/max/762/0*gjKmFUaHgFyAfIK4.png" /></figure><h4><strong>Metrics Strategies: you asked, we answered.</strong></h4><p>Our integrations are a fast and easy way to see your data in your dashboards, but we’ve heard that people are still looking for more guidance about what they should be tracking. With Recipe Bundles in our Action Plan, you will now see a call-out to add recommended metrics directly to your dashboard.</p><figure><img alt="onboarding-select-template.png" src="https://cdn-images-1.medium.com/max/775/0*U4TutDNPo5KAjQH3.png" /></figure><p><em>(Note: whenever you create a new dashboard, you will be able to select from a set of recommended bundles.)</em></p><figure><img alt="onboarding-template-db.png" src="https://cdn-images-1.medium.com/max/1024/0*GFq_hIfmQmwrxmXB.png" /></figure><p>Recommended templates appear on a dashboard just like regular metrics and only require a few small steps to activate. In this example, we have a set of metrics that are optimized for teams undergoing an <a href="https://www.leadingagile.com/">agile transformation process</a>, focusing on accuracy and quality.</p><p><em>(Hint: if you don’t want to track one of the metrics, click the icon in the bottom right corner of the metric card to drag and drop the metric to the trash.)</em></p><h4>Setting up your first metric</h4><p>Similar to our metrics in the Recipe Library, once you click a metric template, you’ll see that nearly everything is set up for you.</p><figure><img alt="template-name.png" src="https://cdn-images-1.medium.com/max/902/0*KfWmQRNvMvH-H5mV.png" /></figure><p>Feel free to edit the name and description from the defaults to customize the metrics to your teams.</p><figure><img alt="template-equation.png" src="https://cdn-images-1.medium.com/max/897/0*WqQJITkUhbrBRBil.png" /></figure><p>The equations for your metrics will also already be defined, but you can always customize these as well.</p><figure><img alt="template-assignment.png" src="https://cdn-images-1.medium.com/max/898/0*9e6qEXES23buSK9a.png" /></figure><p>The only thing you will need to do is assign who will be reporting on the ingredients. You can assign them to yourself, to new or existing team members in your Notion account, or even use ingredients you have previously built with one of our integrations.</p><figure><img alt="template-display.png" src="https://cdn-images-1.medium.com/max/900/0*mQ_6xiWuzWZBs0YK.png" /></figure><p>Finally, you’ll want to review the display options to make sure the data is reported on the correct day (in this example, the last day of the sprint).</p><p>If a target isn’t set, you can also use this opportunity to set one. Not only will the target insights feature require a target to be set; targets are also a simple way to define benchmarks for your team’s progress and clarify expectations for overall goals.</p><h4>Adding data to your metrics</h4><p>Once your metric is saved, click the red “submit data” button above the chart and you’ll be taken to a table where you can quickly enter in current and past values.</p><figure><img alt="metric-enter-data.png" src="https://cdn-images-1.medium.com/max/945/0*OPoYutVFqQ9Gp-HR.png" /></figure><p>If the ingredients have been assigned to team members, they will receive an email notification with a link to report on the data.</p><h4>Watching targets and increasing benchmarks</h4><figure><img alt="onboarding-db.png" src="https://cdn-images-1.medium.com/max/1024/0*twUoKEtnfSZwSgY8.png" /></figure><p>Within just a few minutes, you’ll have your team dashboard up and running. And along with the targets you set, your team now has direct visibility into progress, performance, and bottlenecks.</p><p>As data continues to be reported, you can identify trends, discover what is working, and which areas need attention.</p><p>And thanks to the new target insights, you’ll be notified in the activity feed (and weekly digest) when a target has been achieved.</p><figure><img alt="activity-feed-insights.png" src="https://cdn-images-1.medium.com/max/830/0*M7zXmCv5t4o1ux8a.png" /></figure><p>When a target is achieved, it’s a great time to revisit your goals as a team and see if it makes sense to push back the goal posts.</p><p>Individual metric pages will keep track of which goals you have achieved and when, so you can continue to track progress over time.</p><p>Empowering your team with the tools they need to improve productivity and encourage collaboration are core to the Notion experience. We are excited about these new features and look forward to seeing how your team implements them!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3610535a30e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/transform-your-team-with-smarter-dashboards-and-better-insights-d3610535a30e">Transform Your Team with Smarter Dashboards and Better Insights</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strategies for Integrating Client Feedback into Your Product Vision.]]></title>
            <link>https://medium.com/data-driven/strategies-for-integrating-client-feedback-into-your-product-vision-d509a03e2ca6?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d509a03e2ca6</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 20:53:31 GMT</pubDate>
            <atom:updated>2017-11-07T18:54:30.051Z</atom:updated>
            <content:encoded><![CDATA[<p>In our most recent <a href="http://theproductstack.com/">Product Stack</a> webinar, I was fortunate to join Dan Podsedly from <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a> and Greg Goodman from <a href="https://www.productplan.com/">ProductPlan</a> 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.</p><figure><img alt="product-stack.png" src="https://cdn-images-1.medium.com/max/1024/0*g6aH25BVc_CKJ1Cm.png" /></figure><p>During the webinar, Dan spoke about the difference between simply <em>hearing</em> versus actually <em>understanding</em> customer feedback. Greg highlighted ways to balance the needs of what to build next. And I ran through key metrics you and your team can track to make better decisions around customer feedback.</p><p>Throughout the webinar (which can be watched in full below), we also received dozens of excellent questions — some of which we didn’t have time to address. (<a href="http://theproductstack.com/">You can hop into our Slack group and reach out to us directly, if you like.</a>)</p><p>So I’d like to respond to one that came up from a couple different folks:</p><blockquote>What are the strategies to integrate client feedback into a larger product vision?</blockquote><p>This is definitely a challenge that all teams have to juggle and struggle with. The key metrics I speak about in the webinar are obviously one such strategy, so I do recommend watching the video. But there are a handful of other ways to integrate feedback into your product vision and decision making process.</p><h4><strong>Run “safe to fail” experiments</strong></h4><p>When a feature request comes in, there is typically some inherent risk associated with it. “Should we build this? Will other customers use this? How much will it cost to build and maintain?” I’m sure these are just <em>some</em> of the questions that run through your head.</p><p>So what is one to do? Build a culture focused on running experiments and set the tone early that it is ok to fail.</p><p>Experiments should be thought of as iterative, non-binding, and low-effort approaches to learning more about the biggest unknowns related to a feature request.</p><p>The experiment can take many forms. It can be a simple survey that you share out with your most vocal customers looking for validation on a use case. It can be a paper prototype or wireframe used to walk customers through well before any code is actually written.</p><p>And since experiments can look different for each situation, it is important to be consistent in one key area: always make sure you have a clearly defined objective for the experiment and actionable next steps (even if that next step is to shelf development).</p><h4><strong>Send company reports from your Customer Success team</strong></h4><p>Sometimes the biggest hurdle faced in getting the team to buy-in on customer feedback is an issue of visibility. Depending on the organization of your team, the value of, or real need behind, a feature request can be lost in translation as it travels from your customer success team to your business analysts to your product designers and to your developers and then back up the chain to your marketing team.</p><p>Encouraging your customer success team to keep organized documentation of all requests that come in on a weekly basis and making sure they are accessible company-wide is a simple exercise that results in direct insight into feature requests for everyone on the team.</p><p>Once everyone has a better understanding of the root cause and can relate to it on a personal level, more creative (and sometimes simpler) solutions often rise to the top.</p><p>It’s very lightweight and your team can get started on it today. We organize the feedback with a folder in Dropbox Paper, and every Friday a new doc is added and sent out in our #stand-up channel in Slack.</p><h4><strong>Product Parties</strong></h4><p>When it comes to making changes to product vision, there is another straightforward way to make sure everyone on the team has a seat at the table: literally gather everyone around a table and discuss feature requests.</p><p>At Notion, we call these Product Parties. We’re small enough that we can gather the entire company, but if you are at a larger company try to at least have one representative from each department.</p><p>The objective of these parties (don’t call them meetings!) is to make sure there are no surprises if a shift in product direction occurs and to give everyone an opportunity voice their opinions or concerns about any changes.</p><p>No one on the team likes being kept in the dark only to later find out that the product vision is changing as a result of customer feedback they knew nothing about.</p><h4><strong>Transparent roadmap planning</strong></h4><p>Similarly to Product Parties, having a transparent roadmap with your team and involving everyone (or representatives from each department) at planning meetings is the last strategy I’ll talk about.</p><p><a href="https://productplan.com/">ProductPlan</a> is a great tool for this and we use it at Notion. Once a quarter, we try to bring the whole team together again and review upcoming features and walk through the benefits and risks of each one. It’s a great way for the dev team to learn about customer signal, as reported by the support team. And it’s a great way for everyone outside of the dev team to understand the dependencies or scope challenges of a feature that may explain why it gets pushed back.</p><p>The outcome of these meetings isn’t a set-in-stone list of features to build in order. Rather, it provides the entire team with visibility into all the moving pieces that go into the decision making process that will ultimately fall on the product managers to decide.</p><p>Regardless of the tool you use, what is important is to make sure everyone has visibility into the process. That way, when customer feedback comes in and it feels like an immediate, must-act-now response is what is desired, you can push back and remind everyone that there is a process in place and it needs to be evaluated against everything else that has already filled up the near-term roadmap.</p><p>Hopefully you’ve found at least one of these strategies to be actionable for your team. We’d love to hear if you have any more! Here’s a link to our Slack channel.</p><p>If you’re looking for even more help knowing how to incorporate customer feedback into your product strategy, check out these posts from ProductPlan and Pivotal Tracker that answer even more of your webinar questions.</p><p><a href="https://www.productplan.com/recurring-feature-requests/">ProductPlan: When should reccuring feature requests lead to re-evaluating your product strategy?</a></p><p><a href="https://pivotaltracker.com/blog/product-stack-webinar-follow-up/">Pivotal Tracker: Following up from the ProductStack webinar</a></p><p>And as promised, here is the full webinar from the Product Stack team.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F233343090%3Fportrait%3D0%26byline%3D0%26title%3D0&amp;dntp=1&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F233343090%3Ftitle%3D0%26byline%3D0%26portrait%3D0&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F654649925_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/1db9545d7c167d4d10b53ebeb2577c07/href">https://medium.com/media/1db9545d7c167d4d10b53ebeb2577c07/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d509a03e2ca6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/strategies-for-integrating-client-feedback-into-your-product-vision-d509a03e2ca6">Strategies for Integrating Client Feedback into Your Product Vision.</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shining a Light on Customer Superstars: Meet Michelle and Avid Technology]]></title>
            <link>https://medium.com/data-driven/shining-a-light-on-customer-superstars-meet-michelle-and-avid-technology-3fd99bfbe993?source=rss-3f1c6f3fd94f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fd99bfbe993</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[notion-case-study]]></category>
            <dc:creator><![CDATA[Notion Data]]></dc:creator>
            <pubDate>Thu, 27 Jul 2017 02:02:22 GMT</pubDate>
            <atom:updated>2017-11-10T18:52:07.876Z</atom:updated>
            <content:encoded><![CDATA[<p>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.</p><p>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.</p><figure><img alt="avid logo.jpeg" src="https://cdn-images-1.medium.com/max/338/0*rdR2Vc607R0ExGji.jpeg" /></figure><p>We’re starting this series with <a href="https://www.linkedin.com/in/michellemelancon/">Michelle Melancon</a> of Avid Technology. She’s an agile coach and manages the Atlassian Suite Team at Avid. Last time we checked, Avid was Atlassian’s largest JIRA Cloud customer, since they run 60+ scrum teams and a host of other departments on a variety of Atlassian products.</p><h4><strong>Tell us about your product.</strong> What do you spend your days building? What’s the coolest thing about it? Why do your customers love it?</h4><blockquote>Avid builds so many cool products that I can’t list them all here! Pro Tools, Media Composer, Avid NEXIS, Sibelius just to name a few. Essentially we build products for very creative people to master their art and tell their stories and that’s why they love our products and we love them. Honestly, they tell their stories better than I can! Check us out. <a href="http://www.avidblogs.com/">http://www.avidblogs.com/</a></blockquote><h4><strong>Tell us about your team</strong>. Why are they amazing? What is your favorite thing in working with them? If you could do anything to help them, what would it be?</h4><blockquote>My team is THE BEST! We manage the Atlassian suite and related applications. I think my favorite thing about my team is that we take a huge amount of pride in doing whatever we need to do to provide the teams that rely on us the best solutions possible. Really, I’m super proud of my team! Being in a service organization means that no news is good news. If I could do anything for my team I think it would be letting them know publically that they are very appreciated. See what I did there?</blockquote><h4><strong>Tell us about data, numbers, metrics.</strong> What sources do you track? How does data help your team be successful? What’s your biggest struggle in using data?</h4><blockquote>Notion really saved the day here. Tracking velocity and sprint data is important for our teams and our organization. Being able to review sprint data for numerous teams in JIRA is not possible and is a painful process. (no offense Atlassian!) Being able to see multiple team data in a single dashboard has been a lifesaver. This provides us an easy way to gauge how we are doing from sprint to sprint and identify any opportunities to help out teams through our agile transformation.</blockquote><h4><strong>Tell us about Notion.</strong> When do you review your Notion data? How have you incorporated Notion into your team workflow/processes? What problems has Notion helped you solve?</h4><blockquote>Right now Notion is providing visibility via a dashboard that we are using to wrap up our agile transformation. We are able to see our updated dashboards at the end of our sprints. At this point we are really only using a fraction of what Notion can do. There are so many options in Notion that the only thing needed is to determine what it is that you want to improve on and simply create a dashboard to easily see where you are currently and track your improvements. I absolutely LOVE the team polls. Getting feedback related to the teams perspective is invaluable.</blockquote><blockquote>I was asked to come up with a way to show multiple team sprint data in a central location. Easy right? I was ready to throw in the towel on being able to deliver a solution that could show multiple team data from JIRA. This was very frustrating and I am sure other Atlassian users can relate because the data is right there but you are stopped short of being able to present it in any useful way. When I came across Notion I was practically in disbelief but the concept is brilliant and it delivers what you would think is impossible.</blockquote><h4><strong>What would you say is the greatest benefit to using Notion?</strong></h4><blockquote>Well the tool is awesome but the people at Notion are incredible. The personal attention and assistance is second to none. We talked about what we needed, the problems we wanted to solve and Notion went over and above any expectations that we had. Seriously, best customer service ever. Ever.</blockquote><h4><strong>What would happen if we took Notion away?</strong></h4><blockquote>I’d cry. A lot. <em>(ed. note: Us too, Michelle. Us too.)</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fd99bfbe993" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-driven/shining-a-light-on-customer-superstars-meet-michelle-and-avid-technology-3fd99bfbe993">Shining a Light on Customer Superstars: Meet Michelle and Avid Technology</a> was originally published in <a href="https://medium.com/data-driven">The School of Little Data</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>