Recently I spoke to a class at the UCSB Technology Management Program about market validation and failure testing – the process of testing whether customers will buy your product before you build it. I was part of a startup several years ago that raised millions – we spent about$10 million of it developing and launching a product that no one wanted. It was a mistake that was avoidable. Download the Anatomy of a Product Launch ➜ hbspt.cta.load(3434168, '0edb2611-2761-4434-90b0-f055704d9daa', {}); Through that failure, I learned how to first validate product concepts before building andscaling them. I’m a believer in the process and have used it successfully for many products and services, including GoToMeeting, GoToMyPC, AppFolio, and LIKE.TG. Here are seven best-practices I outlined in my talk that you can use in your market validation and failure testing efforts. 7 Steps for Testing if Your Product Will Fail 1. Adopt the philosophy of market validation. “My assumptions may be wrong.” For me, this approach underlies everything about market validation and customer development. Too many entrepreneurs and product managers are too rigid in their belief that they know what’s best for the customer – this only increases the risk of failure. 2. Write a testable hypothesis. Write a testable hypothesis for the market segment, problem, product, and business model. You can document your hypothesis in several different ways, whether that’s the Business Model Canvas, the Lean Canvas, a simple document, or sticky notes. 3. Focus first on the problem, not the product. Understand the problem thoroughly by first conducting 10 problem discovery interviews. I find that by focusing on the problem first, the product concept falls into place much more rapidly. 4. Ask open-ended questions. Make sure you understand your customers and are nailing the real customer pain. I wrote about this in 10 Great Questions Product Managers Should Ask. 5. Pitch your solutionto 20 customers after you have nailed the problem. An ideal pitch tells them their problem and how your solution solves that problem. It also describes what your product won’t do and potentially tests pricing. 6. Iterate your hypothesis as you learn. In the spirit of agile, you should iterate as you learn. However, unlike many Lean Startups, you are iterating on a concept or prototype rather than an actual product. 7. Track your interviews. I use a template for tracking customer problems, value propositions for our product, must-have features, objections, probability of buying, and interesting quotes. Keeping good track of interview notes isessential when conducting dozens of interviews. The notesalso serve as great customer evidence for justifying product initiatives to stakeholders. I then summarize what I’m hearing into a spreadsheet to make it easier to digest the massive amount of qualitative information I’ve gathered.

Deciding which initiatives to include in your futureproduct releases can be daunting. Product prioritization is even more difficult when there are too many opportunities to choose from and too many stakeholders to satisfy. Often these all-important decisions are disconnected from a company’s strategic goals, with product prioritization discussions dominated by opinion, a knee-jerk reaction to the latest lost sale, or the influence of a, particularly vocal executive. By using a scoring method to guide your product prioritization discussions, product managers can facilitate a more productive conversation about what to include on the product roadmap. While there are many inputs that ultimately go into a product decision, a scoring model can help the team have an objective conversation about product prioritization. One way to work through the process is withLIKE.TG’s Planning Board, a framework to help prioritize product opportunities. Based on product management best practices, the Planning Board helps you and your team objectively score new initiatives.More importantly, the Planning Board gives you a process to guide your strategic discussions. Whether you use a spreadsheet or the Planning Board, this method can make the product planningprocess more productive and help you get buy-in from key stakeholders. Think Benefit versus Cost Every potential initiative has two major considerations: the business Benefit and the associated Cost of implementing it. Product managers implicitly or explicitly use this calculation when prioritizing. The priority of an initiative is a composite of Benefit versus Cost (clearly, items with high Benefit and low Cost get higher priority). Benefits can be described as customer value, strategic value, revenue potential, cost reduction, or any other strategic objective your company may have. Costs often include implementation or development effort as one of the key categories. You may also want to include the impact on ongoing operational costs, or even an initiative’s risk factor. With the Planning Board you prioritize opportunities based on a customized set of Benefit and Cost categories. For example: Your company’s specific Benefit and Cost categories will be different – some companies based their categories on an ever-evolving set of criteria, while others use the company’s strategic initiatives as a basis. Whatever categories you choose, thePlanning Board is customizable. The Planning Board takes into account the relative weighting of each category that you assign (the weight can add up to any number you choose). Discussing the weighting of each category in your planning meetings is a great way to get an agreement on what’s important to the organization. hbspt.cta.load(3434168, 'e1e87713-3763-4c27-8f73-f817614e5f52', {}); The Scoring Discussion: It’s All Relative Once you have an agreement on the Benefit and Cost categories, you can begin scoring the initiatives. The Planning Board uses ascale of 1-5 to rank each opportunity in a category: One (1) is low Benefit or low Cost. Five (5) is high Benefit or high Cost. It’s important that you score items relative to other items. In other words, an initiative’s score only matters when you compare it to another initiative. And because business objectives can change, scores can change as well. Once you have a score for each item, you can have a fact-based, objective discussion with the team about what to include on the product roadmap. Of course, simply because an item has a high score doesn’t mean you add it to the roadmap. You still need to practice good product management, and that includes assessing many more variables than could be included in a product prioritization framework. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); The total score and rank is a composite of Benefit versus Cost and takes into account each column’s weighting. For example, an item with 5’s on the Benefit side and 1’s on the Cost side will calculate the maximum score. Which initiatives should you score? At LIKE.TG we recommend you use this model for only big features, themes, epics, and strategic initiatives rather than smaller features. In other words, use the framework for evaluating the needle movers that make an impact on the strategic goals. We’ve made the Planning Board flexible enough that you can pull in opportunities from the backlog (Table Layout) or items that are already on the roadmap. LIKE.TG is a web-based product roadmap software. If you haven’t already, feel free to sign up for a 30-dayfree trial.

A few days agoI had lunchwith the product team of a mid-sized software company, and one of the product managers had a conundrum: “Sometimes I hear the same feature request over and over, but when we finally release it customers barely use it.” Does that sound familiar? How can we as product managers avoid these dead-weight product features? How can we determine whether to 1.) implement a feature exactly as customers request, 2.) defer it, or 3.)deliver something that is completely different than requested but solves the core problem? hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); In my experience, good product managersoften combine all three (especially the deferring part). But for the product features you decide to includeon the roadmap, there is one practice that can help you make sure they will add value and get used: Set aside the feature request andfirst understand the job that customers need to accomplish. I’m assuming you’ve already nailed the basics: You have a process for validating prototypes with customers, and once you release a feature, you have the metrics to measure the success of the feature. “I need the following product features…” Before LIKE.TG I worked fora SaaScompany developing business software for vertical markets. The software was complex, including accounting, CRM, and marketing. Everycustomer came to our solution from another solution, and they often came to us with a pre-conceived mindset about what features the softwareneeded to have. We routinely gotrequests for product features and reports that (surprise) mirrored exactly what they were using in their previous solution. Sure, it would have probably satisfied the customers to simply add the button, feature, or report they asked for. But through understanding the job they were trying to accomplish we were able to imagine solutions that they were not able to imagine themselves and deliver product features that completely revolutionized their workflow. Download Building Your First Product Roadmap ➜ hbspt.cta.load(3434168, 'a81908bd-d7dd-4be2-9d7e-cb09f3f90137', {}); Case Study: Eliminating Hours of Work with a Few Clicks Withtheir previous solution, our customers would print out reports that needed to be producedevery month. In some cases this process would last for days; printing hundreds of reports, collating them,attaching checks, and stuffing it all into manila envelopes to be mailed. It was a cumbersome, horrible process. Some even had family and children join them for “stuffing parties” because it was so time-consuming. But this was a part of their life and they expected our software to support this workflow with the appropriate reports, printing, and buttons, and so on. Before building our solution, we spent hours onsite at the offices ofour earlyprospects to understand their workflow, hear their pain points, see the stacks of paper on their desk, and internalizewhat they were really trying to accomplish. We watched over their shoulder, asked a lot of open-ended questions, shot hours of video, and ate (too many) donuts with them in the break room. We thoroughly understoodthe job they needed to accomplish: delivering reliable information and payments to their customers (to be clear, the job was not printing reports and mailing checks). We envisioned how their life could be different by using the latesttechnology to optimize their workflow. We knew how it could improve their business and how much money they would be saving if we could shave hours off their process by moving the information and payments electronically. Once we understoodthat, we were able to release innovative product features that our customershadn’t considered or thought possible. For our customers, what previously took hours or days could now be accomplished in a few clicks. The results were wildly successful features that contributed to ourcustomers becoming hugepromoters of the software. Not every feature needs to be re-imagined. Sometimes there is low-hanging fruit you can deliver that happens to match exactly what customers request. But there are often product features that warrant further digging to really understand the job the customer is trying to accomplish, and get the right initiatives onto your product roadmap. hbspt.cta.load(3434168, '5894a003-79ce-4ea3-9804-dae280a96106', {});

A few well-phrased questions can yield fantastic customer insights. But knowing the right questions to ask during customer conversations and win-loss interviews takes a lot of practice and a healthy dose of curiosity. Here are ten open-ended customer interview questions I have in my arsenal that have worked well for me over the years when engaging with prospects and customers on products including ProductPlan. Asking a few of these questions can make a difference in the features you decide to include on your product roadmap. Download My Customer Interview Tool Box ➜ hbspt.cta.load(3434168, '7f735619-2494-4c81-b86b-cf6e764a20c3', {}); 1. Why? This is by far the most powerful question you can ask, so ask it often. Product managers should rarely accept a customer’s initial response; promptly moving onto the next point without pressing further can cheat your own understanding. By asking “why” as a follow-up question you can often extract a more enlightening response and get to the crux of their issue. For example, when I interviewed people about the product concept that became Citrix GoToMyPC we spent less time talking about remote access features and more time asking why their life would be better with our solution. As a result, we uncovered a stronger value proposition for the product. 2. How do you do that today? This is a great question when a customer asks you for a specific feature. Rather than taking their feature request at face value, dig in to really understand how they are accomplishing the job today. If you can, have them show you their process or how they are using their current product. This line of questioning proved particularly useful for LIKE.TG when we interviewed product managers to understand how they were building and communicating their product roadmap. 3. How do you know you’ve had a successful year/month/day? This is a valuable question for business products where you are trying to uncover metrics and customer goals. If your product can help your customers achieve their goals or help make them more successful, you are well on your way to a valuable product. 4. How do you feel about your current solution? This one is good for understanding opportunities to differentiate your product from competitors, especially during win-loss interviews. A good follow-up question might be “Where does your current solution provide the most benefit? What do you like best about it?” These questions make it clear that you are searching for opportunities to understand the motivations behind their choice; not judge the chosen solution. 5. What is the most frustrating thing about your current solution? This is a multi-purpose, open-ended question that you can use to open up the conversation flow and to discover pain points. If the solution you are validating doesn’t solve a real pain point, it might not be valuable enough for your target users. 6. What do you wish you could do that you can’t do today? This is a variation on the “If you could wave a magic wand…” question asked by many product managers. I’ve found that questions like these work well for very specific features or use cases. Be careful about asking this question in too general a fashion or too early, as it can lead to ambiguous results or a blank stare. 7. How would your day/job/task be different if you had this? I use variations of this question depending on the circumstances, but the objective is the same: understanding how your solution or feature solves a problem and what type of value a customer would place on solving that problem. Download the Customer-Centricity Checklist ➜ hbspt.cta.load(3434168, '18e41c50-6f24-4828-9f8d-c263df079a5e', {}); 8. Can you give me an example? This is another great general-purpose question that can give you a goldmine of supporting evidence for your new product or feature. In customer interviews, especially for early-stage market validation, it can be easy for conversations to stay high level. Asking for specific examples lets your interviewee know that you are willing to dive into the details, which will provide you with much more information than a higher-level discussion. 9. If this were available today, would you buy/use it? This question in itself may not result in an accurate answer (and can often lead to false positives). It’s what you do after this question that counts: Ask this question and then be quiet. Listening to their response for 60 seconds can give you insight into their decision process and the value they place on your product or feature. Make sure to follow-up with detailed questions such as “Would you walk me through the purchase process?” 10. Why would you recommend our solution to others? You can use variations of this “ultimate question” to gauge satisfaction with your solution and then ask follow-up questions. Try a few of these questions with customers or prospects during your next interviews. Some are better suited for new product development, but most will work well for your ongoing feature validation and win-loss interviews.Of course, great questions aren’t worth much unless you listen closely, read between the lines and then ask deeper follow-up questions. If you’re interested in more information on customer interviews, check out our Customer Interview Tool Box. It’s packed with tips and best practices for product managers looking to get the most out of their conversations with customers.

More product teams are taking advantage of the Minimum Viable Product concept—deploying products early to customers in order to learn and iterate. MVP is a fantastic approach for releasing products and features faster with less waste, and one that is often utilized in agile product management. But I’ve consistently found that it’s essentialtocombine the MVP with features or value propositions that directly relate to the customer’s biggest pain point. When you do this, it’s possible to release successful newproducts thatare evenless thanthe “minimum.” You might call this the 80% MVP. I base this 80% concept from releasing many minimumproducts over the years, including GoToMyPC, GoToMeeting, AppFolio, and LIKE.TG. Here are a couple of my observations: The MVP is subjective, and only byreleasing can we learn what the real minimum is. Even after conducting dozens of customer validation interviews for a product,I consistently discoverthatone or twofeatures I thought were necessary to include in the MVP could have been released later. I learn that there are otherthingsthat would have added evengreatervalue. The MVP must tie back to high priority customer problems that were discovered during validation. Delivering acompellingproduct thatrelieves pain candelight customers, even if it’s lacking features. Customers are forgiving if you show them you are focusing on high-value items for them rather than striving for the “perfect” feature set. My advice to you:Skip perfection and get a minimum compellingproductinto the hands of real customers.Tweet this Look, you still need to deliveronthe basics: products with features that are valuable,easy to use, and thatdelight customers. I’m not advocating releasing crap. But in my experience, to create successful products you need to combine MVP with unique and compellingvalue. This is how youcan make your product apurple cow. Does Your Minimum Viable Product ProvideEnoughValue? Compelling productsaren’t necessarily limited to features – it can beyour pricing, packaging, or anything that solves a top customer problem. For example, with GoToMeeting, our initial product lacked many features that were availablein competitive products such as video. However, our “all you can meet” pricing was a unique differentiator that solved multiplefrustrations customers had with the current solutions. This philosophy works wellfor new products as well as future initiatives you are adding to your product roadmap. Here is my high-level process for defining a compelling MVP: First, engage customers by conducting problem discovery interviews. Define your proposed features, making sure that features tie back to problems you discovered. Validate the productin subsequent interviews. After validation, cut features further, making sure to retain one or two valuablefeaturesthat hit the biggest pain points uncovered during problem discovery interviews. Cut the MVP to less than you are comfortable with. AtLIKE.TG, we released the original product and continue releasing features based around this philosophy. We have several in-depth interviews with customers to understand the pain, the value, review prototypes, and understand the minimum feature set. We then ruthlessly prioritize and cut the MVP but make sure to include features that are highly compelling and differentiated. For example, our product includes aprioritization frameworkfor making product decisions. We interviewed dozens of product managers to understand how they were prioritizing features and their challenges with prioritization. Our first release of this feature was a mere shadow of the feature we ultimately envisioned. But there were several compelling elementsthat made it superior toanything our customers had: It was collaborative and shareable. It was integrated with the visual product roadmap. It provided transparency. It was based on industry best practices. After releasing our MVP for the prioritization feature 1.) customers used the feature and 2.) got value out of it (or rather, they gotenoughvalue out of it). Because we solved painwith ourinitial release,our customerswerepatient and engaged as wecontinued to enhancethe feature based on their input. We still have far to go torealize our full visionfor the feature, but the stage isset for success. All product managers at one point have wondered whether they’ve prioritized the right features beforereleasing a new product. Sometimes deciding that your feature or product is ready for release is tough.The bottom line is to first fully understand customer problems before deciding your MVP and compelling value. Then pull the trigger faster to get your product out the door.

Pricing SaaS products presents unique challenges—and opportunities—for product and marketing teams. In the past few years, I’ve had a hand in setting pricing for several successful SaaS products, including GoToMeeting, GoToMyPC, AppFolio, and LIKE.TG. In the next few articles, I’ll review lessons for how to price a product that I’ve learned along the way. This first article is about what I consider to be the #1 mostimportant element for pricing SaaS products: customer value. Understanding customer value is essentialfor pricing all software products, but even more so with SaaS. Read the Power of SaaS Pricing Experiments ➜ hbspt.cta.load(3434168, 'c948d259-0fb9-457e-aece-634799b48e6d', {}); Because mostSaaS products are priced witha recurring subscription, every month or year your customers reevaluate whether they want to continue subscribing. This makes it even more critical to ensure pricing is in line with the value your customers receive. Let me define what I mean by “value.” First, a value can be quantitative, such as time saved or additional revenue earned. Measuring this is straightforward, and is the basis of Return on Investment calculations. If your product is B2B SaaS, you are likely already factoring this into your pricing decision. But here is the tricky part: Value can also be qualitative, such as pain relief or lifestyle benefits your product provides. By thoroughly understanding and documenting this sometimes nebulous qualitative value through customer interviews, you can begin to narrow in on possible pricing models and a price range. It’s understanding this qualitative value that can help product managers set theirproduct apart from the competition. I believe that customervalue should be the primary consideration for your price and pricing model. Notfeatures. Not what competitors charge. And definitely not your costs. Pricing SaaS Products: A Case Study When we were determining pricing for GoToMeeting, I interviewed dozens of potential customers to gain a deep understanding of customer pain and the value they might receive from conducting online meetings with our concept. We discovered: Cost and time savings from reduced or eliminated travel (quantitative value) Cost savings from switching to our solution versus expensive per-minute pricing of existing solutions (quantitative value) Increasedusageof online meeting technology because users were no longer tied toper-minute charges (quantitative value) Lifestyle benefits from conducting meetings remotely (high qualitative value) Reduced frustration by eliminatingcomplicated online meeting solutions (high qualitative value) By understanding thesequantitative and qualitative values, we developed GoToMeeting’s unique $49 “All You Can Meet” flat-rate pricing (an industry-leading innovation at the time). Pricing and your customers The pricing model directly relates to the pain and frustration we heard from prospective customers in our interviews – the current solutions were difficult to budget because the per-minute charges varied so widely. The buyer experienced sticker shock every month. Therefore, peace of mind wasanother qualitative value we could provide customers with our pricing model. While it’s hard to assign a dollar amount to qualitative values, these are the benefits that ultimately made GoToMeeting a no-brainer for millions of customers. Because the product was SaaS, we had the flexibility to price our product differently from the competition and create a unique product in the market. In a sense, we made pricing a part of the product. It became a differentiating feature that marketing promoted heavily. Most product managers already know that finding the right price is more art than science. However, if you thoroughly understand the value of your SaaS product, you can delight customers, provide competitive differentiation and ultimately launch a more profitable product. In the next articles, I’ll describe other lessons for pricing SaaS products including how to develop unique pricing models and several tips for setting the right price.

Most product people are familiar with the sticky problem of feature bloat. You may also recognize the issue by its other uncomfortable names: feature fatigue, feature creep, or feature overload. It’s the thing that happens when, for instance, the machine you bought to make the world’s best, quickest espresso also tells you the weather and time, is equipped with an AM and FM radio, has ten settings for temperature, bonus options for froth consistency (thin to thick), and comes equipped with iPhone-integrated alarm tones that tell you when your espresso is done (that part admittedly sounds sort of neat). While the makers of this espresso machine may have listened to user wants, the inevitable loss of frustrated and confused current and potential users would indicate that the creators didn’t focus on user needs. Yeah, a handful of users may have asked for bells and whistles, but fundamentally what they wanted was a damn good, quick espresso. Put another way, the espresso machine makers prioritized capability over usability and ignored real customer needs. As MSI.org wrote in a study of the feature fatigue problem over a decade ago: “Because consumers give more weight to capability and less weight to usability when they evaluate products prior to use than they do when they evaluate products after use, consumers tend to choose overly complex products that do not maximize their satisfaction, resulting in ‘feature fatigue.’” Echoes Rian Van Der Merwe in his more recent article How to Avoid Building Products That Fail: “…more isn’t necessarily better.” Touché. While loading up features in the beginning may buy you some early users, the high cost of alienated, churning customers, the expense of accruing and paying down additional technical/engineering debt, the potential confusion regarding your product and brand identity, and frustration from engineering and product teams (complete with a loss of organizational trust in your decisions) can lead to catastrophe. Of course, the espresso machine is a simplified example. In reality, your product-bloating features may initially seem essential but turn out in time to be unnecessary — at which point it may be too late. Your challenge, then, is to decide which features your product and customers actually need and which you can realistically afford and to avoid the others like the plague. So how to avoid falling into the tempting trap of feature overload? With the laser-focused ammo of a four-tiered process: be informed, mindful, selective, and cutthroat with your feature decisions. 1. Make More Informed Decisions by Validating Feature Requests Considering all customer feedback does not mean taking all customer feedback. This means you must separate the signals — the worthwhile feedback — from the noise. You can do so by asking validating questions about the quality and significance of customer feedback before acting on it. Primary indicators of “valid” feedback include volume, frequency, request source, and intent. Is a feature request high-volume or limited to a few customers? Does it come up with some frequency? If you say “no” to one or both of these questions, it may be a sign that the request is noise. Additionally, the source of the feature request matters: you should know how long the person behind a request has been a customer, their use case, account plan/level/type, their industry, and — depending on your company — how satisfied they are with your product overall (NPS). This will give you a greater measure of the request’s relevance. If the feature seems actionable, then dig a little deeper to ask what the intent of the request is: What is the underlying pain behind the request? Is there an underlying pain that justifies the feature request? It is your job to use the product management resources at your disposal — from usability tests to field studies to surveys — to uncover your customers’ true needs. Ensure that you only build things that solve actual, real problems, or you may find yourself sagging under the weight of unnecessary features. 2. Make More Mindful Decisions By Considering Complexity Costs and Technical Debt You know the old saying, “There’s no such thing as a free lunch?” That adage applies to features, too. Development and support costs are just the beginning of a feature’s expense. But woe to the product manager who does not consider the complexity costs and technical debt a given feature adds to their product. As Kris Gale, VP of Engineering of Yammer put it to First Round Review: “Complexity cost is the debt you accrue by complicating features or technology in order to solve problems. An application that does twenty things is more difficult to refactor than an application that does one thing, so changes to its code will take longer.” What may take two weeks of coding to develop, for instance, may take much more work and time to maintain down the road. You must decide whether or not a feature’s complexity cost is necessary or unduly burdensome. A potent mix of common sense, intel from engineering, and data testing that evaluates the feature’s usability and usage can help drive this interrogation. If you do decide to move forward, make sure to continuously check that customers are using and getting value from the feature (see: that it’s meeting your customers’ needs). Have you accidentally made their experience unnecessarily complex? If so, take stock, pivot, and be more mindful moving forward. 3. Make More Selective Decisions By Considering What Matters and Saying NO “Yes” sounds good, doesn’t it? We tend to equate “yes” with positive, happy things, and “no,” with negative, bad things. But it isn’t that simple. Oftentimes a “no” to a feature request can actually mean a yes — a yes to remaining aligned with your product vision, your overall product strategy, and other business goals. These are the things that really matter and can be forgotten when in the weeds of product and feature development. Feature doesn’t solve an actual problem? No. Doesn’t align with your company’s core purpose? No. Not enough demand for a feature (as you’ve discovered when validating it)? No way, José. If you’re doing your job, “no” should be the answer to the majority of your feature requests. That way, the features that get a “yes” are the ones you, your team, and your customers know have real value. Being more selective also has the added, crucial effect of making you a more trustworthy product manager, which means you can more effectively make decisions that combat the feature bloat that make your team and customers feel, well, sick. 4. Make More Cutthroat Decisions by Removing Bad Features Saying no to proposed features is often not enough. Sometimes you’ll need to be even more brutal by doing away with poor product features entirely. These are vampire features — learn to recognize them, and then kill them before they kill your product. If a feature’s complexity cost outweighs its benefits, if it doesn’t meet real customer needs, if only a handful of customers use it, if it’s outdated or irrelevant, etc. etc. — take a deep breath and cut it. Yes — you (and your engineers… and others) have given this feature life, nurtured it, and even made sure it’s easy on the eyes. But what has it done in return? It’s harmed your business and the integrity of your product. Make like a mob boss and whack it. In Sum Feature bloat can cost you precious resources, weigh down your team, and harm the integrity of your product. By making informed, mindful, selective, and cutthroat feature decisions, you can ensure that you’re building a focused, manageable product that meets a true customer need. About the Guest Author: Sara Aboulafia is a member of the marketing team at UserVoice. Outside of work, Sara writes and performs music, binge-watches comedy, and spends an unhealthy amount of time futzing with technology before happily retreating to the woods.

The Definition of the Key Responsibilities of Product Managers In most cases, your core role as a product manager will be two-fold: First, to set the long-term vision and strategy for your company’s products. To communicate this strategy to all of the relevant participants and stakeholders. Typically, the primary tool you will use to accomplish your key roles will be a product roadmap, a strategic, high-level visual document conveying the “why” behind the products you’re building. The product manager’s job description is often not well defined for such a vital and pivotal position within many companies. In addition, product manager responsibilities often vary from company to company, and at first glance, it seems like no two product manager jobs are identical. Case in point: The three statements below come from three very different (and accurate) product manager job descriptions and the key responsibilities of product managers. Example Job Descriptions of the Key Product Manager Responsibilities: Manage from concept to design, sample production, testing, forecast, cost, mass production, promotion, support, and finally, product end of life. Delivers the operating plan: the achievement of growth objectives, including market share, revenue, profit, and return on investment for all the channels/categories of business and key customers. Responsible for managing and implementing marketing activities through research, strategic planning, and implementation. That’s quite a variety of skills. Whether we look at three or ten job descriptions, you can see that each product management role is varied and unique. I’ve seen the role and influence each product manager has depending on many dynamics—the company’s size, the type of company, the type of product, and the stage of the product. We recently reported the key skills for the role, metrics, and challenges between large and small companies differ significantly. So, what are the key responsibilities of a product manager? What do they all have in common? Moreover, how can you use the role most effectively to usher successful products into the world? 4 Key Responsibilities of Outstanding Product Managers As a product manager, it is essential to understand that you are a central hub within your company for a lot of critical information about your products, market, competitors, customers, prospects, fundamental industry analysts, and many other constituencies. To succeed, you will need to continually gather and analyze data and business intelligence from all of these sources (as well as your internal sources like sales and customer service). Then, use this data to inform the creation of your roadmap strategy. You will interact with a broad range of departments to ensure your products’ success. You will also translate the input and data you gather to build a case for many decisions you present in your roadmap. As such, there are several vital skills you’ll need to bring to your role as a product manager. 1. Be transparent about your prioritization and roadmap process. Remember, much of your role as a product manager will be explaining “why” to various stakeholders and constituents. Why you’re prioritizing one feature or theme over another in a release; why you’ve chosen to focus more on one particular goal for the next two quarters versus another goal. The best way to get the relevant constituencies — sales, marketing, engineering, your executives — on board with your strategic thinking is to be clear and open with them about why and how you are making decisions. 2. Be able to say “no,” but explain why in terms that stakeholders understand. There will be plenty of times when an executive will ask for a new feature his gut tells him will be great… when an engineer will suggest tabling the development of a feature set to save time on the next sprint… and when a sales rep will ask (even beg) you to add a specific tool to the next release because a prospect has promised to buy if it’s included. But if those requests will undermine your strategic objectives for the product, you will often have to say no. The key will be in your ability to articulate why (that all-important word in a successful product manager’s vocabulary) you cannot accommodate the request. Again, the more strategic and backed by evidence you can make your roadmap, your constituents’ more likely to understand when you need to say no. 3. Be a ruthless prioritizer while balancing the needs of customers and stakeholders. Regardless of your company’s size or budget, you will always face limited resources for your product development. That means you will always need to prioritize and continually weigh the competing factors of your products, your company’s limited resources, and demands from various stakeholders. If you’re unsure how to set priorities or weigh various factors in developing your roadmap, several great models canhelp you get started — such as weighted scoring and the Kano model. Some of our team explained more about how the model works in the video below. 点击播放声音 @keyframes VOLUME_SMALL_WAVE_FLASH { 0% { opacity: 0; } 33% { opacity: 1; } 66% { opacity: 1; } 100% { opacity: 0; } } @keyframes VOLUME_LARGE_WAVE_FLASH { 0% { opacity: 0; } 33% { opacity: 1; } 66% { opacity: 1; } 100% { opacity: 0; } } .volume__small-wave { animation: VOLUME_SMALL_WAVE_FLASH 2s infinite; opacity: 0; } .volume__large-wave { animation: VOLUME_LARGE_WAVE_FLASH 2s infinite .3s; opacity: 0; } 3:43 #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset{font-size:14px;} #wistia_chrome_23 #wistia_grid_43_wrapper div.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper span.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper ul.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper li.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper label.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper fieldset.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper button.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper img.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper a.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper svg.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper p.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper a.w-css-reset{border:0;} #wistia_chrome_23 #wistia_grid_43_wrapper h1.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:2em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper h2.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:1.5em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper h3.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:1.17em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper p.w-css-reset{margin:1.4em 0;} #wistia_chrome_23 #wistia_grid_43_wrapper a.w-css-reset{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper span.w-css-reset{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper svg.w-css-reset{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper ul.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper ol.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper li.w-css-reset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper ul:before.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper ol:before.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper li:before.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper ul:after.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper ol:after.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper li:after.w-css-reset{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper label.w-css-reset{background-attachment:scroll;background-color:transparent;background-image:none;background-position:0 0;background-repeat:no-repeat;background-size:100% 100%;float:none;outline:none} #wistia_chrome_23 #wistia_grid_43_wrapper button.w-css-reset{background-attachment:scroll;background-color:transparent;background-image:none;background-position:0 0;background-repeat:no-repeat;background-size:100% 100%;border:0;border-radius:0;outline:none;position:static} #wistia_chrome_23 #wistia_grid_43_wrapper img.w-css-reset{border:0;display:inline-block;vertical-align:top;border-radius:0;outline:none;position:static} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset button::-moz-focus-inner{border: 0;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree {font-size:14px;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree div{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree span{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ul{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree li{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree label{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree fieldset{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree button{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree img{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree a{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree svg{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree p{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree a{border:0;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree h1{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:2em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree h2{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:1.5em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree h3{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:1.17em;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree p{margin:1.4em 0;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree a{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree span{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree svg{display:inline;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ul{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ol{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree li{box-sizing:inherit;box-shadow:none;color:inherit;display:block;float:none;font:inherit;font-family:inherit;font-style:normal;font-weight:normal;font-size:inherit;letter-spacing:0;line-height:inherit;margin:0;max-height:none;max-width:none;min-height:0;min-width:0;padding:0;position:static;text-decoration:none;text-transform:none;text-shadow:none;transition:none;word-wrap:normal;-webkit-tap-highlight-color:rgba(0,0,0,0);-webkit-user-select:none;-webkit-font-smoothing:antialiased;list-style-type:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ul:before{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ol:before{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree li:before{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ul:after{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree ol:after{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree li:after{display:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree label{background-attachment:scroll;background-color:transparent;background-image:none;background-position:0 0;background-repeat:no-repeat;background-size:100% 100%;float:none;outline:none} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree button{background-attachment:scroll;background-color:transparent;background-image:none;background-position:0 0;background-repeat:no-repeat;background-size:100% 100%;border:0;border-radius:0;outline:none;position:static} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree img{border:0;display:inline-block;vertical-align:top;border-radius:0;outline:none;position:static} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-tree button::-moz-focus-inner{border: 0;} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-max-width-none-important{max-width:none!important} #wistia_chrome_23 #wistia_grid_43_wrapper .w-css-reset-button-important{border-radius:0!important;color:#fff!important;} Download the Prioritization Guide for Product ManagersFirst Name*Last Name*Job Title*Phone Number*Email*LIKE.TG is committed to protecting and respecting your privacy, and we’ll only use your personal information to administer your account and to provide the products and services you requested from us. From time to time, we would like to contact you about our products and services, as well as other content that may be of interest to you. If you consent to us contacting you for this purpose, please tick below to say how you would like us to contact you:I agree to receive other communications from ProductPlan.In order to provide you the content requested, we need to store and process your personal data. If you consent to us storing your personal data for this purpose, please tick the checkbox below.I agree to allow LIKE.TG to store and process my personal data.*You may unsubscribe from these communications at any time. For more information on how to unsubscribe, our privacy practices, and how we are committed to protecting and respecting your privacy, please review our Privacy Policy.#wistia_grid_43_wrapper{-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box;font-family:Arial,sans-serif;font-size:14px;height:100%;position:relative;text-align:left;width:100%;} #wistia_grid_43_wrapper *{-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box;} #wistia_grid_43_above{position:relative;} #wistia_grid_43_main{display:block;height:100%;position:relative;} #wistia_grid_43_behind{height:100%;left:0;position:absolute;top:0;width:100%;} #wistia_grid_43_center{height:100%;overflow:hidden;position:relative;width:100%;} #wistia_grid_43_front{display:none;height:100%;left:0;position:absolute;top:0;width:100%;} #wistia_grid_43_top_inside{position:absolute;left:0;top:0;width:100%;} #wistia_grid_43_top{width:100%;position:absolute;bottom:0;left:0;} #wistia_grid_43_bottom_inside{position:absolute;left:0;bottom:0;width:100%;} #wistia_grid_43_bottom{width:100%;position:absolute;top:0;left:0;} #wistia_grid_43_left_inside{height:100%;position:absolute;left:0;top:0;} #wistia_grid_43_left{height:100%;position:absolute;right:0;top:0;} #wistia_grid_43_right_inside{height:100%;right:0;position:absolute;top:0;} #wistia_grid_43_right{height:100%;left:0;position:absolute;top:0;} #wistia_grid_43_below{position:relative;} For a detailed explanation of these and other proven models, you can use to prioritize your roadmap in an environment of limited resources, download LIKE.TG’s free book: Product Roadmaps: Your Guide to Planning and Selling Your Strategy. 4. Bring evidence-based decision-making to your communication. As I’ve stated previously, one key trait of successful product managers is their ability to answer “why” to the many questions they must field from stakeholders throughout their organizations. One of the most effective ways to answer why is with evidence. It’s much more compelling than your opinion — or anyone else’s. If you have real-world user data, customer feedback, and metrics on your product, then you already have an excellent source of business intelligence to inform how best to build your product roadmap. So let your analytics help guide your decisions. If you don’t have real-world user data on your products yet, don’t worry. There are plenty of other ways to gather useful intelligence about your product, customers, and market. Ask your customers directly. Study your competitors’ products. Read online communities or comments on your company’s blog where your prospects or customers discuss your products or your competitors’ products—study research reports from the analysts who cover your industry. When an executive or sales rep asks why you’ve selected one direction over another for the next iteration of your product, your ability to present a compelling explanation backed by real data will go a long way toward earning their buy-in. hbspt.cta.load(3434168, '95beb659-8ca3-4c13-b7a2-32365cbd3900', {}); Because you play a central role in your organization — always gathering valuable intelligence from various stakeholders, customers, and your market — you are in a unique position to define the success of your product. Your role as the product’s strategist and evangelist will be central to your success and the success of your products. Ready to put these skills into practice? hbspt.cta.load(3434168, 'e29c8e8c-234d-44fc-985b-67a542504810', {});

Pricing is such a core part of a SaaS product’s business model that you need to get it right. In this series, I’m writing about SaaS pricing lessons I’ve learned from launching several SaaS products including GoToMeeting, AppFolio, and ProductPlan. In the first part of our series, we reviewed why pricing based on customer value is key to a great product strategy. In the second part, I described how SaaS gives product managers flexibility to be creative with pricing models. We cover the art of subscription pricing in our webinar below: Here are 10 tips for how to price your SaaS product that you can use. While many of these apply to SaaS products, the lessons overall apply to software product pricing in general. Read the Power of SaaS Pricing Experiments ➜ hbspt.cta.load(3434168, 'c948d259-0fb9-457e-aece-634799b48e6d', {}); 10 Lessons for Pricing SaaS Products Pricing must be a part of early validation. While you may not nail your final pricing until later, the earlier you can zone in on your SaaS pricing model, the better off you will be. This gives you a greater chance of building your pricing modelintothe value proposition. At a minimum, during the product conceptualization stage, actively interview potential decision-makers about their purchase process, how they purchased their current solution, and frustrations with the current solution’s pricing. BallparkLTV as early as possible. Customer Lifetime Value (LTV) is socritical to a SaaS business model that you need to estimate it as early as possible – wellbefore you have customers and revenue. LTV influences the sales model and what you can afford to spend to acquire customers. While there are lots of ways to calculate LTV, I recommend keeping it as a simple back-of-the-envelope calculation with input from customer interviews and similarproducts. LTV > CAC. The formula for success is simple in the SaaS world: LTV overtime must be significantly greater than customer acquisition cost (CAC). SaaS companies with a recurring revenue stream like Salesforce.com have LTV multiples that are three to five times the cost to acquire that customer. Doing back-of-the-envelope calculations on CAC will help you avoid surprises down the road. Your sales model influences your pricing. Conversely, SaaS pricing constrains the sales model options available to you. For example, if you have an expensive field sales force, you need to ensure that your customer LTV is high enough to support that model. You’ll struggle if your average customer purchases $50/month over a two-year lifetime. Ultimately, your buyer persona determines your sales model, so make sure you understand the expected purchase process. Create upsell opportunities within your pricing model. One of the advantages of SaaS is the ability to offer upgrades and services that drive additional revenue. Consider these within your SaaS pricing model, as they can make a substantial difference in long-term product revenue. This is the model we used with great success at AppFolio. Use caution when offering annual prepurchase discounts.Many SaaS products that license on a monthly basis will offer a discount for annual prepurchasing. However, with SaaS pricing, use this with discretion. Analysis shows that over the long term, you leave significant revenue on the table. Consider free trials.If your acquisition and activation model is simple enough, providing a limited free trial is a great way to increase your sales conversions. It’s common to offer 15- and 30-day trial options. Service is key.Because SaaS is typically licensed as a subscription, your customers are at risk of churning every renewal period. Service and support are even more critical than with traditional software. For this reason, many SaaS products build support and regular upgrades into the standard licensing fee. Consider whether your customers will be receptive to additional fees for support and maintenance for a product that they expectto work flawlessly. Customers don’t care about your costs. I’m not suggesting you ignore your costs, but don’t price your product working backward from cost. This is not how your customers will think about the pricing. Sure, the cost of goods sold needs to be a factor for you to be viable, but this is not related to how customers value your product. Pricing perception doesn’t follow economic rules. Customers often buy products for reasons that seem disconnected from the Return on Investment calculation. Pricing, specifically SaaS pricing, is highly psychological. For this reason, the demand curve is not linear – a lower price doesn’t necessarily equate to more customers and revenue. Take this into account by thoroughly understanding the qualitative value that your product provides. Takeaways With web-based SaaS products, it’s easier than ever to conduct A/B tests to gauge buyer behavior, pricing, and acquisition costs (before and after launch). As you test the user interface, I encourage you to test your pricing with equal fervor. Use qualitative customer interviews to get enough data points to make good decisions. Get it right for SaaS pricing, and you have a recurring revenue stream that places your product’s portfolio value well above traditional software products. Pragmatic Marketing Webinar:Missed Jim Semick fromLIKE.TG for the Pragmatic Marketing Webinar? Watch the recording to learn more about pricing software products. Learn why LIKE.TG is the easiest way to plan and communicate your product roadmap.Try it freetoday.

No doubt you’ve heard of the coming Internet of Things (IoT) and how it’s going to change our lives through billions of Internet-connected devices and sensors. But is IoT mostly hype? And if it’s not, how can product teams prepare? Preparing for the Internet of Things Last monthI moderated a panel discussion for the MIT Enterprise Forumto discuss IoT opportunities and challenges. Our panelincluded device, data, and security experts as well as representatives from companies launching IoT products. To be honest, before I began preparing for the event I wasn’t convincedabout the impact of IoT. I thought that products like Nest, Dropcam, and pill bottles that remind us to take our medicine are cool, but wondered if a world of Internet-connected washing machines was really all that special. But after talking with the experts and moderating the event, I have come to realize that over the next few years there is a huge opportunity for companies providing hardware, software, data, and services for customers in almost every industry. My takeaway is this: product managers and product teams need to be prepared to capitalize on IoT – it will eventually deserve a place on your product roadmap. Product teams will want to consider these areas for the future: Prepare forthe data. Each device will create immense amounts of data. There will be challenges with processing the data and connecting different data sources together. Business intelligence and data discovery systems will become more important to organizations. There will also be opportunities to make innovative connections between data and devices that weren’t previously possible. Interaction design will be more important than ever. Every device will need an interface. While there are efforts to create standards, today each device interface is often a separate ecosystem. This will create opportunities for UX and interaction teams to provide innovative interfaces that include visual, audio and tactile feedback. Security and privacy will be challenging. Any new technology introduces security and privacy concerns, and IoT presents special challenges. Devices can give access to our homes. Databases contain confidential information about our health. Companies will need to give cybersecurity and privacy high priority as they introduce new products and services. Low-priced sensors will spur innovation. There already is a growing array of sensors and the price is dropping rapidly. Sensors that can measure light, humidity, sound, location, movement, temperature and other items will give product teams incredible opportunities to innovate. Whether you are in the consumer, automotive, healthcare, manufacturing, construction, or another industry, IoT will affect your products and services. Teams willneed to have a strategy to innovate and rework legacy products to fit into this new world. Image credit: Nest Labs

Henry Schein, Inc. is the world’s largest provider of health care products and services to dental, animal health and medical practitioners.Teams at Henry Schein rely onLIKE.TG for strategic planning and roadmap communication. We chatted with product manager Dan Larsen about how he’s using LIKE.TG: What are you using LIKE.TG for? “We share alive version of the roadmap with teams in remote offices. We also use the Planning Board to conduct benefit versus cost weighting.” How has LIKE.TG helped you? “We’ve saved a huge chunk of time. LIKE.TG has helped us improve the business by giving us back our time to think strategically about the business, and not tactically about how to share information.” What is your favorite feature? “What I immediately liked about LIKE.TG is that it was super simple to start using.One of the first times I had one of those ‘Oh wow, this is cool’ moments was when I started using the Planning Board for scoring.” Read the full Henry Schein customer story. Read more about teams doing great things with LIKE.TG.

Like you, we have now seen a dozen articles predicting the top trends for product managers in 2016. Yes, we know that better communication is on the rise. But what is really happening in the product management world? At LIKE.TG we have the opportunity to engage with hundreds of PMs every month. We’ve identified some long-term trends that will take place not just in 2016, but in the coming years. If you are looking for a new product management job, here are five trends that should be on your radar. 1. It’s time to boost your skills: More training choices than ever We’ve noticed a proliferation of training and other opportunities to learn the skills that product managers need. This includes training classes, both through traditional organizations such as Pragmatic Marketing and newer entrants such as General Assembly. Even academia is getting involved, with several universities offering continuing education and specialized programs for product management and software product management. We expect that this trend will continue with grassroots events such as ProductCamp, meetup groups, and other informal learning opportunities that appear for product managers. 2. Lean startup methods will continue to be in demand Companies — even large enterprises — are continuing to embrace lean startup and customer development processes. As a product manager, it’s important to continue to read up and practice these skills in your role. These skills include rapid prototyping, engaging early with customers, iterating rapidly, and killing bad ideas. 3.Product Managers will have access to more data than ever With so many data and analytics tools coming on the market in the last few years, product managers have more metrics-driven data for making decisions. But with the good comes the bad — there is a firehose of data. As a product manager, you’re at the intersection of so many data streams from support, finance, sales, IT, and other departments. Product managers are needing to deal with more complexity than ever. Luckily these tools continue to become more mainstream and refined. And the best practices around metrics-driven product management are becoming more well known and written about. Many of these tools such as Pendo.io, Kissmetrics, Intercom are specifically geared towards product and customer engagement. 4. Proliferation of product management tools In 2016, vendors will continue to fill software gaps and product managers will have a stronger set of purpose-built tools at their disposal. With specialized tools for roadmapping, customer engagement, analytics, project management, and more, product teams will be able to work more efficiently than ever. For example, our 2015 product roadmap survey revealed that most product managers are still using and are frustrated by presentation software (PowerPoint) and spreadsheets (Excel) to manage their roadmaps. PMs are hungry for new solutions that let them engage with stakeholders in a more productive way. 5. Living roadmaps will become more predominant A roadmap should be agile and thought of as a living document rather than a plan set in stone. Unlike the product roadmaps of a few years ago, today’s roadmaps, at least in the longer term, are now fluid. This is partly the result of agile development techniques, but also because of a growing awareness that decisions made in the executive conference room may not be the right answer once customers are engaged in the validation of new ideas. Like the backlog, the product roadmap should be regularly discussed, prioritized, estimated, updated, and shared. And product roadmap software or other web-based tools enable the roadmap to adapt quickly as decisions are made. [Free book] Backlog Refinement: How to Prioritize What Matters ➜ hbspt.cta.load(3434168, 'ba6d6ffb-c21a-41c0-8f7e-7f79e553dae1', {});

Orion Health develops software solutions for healthcare organizations worldwide, helping to improve the care of 35 million patients. Founded in New Zealand in 1993, Orion Health now has 27 offices in nearly every region of the world. Orion Health uses LIKE.TG to create roadmaps that easily communicate vision and strategy to stakeholders across the company’s many teams and regions. We chatted with Mark Robertson, Strategic Project Manager, to learn more. Here are some highlights from the conversation. What do you like most about LIKE.TG? Mark: “Most tools claiming to do roadmaps were cumbersome, hard to set up, and complicated to manage. I knew we’d end up not using them. But LIKE.TG was a clean, visual roadmap tool — and it was so intuitive that you could start using it in minutes.” What are you using LIKE.TG for? Mark: “The product roadmaps we’ve created with LIKE.TG make it so much easier to quickly communicate information across teams. LIKE.TG gives any of us in the company — no matter what team or part of the world — a common place to start a conversation about a project.” How has LIKE.TG saved you time? Mark: “We were using highly detailed tools like JIRA, Excel® and an internal wiki to track everything. Sure, if a salesperson in the US or an executive in New Zealand knew exactly where to look, they could figure out what was going on. But otherwise, we really had no way of quickly communicating the high-level view of our ongoing projects” How has LIKE.TG helped your organization? Mark: “Here’s an example of what we were up against our old approach. Our security team wanted to propose a new process, and we needed management buy-in. So they built a 12-column Excel spreadsheet to present the idea. When the steering committee saw it, their eyes glazed over, and they assumed we had no plan — because we weren’t visually depicting it for them. This time, [with LIKE.TG], the stakeholders got it right away. We haven’t gone back to our old Excel model since!” Read the Full Orion Health Customer Story:Visual Product Roadmaps Improve Communication

It’s a brave new world for pricing software-as-a-service products. Gone are the days of simply setting a per-seat fee and launching. How can you choose the best SaaS pricing model for your product? In this SaaS pricing series, I review lessons I’ve learned from helping set pricing for several successful SaaS products. In my first article, I reviewed why pricing based on customer value is so important. This second articlereviews why SaaS gives product and marketing managers unprecedented flexibility to chooseunique pricing models. Models that can differentiate your product in the marketplace. Models that ideallyalign with your customers’ goals. SaaS Pricing Flexibility One of the exciting advantages of SaaS is that youcan think differently about pricing models. Unlike traditional software, customers licensing SaaS products pay for your product on a recurring basis. Your product is no longer tied to a one-time purchase. And because the product is centrally hosted, you have additional flexibility for offering your product in unique packages. Read the Power of SaaS Pricing Experiments ➜ hbspt.cta.load(3434168, 'c948d259-0fb9-457e-aece-634799b48e6d', {}); SaaS Pricing Models: a Short List SaaS gives you the ability to consider revenue models that weren’t previously possible. Here’s a short (and by no means exhaustive) list of SaaS pricing models used today. Many products use a combination of these models: Per-user(many SaaS products) Per-user with free participants (GoToMeeting, LIKE.TG) Storage (Dropbox) Features(plans based on feature tiers) Project (Basecamp) Freemium (LinkedIn) Per item/contact (AppFolio, Hubspot) Per Node/Server (Hadoop) Per Visitor/Traffic(AdRoll) Processor time/Data transferred (Amazon Web Services) Open Source (free with paid services) Advertising (Facebook) Broker fee (AirBnB) Feel free to add to this list in the comments. My point is that with so many options, you now have the ability to discover a pricing model that aligns with your customers’ goals. To learn how to make subscription pricing work for you, watch our webinar: Success-Based SaaS Pricing Model Example For AppFolio’s property-management software, we developed a unique pricing model based on the number of rental units managed by a property manager. Because we charged a flat $1 per rental unit per month, the pricing was simple and easy to understand. This SaaS pricing model resonated with customers because it aligned with their business goals. They paid more for our product only if they grew their business by adding rental units to their portfolio. If they were more successful, we were more successful. Don’t be Tempted by Competitive Pricing When pricing a new product, there is a temptation to set your pricing relative to the competition. It’s common for new products to price using the same model as competitors, but slightly lower. Sure, you can price your product the same way as your competitors, and perhaps that’s what your customers expect. But with SaaS, there are so many ways to price the product that you have the ability to stand out in the market by thinking differently. Capitalize on the approaches that your competitors haven’t considered. In my previous article, I described how we launched GoToMeeting with innovative pricing that disrupted the competitors. Keep it Simple Don’t overly-complicate pricing. With so much flexibility in SaaS pricing model options, there is a temptation to offer various flavors and packages. Sometimes there are legitimate reasons for doing so. For example, it’scommon to have three packages based on features. Studies show that this approach anchors customers, and can be an effective technique for driving customers to your best-performing package. That’s fine if this is your goal. However, creating an overly complicated pricing scheme has the potential to confuse customers and create a nightmare for your finance team. Keeping it simple reduces headaches and may even provide more revenue over the long term. For example, atLIKE.TG (product roadmap software), we saw that products in our space had complicated licensing options. Many required a paid license for every software user. Several offered complicated pricing tiers based on packages. We took a different approach to simplify pricing. We charged only for editors of roadmap data and offered free licenses to other collaborators. Rather than offering complicated pricing tiers based on features, we offered unlimited use of all features for one price. Because the product managers want to widely distribute the product roadmap to stakeholders, this SaaS pricing model benefits the customer. It’s aligned with their goals. In addition, this model gives our product more exposure within the organization, so ultimately we sell more licenses when other departments ask to use the software. In the next article, I’ll review several tips for successful pricing, including estimating lifetime value.

New product managers will find themselves asking this question a lot: “How do we build a prioritized product roadmap so that we have the best chance of making something people want?” Purposeful Prioritization of Features In order to achieve our goals, we need to be clear about what the purpose of prioritizing product features is. There are two approaches to prioritizing product features: You prioritize the features and initiatives that you, your team, or your stakeholders think would be a good idea—and hope that it works out. You start by figuring out which features have the highest engagement and which ones don’t get used. Then you identify which steps in your workflow cause the biggest drop-offs—where users are getting stuck. And finally, seek to understand your users’ needs, their sources of hesitation, and the conversations going on in their minds. This should be a no-brainer. You have a much better chance of making things people want if you understand what the market needs are, and if you focus on fixing the areas where your product has the biggest leaks. hbspt.cta.load(3434168, 'e1e87713-3763-4c27-8f73-f817614e5f52', {}); Prioritization struggles of teams But many product teams still operate using the first approach—they make decisions based on their own opinions, rather than data-informed, educated hypotheses. LIKE.TG’s co-founder Jim Semick talks to a lot of product leaders in his line of work. And in one of his recent webinars, he mentions that even large, well-known companies struggle with: Decisions not being tied to strategic goals Stakeholders questioning prioritization Priorities being driven by the loudest executives or the latest sales prospects Clearly these organizations are doing something well, otherwise, they wouldn’t be well-known. But the wasted opportunity is huge. Companies that build products based on internal opinions will eventually get beaten by the competition. So how do you make sure you’re newly prioritized product roadmap includes features and initiatives that will really move the needle? What you need is a process for generating ideas, prioritizing which ones to focus on, and getting buy-in from key stakeholders. In the following sections, I’m going to break down a step-by-step framework—originally pioneered by conversion optimization expert Peep Laja—to help you do just that. Step 1: Gather Actionable Data Like we talked about earlier, rather than creating a prioritized product roadmap based solely on our opinion, we’re going to use a data-informed approach. So how do we go about gathering data? There are 5 steps (followed by creating a master list of all the issues you found that we will then turn into potential product features, fixes, and action items): Product analytics — Identify specific steps in your product workflow where users are getting stuck and leaving instead of taking the action you want them to take. Mouse tracking analysis — This lets you record what people do with their mouse, and this can give you insights into where users are paying attention to your product. On-page surveys — If you want to find out what’s stopping people from performing a specific action, put Qualaroo on your page and ask them. Support transcripts — Dig into your customer support transcripts to find out why people are reaching out and asking for help. They usually reach out with frustrations and confusion, and that can give you insight into things you can fix. User testing — Observe current users and potential users as they interact with your product while they speak their thought process out loud. User session is also great because they anonymously record videos of your users as they use your product, allowing you to see everything they do. As you analyze the results of your research, make a list of all the places where users get stuck or frustrated, where people aren’t doing what you want them to do, and where you see things that need to be improved. If you want a more detailed explanation of how to execute each of these research methods, go check out this article. Step 2: Identify the Highest Value Initiatives Okay, so you’ve generated all of this quantitative and qualitative data… what now? Well, at this point you’ll have identified a big list of product issues and feature ideas. The next step is to figure out which initiatives are worth working on, and weeding out the ones that aren’t. First, start by thinking through each of these potential opportunities and plotting them on the matrix below. The y-axis represents the value that each initiative delivers to either the company (e.g. gets you more sign-ups) or the customer (e.g. saves them time). And the x-axis represents how much effort, time, money, and other resources each initiative will take to implement (e.g. development hours). For example, let’s say ‘Item B’ is a redesign of one of your current features. It’s not going to take much effort, and it’s going to deliver high business value. Once you’ve plotted all the initiatives you identified in your initial research, the next step is to prioritize the highest value items and figure out which ones to say “no” to. To help you make this decision, start by overlaying this grid on your matrix: As you can see, the initiatives in the upper-left side of this graph provide high business value and require low effort—this is the low-hanging fruit that you want to start with. The items that fall into the upper-right quadrant will also deliver a lot of value, but they’re more complex and require more effort to implement. These are important but should get done after the items from the first quadrant. Some of the ideas in the lower-left section may be able to deliver some quick wins, but since they provide low business value you need to seriously question whether they’re worth prioritizing. And finally, you definitely shouldn’t consider any of the ideas that are high-effort low-value. Step 3: Score Your Initiatives Now that you’ve weeded out all the potential opportunities that don’t provide strategic value, the next step is to score your remaining initiatives. Think through the benefits that your organization will receive and costs it will require to implement, and then rank each factor on a scale of 1 – 5 (1 being low benefit/cost and 5 being high benefit/cost). You can either use tools like LIKE.TG for your scoring model, or you can create your own process using a spreadsheet. And of course, this scoring model isn’t the only factor that goes into deciding which features to prioritize—you also need to take your competition, market, and customers into consideration. But this analysis can be critical for getting stakeholder buy-in. Step 4: Get Stakeholder Buy-In on Your Newly Prioritized Product Roadmap Creating alignment with your product strategy and getting buy-in from executives and managers can be tricky. But you can make it less of a challenge by proactively addressing a few of their key concerns. Our first recommendation is that you walk your stakeholders through the process you used to create your prioritized product roadmap. Demonstrating that you used a structured thought process to evaluate opportunities—rather than just going by your gut or your opinion—is an effective way to get stakeholders on board. Second, bring customer evidence to the table. This is where the data you gathered in step 1 comes into play. You’ve gathered real evidence about your product from both existing and potential customers, and this sort of data is more compelling to executives and managers than your opinion. So back up your decision with hard data. Use the metrics you gathered from your analytics tool to show them what users are doing. And then use video clips of users interacting with your product, and direct quotes from your customers to explain why. And finally, always tie your priorities back to the organization’s strategic business goals. Doing this right off the bat will help answer the question in everyone’s mind of “Why are you doing this instead of something else?” Rather than just talking about what a new feature will do, tell them how it’s going to impact the bottom line and move the needle on the KPIs that your stakeholders care about most. For example, the data shows that we’re killing it when it comes to user acquisition, but we struggle to get those users to come back over the long-term. So we’re implementing this initiative in order to improve our retention rate. Takeaways Whether you’re using a scoring model or some other kind of model to evaluate and prioritize opportunities, the technique you’re using is ultimately less important than the conversation that you’re having with your stakeholders. Regardless of the tools and techniques you use, it’s important that you’re transparent with your stakeholders, and that you give them some insight into the process you used to create your prioritized product roadmap. By addressing their concerns and objections proactively, you make it much less likely that you’ll get pushback. And the best way to do that is to show them that you used a systematic process, you based your decisions on hard data (not your opinion), and that your priorities are aligned with the strategic goals of the organization. What do you think? What process do you use to make sure you’re prioritizing the right initiatives and building things people want? Share your thoughts on building a prioritized product roadmap in the comments below! About the Guest Author: Spencer Lanoue is a marketer at UserTesting, where he helps UX designers, PMs, and marketers create great experiences. Follow him at @slanoue.

Most product managers know the product roadmap can be your best friend, or your worst nightmare. When used in the right way, the roadmap can help explain how you’ll achieve your vision. And when used in the wrong way, the roadmap can sink you with endless PowerPoint updates, meaningless features, and commitments that can never be delivered. At a recent meetup, I sat with a diverse group of product managers, to get to the heart of the roadmap issue. The folks in the room came from corporate and startup and had a range of experience. Most were working locally in Sydney, Australia, but we were also joined by an expat who was on sabbatical from Silicon Valley. In two hours, five key insights emerged around the problems that can make roadmaps ineffective and troublesome. 1. Your Organization Has Too Many Priorities One participant shared with us that his startup had seven KPIs they were tracking, essentially seven priorities… as you can imagine, this was making his job as product manager incredibly difficult. How can you prioritize development when you’re trying to move the dial on seven things at once? In situations like these, it can be easy to fall into the trap of building a little bit of everything, to somewhat satisfy each of the KPIs. But it’s also easy to fall short on every single one of those priorities and create a Frankenstein product in the process. The hard road is to push back and work with the team to identify a single clear priority, whether that be revenue, user acquisition, learning goals, or something else. This is a potentially confrontational discussion to have, but one that will pay off in terms of being able to get traction on that single goal. 2. Your Roadmap Isn’t Visually Attractive This one may cause some debate. One of our participants recounted that his CPO claimed he’d never known an ugly roadmap to be successful. Roadmaps are communication tools, so if good design results in the roadmap being easy to understand, that’s obviously an essential requirement. But of course aesthetics can go much further than that, and represent real beauty, design and style. There’s a strong argument that aesthetics lend credibility. They give your document the sense of being crafted with care and attention. They suggest to the audience that you’re a professional who can be trusted to deliver on the vision. When the audience has that level of faith in you and the roadmap, it helps drive their future behavior to support those outcomes. The keyword, of course, is audience. It’s common to create different versions of a roadmap for different audiences – a practice often focused on the content of the roadmap, but sometimes design too. Some personalities will value aesthetics, while others won’t. A product manager can deduce the preferences of the audience and consider the context to hit the right note on visual appeal. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); 3. Your Roadmap Was Created in a Vacuum Stakeholder management is the bread and butter of product management. And I have a theory that the skill of being a universal translator is what lands many people in the product management field. (That means I think you’re pretty good at it already). But sometimes, the need to own the roadmap drives product managers to produce it alone, or without the input of some parts of the wider organization. This mistake is avoided with a balance of ego and humility. Product managers have to be humble enough to recognize the best ideas, even when they aren’t their own. They also have to be strong enough to push back on ideas that have no links to strategic objectives or the target customers. By walking this balance, product managers can own the roadmap, while keeping stakeholders involved in the process. Ultimately this provides the foundation for the organization to deliver on the roadmap together. Alignment like that is a powerful force. 4. Your Roadmap Lacks Links to The Product Vision A roadmap should describe how the product is going to move the product toward the vision. I hear this mantra a lot and our meetup group spent some time discussing this concept. It’s not that product managers disagree with this one, it’s just sometimes hard to bring to life in the roadmap document. Some say we never see good examples from real companies, while others aren’t sure links to strategic goals can be concisely communicated. Think of it this way. Your roadmap is not a list of features and functionality and it’s not a project plan. It’s the document that shows how your organization will get from where you are today to the product objective. Tell your product story in a compelling way. This story will include people (your users), the journey the product is going on (the roadmap), and why it’s important (the link to the vision). hbspt.cta.load(3434168, '5894a003-79ce-4ea3-9804-dae280a96106', {}); 5. Your Roadmap Changes Every Other Week One of our meetup participants shared that his roadmap was changing on a fairly regular basis. This creates a lot of busy-work to keep the roadmap up-to-date, but more importantly, when the roadmap changes constantly it’s unlikely you’re getting any closer to those strategic goals. Roadmaps can change, in fact they should change, in response to learning, shifts in the market, and sometimes competitor activities. But too many changes suggest indecision. They suggest the organization isn’t sure how to achieve its strategic goals. If that’s the case, then it’s time to take action around that indecision. Dig into what’s driving it and set learning goals designed to reduce risks and doubts. Ruined Roadmaps Saved… There is no magic wand. Like our products, we need to iterate ourselves, constantly observing our successes and failures to improve the roadmaps we present. Many of the senior product professionals I meet say their on the job experience provides the most powerful learning opportunity, but talking with peers about the challenges they face also figures strongly in the way they build their capabilities. Meetups – or getting the perspective of another product manager – can provide an alternate view on the roadmap, which just might help reveal you’ve fallen into one of these traps. We’ve all done at least one of these at some point in our careers (Yep, I admit to it!) And we’d probably like to avoid making the same mistake again. About the Guest Author: Jen Marshall is CEO at Brainmates, the Australian Product Management Training and Consulting company that organizes the Leading the Product conference in Sydney and Melbourne. In her spare time, Jen practices Vinyasa Yoga, dabbles in philosophy and listens to crime and mystery audiobooks.

Much has been written over the last few years on the idea of the featureless roadmap, which challenges product teams to present their plans grounded more in strategic vision – or by themes – rather than a laundry list of specific features. LIKE.TG alone has several articles on the subject that demonstrate the many virtues of this outcome-focused approach. It’s becoming more and more widely adopted by Product Management organizations across the globe. One of the critical considerations in developing your theme framework is to ask what drives the need for this theme? There is a genuine risk that a well-meaning product manager might simply group and categorize the existing feature list as a means for determining the theme. However, the real goal of the themed roadmap is to let the desired outcomes define the features. So how do you zero in on the most meaningful outcomes from which to center your roadmap themes around? How to Decide on Roadmap Themes that Produce Meaningful Outcomes I’ve seen several different approaches, including themes that align with high-level business goals (acquisition, growth, customer satisfaction, etc.) or more granular focus areas like the example in Jim Semick’s article of increasing satisfaction within a user persona group. There are pros and cons to each of these approaches. For example, the business goals approach is static over time, so the themes themselves stay consistent and maintain a pulse on the longer view. But the themes in and of themselves are a bit uninspiring and don’t do much to communicate customer value. In the more granular approach, the focus is more laser-sharp and centered on a specific customer outcome. However, this approach runs the risk of myopia and losing sight of new emergent opportunities that might outweigh the theme’s value. A compelling theme should be centered on the exchange of value between the business and the customer, and the above examples are hyper-focused on one or the other. hbspt.cta.load(3434168, '5894a003-79ce-4ea3-9804-dae280a96106', {}); One way to achieve this balance is to organize your roadmap themes by each phase of the customer journey. This customer journey approach provides a widely universal framework for both business and customer outcomes and promotes a constant, bird-eye perspective on the end-to-end customer experience. The Customer Journey Framework The customer journey chronicles every customer interaction and touchpoint with your business—from becoming aware that you exist to making a purchase decision, using, and then eventually renewing with your product or service. The journey is depicted in different phases, which are relatively universal (but might be customized by a business that has done the work to map their customers’ journey). Those phases include Become Aware, Evaluate and Buy, Set Up, Happily Use, Get Support, Add Services, and Renew. The Benefits of Defining Product Themes by Customer Journey Phases Breaking down the customer’s end-to-end journey is a highly effective framework that enables an outside-in perspective and customer empathy as a means to drive value that is reciprocal to both customer and the business: Journey maps, then, are highly applicable to the goal of defining product roadmap themes since successful customer outcomes are at the heart of each phase. Besides the apparent value exchange, the customer journey is a universal perspective that transcends organizational silos. Each phase of the journey has pretty clear stakeholders, for example, generating awareness is usually assigned to the marketing team, and the customer success department usually owns the support experience. Focusing your themes on phases of the customer journey enables stronger partnerships between the product team and other functional groups because their goals become less disparate from the product strategy. It changes the conversation from other departments vying for a slot on the product roadmap to one that is much more strategic. Both groups can become collaboratively responsible for goal setting within the shared theme. Another benefit of the journey-based roadmap themes is that it inherently promotes customer empathy. Everyone in the company who looks at your product roadmap can evaluate it, not from just a customer perspective, but a timeline-based customer perspective. The customer journey enables individuals and teams to consider the context of their work within the customer’s end-to-end experience. Leading with this genuine care, curiosity, and perspective of the customer can have profound cultural effects on a business. Customer-centered cultures foster a bottom-up drive for innovation based on the desire to solve customer problems creatively. Problems are fluid, and markets are changing rapidly, so the work of a product manager to effectively prioritize work is a constant challenge effectively. Choosing the right theme altitude is critical to keeping eyes and ears open for emerging opportunities outside of the current focus areas. I like using customer journey phases as themes because, while customer needs may fluctuate, their journey stages are static. Maintaining consistency and continuity in themes provides a clearly defined lens from which to scan the customers, trends, and competition. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); Customer Journey Roadmap Themes in Practice Let’s look at some tangible examples of how each theme may be planned and presented from the perspective of a fictitious e-commerce platform company. Phase 1: Become aware Prospects know our product exists, and it has a positive reputation. Generating awareness includes all of the things your marketing department is doing to reach new prospective customers. In this example, the product and marketing teams establish a mission to grow the reputation of the business by addressing issues raised by contributors to software review sites and focusing on a specific feature and usability gaps common among the less-favorable reviews. CUSTOMER KPI: Reach BUSINESS KPI: Reach as a % of Total Addressable Market (TAM) STAKEHOLDER PARTNER: Marketing Phase 2: Evaluate buy Make it easy for prospects to choose and purchase our product. Reducing friction between a prospect and their willingness to buy is a key concern for sales and product management teams. Having a theme dedicated to this experience drives constant focus in this crucial area, like in this example, where the goal is to reduce sales objections by adding the top payment options prospects are demanding. CUSTOMER KPI: Time to deal close BUSINESS KPI: Maps to sales booking goals STAKEHOLDER PARTNER: Sales Phase 3: Set-up New customers can take immediate advantage of our product. Product onboarding encompasses all the activities a customer or user engages in to configure, learn, and start using a product. In this example, the teams at our e-commerce platform are working on ways to do just that by introducing two new, self-guided onboarding flows within the product. CUSTOMER KPI: Time to the first use of the critical feature BUSINESS KPI: Time to goal monthly recurring revenue (MRR) STAKEHOLDER PARTNER: Customer Success and/or Onboarding Teams Phase 4: Happily use Customers get so much value from using the product, and they love it! Naturally, the phase focused on product use is how much of mainstream product management is currently categorizing their work. Given the above examples, one can begin to ascertain the benefits of instead capturing work in terms of the different outcomes defined by the customer journey. Keeping the outcome of this theme narrowly focused on adding value makes it an excellent space for prioritizing feature requests of current customers, usability improvements, addressing technical debt, and, as in this example, improving product engagement of a specific feature set. CUSTOMER KPI: Transactional Net Promoter Score (tNPS), System Usability Score (SUS) BUSINESS KPI: Critical engagement metrics STAKEHOLDER PARTNER: Product Development (Product, UX, Engineering) Phase 5: Get support Customers rarely need help, but when problems arise, they are quickly solved. The support phase is focused on making support resources easily accessible, improving resolution speed, building out various support channels, and reducing the need for support in the first place. The product team can have a significant impact on this outcome by doing this, like implementing an in-product support experience or, as in the example below, dedicating focus to address the top product case drivers. CUSTOMER KPI: Transactional Net Promoter Score (tNPS), Time to case resolution BUSINESS KPI: Tracking against operational cost efficiencies STAKEHOLDER PARTNER: Customer Support Phase 6: Add services Customers are compelled to upgrade and subscribe to value-add services. The heart of the add services phase is in upgrades, upselling, and the purchase of additional products and services, all tied to a business’s growth initiatives. This theme can capture things like improving the discoverability of value-add services, adding features to be repackaged as a new subscription tier, or, as in this example, building out new features or services that customers would be willing to pay extra for. CUSTOMER KPI: Reach/Conversion BUSINESS KPI: Average Revenue per Unit (ARPU) STAKEHOLDER PARTNER: Customer Success and/or Sales Phase 7: Renew Customers remain loyal advocates of our product and business. The renew phase looks at every opportunity to keep customers happy coming back to your product or service. Almost all SaaS businesses are looking at churn, and addressing those reasons is perhaps the most apparent epic under this theme. But, similar to some of the other themes, there may be opportunities to reduce effort by integrating account management experiences within the product, such as this example that would introduce a renewal flow and add the ability for SaaS customers to pay their invoice online (instead of sending a check). CUSTOMER KPI: Net Promoter Score, Customer Satisfaction (CSAT) scores BUSINESS KPI: Churn STAKEHOLDER PARTNER: Customer Success Considerations for Journey-Focused Roadmap Themes A highlighted benefit of having high-level themes that align with phases of the customer journey is that the themes are universally applicable across every department of the business. Sharing goals across business functions create a substantial competitive advantage for consistently delivering high-value, end-to-end experiences. There are, however, some aspects of this approach to be mindful of, which include: Avoid creating silos by phase. People and tactics may be focused on a specific phase. However, Product and Design need to maintain their awareness of their work’s context within the end-to-end journey. Phases require prioritization. While I advocate for having the same consistent themes, I don’t believe that work needs always to be happening equally within each. Certain phases will have a greater need than others. It’s up to the product team to appropriately allocate focus where the greatest needs are. Phases often have embedded journeys of their own. This is especially true for the Add Services phase, where there is a complete cycle of awareness to renew to consider. Keeping customer outcomes at the heart of your roadmap, effectively mapping them to business outcomes, and sharing those outcomes across your organization is an excellent recipe for driving innovation and building reciprocal value between your customers and your business. The phases of the customer journey already have this value exchange baked-in. They can be a highly effective lens through which to view and prioritize the opportunities on your product roadmap. Read the Strategic Roadmap Planning Guide hbspt.cta.load(3434168, 'e23dbd3d-c389-4aba-b537-43c357b5672a', {});

When you’re new to a product management role, you enter the situation with minimal credibility, name recognition, or trust beyond your hiring manager. When your entire job is to define a direction for the product and convince everyone else it’s the right one, that clean slate isn’t helpful. For this role, it’s essential to grow your sphere of influence. You need to win people over and give your ideas and suggestions a fair shake. Do this by convincing colleagues that your strategic decisions are based on sound data, adequate deliberations, and keen insight. This is why you need to establish allies and supporters early on and before you try to shake things up. 6 Steps to Building Your Sphere of Influence in Your First 90 Days A constant theme for new product managers is managing their sphere of influence. If you are new to the role or new to an organization, your starting months are critical. During a recent webinar hosted by The Product Stack entitled “Your First 90 Days as a New Product Manager,” Roxanne Mustafa, Design Lead at VMware, and Pivotal Tracker provides advice to new product managers. 1. Play the “newcomer card.” You only get to be new once. Don’t miss your chance to let your newness pay dividends. For a few months, you get to ask whatever questions you want. Explore assumptions and delve into the product and organization’s history with honest curiosity. Ask fundamental questions that you won’t be able to later. Probe in a non-confrontational way. Challenge ideas before the legacy of previous PMs clouds you. Learn the history, but don’t resign yourself to relive it. This will help you understand how and why things ended up where they are. Remember, you’re on a fact-finding mission. Your mission is to understand the tribal knowledge and what things were already tried and failed. To understand how failure was defined in the first place. hbspt.cta.load(3434168, '8bd83652-2868-48a8-9b9c-ebb8e0b9c945', {}); 2. Utilize one-on-ones. Mustafa says the most important thing you must do is figure out who you must talk to and what conversations you should be having. The best way to do this is to start scheduling intimate meetings withstakeholders across the organization. Starting with the product owners. Stay in listening mode as much as possible, using the various insights you gather to slowly build up your opinions. Be sure to see whose names keep getting dropped. This way you get a sense of where the power centers are and who are the key influencers, then add meetings with those individuals to your calendar. Make sure you get on any relevant email lists, Slack channels, or standing meeting invites. Ask how each stakeholder and team defines “value” and “success.” This may not be consistent across the organization. Knowing which benchmarks and preferences each team has are useful. Particularly in understanding product managers’ views. Keep your one-on-ones on the shorter side to be respectful of their time. Thirty minutes should be plenty for those initial getting-to-know-you sessions. Follow up after the initial round when needed. 3. Demos, demos, and more demos. Any product manager should be familiar with their product and value propositions to give aproduct demo at the drop of a hat. As someone new to the product, demos can play an instrumental role in understanding the product. Seeing what different stakeholders think about it, and emphasize is important. So is showing existing colleagues that you’ve digested what the product has to offer and how to position it. To do this, schedule sessions with multiple people or teams individually. You’ll want to see sales, engineering, and the existing product team demo the product in isolation. This way their commentary and presentation aren’t influenced by whoever else is in the room (or on the Zoom). Each demo will vary in what they show off (versus gloss over) and what language they use. Seeing how sales sell the product versus what engineering believes is essential can be eye-opening. This gives insight into what each group prioritizes. You can document the gaps. Once you’ve witnessed everyone else’s take, it’s your turn. Your demo will not only illustrate that you’re now quite familiar with how the product works and the key talking points. It can also synthesize the different messages you picked up from your colleagues to give a more holistic view of things. 4. Ride shotgun with sales and support. Salespeople and support staff are the folks having the most interactions with actual customers and users. Sitting in on their calls can be very illuminating. Not only will you get a heavy dose of the voice of the customer and reinforce your commitment to customer-centricity, but you’ll also get a sense of your new coworkers. Don’t try to jump in and take over, although you can occasionally interject with a question or clarification. The real opportunity for interaction is when the call is over, and you can debrief with your colleague. These interactions can help build a report with them and show them you’re an inquisitive, thoughtful product manager. Not just some new person with a pile of opinions and assumptions. You’ll also be able to spot low-hanging fruit for some quick wins when the time comes to start prioritizing items. Be sure to ask whether anything that stood out on the call was an outlier or something they encounter. This will help you categorize what you hear as anecdotal or pervasive. 5. Search the archives. Can’t get enough forthcoming team members to talk? Support tickets and the support team can be another great resource. Reviewing these gives you insight into the current state of your customers. From there, you can review the product backlog. Note which stories were accepted in the past, the key milestones used, and how releases were packaged. You can peel back the onion even further by reviewing the conversation logs. This helps your understanding of how decisions were reached. In addition to what variables got a lot of attention, and who were the key players. Retrospectives will give you a sense of morale and feelings. If there were minutes or action items from previous retrospectives, these could be mined for details. If you’re able to attend (or even facilitate) a retrospective of a recent release, you can witness it all in real-time without any prejudices or skin in the game. Just be sure to stay in “listening mode.” hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); 6. Take a holistic approach. When you’re first learning the ropes, it’s natural to stick close to the other product team members. Or devote much of your time to building your relationship with engineering, but Mustafa warns against this. It’s important to expand in order to create your sphere of influence. Instead, she recommends taking a 360-degree view of the organization. Getting input and making connections with every department will help you get a fuller, less-biased picture. This will help you to forge connections with the organization’s broader swath and develop your sphere of influence. You never know when that will pay off, and it will certainly help you build cross-company support down the line. Make sure you also know what you’re accountable for. If the executive team expects a weekly dashboard or monthly update at an all-hands, find out and get ahead of it. Takeaways It can be hard to avoid speaking your mind and fixing obvious flaws as soon as you notice something awry. Reserving your opinions until later in tenure is the right move. You don’t want to suggest new ideas or try to impose any new methodologies until you have a solid baseline of understanding and discretely vet your ideas among a smaller, friendlier audience. If you come out shooting, many of your good ideas will be ignored or forgotten. At least until you’ve built up a stable of allies and established a favorable reputation throughout the organization. While your first 90 days isn’t your only opportunity to build your sphere of influence, it’s a great opportunity can set you up for an easier path to ship great products moving forward. Read the Career Guide for Product Managers hbspt.cta.load(3434168, '51f4627c-aefd-4981-92a8-41fe12455dbe', {});

I have been a part of two successful startups and product development teams for the past 17 years. The first was acquired and thrives today with products such as GoToMeeting and GoToWebinar. The second one, AppFolio, went public and also thrives with its software for property management companies and law firms. The key takeaway from watching each of these companies grow from roughly 10 employees to 600+ each is this: It’s all about building relationships. It is just like exercise. If we exercise regularly, a side effect is that our diet typically improves. If we build relationships and really know and care about the people we work with, everything else comes easier. So how can we build relationships on our product development teams and thrive? Here are five ways. 1. Sit Together At my first startup, engineering and product development teams sat separately, and we all had our own individual offices. As our departments grew, we were spread even farther from each other. As a result, informal interactions between different groups went away, or became more challenging. Our communication would primarily take place over email or on the phone. Our engineering and product groups would only meet weekly or biweekly to review progress. We’d attempt to “be on the same page”, and that “page” was typically a schedule expressed in Microsoft Project. We weren’t exactly “strangers” but we really didn’t “know each other”. We learned — when we don’t see the people we work with on a regular basis, we make assumptions and distance grows — “us” and “them”; and “we” and “they” language emerges. Working together becomes harder. Years later at AppFolio, my second startup, we hired Jason, the product manager I worked with closely at the first startup. At that time, our entire company was in one room with an open floor plan. We’d have casual conversations, and share the antics of pranking people’s desks when they went out on vacation. Once when Jason was out we upgraded his computer with the latest hardware from the 80s as shown below! We were all thrilled when our property manager software was fired up on his screen. It was a fun moment for everyone, including Jason. It felt like we were all on “one team” when we were in the same room. Jason returns from vacation to find a “state-of-the-art” computer setup on his desk. I remember reflecting with Jason about being together with our groups in the same space at AppFolio versus being in different wings of a building when we were at the first startup. From there, we made a pact that our groups — engineering and product — would all sit together in the same open space going forward. It’s now about nine years later, and we still work in open areas and are together as cross-functional teams of engineers, QA, UX, product managers, and agile coaches. Example of a cross-functional team area at AppFolio. Sitting together does not come easy if there are remote teams and offices. Workarounds such as Google Hangouts and GoToMeeting are available to help in such situations. We promote the use of video for our remote friends as it helps to level the playing field and bring us closer. View of our satellite office via Google Hangouts at AppFolio headquarters. View of AppFolio headquarters on screen via Google Hangouts from our LA office. 2. Actively get to Know Each Other and Build Trust Doing activities to help get team members to know each other on a personal basis is an incredible strategy for team-building and raising the level of respect on teams. At AppFolio, when we reteam or change up team membership, we have deliberate discussions about how we want to “be together” as a team. We determine what we want it to be like in our physical team spaces. We elicit team members’ preferences regarding communication and interruptions, and vision out the characteristics for our team in order to flourish. This includes understanding how we will operate when things get difficult. Because they “will” get difficult. This raises the positivity in the environment and makes conflict easier to bear. Examples are: team members’ desire to go together for a walk outside if they have a conflict, or to give “alone time” to someone you overheard having a challenging phone call. The book, Creating Intelligent Teams by Anne Rød and Marita Fridjhon, gets into the specifics of designing “team contracts” like mentioned above. We also do many other activities to deliberately enhance the experience of getting to know one another and build trust. One of them is a modified version of the Market of Skills activity from Lyssa Adkins’s book, Coaching Agile Teams. If you walk through AppFolio today you are likely to find one of these Market of Skills posters hanging on a wall or the side of a desk. Team getting to know each other via Market of Skills activity at AppFolio. We also go on short outings together as a cross-functional team. We are fortunate to be located in Santa Barbara, California. I like to take teams out on hikes and combine it with sharing personal stories to bring us all closer. A favorite activity of mine is a “Fulfillment Hike”, an activity inspired by “Co-Active Coaching”. In this activity, we share with each other a “peak experience” in our lives about something that is personally meaningful to us. At the top of the hike, we stand or sit in a circle, and go around sharing the stories we heard from our partners. Together we derive the values from each of our stories and have a discussion about which values we would like to carry over into our daily work. We put up these values on a poster in our team area as a reminder of what we want. Photo of cross-functional team on a hike up Inspiration Point trail in Santa Barbara. By actively getting to know each other, we can empathize well with each other and can build great trust and camaraderie. 3. Share and own Challenges Together During the early years of my first startup, waterfall-style development was the norm. Unable to predict, product development teams would promise a deadline but deliver late. Discussions about this topic were extremely stressful and difficult. The saving grace of this type of thing was to cut back scope (ideally) in order to get as close to the committed date as possible. Conversations about this topic between engineering and product groups couldn’t just happen on the fly. They needed to be “scheduled” due to the distance between our groups. This took time and elevated tensions among our groups. We learned that our practices prevented us from sharing and owning challenges together. We had to fix that. Fast forward to AppFolio… due to physical proximity and actively getting to know one another, product managers and engineers are more open and honest with each other. Product managers get a daily or even hourly understanding of where things are at. Everyone is present together in their work-area and at regular team events. We can even discuss our work challenges during a team hike while going through a physical challenge. The chance of having negative surprises is greatly reduced. Example of product development teams discussing work visualized on a board in their team area. Cross-functional product development teams can also share the challenge of onboarding new team members. When team members share the mentorship of a new employee, the load is lighter. And, the person being mentored gets more attention, and is exposed to different styles of working. This can include cross-group mentoring. For example, experienced engineers can help out in mentoring new and experienced product managers. In summary, we are stronger when we face challenges together — regardless of what group we are in, or what reporting structure we have. Helping each other succeed helps us realize our goal of delighting our customers with our product development roadmap. hbspt.cta.load(3434168, '9e6140b2-e382-45fd-ace0-16435228cf7b', {}); 4. Help Each Other Succeed I remember talking to our AppFolio co-founder and CTO Jon Walker about a challenge I was having with a fellow team member. He looked at me and said, “Heidi, how can you make this person successful?” That simple phrase changed everything for me, and I’ve come back to it over and over again as I coach people around me. When we hire people, we want them to thrive and be successful. That’s why we hired them. Helping to educate team members on this simple yet powerful topic can make an incredible impact. When I hear complaints about another person, I even find myself echoing Jon by saying, “How can you help them be successful?” When I mentor people at AppFolio I like to teach them the concept of Net Promoter Score (NPS) applied to us as individuals. We use the concept of NPS with our AppFolio customers on a regular basis. It tells us how likely our customers are to recommend our software to other people, as well as collects qualitative comments that we analyze for improving our products. It comes from the book The Ultimate Question by Fred Reichheld. When applied to people, I encourage people to think about their behavior and actions and how they think others might perceive them in their teams and outside their teams. Are they “creating promoters” for themselves? What are the chances that their behavior will be championed by other people around them? Teaching team members tools and techniques for communication challenges they are experiencing is a great way to support them and to help them grow. In recent days I have been teaching managers techniques to use with people on their team to help prepare them for having what they perceive as “difficult” conversations with others. We do an empathy building exercise based on a modified “3rd entity” activity from Organizational Relationship Systems Coaching (ORSC). When you reteam at AppFolio, you have the opportunity to work and learn together with different people. But you might be used to the style of a particular team member and expect that the people on your new team will act in the same manner. This is the type of scenario you face with a fast-growing company like ours. Deliberately promoting the attitude to help one another encourages everyone to be “in it” together. This might mean building more patience and helping fellow team members along the way that are new to their roles. It also might mean putting our named “roles” aside and doing whatever to help the endeavor move forward. 5. Have Outings and Learn Together At the first startup, we had the tradition of having annual retreats where our engineering department would go camping, white water rafting or some other trip typically involving the outdoors. The tradition originated, according to our founder Klaus Schauser from an experience he had with a student group that he was a part of at UC Berkeley. AppFolio was co-founded by Klaus, and when we were a startup we continued this tech retreat tradition, starting with our inaugural retreat white water rafting on the Kern river. Photo of AppFolio as a startup after its inaugural tech retreat rafting on the Kern river. Since we had the pact to always sit together with product and engineering, it seemed fitting to continue that vibe by inviting and having our product development teams go with us on every tech retreat. It’s now almost nine years later and the groups have gotten much larger. Still, all of the people who work on building the products together — engineers, QA, UX and product managers go on this annual trip together. It’s nothing short of epic! We have done camping at the Channel Islands together, white water rafting, high ropes, and have even been to Disneyland. Teams have quarterly budgets to do local events together as celebrations to mark milestones, or they can do them just for the sake of bonding and getting to know each other better. This organizational support has helped us thrive, especially for the years in which our engineering and product teams doubled in size. Often different groups also bond by going to conventions together, where we learn together and get to know each other in a setting apart from the office. We’d also plan and organize extra social events while in the corresponding city. Last year we were in Washington DC together, and we visited several sight seeing locations, and even rode a ferris wheel. In the photo below are two engineering directors, two agile coaches, three product managers, one UX engineer and one QA engineer. Having this shared learning and joyful experience brought us closer together and it was just plain fun. Photo of team members after they rode a large ferris wheel in Washington D.C. Summary Reflecting back on the experiences I have shared at both startups, I can tell you that relationship building is critical. As individuals, we are at our jobs to make money and to survive as independent people in the world. We spend more time at work typically than we do with our families. The time we spend with our co-workers, our friends, can include some of the most memorable and incredible times in our lives. We can work together and create incredible products for our customers, and love every minute of the experience together. If you know and care about the people you work with, everything else comes easier. About the Guest Author: Heidi Helfand has 17 years coaching and influencing cross-functional product development teams at pioneering web software companies. At Expertcity, Inc. (acquired by CitrixOnline) she was on the initial team that built GoToMyPC, GoToMeeting and GoToWebinar. She is currently Principal Agile Coach at AppFolio, Inc., a SAAS workflow software company with property management and legal practice management software. Prior to that, Heidi consulted for the State Dept. on website development, and has taught ESL at several US Universities. She has an M.A. in teaching from the University of Illinois at Urbana-Champaign and is a Certified Professional Co-Active Coach (CPCC) and Associate Certified Coach (ACC) through the International Coach Federation (ICF). Follow her on twitter @heidihelfand For more information visit heidihelfand.com Acknowledgements I would like to send out a special thanks to my AppFolio friends Jon Walker, Rahul Sawhney, Regina Rodwell, Jennifer Payne, and Ellie Thomas for their feedback on early drafts of this blog. I’d also like to thank Joshua Kerievsky of Industrial Logic for his thoughtful comments and encouragement. References Rod, Anne Fridjhon, Marita. “Creating Intelligent Teams” KR Publishing, 2016. Adkins, Lyssa. “Coaching Agile Teams: A Companion for ScrumMasters and Project Managers in Transition” Addison-Wesley Signature Series (Cohn), 2010. Kimsey-House, Henry; Kimsey-House, Karen, Sandahl, Philip, Whitworth, Laura. “Co-Active Coaching: Changing Business, Transforming Lives.” Nicholas Brealey America, 2011. Reichheld, Fred Markey, Rob. “The Ultimate Question 2.0: How Net Promoter Companies Thrive in a Customer-Driven World.” Harvard Business Review Press, 2011. CRR Global, Organizational Relationship Systems Coaching (ORSC), http://www.crrglobal.com/coach-courses.html

Be a hero, follow the money, and market yourself. Got it? Really? On top of everything I am responsible for as a product manager, you’re telling me I should care about content, too? Isn’t that someone else’s job? Yes, you should care. Even if there is a dedicated product marketing manager responsible for messaging, demand generation, and sales enablement, as a product manager, you should contribute content. And if you are responsible for the go-to-market side of product management, you absolutely positively should contribute content. But who has time? If one more person asks me for screenshots, I’m going to scream. Sounds like a software product manager! Screenshots are not content marketing. Not that marketing doesn’t need them to create product assets, but what I’m talking about is providing context around personas, market problems, market stories, and customer successes with your product. Content that leads to your product, not with your product. Content that helps buyers buy and helps move them along their journey to buy and use your category of products. Raw content that can blossom into engaging content that buyers want to consume. The content might spawn an ebook or video or blog entry or infographic or short social media post. And no, I’m not saying you are responsible for producing the content into finished form (more about this later). About screenshots: If you just grab a lot of screenshots without first understanding what story the screenshots should tell, you’re wasting time (yours and marketing’s). Start with the problems you solve and tell the stories of how your product solves those problems within the context of your personas’ lives. Otherwise, why should they care? Seriously, why should I care about content marketing? One more time, three great reasons: 1. Be a Hero Product managers are often compared to superheroes. After all, it takes superhuman strength and superpowers to identify market problems worth solving, get your product funded, guide development to build what the market wants to buy, help marketing tell the world your product exists, help sales figure out how to sell it, and keep the product, marketing, and sales machines fueled, maintained, and operating at full capacity. All good. But even if you are doing a great superhero job, you might still blend into the background at your company. Like Clark Kent. Sometimes you need to put on your cape and tights and let everyone see your heroic activities. Translation: Create some content to help market and sell your product. After all, you can have the greatest product in the world, but if no one knows about it, who is going to buy it? You need this to have a successful product. Be a hero for the product manager (you). If you’ve been doing your job right, listening to and observing the market, looking for compelling problems to solve, understanding the context of users trying to get their jobs done, and hearing what buyers want and why, you have the basis for content to help buyers buy. Share, share, share your knowledge! I’m freaking out. Are you saying I need to produce all of this amazing, finished content? Breathe. Unless you’re two guys in a garage in pre-startup mode with no money, what you need to provide is the market context, not the finished production-quality content. It’s like working with development. You provide context about what the market needs and they build the product. Which brings us to the second reason you should care about content marketing. 2. Follow the Money If you look at the departments you work with, only one of them seems to have money to spend. Marketing! According to an infographic created by TAMBA (a social media agency), the average marketing organization is spending a sizeable chunk of their marketing budget on content. B2B marketers are spending 28% B2C marketers spend 25% According to TAMBA’s research, the top 2 most outsourced content marketing activities are writing (44%) and design (41%). Cool! Let marketing fund the production of the content while you provide the context. Just like working with development where you create user stories, requirements, or some other form of context so they can build the product, you need to transfer your market knowledge to someone who will manage the production of the content and turn it into tasty, engaging content treats. If done right, some of the context you provide for development may be reusable to educate marketing. The essence of what you need: Problems you are trying to solve for your customers. Describe this as if you were telling a friend or family member what the situation is that causes the problems. If you’ve been spending time in the market like you should, share specific stories about the problems customers face and why they need the problems solved. And the problems are not “need more revenue” and “we’re spending too much”. You need enough context that the resulting content is not so generic (“for everyone”) that it resonates with no one. Buyer and user personas.The better you can profile your personas around the issues they face, how they consume information, where they go for advice, how to find them, what their spending authority is, what their aspirations are, and how they are motivated, the better your content will be. If you don’t know anything about the people who buy and use your products, focus your research efforts on learning about them. How your company can help: Offer advice, resources, survey results of others like them, “how to” tips and tricks, “what’s cool”, “what’s new”, risks and rewards, customer success stories, and how your solutions solve the problems. If you stay close to your market, every time you learn of a new problem they have can be an opportunity to create content that empathizes with them and advises them on how to solve the problem (whether it’s through your product or not). You may be begging marketing to create marketing stuff to generate demand for your product. If you want them to pay attention to you, give them what they need most from you: context to create the finished marketing asset. To create effective marketing programs, marketing needs context about why buyers should care about what you sell, starting with non-product advice about solving their problems. It’s really hard to market without effective, relevant content. It might be impossible. The content is the fuel that drives marketing activities and the marketing machine. You will be a hero to marketing (see reason #1) if you provide the market context that will help the product fly off the shelves, and marketing will be more likely to spend money promoting your product if you give them the delicious raw materials of compelling market stories that engage buyers. 3. Market yourself As product managers we get so busy, we forget to market ourselves. Don’t wait until you need a job to focus on your career. Do a great job for the company you work for, but use your successes to help you reach your career goals. If a job opportunity comes to you next week, what will your potential employer find when they Google your name? By sharing great content on your social media platforms, you can build a presence and reputation that can help you in the future. “Don’t wait to dig the well until the well goes dry.” Too late! Remember that you don’t have to “build” all content yourself. In your product, you should be making “buy, build, or partner” decisions to solve problems, why not do this for content? BUY No money? See #2. And help marketing spread the word about the content by sharing on your social media platforms. BUILD If you want to be considered a thought leader in your category or industry, you need to create some of your own content (not the creative design, but the ideas). Maintain a list of potential topics and carve out time to periodically: Write a post for your company or personal blog Write an update for LinkedIn Post comments on LinkedIn groups Participate in LinkedIn discussions Do a speaking engagement (online or in person) and post the slides on SlideShare Tweet to drive traffic to your content PARTNER Curating content from other sources is a great way to amplify your social media presence. Be thoughtful about what you share, however. If a potential employer or recruiter sees the post, does it help tell the story of who you are and what you care about? And have you added your point of view to the content you are sharing? Always respect copyrights and source the content you’re curating. It’s the right thing to do. But add your point of view to augment what you’re sharing to illustrate your expertise, knowledge, or opinion. So what is content marketing, anyway? One of my favorite marketing bloggers is Jay Acunzo. He wrote the funniest blog at Sorry For Marketing defining what content marketing is (and isn’t). According to his Jargon Monster: “Content marketing is an umbrella term covering a set of strategies, techniques and tactics to fulfill business and customer goals by using content across the customer life cycle and the business functions in a consistent, integrated and continuous way.” Read that again because you may not have really gotten it. What?? Really? If someone can’t get what you write the first time, then maybe it’s gobbledygook. Sadly, this was probably written by a marketer… Shameful. Here’s what Jay’s Naked Little Truth says: “Content marketing is just solving the same customer problems as your product but through media you create and distribute.” (My emphasis.) Imagine that. Solving the same customer problems as your product. That’s when the lightbulb went on for me about why product managers should care about content marketing. You already have the knowledge to create great content. You need the same context to define your products and services. A great example of content that solves the same customer problems as your product is this ebook from LIKE.TG: This ebook is chock full of ideas and content addressing the challenges product managers have. When I first saw this on Twitter, they had me at the title. Click, register, download. If the title isn’t enough for you, what about: How to develop a winning product strategy Best practices for building your roadmap 9 example roadmaps to get you started If none of this resonates with you, you’re not a good prospect for the product anyway. Move on. If you want more examples of great content, check out what my marketing team at Sage Construction did with our Job Ready program. Don’t be intimidated by the depth and breadth of content, however. We built this program agilely, theme by theme, quarter by quarter. Content became the basis of our marketing strategy, fueling the marketing machine throughout the customer journey. I’d love to hear your successes about how your content rocked it. Did content make you a hero? Did marketing embrace your content and create awesome assets leading to lots of business? Did content help your career? About the Guest Author I wasn’t always a marketing executive and consultant. My journey from the trenches to management to the executive suite to becoming an elite member of the Pragmatic Marketing team of instructors and back to the executive suite has given me a unique perspective on technology marketing. Let me apply my expertise and passion to help you unlock your story to engage colleagues, customers, and buyers. From idea to content to visuals to delivery. Contact or follow me: [email protected], @barbaragnelson, LinkedIn.

I still cringe when I think back to the first roadmap I put together. Like most of us who find ourselves in product management, at the time I didn’t even realize I was doing “product management.” I was the lead of a UX team and saw a bottleneck between our work is designed and being implemented by the development team. So I sat down and wrote out the requirements and the order in which I thought the work should be done. As you might expect, it was a terrible roadmap. Cobbled together in a spreadsheet with links to a prototype serving as the only design specs, there was little visibility into what we were building, let alone why. I can’t believe my teammates put up with it. Thankfully, much has changed since then. For starters, I’m officially running product at my new company, Notion. More importantly, we have a process in place for team-wide alignment on our roadmap thanks to increased visibility and understanding of why we are building what we are building. We accomplished this by gathering what we call Little Data to tell the story of how we align and adjust our roadmap. Aligning the Roadmap LIKE.TG’s Planning Board feature is a great way to align your team around upcoming features. Thanks to their built in Weighted Scoring Model, it’s easy for the entire team to rate features as they relate to your goals as a company. At Notion, our benefits are designated by Customer Signal, Quarter Strategic Value, and Growth Opportunity. In other words, we rate a feature based on how high the demand is, its alignment with our growth goals, and how marketable it is. Our costs are broken down by Estimated Sprints, Unknowns, and Risk. These help us identify how long a feature will take to build, how much discovery still needs to happen, and whether or not the feature jeopardizes other elements of the app or user experience. After rating and reviewing these as a team, we are left with a prioritized list for the quarter based on the final score of each feature. That doesn’t mean we always build in that exact order, but we now have a baseline to measure any changes to the roadmap against. If anyone on the team wonders why we are building something, we can point back to the list and (hopefully) be able to explain our decision process. It’s a massive improvement from the laundry list of features I used to keep in Excel and has really increased team buy-in on what we are building. To learn how to build a data-driven roadmap of your own, watch LIKE.TG’s webinar: Adjusting the Roadmap The prioritized list from LIKE.TG serves another purpose. The synthesis of the costs and benefits correlates to the perceived value we are delivering to our customers. The higher the rank, the higher the value. This is critical data to reference as we measure our success goals since the other half of owning a roadmap is being able to make adjustments to it. hbspt.cta.load(3434168, '1f74539e-d4fc-4cb3-97c6-fd86de2bf62e', {}); We gather this data in Notion itself. As a tool, Notion brings together team, product, and performance data to help you make smarter, faster decisions. This means as a team, we are able to dogfood our own product to improve our own product. At the end of each sprint, we poll the team on a few team health metrics, one of which is how much value we think we are delivering to our customers. We can compare that value alongside other metrics we track in Notion like conversion rates, growth rates, and user activity around specific features. A dip in delivered value may result in undesirable drops across the board. We’re also in frequent contact with our customers to get a better sense of what is and isn’t working for them. If adjustments need to be made, we use this data to support our decisions. We can go back to the Planning Board and identify where we may have missed in our initial estimations, make the necessary adjustments, and document it so we can avoid the same mistake again in the future. Getting Started If you are interested in approaching your roadmap this way, my best piece of advice is this: Start small and be flexible. There is no secret set of metrics that will apply to every team or company. Plus, your needs and goals as a company will most likely change over time. Align your team by creating visibility into and understanding of your roadmap goals. Once this exists, the metrics you need to track should be easier to identify. For more tips on how to get started, you may find our School of Little Data helpful. Or feel free to reach out, we’re always happy to chat. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); About the Guest Author: Kevin Steigerwald has been designing, researching, marketing, planning, and building products big and small for over 10 years. He is currently the co-founder and CPO of Notion in Portland, Oregon.

At LIKE.TG, we meet hundreds of product managers across virtually every industry. Their experience gives us invaluable insight into the profession, its challenges and its best practices. Today’s post is based on an interview with Julie Hyman, Senior Product Manager for Dell Software Group. A product manager with more than a decade of experience, Julie now manages several data prep applications in Dell’s Toad suite. LIKE.TG: If you could give only one piece of advice to a new product manager, what would it be? Julie Hyman: This one really took me a long time to learn — you always, always need to keep customer experience as a top priority. It sounds obvious, because in the end, of course that’s what makes for a successful product. But what you’ll find throughout the development process is that many constituencies in your organization are going to be coming to you with different agendas. Sales will come to you and ask to break the app you’re building into two separate pieces, “So we can sell two SKUs.” Development might recommend you code the product differently from the way you have it on your product roadmap, “Because this other way will work more seamlessly with our backend system.” Even your executives might ask for shortcuts, “Because we really want that product rolled out for GA this quarter.” You know what’s missing from all of those conversations? How any of those decisions will affect the customer experience. So that would be my one piece of advice: Always be your customers’ strongest advocate. Always keep their interests and their experience in mind. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); PP: What are the big mistakes that you’ve seen product managers make? JH: The biggest misstep I see is product managers getting too comfortable in one of two areas — either a strategic focus or a tactical focus — and then staying in that mindset all the time. To be an effective product manager, you really need to bounce back and forth between the two. Here’s what I mean. Let’s say a software product manager really enjoys thinking big picture. So he holds lots of high-level, strategic meetings with executives and with marketing and sales to discuss five-year plans for his product. Or to discuss huge undertakings, like how the product will be adapted for mobile or the cloud. These are great conversations to have, but that same product manager is also responsible for the next release of the product, which means he’s got to spend time with his developers and his scrum master talking about features and other more tactical details. I’ve also seen product managers make the exact opposite mistake — spending all of their time in the weeds, working every day with their development teams on the smallest details like the product’s background color and the size of the shadows on a button. Those are valuable conversations to have, too, but that product manager needs to lift his head up regularly, step back, and examine his product from a more strategic perspective. What I’m saying is, product managers can’t really afford to be specialists. You need to know your product, yes, down to small details. But you also need to spend time and focus gaining insights into your company’s overall strategic goals, your market, your customer personas, your competitors, and plenty of other strategic items. To be an effective product manager, you’re going to need a big shelf for all of your hats! PP: How do you learn what your customers really think about your product and what they want from future versions? JH: I ask them — directly. Feedback tools like SurveyMonkey can be effective, but in my experience nothing beats actually meeting with someone who is using your product in their everyday workflow, sitting next to them, and watching how they actually interact with it. Or getting on the phone with someone who is using your product and hearing what they have to say about it, the good and the bad. This is another misstep I’ve seen a lot of product managers make. We can easily become too insulated, reading the industry magazines and analyst reports, and talking with our own colleagues, and substituting those opinions for our own market research. When you think about it, it makes no sense to do it that way because we obviously have a much richer source of feedback — our own customers! We still need to use that third-party research from the analysts, of course. That research also includes invaluable information on the personas who don’t actually buy our products, the people who instead buy from our competitors, or who decide they don’t need a solution from any of us. We need to learn about what informs those decisions. But I am always surprised at how many product managers I meet who have all of these opinions about why their products are succeeding or failing, and yet don’t go out and actually talk to their users, or who talk only to the same handful of “friendly” users all the time. So my advice here would be to use it all. Read the independent industry research. Do your own SurveyMonkey surveys, but use them sparingly enough that you’re not turning off your customers or wasting their time. But above all, go visit your customers face-to-face, or get them on the phone for 20 minutes. Let them tell you in their own words what they like, dislike and want in your product. PP: What would you say is the most important skill for a product manager to have? JH: Above all else, I think that to succeed as a product manager you have to be an effective influencer. Here’s why. Your title in most cases won’t give you the luxury of ordering people within your company to do things in a certain way or within a certain timeframe just because you want them to. In fact, you’ll often find that in many situations where you need to work with other teams, you won’t have any organizational authority. The development constituents you work with could be anything from scrum masters to vice presidents — farther up in the company’s hierarchy than you are. Same with sales or marketing or PR. The people in these departments whose help you’ll need to drive your product development could all be higher than you are on the org chart. So, how can you move these constituents to work with you, in a way that’s consistent with your vision, and bring your product successfully to market? You have to use your powers of influence. In other words, you can only earn your authority with these constituents, by convincing and persuading your colleagues to see and agree with your strategic vision for your product. And to do that effectively, you need to use your knowledge, your reason, and your ability to paint the picture for them of where you want the product to go. (Enthusiasm doesn’t hurt, either.) And how do you do this? Have good data. Use logic. And just as important, tell good stories. There’s an emotional component to a story, and it is how people will understand and relate to what you’re suggesting. That means you need to communicate a successful vision of your customer’s experience. You need to paint a clear and compelling picture of what you’re trying to achieve for your customers. Then you need to use your powers of persuasion to bring all of these constituents onboard. In the end, I think that the simplest way to think of your job as a product manger is as your product’s chief influencer. Here’s another way to think of it. Being a product manager is more like being a coach than a supervisor. You can’t force it. These different teams, who will be so instrumental in helping you bring your product to market, will need to stay motivated and working toward a common objective through a development cycle. You need to convince them — and keep convincing them, over this development period — that the path they are taking with you is the best road to a successful product.

Public speaking isn’t usually included as a required skill in a typical product manager job description. But it should be. Today’s article on public speaking tips is written with product managers in mind, but is broadly applicable to many trades. We’ve been trained to think of public speaking in only the narrowest sense: a professional standing on a stage or at the front of a large room, often behind a podium, delivering a speech to an audience. But for product managers, public speaking can take many other forms. In this broader context, a product manager’s job often requires public speaking — at product roadmap meetings, development meetings and daily scrums, sales meetings, executive stakeholder meetings, analyst briefings, product demonstrations to prospects, customer site visits, and many other settings. Then there are all of the other public speaking opportunities designed to establish product managers and their companies as thought leaders in their industries. These include sitting on discussion panels at conferences, tradeshows and other events; hosting educational webinars on issues related to their products; and being interviewed by reporters or analysts as public representatives of their products and industries. In fact, you can even think of a product manager as her product’s chief public speaker. Given how important public speaking is to a product manager’s job, here are some tips and strategies to help you become a more effective public speaker — and, as a result, more effective as a product manager. How to be an effective public speaker Speak with Authority — by Using Data This tip will apply in virtually every situation where you have to speak to a group — whether you’re running a development meeting to discuss features and product details, or delivering a high-level product roadmap overview to your executive stakeholders. As a product manager, you have the data that support your decisions for which features your next product iteration should prioritize, how to adjust your pricing scheme, and what the best time will be to roll out your product for general availability. The data can take the form of quantitative metrics related to the product or qualitative data such as the results from customer interviews. Using data to support your talk can give you two important advantages in persuading whatever audience or constituency you are speaking to. First, bringing relevant data into your discussion positions you as the authority on the topic. This credibility can help you overcome the barriers product managers often encounter when, for example, trying to convince executives to green-light to a new initiative, or when trying to persuade a sales team to agree to a new pricing structure for the product. A second advantage of supporting your talk with data is that it signals to your audience that your suggestions and requirements are not simply your opinion but rather the result of real-world evidence. This will often give your constituencies more confidence in your decisions than if they believed those decisions were only the result of educated guesses. Some product managers are reluctant to deliver presentations or run meetings based on statistics, charts or other data, because they worry that the material will be boring. This is a valid concern: A talk or meeting driven entirely or primarily by dry statistics can cause you to lose your audience to thoughts about what to have for lunch. But you can find ways to include credibility-enhancing data points in your discussions without losing the room’s attention or enthusiasm. The best way is to use your data points sparingly, and to build them around a lively, more interesting mechanism for delivering your talk. Which leads to tip 2…. Build Your Talk Around Stories Often the best way to structure a presentation or other public talk is to deliver it in story form. People respond to stories. They remember stories. Stories provide a convenient framework for a complex discussion, allowing you to quickly bring everyone in the room onto the same page in terms of the big picture, before you dive into any details. To explain why this works, let’s use a story. Say you need to present your strategic plan for an overhaul of your site’s e-commerce experience to your executive team. You’ll need their buy-in before you can move forward and commit development and marketing resources to the project. You could walk into your discussion with a slew of data to back up your argument that your online shopping page needs an overhaul. Your shopping experience currently takes 45 seconds longer than the average site selling a comparable product. Your e-commerce page has been rated among the lowest of its kind by third-party review sites. Your shopping-cart abandon rate is 23% higher than the industry norm. And on and on. Some of your executives might even be persuaded — if the PowerPoint slides filled with charts and raw statistics don’t send them deep into thought about lunch. But now imagine that instead, you walk into your meeting and open with a story. It goes like this. “Our new marketing campaign catches the attention of Kirk, our primary persona and ideal customer. He comes to our site, spends a few minutes reading our blog… a few minutes more checking out our testimonials page, and then he….” (Note: At this point, your executives are likely all listening intently, interested to know what happens next with Kirk. Not one of them is daydreaming or making mental lunch plans.) “Finally, Kirk heads to the pricing section of our website. After a few minutes on that page, he clicks buy. Everything is working according to plan! “Kirk selects the most expensive version of our product, inputs his credit card information… and then four minutes later abandons his shopping cart. He also ignores our follow-up asking if there’s anything we can do to help him complete his purchase. “What happened?” Because you’ve introduced the discussion topic — your strategic plan to improve your site’s e-commerce experience — using an engaging story, told from the point of a customer, your executives are now ready to listen to your evidence. And because you’ve established the framework for your topic using a story that everyone in the room intuitively understood and related to, your evidence will carry far more weight with your stakeholders than if you had simply recited it without first putting it in context. Be Flexible Let’s say you’ve built your new product roadmap and have scheduled a one-hour meeting with your sales and marketing teams to run through it. You’re planning to start the discussion at a high level, providing a strategic overview of the product’s current position in the market and where you plan to take it with the new roadmap. Maybe you’re even planning to open with a story. These are all smart public speaking strategies. But a couple of sales executives who will be in the meeting tell you just beforehand that they’ll need to cut it short. Now you’ll have to deliver essentially the same talk in only 15 minutes, including QA. Or assume one of the sales executives catches you in the hallway and asks you to pop into an empty conference room and quickly explain your thinking behind the new roadmap. In other words, in this instance you’ll have to deliver the same talk in five minutes! As a product manager, you might be called on to discuss your product vision at length, or in just a few minutes; to a technical audience, or to a non-technical sales rep. Part of the value you bring to your company is the ability to quickly and persuasively articulate that information under just about any conditions. Keep Your Talks Positive Enthusiasm is contagious. So is negativism. That means as a public speaker, you have more power than you might realize to influence your audience’s perceptions and feelings about your topic. One of a product manager’s many roles is to serve as her product’s chief evangelist. So it is important that when you speak about your product in any context, to any constituency, you remain positive, and focused on moving forward to achieve your strategic goals. It’s easy in a product roadmap meeting or a scrum meeting to be taken off track and discuss past development cycles, or dwell on what went wrong with a previous release and who’s to blame. These detours almost never lead to any enthusiasm or positive feeling among the people whose hard work and dedication you will need to move the product forward. Because you are the person driving these meetings, you can implement a culture that guides your teams to focus on the positive. What’s more, as the lead speaker in many of these settings, you always have complete control over what you say. Another trait of great public speakers is that they stay positive and forward-looking — and, leading by example, they encourage similarly positive feelings among their teams. Conclusion: Public Speaking Ability is Essential to Effectiveness as a Product Manager You might not have been asked about your public speaking ability in your interview for any product manager position you’ve ever applied for. And you might never have given much thought to the importance of honing this skill just as you would the ability to understand technical jargon or read a profit-and-loss statement. But as you have probably found if you’ve spent any time in a product management role, it is difficult to make it through a week without having to do some form of public speaking — whether that means leading a meeting, presenting a product roadmap to one of your constituencies, or accompanying a sales rep to a customer site to talk about your product. Public speaking is a vital tool in the arsenal of any product manager, not to mention an invaluable skill to have in any area of life. So there is plenty of upside — and no downside whatsoever — in devoting time and energy to becoming the best public speaker you can be.

There’s no shortage of sage advice for product managers. However, all advice may not be the best advice. To rectify this, we’ve sifted through years of our articles, blog posts, and booksto provide you with the top six product management tips. These nuggets of wisdom—based on decades of experience in this unique profession—focus on what’s essential. While you might disagree with our curated list, we believe you will find at least one of our product management tips useful in your career. Our 6 Best Product Management Tips 1. Always take a collaborative approach Probably one of the most important product management tips is to take a collaborative approach. Each individual has a unique approach to accomplishing a task. They have different work styles, communication preferences, and opinions. Working with others comes with a host of challenges. Yet, though complex at times, those challenges bring a ton of value to the table, especially when working with engineering and design teams. In some organizations, the three-way relationship between the coders, designers, and product people may lead to teams challenging each other. Collaboration can help each team come to a consensus and find common ground. Contentious environments discourage innovation and risk-taking. Product professionals need to be aware that varying insights and ideas are available when everyone gets a voice. By welcoming stakeholders from different departments into the conversation, the product and its customers reap the rewards. From assessing an idea’s feasibility to unconventional user experience concepts, feedback helps the product team prioritize better. They can provide optimal solutions that encompass the ideas and solutions from both the engineering and design teams. The partnership often pays further dividends throughout the product development process as a closer and trusting relationship creates a more open and honest dialogue. Minor issues get raised and addressed before they become big problems when everyone feels like they’re on the same team. Watch our webinar below: 2. Be confident in your soft skills Product managers don’t necessarily need to be technical, but they need to work well with others. They have become adept at communicating with stakeholders, listening to customers, and developing empathy, which doesn’t come naturally. Developing your soft skills remains an essential product management tip. It’s essential to understand why these soft skills are imperative. Practicing and honing these things makes you a better product manager while simultaneously making your job easier. Listening skills Let’s start with listening. Addressing your customer’s problems requires a deep understanding of the issues they face. Though, it’s understandable that a lot of us dream about the prospect of reading our customers’ minds. Instead, you find out what really matters by talking to customers, asking them questions, and—most importantly—listening to what they have to say. The most successful product managers are active listeners who engage in follow-ups and have a general openness to customer feedback, which doesn’t come easily to everyone. Check your impulses, move into “receiving mode,” and take the feedback in with as open a mind as possible. Empathizing with customers allows you to feel their pain. By placing yourself in their shoes, you can evaluate and appropriately respond to their feedback. Communication skills Communication, of course, is a two-way street, so your listening skills should match your ability to convey information clearly. As a product manager, you need to understand their biases and assumptions when framing your message and deliver it via a method that will garner a response. Not everyone has the same communication style or prefers the same medium. The burden then falls upon you to tailor your communication based on the individual or group. The skills listed above merely scratch the surface when utilizing soft skills to improve your effectiveness and efficiency as a product manager. Serving as a product evangelist, facilitating stakeholder alignment, and leading prioritization exercises are a few other examples where these essential capabilities come into play. hbspt.cta.load(3434168, '83f51649-b6bd-42f2-9c45-d58c5fba5ca3', {"region":"na1"}); 3. Manage your own career A fatal flaw for any employee is to expect others to worry about their career development and progression. For this reason, we ranked “manage your own career” as one of our top product management tips. While managers and mentors may step up and take you under their wing, your boss may be solely focused on shipping products and keeping things under budget. Product professionals should always be mindful of their career path with no guarantee that anyone else will look out for their interests and invest in their future success. Successful product professionals build up their skills by getting the experiences they need to round out their resumes. Furthermore, they identify and pursue opportunities for growth and advancement. Product management professionals face additional challenges in advancing their careers because so much of what they do is behind the scenes. To bolster your image and get on the radar of hiring managers, use platforms such as all-hands meetings to promote yourself internally while participating in industry events to maximize networking opportunities and finding other chances to become a thought leader in your space. 4. Embrace visual roadmaps In the age of Agile, product managers don’t produce as many requirements documents. Our user stories reside in the tools of the product stack, and our insights get shared in standups and prioritization meetings. In turn, a scant “paper trail” of evidence of our hard work and an absence of documentation reviewed and referenced by stakeholders. Product roadmaps, however, remain the exception, and their importance has never been greater. Some product managers cram everything into their roadmaps since it’s the only documentation colleagues will see. Then again, the concept goes against the “less is more” rule of thumb, which guides everything product managers produce. Instead, leave out the details and allow visualroadmaps to be one of your essential product management tips. Themes tell the story, color-coding ties work items to desired outcomes and goals, and the focus remains on the items of strategic importance. And, when you use a purpose-built roadmapping tool such as LIKE.TG, you’ll spend less time creating and updating these visual roadmaps and be confident that stakeholders are always viewing an up-to-date version. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); 5. Don’t settle for a stale prioritization framework Figuring out what to build next and leave out is a key part of product management. To make it collaborative and incorporate multiple viewpoints and opinions, using prioritization frameworks for these exercises gets more folks involved and creates additional transparency to silence the naysayers. However, we live in the golden age of prioritization methods, so product teams shouldn’t stick with a framework that doesn’t truly fit their business. With dozens and dozens to choose from, each with its strengths and weaknesses, make sure you and your team are satisfied after using them. It can also help to shake things up now and then and try a new framework. Not only can it turn up some new insights, but it may also reinvigorate the entire prioritizing team by giving them something new. 6. Lead with IMPACT Our final top tip emphasizes prioritization differently. It’s a mindset universally applicable to every aspect of product management, from who you hire to what you work on to how you spend your time. Using a consistent lens, product teams can ensure they’re focused on what matters most by assessing how each potential item rates against these six fundamental aspects: I – Interesting: Does this address the things our customers care about? Can we tell a story of how we’re creating positive change for them? M – Meaningful: Are we moving the business forward toward measurably reaching its goals? Are we providing real value to our users? P – People: Who is impacted by this? Who uses it, who sees the benefits, and who pays for it? A – Actionable: Are we coming up with ideas that can be implemented and realized? Do we have the resources, budget, and expertise to execute? C – Clear: Do we truly understand what we’re trying to do? Can it be concisely articulated so even a child could understand? T – Testable: Can you try things out before committing? Are there ways to experiment and measure success on an ongoing basis? Keeping IMPACT top of mind helps everyone maximize the value they’re creating and keep their eyes on the prize. Download our free ebook to explore how to incorporate it into different facets of your work and career. Looking for more pointers on excelling in product management and other product management tips? Visit our Learning Centertoday.

As a Customer Success Manager at LIKE.TG for the past two years, I’ve worked with hundreds of our customers on establishing their roadmapping processes. Throughout my time with LIKE.TG, one of the most common roadblocks I see inhibiting a successful roadmap process is a lack of accountability on roadmap editors. 6 Ways to Create Roadmap Accountability with Your Team So, you’ve invested in a standardizable roadmapping tool for your team. That’s a great first start, but how do you ensure that they actually update their roadmaps? As you build out your roadmapping process with your team, the tips below will ensure roadmap accountability. 1. Establish a Champion of the process An essential part of creating accountability is establishing one or more persons as responsible for the outcome. This person can be an executive sponsor or a champion of the process appointed by the team. The champion must set expectations, goals, and guidelines for success with the Roadmapping Process. Setting expectations early on in the process is essential. However, without a champion to hold the team accountable, they will be ineffective. The champion can also continuously evaluate whether they’re meeting the goals of the roadmapping process. If so, then champions have fodder to provide the team with ongoing motivation. Whereas if the team is not meeting goals, having a champion to shepherd a change in the process is key. Build a Visual Product Roadmap ➜ hbspt.cta.load(3434168, 'a81908bd-d7dd-4be2-9d7e-cb09f3f90137', {}); With LIKE.TG, the champion of the account typically has admin rights to the account. It gives the user the ability to see each team member’s last activity as well as a list of roadmaps created by each member of the team. It’s an efficient way to verify editors are meeting expectations and following guidelines. The team’s champion also plays a critical role as the liaison between the software and the team. As a Customer Success Manager, I’ve worked with several teams that lacked a clear and established champion of the tool. These are the most common outcomes I see in response: users don’t end up using the tool in the first place, or they start using it but without direction and not following best practices—which causes frustration and ultimately leads to non-use, as well. More often than not, these accounts end up reverting to whatever the inefficient process was they were trying to move away from and end up back at square one. 2. Start with your “Why?” Realistically, not many people like being told to do something blindly. An essential step for getting any team invested in the roadmapping process is communicating the why behind it. Start at a high level; why does your team need to implement a new process? What challenges are you looking to solve for the team? Then move towards the specifics, why did you choose the tool you’re asking the team to use? If your team evaluated multiple tools, it could be valuable to share the criteria your team was looking for and how the tool you selected stacked up. Switching to a new tool or implementing a new process is always going to require some manual effort, understanding the why behind it is essential to motivate users to put in that effort. Understanding a team’s “why” is also critical for me to help, well, manage a Customer’s success. Every team has different goals they are trying to achieve with their Roadmapping process. Establishing those goals at the beginning of the process gives the team something to work towards and gives both you and your Customer Success Manager something to measure against. If I don’t know what your idea of success is, how can I help you get there, and if your team doesn’t have an idea of what success looks like, how do they know that the work they’re putting in is worth it? 3. Team-wide roadmap sharing One of the most important ways to ensure roadmapping success is to keep the process collaborative. One easy way to do this is to encourage users to share their roadmaps right away. Often a user’s gut reaction is to keep the product roadmap hidden until the final draft. While this might work for a static PowerPoint slide, a live roadmap will never be finalized. Roadmaps are continually evolving, sharing your roadmap from the start will give your audience context to its development. Knowing that your roadmap might be viewed at any time will help foster an environment where Editors update their roadmap on an ongoing basis rather than only before a big presentation. The importance of sharing roadmaps early on clicked with me while working with a group that was entirely new for roadmapping. I scheduled a call with all of the Editors of this group a few weeks after their first training to make sure there weren’t any lingering questions and hear how the roadmapping process was progressing. When we got on the call, my questions were met with an awkward silence because, as it turns out, no one had touched their roadmaps since our last call. When I asked why the users admitted they didn’t know when they were supposed to have their roadmaps ready, so they didn’t work on them. By sharing your roadmap at the beginning, there’s no concept of a roadmap deadline, so updates stay an ongoing habit. Luckily LIKE.TG and most roadmap software include a team-wide sharing functionality that grants roadmap access to your entire team as quickly as one click. As an easy way to ensure roadmaps are being shared throughout the roadmapping process, encourage users to share new roadmaps with the team upon creation. 4. Implement a cadence for roadmap presentation Setting up a recurring roadmap meeting or designating time in a pre-standing meeting for roadmap updates can be an effective way to give users a sense of urgency to update their roadmaps. In an ideal state, roadmap editors are regularly updating as work items progress or change. Unfortunately, though, this is not always the case. Devoting a recurring time to the roadmap presentation will create a baseline cadence for updating. Some of the larger companies I work with establish bi-weekly roadmap forums where the team can get together and go over their roadmaps, talk about what’s working and what isn’t, and discuss updates to the process. One champion mentioned to me that this was the key to establishing standardization in their roadmapping process because it allowed them to quickly identify users who weren’t following the guidelines as they presented their roadmaps. A built-in presentation mode makes pulling your roadmap up during a meeting easy. We recommend sharing your roadmap live during these meetings so that it remains interactive. With a live roadmap, you can present in differing granularity levels, dig deeper into any items you want more detail on, and adapt as necessary. 5. Utilize integrations Keeping editors motivated to update their roadmaps is an easy way to keep editors by making the process as simple as possible. One of the most valuable ways the roadmapping process can be simplified is through the use of integrations. Nobody wants to be doing redundant work, the goal of Roadmap integrations is to make getting information that has already been created elsewhere into your roadmap with ease as well as keep it updated with no manual effort. The more places a user has to update information, the more opportunities arise for something to fall out of date. Why not only worry about updating information once and have that carry over to your roadmap? For example, LIKE.TG integrates with several Project Management Softwares: Jira, Trello, Azure DevOps, and more. Use these integrations to import items directly into your roadmap, making it possible to build an entire roadmap within minutes. Syncing your roadmap automates the process of keeping your roadmap updated. It removes the burden of tedious updates from your editors, leaving them time to focus on the big picture of the roadmap. Integrating your roadmap simplifies the process for editors, but it also helps to establish your roadmap as a source of truth by creating less opportunity for error. 6. Regular account reviews with your Customer Success Manager Okay, I might be a bit biased on this one, but hear me out. It’s your Customer Success Manager liaison’s job to help your team establish and maintain a successful roadmapping process. The best way we can help your team maintain success is through account reviews. These are a way for us to touch base with the champions and perform a pulse check on the account. We’ll ask the team leads to gather feedback from both editors and roadmap viewers; this will tell us where the process is working and also help identify any areas for improvement. We’ll also take an in-depth look at the team’s usage with the champions. We’ll uncover what features to utilize or not and any patterns in team use. Together we’ll analyze the overall account health and compare the current process to the goals. While reviewing guidelines set at the beginning of on boarding, we’ll see where they are being met or falling short. It helps us develop the next steps for training, but it will also equip the champion with concrete usage metrics that they can bring back to the team to foster accountability. hbspt.cta.load(3434168, '3f36d63f-fe4f-400d-ab83-a64b28767625', {"region":"na1"}); Takeaways Getting your users to adopt a new roadmapping process isn’t as simple as buying a shiny new tool. However, with the proper structures in place, getting your team to update their Roadmaps doesn’t have to be like pulling teeth. Best of all, with LIKE.TG, you don’t have to do it alone because that’s what I’m here for. Ready to build your own roadmap? Get started with a free trial.