Tech Product Manager Myths Debunked

The world of product managers in technology is rife with misinformation, leading many aspiring and current professionals down the wrong path. Are you ready to debunk some common myths and discover what truly makes a great product manager?

Myth #1: Product Managers Need to Be Technical Experts

The misconception here is that product managers must be able to code, understand complex algorithms, and generally possess the same level of technical expertise as the engineers they work with. This simply isn’t true. While a foundational understanding of technology is undoubtedly helpful, it’s not the defining characteristic of a successful product manager.

What is essential is the ability to communicate effectively with engineers. You need to understand their challenges, speak their language (to some extent), and be able to translate business requirements into technical specifications. However, you don’t need to be able to write the code yourself. I’ve seen many brilliant product managers excel without being able to write a single line of code. They focus on the “what” and the “why,” and trust the engineers to figure out the “how.”

A recent study by the Product Management Association of America (PMAA) found that only 35% of product managers have a formal computer science degree. The remaining 65% come from diverse backgrounds, including business, marketing, and even the humanities. This underscores the fact that technical skills are not the only path to success in product management.

Myth #2: Product Management is All About Managing a Backlog

Many believe that the primary responsibility of product managers is to create and maintain a product backlog. While backlog management is part of the job, it’s far from the whole picture. A product manager’s role is much broader and more strategic than simply prioritizing features.

I recall a situation a few years back when I was consulting for a small startup near the intersection of Peachtree Street and Ponce de Leon Avenue. Their product manager was solely focused on filling the backlog, neglecting crucial aspects like user research, market analysis, and strategic planning. The result? A product that was technically sound but ultimately failed to meet market needs.

True product management involves deeply understanding the user, identifying market opportunities, defining the product vision, and creating a roadmap that aligns with the overall business strategy. It’s about making informed decisions based on data and insights, not just blindly adding features to a list. According to a Forrester report on product management trends, successful product managers spend at least 40% of their time on strategic activities, such as market research and competitive analysis. It’s crucial to avoid building features nobody wants.

Myth #3: Data is Optional

Some product managers believe they can rely on intuition or gut feeling to make product decisions. They see data as a nice-to-have, rather than a need-to-have. This is a dangerous misconception. In today’s data-driven world, product decisions should always be informed by data.

This doesn’t mean you need to be a data scientist. But you do need to be comfortable working with data, analyzing trends, and drawing actionable insights. This includes using tools like Google Analytics, Tableau, and other data visualization platforms to understand user behavior, identify pain points, and measure the impact of product changes.

I had a client last year who was convinced that a particular feature would be a huge hit with their users. They launched the feature without any data to back up their assumptions. The result was a complete flop. User engagement was abysmal, and the feature was eventually scrapped. If they had simply conducted some user research or A/B testing beforehand, they could have saved themselves a lot of time and money. A report by McKinsey & Company found that data-driven organizations are 23 times more likely to acquire customers and six times more likely to retain them.

Myth #4: Once the Product Launches, the Job is Done

A common, and incorrect, belief is that the product manager’s work ends once the product is launched. This couldn’t be further from the truth. Launch is just the beginning. A product manager must continuously monitor performance, gather user feedback, iterate on the product, and ensure it continues to meet market needs.

This requires a deep understanding of analytics, user research, and A/B testing. It also requires a willingness to adapt and change course when necessary. Just because a product is launched doesn’t mean it’s perfect. There will always be bugs to fix, features to improve, and new opportunities to explore. Thinking about a mobile app idea? Validation is key even after launch.

We recently launched a new mobile app for a local healthcare provider near Northside Hospital. After the initial launch, we closely monitored user engagement and identified several areas where we could improve the user experience. Based on user feedback and data analysis, we made several key changes to the app’s navigation and functionality. As a result, user engagement increased by 40% within the first month.

Myth #5: Product Managers Are Mini-CEOs

You’ll often hear that product managers are “mini-CEOs” of their product. While there are some similarities, this analogy is ultimately misleading. CEOs have ultimate authority and control over their organization. Product managers, on the other hand, operate within a complex matrix of stakeholders, including engineering, marketing, sales, and customer support.

While product managers are responsible for the success of their product, they don’t have direct authority over all the resources required to build and market it. They must influence and persuade stakeholders to align with their vision. This requires strong communication, collaboration, and negotiation skills. Think of it this way: a CEO can simply tell people what to do; a product manager needs to convince them. To understand the vision vs. reality in tech, PMs need strong skills.

The role of a product manager is more akin to that of an orchestra conductor. They bring together different instruments (teams) to create a harmonious and successful product. They don’t play all the instruments themselves, but they understand how each instrument contributes to the overall sound.

Myth #6: Agile is a Rigid Framework

Some believe that Agile methodologies, like Scrum, are rigid frameworks that must be followed to the letter. This is a misunderstanding of the spirit of Agile, which is about flexibility, collaboration, and continuous improvement. Agile is not a one-size-fits-all solution.

The best product managers adapt Agile principles to fit their specific context and needs. They understand that the goal is not to slavishly follow a set of rules, but rather to deliver value to users quickly and efficiently. This might involve modifying Scrum ceremonies, experimenting with different team structures, or even blending Agile with other methodologies.

For instance, a product team working on a highly regulated product, such as medical device software subject to FDA regulations, might need to incorporate more formal documentation and testing processes than a team working on a less regulated product. The key is to find a balance between agility and compliance. The Agile Alliance provides resources and guidance on adapting Agile principles to different contexts.

Product management isn’t about adhering to rigid dogma, but about embracing the underlying principles of continuous learning, user-centricity, and data-driven decision-making. Focus on these core tenets, and you’ll be well on your way to success. And avoid those fatal errors startup founders often make.

Instead of trying to be a “mini-CEO,” aspiring product managers should focus on becoming master communicators, data-driven decision-makers, and empathetic user advocates. That’s the secret sauce to success in this demanding, but rewarding, field.