6 Things to do as a new Product Manager
Settling into a new job can be quite the trip. You have a lot of things to learn about and even more changes to adapt to. Like all other job roles out there, product management is no different and, if you are new to the product management field as I am, then there is a lot more at play.
Initially, it might be tricky to know what’s expected of you and know how best to apply yourself. However, just like everything in life, there is always light at the end of the tunnel (let us agree to disagree). The trick is for you to identify how you can push through the challenges you face and become the best product manager in the end (or whatever your endgame is).
Being a product manager has been very insightful thus far. Learning new things (which I love dearly) is the dish of the day, every day. But of course, I have different challenges and, the one question on my mind is how do I push through and achieve my endgame result— to become a badass Product Manager?
The answer — Is identifying at the high level the things that make a good product manager (or at least a good-new-to-the-field product manager) and working towards achieving those things at the low level.
Based on my short time as a PM, I think I know what some of those things are. Of course, it may not be perfect but, these attributes and principles I apply have helped me and, I want to share them with you. So let’s begin.
Set clear goals and targets: Starting, you want to identify the things you want to achieve and how you intend on doing this. This was pretty tricky for me at first since this was the first I had even heard the term Product Manager. However, as I began to understand the expectations from my superiors, I made it a point to set out these goals. Some of which include never carry over a task, ensure your product delivery deadline etc. Once you can identify your metrics and know what is expected of you, be sure to set realistic, achievable and ambitious goals and targets.
Be ready to learn: If you’re new in any workplace in general, I think this is a given. The company I work for serves a niche market and, so many of the terms and ideas that get thrown around are very foreign to me. To give background, I work for a LaaS (Lending-as-a-Service) firm based in Lagos, Nigeria. We create mobile and web platforms for parties interested in digitalising their lending business (I think you can guess how niche that is). To keep up with how fast things were moving, I had to (and still) do a lot of reading. You can only go so far with what you know (or think you know) and a very healthy habit to cultivate is to constantly be in the know and work on your technical knowledge as a PM. If you’re not the reading type (lowkey judging you), YouTube has a lot to offer and will definitely give you answers.
Never be afraid to ask dumb questions: This point kind of bats off a medium article I read when I just started as a PM. The writer, Kevin Capel writes “I’ve all too commonly seen new product managers take the path of “going with the flow,” especially as not to seem “dumb,” behind, or ineffective when it comes to product decisions. Nodding and saying “yes” to executives is all too easy to do given the pressure to perform. Resist this notion to the best of your ability without sacrificing cooperation and positive energy. Instead, ask all the “dumb” questions…”. With this in mind, I was (and still am) able to grasp the work expected of me and solve them in time because I did not waste time trying to be a know-it-all. I also try and avoid, where I can, simply swallowing and regurgitating the information given to me. I try as much as possible to break them down, understand and, if need be, ask all the dumb questions. However, applying this principle has its challenges. Sometimes I feel it may become a bit overbearing to my superiors or maybe that’s all in my head.
Know your strengths and play on them: I had the opportunity to attend a webinar hosted by ProductDive. The speaker, Linda Zhaang, spoke on this point. She had mentioned how she used her data analysis skills to assess an issue and use the data to solve the problem. Applying this to myself, amongst my many talents (this may or may not be true), my ability to pay attention to details is one of particular importance to me. I can look past the bigger picture and pick on its components. Now, the trick was to turn this unrefined skill into something meaningful and apply it to my job. Even though I can spot an error miles away, the way I approached it and attempted to solve it is also of great value. I am still learning how to make this skill (and others) very valuable to me in my workplace. So far, I have been able to do some good with it and was commended for my efforts.
Be friendly: This point is partly drawn from the previously mentioned medium article. In the article, Kevin Capel talks about finding a good designer ally. While I agree with this, I also feel this point goes beyond just designers and should extend to developers and fellow PMs. This doesn’t mean one must become a “kiss-ass” but rather develop a relationship with various team members and allow them to open up to you. Create an environment where you both can talk about your strengths and weaknesses freely and in due time, approaching them for help or assistance will be 100 times easier. However, you want to do this cautiously and keep it professional. You don’t want to downplay yourself, as this may allow people to take you for granted.
Be proactive and take initiative: To succeed as a PM, I believe being proactive is vital. Everyone wants a problem solver and forward thinker. They want someone who knows what they’re meant to do and does it in time. To achieve this, one must have confidence in their knowledge of the product(s) they are managing. This may be where I struggle. I am sometimes held back because I feel what I know is limited and not enough. However, I am working towards this. The best way to overcome not knowing is to know and, the best way to know is to learn. Taking us back to my first point, be ready to learn.
Wholistically, the image of the anatomy of a Product Manager attached with this post truly sums up what you need (as an individual) to become a good product manager and I must add, what’s a better way to encapsulate the essence of a Product Manager than the Vitruvian Man?
Finally, let me say this. All I have mentioned are based on my personal experience. Feel free to challenge me and add more to the list. I definitely don’t know it all, after all, I’ve only been a Product Manager for just 2.5 months.
