What are the best ways for Product Managers to develop technical skills?

The best way for Product Managers to develop technical skills is by taking online courses, attending coding bootcamps, reading technical literature, participating in workshops, and shadowing engineering teams. Building side projects, learning about APIs, and staying updated with industry trends also contribute. Collaborating with engineers, utilizing development tools, and attending conferences further enhance technical proficiency.

For me what has been most effective is to consume system design mock interviews. Some of the resources I am following is tryexponent & PM school youtube channel. The system design interviews helps to understand the technical skills in a story format. In a single interview as a PM one can learn about cloud, networking, etc.

The cornerstone was undoubtedly computer science fundamentals, and only then coding basics. Courses like Harvard's CS50 are a game-changer that laid the foundation of my tech knowledge. But the learning continued. Conversations with the CTO helped demystify complex architectures, offering invaluable insights. Plus, participating in technical interviews alongside the CTO has been eye-opening. It not only broadens my understanding of the technical mindset but also highlights the essential skills we, as Product Managers, should acquire. Keep learning, keep growing! 🚀

One thing I've found helpful is to break the problem into "structured thinking" + "coding language semantics". At a minimum, a product manager needs to be able to think about and discuss the solution in terms of "a series of steps", "loops that execute repeatedly", "if/else logical constructs" etc. This is what I mean by "structured thinking" and that's 80% of what a product manager needs to succeed. Once you've mastered this, you can take the leap into building the muscle on the "coding language semantics". The best way to do this is to take online courses, read getting started books, attending technical discussions for your product and getting an awesome tech mentor.

Product managers from none tech backgrounds need to invest some time to bulk up their tech skills by: 1. Picking a programming language to play around with 2. Take some classes on the cloud 3. Play around with API’s on postman and learn to read api docs The above three will give you a solid foundation then just keep an eye on latest tech trends.

My response is specifically for a Product Manager and not a Technical PM or a Program Manager. A Product Manager should know the broad technical knitty grittties just to keep the product aligned with the industry evolution and ahead of the competition. It's important to understand the technical architecture and other aspects, but the understanding should be limited to just knowing how everything stitches together so that the Product Manager can chime in on topics such as costing, resourcing, etc. Apart from this, a PM should primarily focus on the 'What' aspect and let the Enginnering counterpart focus on the 'How'!

System Designing is the best way in my opinion because it gives the right balance between overall system components and integrations. Another important element is that I choose the level or depth that I want to dig in considering my purpose. This helps me to focus on end-goal without getting lost in technical ocean.

Technology holds a key importance on all roles we are in , whether into Product , Program, Technology or Sales. Understanding the technical landscape is not big a challenge, provided there is an intent and commitment to get the concepts clear. For product managers from an engineering background , this understanding is easier basis the courses they have pursued during their education. For rest of the folks , consider it to be like solving analytical problems. Just following the basic principles of Should make it easy. 1. understanding of the problem statement , 2. What the tools used [Basic jargons like programing language, Databases, Cloud etc shall help], 3. how will the architecture solve the problem Just Keep the Learning Hat on!

While diving deep into the architecture is paramount, let's not forget the ever-evolving world of cloud fundamentals. In today's landscape, cloud platforms are revolutionizing the way products are built, scaled, and maintained. And here's my two cents: while it's tempting to become an expert in one cloud platform, it's invaluable to diversify your knowledge across the big 3 - AWS, Azure, and Google Cloud. Why? Because each platform brings its unique strengths, features, and capabilities. By having a holistic understanding of all three, you're not just broadening your horizon but also equipping yourself to make more informed decisions as a product manager.

As product managers, we need to stay updated on the latest trends and technologies. With AI becoming increasingly robust/efficient, it's essential for us to learn it and use the knowledge to empower our products with artificial intelligence enabled features.

The best Product Managers strive to solve "problems they want to fall in love with". These problems could be due to unmet customer needs, societal impact, or a personal passion. With mindset and passion, you'll be well-primed to delve into innovations with greater specificity and willingness to go just beyond your grasp to learn and recommend the technical underpinnings and opportunities/challenges related to innovation.

Product managers need to be aware of latest tech advancements to plan product strategy. e.g. someone not exploring OpenAI might miss on possible product improvements possible owing to this technology. To keep oneself up to date with technology, one can: 1. Follow blogs, podcasts, YouTube channels, websites talking about latest technology trends 2. Invest time to understand a technology if there is a possible play in your product 3. Attend webinars and industry events 4. Use trial period of free tools or services to experiment with your product 5. Keep a close eye on competitors if they are interested in a certain technology

Reading daily about the latest trends and innovations that have an impact in your products and services is essential to sustain the competitive advantage of your products. Also, deeply understanding vertical-specific trends helps you connect the dots to ensure that your product is not just following the market trends but also being able to disrupt it.

Joining tech related communities can be a good start especially if you are new to a particular technology. There is nothing better for knowledge building than a community of like minded people yo help you. Newsletters and subscriptions can be the best way to keep up with the trend if you are a seasoned professional with some level of tech understanding.

Having a mentor sitting across the table to help you is the biggest luxury any learner can have. It is better to find someone from within your team or office to mentor you rather than online. It will help you make sure that mentor's time is well utilized whenever they are available to train you.

Community events and engagements is another effective way of seeking and finding authentic mentors. Discover active communities that are open and inclusive where you can attend events, engage and exchange value. When you find people who are authentic and willing to share knowledge, establish a healthy rapport and start expressing genuine interest in knowing things. Be respectful of their time and always stress on asking practical questions.

One of the ways that worked for me and works always is: to build an actual product using Microservices. This will give me an understanding of learning hands-on so that I remember for a long-time. And, while I research through my idea, I learn new things how Microservices can be developed.

Seeking feedback and mentorship is a valuable step in enhancing technical skills. A mentor provides guidance and challenges for growth. Look for mentors within your team, company, or network. Request feedback from technical colleagues and learn from their insights. Also, be open to offering mentorship to others. This fosters skill improvement, builds trust, and expands your network.

Participate in Code and Design Reviews Another practical way to deepen your understanding and receive feedback is by attending or participating in code and design reviews within your team. While you might not understand every detail, being present can give you insights into the team's thought processes and decision-making. It also offers an opportunity for you to ask questions, providing you with a clearer understanding and allowing the technical team to see things from a product perspective. Over time, these interactions will bridge the gap between the technical and product domains, leading to more informed decisions and better products.

As a product manager, here is the BEST way to develop your technical skills: Participate in a hackathon. A hackathon is a weekend event where you work in a team of 1-4 people to develop an impact solution to one of the given "tracks" at the hackathon. In your day-to-day as a product manager, you will likely need to communicate with engineers and other technical folks. To develop your technical acumen, learn the basics of HTML, CSS, and JavaScript, then use that knowledge to build your own product in a hackathon. In a hackathon, you can: 1. Design the wireframes and a prototype using Figma. 2. Code the structure of your web app using HTML. 3. Style the web app using CSS. 4. Make your web app functional using JavaScript.

Apply your technical skills to build YOUR OWN PRODUCT: The best way to learn any skill is to do the skill, the old fake it till you make it. You won't even fully understand the struggles of being a developer without dipping your toes into their realm. So my suggestion is to build your own product, that dream idea you have been sitting on for years, just build it! Even if you don't get to the finish line the skills you have picked up along the way will be invaluable.

Maximising your technical skills in product work is a game-changer. Elevate your product strategy, shaping it with your technical acumen. Define requirements, user stories, and acceptance criteria. Collaborate effectively with your technical team and stakeholders, ensuring a seamless workflow. Employ your skills for rigorous testing, successful product launches, and continuous iteration. Don't forget to measure, analyse, and optimise product performance and outcomes. This holistic approach empowers you to craft exceptional products, deliver exceptional value, and make a significant impact in your role.

The best way to develop technical skills is by using them. Apply your coding and architectural knowledge to real product scenarios. Work closely with engineers, understand their challenges, and contribute to more informed product decisions. for me "Developing technical skills as a Product Manager is a journey. Start small, gradually build your expertise, and maintain a proactive approach to learning and growth."

By actively applying your technical skills, you not only enhance your product's quality but also foster a stronger partnership with your engineering and technical teams. When you speak their language and understand their challenges, it breaks down silos. This mutual understanding facilitates smoother discussions, quicker problem resolutions, and often leads to innovative solutions that might not have been realized in a more segmented team environment. So, the more you integrate and apply your technical skills, the more synergized and efficient your product development process becomes.

Start with "why" you want to develop technical skills to help determine what technical skills and how you go about it. For me - "the why" is about developing knowledge that helps maximise my contribution to a mission of empowering financial services users through digital experiences. In practice, this may help with non-functional requirements, architectural considerations for scale & stability, or technical client discussions . Hence "what skills?" has always been about understanding the technology that underpins these digital experiences - enabling me to understand the role of infrastructure components, their interplay, benefits and risks. And in terms of my approach? Be curious and start by asking the technical experts in your team.

There is difference between technical project management and product management. I have learnt and experimented with various state of the art coding languages and platforms. But what has worked most for me was beyond reading, try out the tools yourself and become your product's best customer. In other words, how often you yourself use the application that your team built? Once you use it, what kind of technical questions come to your mind of how the experience you saw could be driven by how the system has been built? Once you have curiosity driven questions, ask from engineers & technical team members around you if your assumptions were accurate. This is reverse engineer approach of building technical adeptness for practical use cases.

For me, before doing anything, a product manager should evaluate her background, characteristics, and objectives. Naturally, gathering technical skills can simplify her work. However, this is not the only way to success. One cannot dive into all areas simultaneously. Therefore, prioritising is essential. If the priority is to gain a deep understanding of how to construct a product, then it is worth investing time to become a developer. Nonetheless, if the aim is to become an expert in the underlying industry and ascend to top management positions, the manager could concentrate on communication skills and the ability to evaluate a developer's work from various perspectives (results, participation, robustness, etc.).

Few things to keep in mind while learning and applying a nascent technology in your product: 1. Avoid Trap of 'Have a hammer, will find a nail': Ensure the technology aligns with the product's strategic goals 2. Customer First: Assess if the technology addresses market needs or enhances user experience 3. Scalability and Compatibility: Assess the technology's scalability & compatibility with the existing tech infra 4. Business Impact: Ensure that cost/ effort justifies the impact on business 5. Long-term Viability: Analyze the long-term viability and sustainability of the technology 6. Learning Curve: Assess the learning curve for the team and impact on productivity 7. Compliance: Assess compliance with regulations and data security needs

The best approach is to start by understanding the engineering team's tech stack and start from there. By building an action plan and understanding the end-to-end flow that includes the basics of system design and architecture, basics of programming, communication between applications, basic data querying, hosting code, and user acceptance testing will provide a tremendous learning experience.