<?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 Denise Tilles on Medium]]></title>
        <description><![CDATA[Stories by Denise Tilles on Medium]]></description>
        <link>https://medium.com/@denisetilles?source=rss-7bdad7ed6047------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*YaDRamHLiHf7UEEn2-HX0Q.jpeg</url>
            <title>Stories by Denise Tilles on Medium</title>
            <link>https://medium.com/@denisetilles?source=rss-7bdad7ed6047------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:45:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@denisetilles/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[How These Companies Are Avoiding Zoom Fatigue]]></title>
            <link>https://medium.com/the-produx-labs/how-these-companies-are-avoiding-zoom-fatigue-d6ee3b353ff9?source=rss-7bdad7ed6047------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6ee3b353ff9</guid>
            <dc:creator><![CDATA[Denise Tilles]]></dc:creator>
            <pubDate>Wed, 13 May 2020 16:10:44 GMT</pubDate>
            <atom:updated>2020-05-13T21:57:25.124Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*LwT7cANh7E7FgCjy9v2RXg.png" /><figcaption>Software company Episerver added “shows” to its regular “Episodes” remote meetings for deeper team engagement. Staffers lead exercise and cooking classes, share tips for homeschooling, and more.</figcaption></figure><p>A friend told me about her company’s staff meeting today. As the ~75 people joined the Zoom call, there was some casual talk among a few staff about working remotely; a few comments through chat about the lead engineer’s impressive pandemic beard. Staff members were mostly muted and waiting for the meeting to start. 15 minutes into these unstructured exchanges, the CEO kicked off an informal report on the sales pipeline, then put the sales leader on the spot for color commentary (clearly not planned). And then the 30-minute meeting was over.</p><p>As my friend told me about the meeting (over a glass of wine on Zoom), we agreed it was a lost opportunity to make it a higher-value event for the team. It sounded like most of company had joined the Zoom call. Clearly the staff were eager for connection: an update, some assurance of how things were going — on a business level and maybe even on a human level, too.</p><p>This week, I spoke to several product leaders to understand how they’re handling staff meetings and communications. What does it take to maintain productivity, and bolster staff morale? And how do those things contribute to a hopefully a lagging indicator of steady revenues?</p><p>First the good news: There are a lot of great tools (Zoom, Google, Miro, Hangout, BlueJeans, the list goes on…) to enable meetings and collaboration. Like it or not, video meetings are now the main way to meet and keep the business moving.</p><p>The bad news? ”If you had a bad meeting culture — lack of agenda, lack of data, unclear follow up — remote work made it worse. Fix that first,” says Gijo Mathew, CPO of VTS, the NYC-based leasing and asset management platform in the commercial real estate industry. “Most companies carried the same meetings over and just made them remote,” Mathew points out. “Rethink your meetings just like you are rethinking company priorities.”</p><p>Kevin Broom, CPO of Bynder, the digital asset management company based in Amsterdam, says his team was already highly distributed and the transition was easy. Yet now, “we are exchanging more on our personal lives, especially as it relates to coping,” says Broom. “I believe this is building stronger working relationships and trust in the distributed environment. The standing agenda of OKR progress and blockers, strategic initiative updates is unchanged.”</p><p>In addition to two weekly product meetings, the Bynder exec team made the decision early into the pandemic to have three 20-minute townhalls per week. “We ramped up transparency and attendance is 70%,” says Broom. He had kicked off weekly Office Hours / Ask Me Anythings for his teams pre-outbreak. The mix of questions is 60/40 personal vs professional on the questions. “Interestingly, feedback is that people know me better.” says Broom.</p><p>Getting personal can be just what the team needs. Justin Anovick is CPO of Episerver, a US-headquartered software company with 10+ global offices. The company had been hosting remote meetings called “Episodes,” started as an initiative to educate their employees on what’s happening with the business. They talk about programs, departments, individuals — to help give everyone an understanding of what they’re doing.</p><p>“Once COVID happened we decided to add a twice a week ‘show’ where we talked about things not related to Episerver,” says Anovick. “Our first one was around how to homeschool your kids and other advice for parents about working from home. We then did an exercise episode followed by cooking and recently just did an entertainment one where people reviewed books, movies, tv shows, etc.”</p><p>Anovick co-hosts the show with Amberly Dressler (from Episerver’s Corp Communications). They source all content from employees or relatives. “Our aim is to get everyone together, have fun but also provide some relevant content that people (and their families might enjoy), says Anovick. The benefit of hosting? The swag. All show “talent”/presenters receive a coveted “Episodes” t-shirt.</p><p><em>How are you keeping your teams connected and motivated while 100% remote? We want to hear about your wins, challenges and advice for other product leaders. Share with us on Twitter </em><a href="https://twitter.com/ProduxLabs"><em>@produxlabs</em></a><em>.</em></p><p><strong>This </strong><a href="https://produxlabs.com/blog/avoid-zoom-fatigue"><strong>post</strong></a><strong> was originally posted on </strong><a href="http://produxlabs.com/"><strong>produxlabs.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6ee3b353ff9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-produx-labs/how-these-companies-are-avoiding-zoom-fatigue-d6ee3b353ff9">How These Companies Are Avoiding Zoom Fatigue</a> was originally published in <a href="https://medium.com/the-produx-labs">The Produx Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are You Building an Outcome or Feature-Driven Roadmap?]]></title>
            <link>https://medium.com/the-produx-labs/are-you-building-an-outcome-or-feature-driven-roadmap-903d632a04c7?source=rss-7bdad7ed6047------2</link>
            <guid isPermaLink="false">https://medium.com/p/903d632a04c7</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[Denise Tilles]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 21:12:29 GMT</pubDate>
            <atom:updated>2019-12-17T21:12:29.538Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*9zdeLQEfIXcAOcemNG5luQ.png" /></figure><p>Last week we learned how to <a href="https://medium.com/the-produx-labs/the-path-forward-is-clear-stop-acting-like-it-isnt-5389b0eafcbd">choose the highest value strategic initiatives</a> as you plan for 2020. Now you’re ready to create your roadmap. This is when the product leader really sets the bar for what’s communicated and how. At the very least, a leader should provide guidelines and templates for their PMs’ roadmaps.</p><p>It’s important to understand that the roadmap is a living, breathing document. It provides a guide to where you want to go strategically. But you should plan for — and encourage! — deviations along the way. That’s part of the validation phase you’ll build in, right?</p><p>There are a variety of ways your roadmap can express your strategic intentions. What’s important is to show how you’re driving towards outcomes. And from those strategic intentions, you’ll have initiatives that evolve from a problem into a solution.</p><p>With that in mind, I want to share two specific approaches to roadmapping:</p><p>1)<strong> The outcome-driven roadmap</strong> — geared to your internal development team</p><p>2)<strong> The feature-driven roadmap</strong> — more sales and customer focused</p><p><strong>The outcome-driven roadmap</strong><br>Thanks to the <a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=163de0dc4b&amp;e=362cc3a87d">data you’ve gathered</a>, you have good indications what users might want. However, you don’t <strong>know </strong>what your users want, and so you’re not definitive on what the finished product will look like. This makes it nearly impossible to estimate how long the product will take to build.</p><p>I really like <a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=80719013ff&amp;e=362cc3a87d">Melissa’s Perri’s approach to roadmapping</a>, which allows and encourages the uncertainty for product discovery. Her approach is very practical, with the Product Roadmap made up of outcomes, a theme, and hypotheses. Any unvalidated solutions or features are omitted. In her ideal world, roadmaps are theme based and not committed to specific features before features are validated. The roadmap is clear that the team is experimenting toward solutions for a set of high priority problems, but doesn’t define what components will be involved just yet.</p><p>After validation, your team can scope out releases of features and update roadmaps now that they are more sure of what to build. You don’t want to over promise early on. Roadmaps done this way are about iteration and learning — they start off vague and directional and get more concrete over time.</p><p>This type of planning is great for internal teams made up of designers and developers. That way they know when their efforts will be focused on discovery vs. delivery and how much time is being allocated to each period for a particular problem.</p><p><strong>The feature-driven roadmap</strong><br>Once you’ve established internal alignment on the outcomes you wish to achieve, you can create a more traditional feature-driven roadmap for Sales and Customers.</p><p>With this more externally facing document, be sure to only list an item when you believe it will be delivered (and probably leave some buffer). Also, try to add a note about how items further out are still being explored and may shift if more streamlined solutions can be created. Ideally, your team will list Epic/Initiative level items that have been validated with data about customer/market needs. Then, while working towards completing that epic, the product managers will directly check with users/customers to refine the features and ensure the right things are being built.</p><p>Whatever roadmap type/s you use, remember that your roadmap is a communication tool. It’s ok to have several versions, depending on your audience. The outcome-driven roadmap works well for the internal development team because it clarifies the strategy and focus of the product team. But Sales and customers will need a very different level of detail from engineering, which is why the feature-driven roadmap may be the right solution. We’ll show you a few options of how to present your roadmap in next week’s edition.</p><p><strong>Find the Meaningful Pebbles</strong><br>While you’re working through validating your initiatives, you’ll want to think about balancing the big and small items in your backlog. You need both to communicate to customers that you are innovative and to keep the team feeling great about delivering value. What things can you do to keep momentum and gain some quick wins? The answer lies in your backlog. It likely has different sizes of User Stories — boulders, rocks, and pebbles. First, look for the pebbles, the finely grained stories that are ready for the very next sprint. Tackling customer pain points which align with your overall goals, even if small, can create a lot of payoff for little effort.</p><p>Not seeing many pebbles in your backlog? Overloaded with Boulders? Reviewing CS tickets can provide insight into potential quick wins. Another area ripe for small things to do is <a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=1571a9d9da&amp;e=362cc3a87d">tech debt</a>. Partner with your engineering counterpart to identify the “pebble-y” quick wins. And don’t be scared off by the boulders. You may find something that has no dependencies and could be a clear value add, even if it takes more than 1 sprint.</p><p><strong>Collaborating for the Win</strong><br>And speaking of partnering, you’ll want to stay aligned with UX and engineering at every step of the roadmap process. Buffer in time for cross-team discovery and design iterations, even for solutions you have more clarity on. That goes for QA later in the process, as well.</p><p>Product, UX and engineering can get siloed and sometimes don’t have a shared understanding of the customer or the jobs to be done. <a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=19faf97254&amp;e=362cc3a87d">C</a><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=396dd65435&amp;e=362cc3a87d">ollaborating effectively</a><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=38b6dda3fb&amp;e=362cc3a87d"> </a>can be challenging. All too often product will be heads down in the hypotheses and validation work, and then <a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=8c97e32204&amp;e=362cc3a87d">throw the resulting solution</a> over the wall for UX to design. Needless to say, it’s not a recipe for successful collaboration.</p><p>The same goes with the engineering team. Bring them along on the roadmap journey as well. Walk them through your draft roadmap and solicit input. They may surface up areas for additional exploration, based on their feedback. Even better, engineering may be able to suggest simpler ways of accomplishing your goals.</p><p>Once your roadmaps are created, it’s key to keep the documents updated. You want stakeholders to know that this is the source of truth. The progress you share will bring everyone along as you work towards discovery and delivery.</p><p>We’ll get into communicating out the roadmap in next week’s installment. How do you share it out? What additional information should you include? What format or tool should you use? Tune in next week for everything you need to know about communicating your roadmap. If you missed some of the earlier pieces, click on the links below to catch up.</p><p><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=4046614cc2&amp;e=362cc3a87d">Week 1: Planning Starts with Setting a Vision</a><br><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=bc4fbe0203&amp;e=362cc3a87d">Week 2: Smart Product Bets Start With Data</a><br><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=861740e0d1&amp;e=362cc3a87d">Week 3: Generating the Best Ideas</a><br><a href="https://produxlabs.us10.list-manage.com/track/click?u=96ee124dfa54b31cc706284a7&amp;id=54a6634c16&amp;e=362cc3a87d">Week 4: Choosing a Path Forward</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=903d632a04c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-produx-labs/are-you-building-an-outcome-or-feature-driven-roadmap-903d632a04c7">Are You Building an Outcome or Feature-Driven Roadmap?</a> was originally published in <a href="https://medium.com/the-produx-labs">The Produx Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring a Product Operations Manager? Read this First]]></title>
            <link>https://medium.com/the-produx-labs/hiring-a-product-operations-manager-read-this-first-70bf2d8f75ee?source=rss-7bdad7ed6047------2</link>
            <guid isPermaLink="false">https://medium.com/p/70bf2d8f75ee</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Denise Tilles]]></dc:creator>
            <pubDate>Tue, 26 Nov 2019 18:56:14 GMT</pubDate>
            <atom:updated>2019-11-26T18:56:14.351Z</atom:updated>
            <content:encoded><![CDATA[<p>Which skill sets are right for you and your organization?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*skLC5BRijkm1hM5l--dE8A.png" /><figcaption>Photo courtesy of WOCinTechChat.com</figcaption></figure><p>Let’s assume you understand the value of Product Operations and what it can bring to your organization. Whether you’re at the startup, growth or enterprise stage, you know that Product Operations is the <a href="https://melissaperri.com/blog/2019/7/19/product-operations-the-fuel-for-winning-product-strategies">fuel for winning strategies</a>. You want the the data inputs that connect software development to business outcomes. When your leadership team asks for data, you want to provide the data that they need to make product decisions, not just the data they ask for. You’re efficiency focused. You see how to deliver value faster to customers by shortening feedback loops and sharing knowledge within the org.</p><p>You’re all in on <a href="https://www.insightpartners.com/blog/insight-partners-and-produxlabs-convene-product-leaders-for-first-product-operations-summit/">Product Operations</a>.</p><p>And assuming you’ve allocated — or are considering — a 2020 headcount for Product Operations, how do you find the right person? What are the right skills and experiences for this hire? How do you source candidates?</p><p>You could just search “Product Operations” on Linked In. Results will show that 5,700+ people on Linked In have Product Operations in their title. In fact, Product Operations as a listed Linked In skill has grown 80% YOY. But once you start looking through the profiles, you’ll quickly notice that Product Operations has many flavors. Some roles veer towards data analysis; others are more integrations and process focused. Sometimes you’ll see a blend of those skills.</p><p>How do you know which skill sets are right for you and your organization? Can you find the unicorn who has ALL of the skills — data analysis, integrations and process management?</p><p><strong>2 is better than 1<br></strong>In my experience as a product leader, I think these skill sets require two different roles. As the former VP of Product at a Saas enterprise company, we created a product analysis team. Our team (1 manager and 2 junior analysts) discovered revenue-driving, churn-reducing insights through data analysis. The team could wrangle revenue inputs from finance, win/loss/churn stats from sales, and user engagement data to tell a cogent story about a customer problem. Then the product team and analysts would collaborate on potential hypotheses to test. The analysts would help us understand risk associated with our hypotheses and validation experiments, including potential revenue increases or losses. We had one big win soon after the team was formed. Based on insights the team unearthed, we created a beta product that generated 7 figures in the first 12 months.</p><p>For our Product Data Analyst roles, we looked for people with past consulting and data analysis background. Sometimes those people are new to product management, which is totally okay. This person is a master of Excel, using formulas and creating pivot tables in their sleep. Someone who loves finding unseen nuggets of info that can lead to a bigger discovery. Job titles to attract the right candidates include “Product Operations Analyst” or “Product Data Analyst.” The leaders at Produx Labs created a sample Product Analyst job description for this role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0NhbtcTKhQwmkYBA-ZXODA.png" /></figure><p>Were my analysis rock stars just as skilled at streamlining product processes? No. From my POV, that requires someone who deeply understands what good operations looks like. This person knows the best development and insight tools. They are familiar with how product gets built. This could be a mid-level product manager who really loves creating efficiencies and more streamlined processes. A chief of staff at a tech org could also be a potential fit. Ideally your process person has coached/mentored more junior team members, experienced world-class product best practices and rituals, and loves improving refining and them. The process operations person has a high EQ. They know how to navigate in a changing business landscape and use influence to get what they need from various teams across a highly-matrixed organization. They’re also a resource to help coach team members in agile and lean methodologies. I’d suggest “Product Operations Manager” as the title in the job description.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_rF-z30sI4ET3Qwyo0jzTg.png" /></figure><p><strong>Which role gets hired first?<br></strong>So if you only have one headcount, which one should you hire first? It really depends on your priorities. One role will focus on a steady cadence of strategy-informing data. The other role brings order and efficiency in the inputs towards successful product development.</p><p>If all things are equally important, I recommend hiring the product data analyst first. Having quality data to make better decisions is essential. Possible outputs of the analyst role (like researching BI tools) can help set up some pillars for the process role. Give it 3–6 months to get your product analyst up to speed and show the leadership team some solid wins. Once you’ve established the analyst as a truly value-add hire, you can turn your attention to making the case to hire a product ops process manager.</p><p><strong>Reporting structures</strong></p><p>My recommendation would be to have your first Product Operations hire — the production data analyst — report to the head of product. When you eventually add the director-level overall process person, that person will report to the head of product. Your Product Operation Data Analyst, an individual contributor, will then will report into the process director.</p><p>In the end, you’ll have the best understanding of which role your team and org need first. To share a different point of view, I spoke to <a href="https://calendly.com/">Calendly</a>’s <a href="https://www.linkedin.com/in/ojiudezue/">Oji Adezue</a> about <a href="https://medium.com/@denisetilles/tips-from-the-top-how-calendly-is-standing-up-product-operations-922dfd90ac31">standing up his team’s first product operations role</a> and which role he’s hiring first.</p><p><em>Hiring for a Product Operations role? We want to hear about your wins, challenges and advice for other product leaders. Share with us on Twitter </em><a href="https://twitter.com/ProduxLabs"><em>@produxlabs</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70bf2d8f75ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-produx-labs/hiring-a-product-operations-manager-read-this-first-70bf2d8f75ee">Hiring a Product Operations Manager? Read this First</a> was originally published in <a href="https://medium.com/the-produx-labs">The Produx Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips from the Top: How Calendly is Standing Up Product Operations]]></title>
            <link>https://medium.com/the-produx-labs/tips-from-the-top-how-calendly-is-standing-up-product-operations-922dfd90ac31?source=rss-7bdad7ed6047------2</link>
            <guid isPermaLink="false">https://medium.com/p/922dfd90ac31</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Denise Tilles]]></dc:creator>
            <pubDate>Tue, 26 Nov 2019 15:13:33 GMT</pubDate>
            <atom:updated>2019-11-26T15:13:33.705Z</atom:updated>
            <content:encoded><![CDATA[<p>Product leaders reach out to us at <a href="https://medium.com/the-produx-labs">Produx Labs</a> to understand how Product Operations can impact their org — and recommendations on what to look for in a hire. Recently, we had a thought-provoking discussion with <a href="https://www.linkedin.com/in/ojiudezue/">Oji Udezue</a>, VP of Product at <a href="https://calendly.com/">Calendly</a>, about their first product operations hire. Post conversation, we followed up with a few questions for Oji about the Product Operations manager search and tips for other product leaders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*qiTyezukqHseb4CyIr-hgw.jpeg" /><figcaption>Oji Udezue</figcaption></figure><p><strong>What made you decide you needed a formalized product operations function?<br></strong>It was a focus on product excellence. We have some great inclusive product processes but we needed someone to help run it consistently and excellently. But not only that, this role will find ways to level up and find areas of constant improvement, so Calendly can have one of the best product teams in the world.</p><p><strong>How did you create a headcount for the role? What was the business case you made to the CEO?<br></strong>Actually, it was easy to make the case that we needed a way to expand the Product team’s capacity to build excellent products consistently and streamline execution.</p><p><strong>Were your priorities clear for what this role would own? (data vs process or both)<br></strong>No, it was not. I had to learn a lot from content produced by <a href="http://link to package on PXL">ProduxLabs</a> (in concert with <a href="https://go.pendo.io/prodops-ebook.html">Pendo</a>) but also by chatting with leaders in ProduxLabs and also talking to other industry experts.</p><p><strong>Are you planning to hire for a blended role (data and process) or one or the other? Why?<br></strong>I think I’m leaning towards mostly process and medium level strategy as a first hire. I think data should be a dedicated role in a scaling organization (that can report to Product Ops).</p><p><strong>You’ve had a Prod Ops job posted. What kinds of candidates have you gotten so far? <br></strong>I’ve been surprised at the quality of candidates applying, actually. To be honest I had low expectations because of the relative newness of this kind of role. But there is clearly a set of people who already do this (with or without the title) or want to, that are high quality.</p><p><strong>What’s your advice for other product leaders standing up a prod ops role/function?</strong></p><ul><li>Do your research.</li><li>Outline specifically what you want from the role for your organization, e.g. responsibilities and outcomes.</li><li>Write out any specific deliverables and projects you want this role/person to get started on initially.</li><li>Make sure you think about how you will introduce this role to cross-functional leaders and how you think they should work with the rest of the organization.</li><li>Since it’s usually a newish role, explain to your PMs how you expect them to work with this role so they’re not wary of it and help it succeed.</li></ul><p><em>More product operations content from </em><a href="https://medium.com/the-produx-labs"><em>Produx Labs</em></a><em>: </em><a href="https://medium.com/p/70bf2d8f75ee/edit"><em>hiring tips</em></a><em>, understanding the </em><a href="https://www.insightpartners.com/blog/insight-partners-and-produxlabs-convene-product-leaders-for-first-product-operations-summit/"><em>benefits of Product Operations</em></a><em>, and more.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=922dfd90ac31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-produx-labs/tips-from-the-top-how-calendly-is-standing-up-product-operations-922dfd90ac31">Tips from the Top: How Calendly is Standing Up Product Operations</a> was originally published in <a href="https://medium.com/the-produx-labs">The Produx Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart Product Bets Start with DATA]]></title>
            <link>https://medium.com/the-produx-labs/smart-product-bets-start-with-data-67b5239d200b?source=rss-7bdad7ed6047------2</link>
            <guid isPermaLink="false">https://medium.com/p/67b5239d200b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Denise Tilles]]></dc:creator>
            <pubDate>Fri, 22 Nov 2019 20:16:00 GMT</pubDate>
            <atom:updated>2021-06-03T16:05:39.360Z</atom:updated>
            <content:encoded><![CDATA[<h3>Defining your current state to support 2020 planning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*s270CMpOwB-zZue21awsaw.png" /></figure><p><a href="https://medium.com/the-produx-labs/annual-planning-that-doesnt-suck-55acc8daea6e?source=friends_link&amp;sk=24f4038501442006442073400ce44dca">Vision and strategic intents are core to product planning</a>. You need to know where you’re going — and why. Another key element to successful planning, at any timeframe, is good data around where you are <strong>right now</strong>. Data will answer key questions, including:</p><p>Do you know the current status of your product’s topline revenue drivers?</p><ul><li>How R+D costs impact ROI?</li><li>Are the bets you made paying off?</li></ul><p>Product leaders have to quickly make solid decisions that can affect the bottom line. You can identify the right growth levers to pull for your company and better understand your current position by having the right set of revenue and cost metrics.</p><p>Knowing that perfect is the enemy of good, what are the necessary things you really need to understand how your resources are performing? The goal is to <a href="https://www.insightpartners.com/blog/b2b-saas-top-line-metrics-getting-more-out-of-your-revenue-measurements/">baseline an understanding</a> of revenue and resources as you craft your 2020 strategy. It is key to understand the drivers of BOTH your top-line revenue and bottom-line profitability.</p><p><strong>Top-line revenue insights</strong></p><p>Taking a <a href="https://medium.com/the-produx-labs/b2b-saas-top-line-metrics-getting-more-out-of-your-revenue-measurements-9227ac29e776">data-driven approach</a> to top-line growth ensures you’re:</p><ul><li>Aligning to the larger company growth strategy</li><li>Demonstrating how your initiatives have measurable impact on the top-line</li><li>Ensuring that the numbers and related story are clear and understandable</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t8VSo3PqRo63QL4r" /></figure><p>For your baseline, you’ll want to know the primary drivers of revenue, including Annual Recurring Revenue (ARR) or Annual Contract Value (ACV). We show it broken out here by new, upsell/cross-sell, downsell and churn in a revenue bridge, a visualization of detailed historical data and logical projection assumptions.</p><p>In this example, your $21.4MM ARR has a 12% churn rate. Typical data points that will indicate potential churn include usage rates, last login date and customer satisfaction. You can pair churn indicator data with qualitative feedback. Ask your support and sales teams to share customer problems/themes.</p><p>Knowing your ARR by # of accounts and by customer will surface the customer segment opportunities in 2020. You can also break out ARR by product and customer concentration by ACV and revenue. <a href="https://www.insightpartners.com/blog/product-strategy-arr-relationship/">This data can guide you towards the segment that may offer the best bet for churn reduction</a>.</p><p>Another helpful data slice is understanding sales’ win/loss numbers. Anecdotal feedback is always useful: Where did the prospect offer clues as to strengths and weaknesses in the product? Those insights may show why the product may not be resonating with a particular segment and why. Or, the win/loss feedback might give you clues that the <a href="https://medium.com/product-manager-hq/validating-and-executing-on-value-propositions-11783cf3594e">value prop</a> needs clarifying.</p><p><strong>Bottom-Line Analysis</strong></p><p>Bottom-line data will give you visibility into your <a href="https://www.insightpartners.com/blog/product-leaders-are-rd-costs-part-of-your-strategic-discussions/">R&amp;D cost allocations</a> and delivery trends. Take a look at this year’s R+D costs. Did the allocations support your company’s strategic intents and outcomes? Where did your bets pay off? Should you have realigned resources? Armed with a clearer view of your 2019 R+D costs, you’re now ready to apply that lens to your strategic bets for the upcoming year. As 2020 progresses, you need to understand how those bets are trending. You’ll want to monitor costs for maintenance, innovation, parity, integration, and, of course, tech debt and customer commits. Tracking your resources confirms right track, or will help inform how you will want to reallocate to align with your business goals.</p><p><strong>Sounds great. How do I get started?</strong></p><p>Having a clear insight into topline and bottom-line revenue is fueled by <a href="https://medium.com/the-produx-labs/product-operations-the-fuel-of-winning-product-strategies-17965c20dc9">Product Operations</a>, a buzzed-about function in the world of product right now. But what is it? Simply put, Product Operations provides the cross-functional visibility and insights needed to define winning strategies.</p><p>The first step in establishing product operations is getting that manual baseline (as we discussed at the beginning of this piece — it’s all coming full circle…!). Inputs for this baseline will come from finance, sales, customer support, data science, engineering, at the very least. Once you’ve created that full picture of topline and bottom line revenue drivers you’ll be well positioned to inform your 2020 planning.</p><p><a href="https://medium.com/the-produx-labs/creating-a-strategy-start-by-generating-the-best-ideas-d8986e0fa9ba">Next week we’ll share tips for identifying key customer needs</a>, including how to surface the best insights from your data and partnering cross-functionally to tap into your colleagues’ expertise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67b5239d200b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-produx-labs/smart-product-bets-start-with-data-67b5239d200b">Smart Product Bets Start with DATA</a> was originally published in <a href="https://medium.com/the-produx-labs">The Produx Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>