Product Manager without a tech background: What are the challenges we face?
What are the first challenges that a non-technical product manager face when is starting their career? How to be prepared to face it?
Nowadays, where technology is transforming every industry; where we need it to evolve and keep the business alive. It is more frequently that non-technical junior product managers ask themselves if they need to study technology to grow in their careers.
What does it mean to have tech study to be a great product manager? It will depend on the product you are building.
In the digital era, tech backgrounds are highly demanding in the market, so it is essential to understand the tech world, but it doesn’t mean you need to code. When I started my product profession, I don’t know anything about software, technology, or software design. I have a degree in Tourism Business Management and work as a junior product manager in an online travel agency.
Here I share some challenges I faced when I started my career in digital products. I feel that many other non-technical PMs passed through that challenges. These are the four challenges and some advice.
1. Learn about the software development process
Understanding the tech world doesn’t mean starting to code. Instead, it is building a common language between the technicals and the rest of the areas.
Start by learning the software development process and different methodologies like agile, kanban, scrum, etc. In the role of product manager, it is essential to understand how to manage a digital product rather than to define the technology to use. (Let who knows it decides it)
2. Find your tech ally
It is not an easy search; we need someone who likes to explain how the software works, the diagrams, and has a lot of patience.
However, it is the best way to learn about the product you are developing and to have the whole picture. This ally helps you answer all the questions you have about how the product works and gives you some topics to learn more in-depth. Finding this ally is the best thing that can happen.
3. Gain the confidence and respect of your technical team.
As in any team, you need to build confidence. I encourage you to participate as a listener in some technical meetings. It is an excellent way to get acquainted with vocabulary and understand how your product/ program works. That will help you when some part of the product doesn’t work as expected. You will be able to give detailed issues to the team and protect them from bugs that aren’t bugs. If you do this well, you will quickly gain the confidence of your team.
On the other hand, it is a must to participate in definition meetings; it is vital to bring the user voice and business objectives to the table and get the right solution.
4. Value your knowledge and share it
In some cases, non-technological persons tend not to value their knowledge enough when they work in development teams. Empower yourself and share your experience and expertise. Teams will be enriched, acquiring different perspectives that will encourage them to take risks and make decisions. I am sure you have a lot to share and teach your team about management, customers, business, or other fields.
Always be respectful, open, kind, and humble.
Thank you to read it.
If you found this article useful and it can be useful to others, share it :)
