Mamuna Oyofo, MBA

My personal take is that when I am speaking with strong product candidates, I can see a few qualities shine through in their story. For me, those are: 1. They are constant Learners/curious They are constantly asking questions and actively listening. They are readers and constant consumers of information. To me, this shows that when they come on the team, they will bring fresh ideas forward. Ask the team questions that others may not consider and bring new information to the table. 2. They are persistent and don't stop at 'no' In this, they are contantly trying to understand constraints and find alternatives. They want to address a problem and flexibly driving towards a solution that will do it. They do not get discouraged when someone says no. Maybe they will flex their soft skills and coax a 'maybe' out of the person saying 'no'. 3. Understand how to balance the art and science Often times when we talk about product management, we talk about the science. Your frameworks, how you manage backlogs, understanding data and tracking metrics and all of those fun items. You'll find a lot of books on these topics because they are measurable and easier to write about. On the other hand, we often forget about the art. The way things get done. How you communicate, show empathy, tell a compelling story and inspire others. How you connect with your customers and their problems, lead individuals without authority. Normally when a PM fails, it's because not enough attention is paid to the art. 4. Focus on problems not solutions Often times when someone is describing a problem, you want to jump to a solution. Technically product management is helping to solve a customer problem... but to truly solve a problem, you must really fall in love with the problem. 5. Able to represent multiple POV They are able to advocate wearing different hats. So they can speak to engineer, executives, marketing, the customer, you name it. They can comfortably devils' advocate ideas and not settle for the first answer suggested. Often in the interview process, you are meeting with different stakeholders and really they are each approaching you with a different lens (or hat) to evaluate your ability to breakdown a problem.

Answered another question about hard skills. I don't think its generally necessary for PMs to read code but I do think it is important for you to understand the concept/principles. An overview would be very helpful in making you a good partner to your other more technical peers. It also helps when talking through any blockers or considerations to keep in mind.

I personally have been teaching at The Product School and have seen benefits/value from those coming out of the course. It is really going to come down to your own learning style however. You could also very much find free reading materials if you are unable to invest in taking courses at the moment. You can go on youtube and simply search 'product management' and consuming videos and talks. You could go on twitter and read through the numerous shared docs there. It really comes down to whether you personally need structure or can create your own structure.

The biggest mistake I will mention here is not getting stakeholder buy-in. A lot of times we make assumptions about what people want and do not take the time ahead of to understand needs. Speak to those needs and share any constraints. Work to bring alignment across stakeholders. In the end, stakeholders lose trust in the product manager because they do not feel seen or heard. It is important that pre-work is done ahead of time so that when roadmaps are being presented, nothing comes as a surprise.

The hard skills that come to mind for me are: 1. Technical - This is going to vary depending on the type of career you want to have and the company you want to work for. Generally, it is important for you to have an understanding of technical development principles and vocabulary. You want to be a strong partner to your peers and competitively, this will put you ahead of others. 2. Analytical - Data is an important part of the product management journey. Someone said "If you care about it, measure it" and its very true. Data is critical to helping you understand how to build your roadmap, see your threats and opportunities and competitive performance. You will want to feel verse in the tools that help you measure and what they are telling you. 3. Business skills - As a PM, you have to understand the product AND the business behind it. You need to speak to revenue and profit, budgeting, forecasting, etc. The ability to have these conversations with company leaders is critical. 4. Industry knowledge - When working on product, you need to understand the landscape in which you are competing. You are tracking key market trends for your project and constnatly reporting on that. 5. Strategic Thinking - You need to be able to make and anticipate paths based on your industry knowledge and business understanding. You'll have to consider company goals and determine what is the best way to get there. 6. Ruthless Prioritization + Decision Making - In product, you will always have too many options. You will have to pick a path and fairly quickly. You will need to understand what things get you to goal quickest. 

I am very much a systems thinker and like to understand the whole. I started my product career focusing on product management but quickly was exposed to the different facets of product management incl product design, engineering and product marketing. I wanted to do a bit of a deep dive in each of these areas so I could better understand how to use them in my craft. So I worked in those spaces, built out teams and best practices around how to do them well. Ultimately, I did that in service of making myself a stronger product/technology leader. I feel that as a product manager, you should be comfortable and aware with product marketing principles and be able to be a strong partner in the space. I'm not sure I ever really chose product management over product marketing. I just incorporated it into my product toolkit.

It's hard for me to think anyone is 'doomed' per se but I would make this a focus area if you are truly trying to get into product management. Making smart decisions quickly is a strong product management trait and so to be successful, you will need to be comforatble doing that. I would probably reverse the lens and ask yourself if you would be happy making smart decisions quickly everyday. Does that excite you? If so, then dive into why you can't or don't want to currently. If it is not exciting, consider what you like about product management and see if you can get that same joy in another role.

1. Understand what about product management is interesting to you 2. Research roles and opportunities that speak to what you find interesting 3. Identify the gaps in your skills or experience 4. Fill those gaps :) Take a course, read, volunteer to build something. 5. Network and build a group of people who can help advocate on your behalf when roles come up in their companies 6. Start the application process 7. Develop relationships with recruiters or hiring managers

There is definitely a fine line here. Every decision cannot be data driven and will likely be informed to some extent BUT part of the excitment of product management is leaning on that intuition. In some cases, you will have data to back up your assumptions and in others you will not. Every situation is going to be different and you'll have to become an educated risk taker. Leaning on previous experiences or patterns you've seen somewhere else.

It likely depends on the type of role you are entering into, the focus and phase of the product. It also will likely depend on whether the company has invested a lot in building out an existing UX team. I am biased because I have built out product design teams and therefore see true value in anyone who is working on product understanding experience fundamentals. If you have the best idea for a product but no one understands how to actually use it and get value, what use is the product to begin with. Instead of coming up with that great idea and then throwing it over the fence to you UX team, it would be better to approach your customer problem roundly and understand what you are hearing fully.