{"id":8323,"date":"2017-04-10T11:00:57","date_gmt":"2017-04-10T10:00:57","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=8323"},"modified":"2017-04-10T11:56:30","modified_gmt":"2017-04-10T10:56:30","slug":"product-manager-problem-manager","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/","title":{"rendered":"A Product Manager is a Problem Manager"},"content":{"rendered":"<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><em>In each entry in this \u201cconversation\u201d series I talk to a designer\/product manager\/engineer on a topic. I want to make basic practical skills education transparent and free.<\/em><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Today I am speaking to <a class=\"link link--blue fontWeight-4\"href=\"https:\/\/www.linkedin.com\/in\/raviakella\/\">Ravi Akella<\/a> who currently runs the product team at the Digital Manufacturing Group at <a class=\"link link--blue fontWeight-4\"href=\"http:\/\/www.autodesk.com\/\">Autodesk<\/a> and is on the PM Leadership Team at Autodesk. His team of product managers focus on engineering simulation technology - modeling, analyzing and visualizing real world phenomenon like response of machines and structures to loads, fluid flow, 3D printing of metals etc. He previously led the product management team for AutoCAD as well. For context, Autodesk is a 9000+ person B2B software company with millions of paying users.<\/p>\n<h2 class=\"pageWrap pageWrap--s marginTop-xl marginBottom-l c-black lineHeight-xl fontSize-xl fontWeight-5 breakPointM-lineHeight-xxl breakPointM-fontSize-xxl\" style=\"margin-left: auto; margin-right: auto;\">Your product is in a mature stage, how do you develop a product roadmap to enter a new industry?<\/h2>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">This depends on the product and where it lies in its product lifecycle because the primary goal of product management is to align development efforts with business goals. Let\u2019s take the example of a roadmap for a product that is widely used like AutoCAD to better serve a new industry while maintaining and iterating on the many industries it already serves.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">We look across the industries(or segments) where the product is currently used and we look through the inputs from stakeholders like customers, sales, support, etc. to understand which industries to prioritize to meet our business goals. We then focus on the target industry and do research to understand the problems and pain points in that industry and come up with personas\u200a\u2014\u200awhich are essentially groupings of real people having the problem we will solve for\u200a\u2014\u200aand the \u2018jobs to be done\u2019 which the goals that these people seek.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><span class=\"long-quote\">\"Once we have have a set of problems we try to group them into themes that are meaningful to the target personas. In some companies, these themes are called initiatives. Essentially you look across all the themes and then prioritize which ones to focus on to deliver the most value to the customers and business.\"<\/span><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Themes are then broken down into Epics which in turn are broken into user stories and ultimately tasks for the engineering team.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Example themes we have had in the past are \u201cCollaboration\u201d which meant improving how people share drawings while aligning with the processes and protocols within the target industry or \u201cContinuous Adoption\u201d which was about how to make it easier and less disruptive for customers to adopt the latest versions of the software.<\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"Look across all the themes and then prioritize which ones to focus on to deliver the most value.\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">So the steps to arrive at the roadmap for a new industry is:<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"style=\"text-align: center;\"><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Research \u2192 Industry -&gt; Personas -&gt; Problems \u2192 Themes \u2192<br \/>\nEpics \u2192 User stories \u2192 Tasks<\/strong><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">I have been on teams that have used tools like <a class=\"link link--blue fontWeight-4\"href=\"https:\/\/www.productplan.com\/\">ProductPlan<\/a> and <a class=\"link link--blue fontWeight-4\"href=\"http:\/\/www.aha.io\/\">Aha<\/a> to manage the inputs to a roadmap. Some of these tools are designed for smaller companies with less specialized roles but there is subset of capabilities that work well for PMs to do upfront product planning in larger organizations. Eventually, of course, most teams manage the Epics and User Stories in Jira that is used across functions by PMs, Design, Development and QA.<\/p>\n<h2 class=\"pageWrap pageWrap--s marginTop-xl marginBottom-l c-black lineHeight-xl fontSize-xl fontWeight-5 breakPointM-lineHeight-xxl breakPointM-fontSize-xxl\" style=\"margin-left: auto; margin-right: auto;\">What are the key inputs for your roadmap?<\/h2>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Most products that I have managed at Autodesk are mature and have hundreds of thousands or millions of users. This means the inputs to the Product Managers come from number of sources like:<\/p>\n<ul class=\"pageWrap pageWrap--s list list--unordered marginBottom-l lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">\n<li>The Sales and Technical Sales teams<\/li>\n<li>The Customer Support teams<\/li>\n<li>Directly from customers: through proactive or reactive conversations, interactions at events, forums (other online channels) where we capture their feedback.<\/li>\n<li>Through customers reported issues (via the Support channels)<\/li>\n<li>Feedback from beta users: We run a lot of betas and get feedback from our customers on pre-release software<\/li>\n<li>From our executives:\u200aThey usually have inputs from their own interactions with customers<\/li>\n<li>Company-wide mandates: These are highly weighted and an example can be a common component (like new licensing) that needs to standard across the entire portfolio. This kind of work just need to get done and is justified because of the value generated to the company through standardization and usually supported by senior stakeholders.<\/li>\n<\/ul>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><span class=\"long-quote\">\"Regardless of the source of the input, the PM has to boil it down to the problem that needs to be solved and the personas that benefit from the solution. Apart from the inbound channels PMs also have to go looking for problems in the data generated by their products. Good PMs are always proactively looking for problems. And, make sure you make time for that and talk to customers directly.\"<\/span><\/p>\n<h2 class=\"pageWrap pageWrap--s marginTop-xl marginBottom-l c-black lineHeight-xl fontSize-xl fontWeight-5 breakPointM-lineHeight-xxl breakPointM-fontSize-xxl\" style=\"margin-left: auto; margin-right: auto;\">What are the different types of personas?<\/h2>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"For B2B products, the personas are not always straightforward and there isn\u2019t just one persona.\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">It boils down to remembering whose problem you are trying to solve and value delivered by solving that problem.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">The personas we keep in mind are:<\/strong><\/p>\n<ol class=\"pageWrap pageWrap--s list list--ordered marginBottom-l lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">User personas:<\/strong> These are the users that are ultimately using the product. In complicated workflows there are many different user personas involved<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Buyer personas:<\/strong> These are the people who are buying the product. In B2B it\u2019s different, the person who\u2019s using the product might not be making the buying decision<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Internal personas:<\/strong> An example of this can be your internal development team when you make investments to make it easier for them to release new code or reduce technical debt<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Sales team personas:<\/strong> This one is unusual but sometimes you need to solve problems for people who sell your product. For example, if you need to development work to consolidate the product offerings, improve cross-product interoperability and make it easier for sales to credibly sell it\u200a\u2014\u200amaybe consolidating many different individually priced modules into 3 tiers etc.<\/li>\n<\/ol>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><span class=\"long-quote\">\"The key thing to watch out for, especially in the landscape of B2B software, is the priority that is put on the buyer persona. Prioritizing the buyer persona too much and not focusing on the user personas runs the risk of making the product hard to use, which is usually why some B2B products are so hard to use.\"<\/span><\/p>\n<h2 class=\"pageWrap pageWrap--s marginTop-xl marginBottom-l c-black lineHeight-xl fontSize-xl fontWeight-5 breakPointM-lineHeight-xxl breakPointM-fontSize-xxl\" style=\"margin-left: auto; margin-right: auto;\">What is your prioritization framework?<\/h2>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">We do our prioritization in two steps. I have arrived at this model after years of tinkering and I am sure there are still many ways to improve it; I am always looking for feedback from my team of Product Managers to enhance it.<\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"It is key to do the problem prioritization first and then prioritize the solutions\/feature ideas.\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Once you have the problem for the personas in the target industry, list them out and score them on the following attributes (on a scale of 10 or similar):<\/p>\n<ul class=\"pageWrap pageWrap--s list list--unordered marginBottom-l lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Severity (how big is the pain)<\/strong>\u200a\u2014\u200aProblem severity is about customer pain and you have to know the persona intimately to assess it.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Pervasiveness (the frequency)<\/strong>\u200a\u2014\u200aFor pervasiveness you have to know the common trends in the target industry or market segment.<\/li>\n<\/ul>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Ideally, the PMs have a continuous flow of problems that they are logging into ProductPlan (or whichever tool) from all their input channels. The PM\u2019s job is to look at them as often as possible and get as much data as possible to score the problems for prioritization. In my current team there are regular touch points with Sales and other stakeholders that give PMs the information needed to score the problems.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Once the problems are prioritized then we get our peers involved\u200a\u2014\u200adesign and engineering\u200a\u2014\u200aand come up with solutions for each problem. This does not need to be a complicated or time consuming exercise just a quick conversation to think through options because each problem can have multiple solutions.<br \/>\nEach solution\/feature idea can then be scored on the following parameters (on whichever scale makes sense\u200a\u2014\u200awe currently use a 1 to 5 scale):<\/p>\n<ul class=\"pageWrap pageWrap--s list list--unordered marginBottom-l lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Differentiation:<\/strong>\u200aThis is how differentiated and unique our solution is compared to the competition. The PM has to do some research on competitive solutions to score this.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Barriers to adoption:<\/strong> This is about being aware of potential barriers to adoption for the solution- the lower the score on this one, the better. For example if the solution requires customers to take special training or buy new hardware or change entrenched processes, there will be significant barriers to adoption\u200a\u2014\u200ayou have know the customers\u2019 environment and processes to think through this one.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Cost:<\/strong> This is the engineering effort required\u200a\u2014\u200athe lower, the better. Keep in mind there is always margin of error here since these are based on quick conversation and not detailed estimation.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Risk:<\/strong> This is how risky the solution is\u200a\u2014\u200athe lower, the better\u200a\u2014\u200awhat are the dependencies that can go wrong? One type of risk is skills risk\u200a\u2014\u200aif engineering is using novel technologies or components that have never been used or implemented before.<\/li>\n<\/ul>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">We use a simple formula\u200a\u2014\u200aa weighted sum of all the positive parameters (severity, pervasiveness, differentiation) minus a weighted sum of the negative parameters (barriers to adoption, cost, risk) to come up with cumulative score for each solution. When teams first adopt this process, they iterate on the weights a few times.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Based on the scoring, you will have a prioritized list with rough estimates of engineering effort. If you can translate that rough estimate into story points and you know what your velocity is (how many points you can hit in a typical sprint) and the number of sprints you have in a release cycle, you come up with what you can credibly deliver in a particular release.<\/strong><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><span class=\"long-quote\">\"One mistake that I have made before and I see PMs often make is they start prioritizing solutions or feature ideas without thinking about the core problem and alternative solutions. A problem can have many different solutions and it\u2019s important to know and communicate to your peers which problem you are tackling. The product manager is essentially the problem manager.\"<\/span><\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"The product manager is essentially the problem manager\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Envisioning solutions is a cross-functional activity. You have to talk to design and engineering before prioritizing them\u200a\u2014\u200aif you don\u2019t talk to others you might just be guessing about what\u2019s possible. Also, bringing in your peers and discussing the problems builds greater trust and commitment in your teams.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">This is why Agile development makes sense. You will always have a margin of error when you are trying to figure out the market, the personas and the priority of their problems. Your judgement is based on the data you have and the time you have to gather that data\u200a\u2014\u200athere is always an error and it\u2019s gets worse when the Product Manager is stretched for time and resorts to guessing. The same is true for engineering estimates, even with the best, most experienced teams, there is always a margin of error.<\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"Envisioning solutions is a cross-functional activity.\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Agile development breaks the work into small enough chunks so you can show it to actual customers and get user and market feedback early. We have betas where the customers are using pre-release code that is released much more frequently than the usual release cycles so teams can learn from the feedback and course-correct.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><span class=\"long-quote\">\"I always remind myself and tell PMs that it is possible to survive a hundred paper cuts but we might not survive a big flesh wound. We are probably always messing up to a certain degree so we should have a process that reduces the business risk of these mistakes and makes them smaller, easier to mitigate. Ultimately, Agile development is about resilience and reducing the wasted effort caused by errors in the planning phases\u200a\u2014\u200ahaving the humility to check your perceptions with real customers on an ongoing basis.\"<\/span><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">The way you prioritize also depends on the phase of the business you are in. If you are in the growth phase then problems and solutions that drive new customer acquisition take a bigger priority (with the assumption you will be able to do the work needed to retain the new customers in time), if you have scaled the business and captured significant market share then retention and reducing churn becomes key.<\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"Have the humility to check your perceptions with real customers on an ongoing basis.\"<\/p><\/span><\/blockquote>\n<h2 class=\"pageWrap pageWrap--s marginTop-xl marginBottom-l c-black lineHeight-xl fontSize-xl fontWeight-5 breakPointM-lineHeight-xxl breakPointM-fontSize-xxl\" style=\"margin-left: auto; margin-right: auto;\">How do you manage stakeholder requests?<\/h2>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">If someone asks for a feature or a solution (let\u2019s build \u2018X\u2019 button) then it is important to use an open-ended discovery method like asking 5 why\u2019s to get to the underlying problem\u200a\u2014\u200awhy do you need this button etc. One needs to be careful so that the requester knows that you are not stonewalling them\u200a\u2014\u200ayou need to have a trusted relationship with them so that they know you are just trying to get at the real problem. <strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">As a PM, if you can\u2019t articulate the problem you are solving then you are not doing your job. <\/strong>That\u2019s the only way you can convince everyone you work with\u200a\u2014\u200adesign and engineering need to clearly understand the problem and it\u2019s priority and they will look to you for that.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Identifying the underlying problem isn\u2019t always straightforward.<\/strong><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Sometimes customers might be asking for something that may have nothing to do with the real problem\u200a\u2014\u200atheir context might be set based on the current product and how a solution is currently implemented. A simple example from my past was when some users of AutoCAD wanted some buttons in the UI to have text labels instead of icons. The issue was not that they preferred text in general, the issue is that the current icons weren\u2019t big enough\/explanatory enough\/ conspicuous enough for users to build muscle memory with them. You can either say yes I\u2019ll build a toggle to show the text or you can dig deeper into the problem along with your peers from design.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Over the years, I have realized that product managers should be good at doing three things under pressure:<\/p>\n<ol class=\"pageWrap pageWrap--s list list--ordered marginBottom-l lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Be optimistic:<\/strong> Paint the picture of a positive future for customers and the business they serve in a confident and trustworthy way.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Have a nose for trouble:<\/strong> Believe that anything that can possibly go wrong will go wrong until there is credible feedback from real customers that the problem has been solved.<\/li>\n<li><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Capture moral high-ground:<\/strong> In the throes of a project you must be ready to do whatever needs to get done to help your team deliver.<\/li>\n<\/ol>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Part of all this is to listen very well and be humble. If a stakeholder is disappointed, find the conflict early, address it directly and resolve it as soon as possible. Everyone changes their mind, the potential for conflict is constant but you can have constructive conflict in a respectful environment.<\/p>\n<blockquote class=\"pageWrap pageWrap--s position-relative marginTopBottom-l breakPointM-marginTopBottom-xl\"><div class=\"blog-quote-before position-absolute bg-marvel\"><\/div><div class=\"tweet-quote blog-quote-after position-absolute bg-marvel cursor-pointer transitionDuration-l transitionProperty-all transitionTimingFunction-cv-easeOutCircular scaleUp--hover zi-weak\"><svg class=\"fill-white opacity-0 pointerEvents-none position-absolute pinCenter transitionProperty-all transitionTimingFunction-easeInOut\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"20\" viewBox=\"0 0 24 20\"><path d=\"M24,2.37a9.64,9.64,0,0,1-2.83.79A5,5,0,0,0,23.34.37a9.72,9.72,0,0,1-3.13,1.23A4.86,4.86,0,0,0,16.62,0a5,5,0,0,0-4.8,6.2A13.87,13.87,0,0,1,1.67.92,5.13,5.13,0,0,0,3.19,7.67,4.81,4.81,0,0,1,1,7a5,5,0,0,0,3.95,5,4.82,4.82,0,0,1-2.22.09,4.94,4.94,0,0,0,4.6,3.51A9.72,9.72,0,0,1,0,17.73,13.69,13.69,0,0,0,7.55,20c9.14,0,14.31-7.92,14-15A10.17,10.17,0,0,0,24,2.37Z\"\/><\/svg><\/div><p class=\"blog-quote position-relative textAlign-center c-marvel\"><span class=\"blog-quote-text transitionDuration-l transitionProperty-all transitionTimingFunction-easeInOut\">\"The potential for conflict is constant but you can have constructive conflict in a respectful environment.\"<\/p><\/span><\/blockquote>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Misalignments and miscommunication happen all the time\u200a\u2014\u200athe key is to calmly work through them without getting defensive. At the same time, you cannot do decision making about product by consensus. Someone somewhere is always slightly mad at you\u200a\u2014\u200ayou have to open and aware but know that this is a normal state of affairs\u200a\u2014\u200ait might actually mean you\u2019re doing a good job.<\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><em><strong class=\"c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl\">Additional Resources:<\/strong><\/em><br \/>\nDefinition of a problem template from Marty Cagan<br \/>\n<a class=\"link link--blue fontWeight-4\"href=\"http:\/\/svpg.com\/assessing-product-opportunities\/\">Assessing Product Opportunities | Silicon Valley Product Group<\/a><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><em>Photo credit: Andrew Welch<\/em><\/p>\n<p class=\"pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl\"><em>This article was originally published on <a class=\"link link--blue fontWeight-4\"href=\"https:\/\/medium.com\/flowcap\/https-medium-com-flowcap-a-product-manager-is-a-problem-manager-7c1a6b8ff1ff\">Romy's Medium page<\/a>. <\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In each entry in this \u201cconversation\u201d series I talk to a designer\/product manager\/engineer on a topic. I want to make basic practical skills education transparent and free. Today I am speaking to Ravi Akella who currently runs the product team at the Digital Manufacturing Group at Autodesk and is on the PM Leadership Team at Autodesk. His team of product&#8230; <a class=\"link link--blue fontWeight-4\" href=\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/\">Read More &#65515;<\/a><\/p>\n","protected":false},"author":118,"featured_media":8328,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-8323","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-viewpoint"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v15.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A Product Manager is a Problem Manager | Marvel Blog\" \/>\n<meta property=\"og:description\" content=\"In each entry in this \u201cconversation\u201d series I talk to a designer\/product manager\/engineer on a topic. I want to make basic practical skills education transparent and free. Today I am speaking to Ravi Akella who currently runs the product team at the Digital Manufacturing Group at Autodesk and is on the PM Leadership Team at Autodesk. His team of product... Read More &#65515;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/\" \/>\n<meta property=\"og:site_name\" content=\"Marvel Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/marvelapp\" \/>\n<meta property=\"article:published_time\" content=\"2017-04-10T10:00:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-04-10T10:56:30+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/marvelapp.com\/wp-content\/uploads\/2017\/04\/product-man.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"2000\" \/>\n\t<meta property=\"og:image:height\" content=\"1125\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@marvelapp\" \/>\n<meta name=\"twitter:site\" content=\"@marvelapp\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"10 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/marvelapp.com\/blog\/#organization\",\"name\":\"Marvel\",\"url\":\"https:\/\/marvelapp.com\/blog\/\",\"sameAs\":[\"https:\/\/www.facebook.com\/marvelapp\",\"https:\/\/www.instagram.com\/marvelapp\/\",\"https:\/\/www.linkedin.com\/company\/marvel-app\/\",\"https:\/\/twitter.com\/marvelapp\"],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/marvelapp.com\/blog\/#logo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/marvelapp.com\/wp-content\/uploads\/2018\/06\/Logo-Light.png\",\"width\":1605,\"height\":1130,\"caption\":\"Marvel\"},\"image\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/marvelapp.com\/blog\/#website\",\"url\":\"https:\/\/marvelapp.com\/blog\/\",\"name\":\"Marvel Blog\",\"description\":\"Ideas and words on user experience, design, collaboration and more\",\"publisher\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/marvelapp.com\/blog\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/marvelapp.com\/wp-content\/uploads\/2017\/04\/product-man.jpeg\",\"width\":2000,\"height\":1125},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#webpage\",\"url\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/\",\"name\":\"A Product Manager is a Problem Manager | Marvel Blog\",\"isPartOf\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#primaryimage\"},\"datePublished\":\"2017-04-10T10:00:57+00:00\",\"dateModified\":\"2017-04-10T10:56:30+00:00\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/\"]}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#webpage\"},\"author\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/#\/schema\/person\/603057c82b613e78a82d695432069e3f\"},\"headline\":\"A Product Manager is a Problem Manager\",\"datePublished\":\"2017-04-10T10:00:57+00:00\",\"dateModified\":\"2017-04-10T10:56:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#webpage\"},\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#primaryimage\"},\"articleSection\":\"Viewpoint\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/marvelapp.com\/blog\/product-manager-problem-manager\/#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/marvelapp.com\/blog\/#\/schema\/person\/603057c82b613e78a82d695432069e3f\",\"name\":\"Romy Misra\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/marvelapp.com\/blog\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/304ebef18215fec17854427d9438cd9675bfd30bd604ce622026cc62c8750af0?s=96&d=mm&r=g\",\"caption\":\"Romy Misra\"},\"description\":\"Romy is the founder of Flowcap, where she publishes content on product management, design and data with the aim of making real skills transparent and free. Previously Senior Director of Product at Visually. Has also taught at General Assembly.\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","_links":{"self":[{"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/posts\/8323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/users\/118"}],"replies":[{"embeddable":true,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/comments?post=8323"}],"version-history":[{"count":0,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/posts\/8323\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/media\/8328"}],"wp:attachment":[{"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/media?parent=8323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/categories?post=8323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/marvelapp.com\/blog\/wp-json\/wp\/v2\/tags?post=8323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}