Know enough to call BS
How much coding, design and data analytics should a PM know?
Every PM at the start of their career would stumble on the question that is “How much coding, designing or data manipulation should I learn?”
PMs don’t need to code.
PMs don’t need to design.
PMs don’t need to write SQL.
PMs need to understand each enough to call BS.
Can you work with an engineer to understand why something can’t be done? Provide context to change the problem’s constraints. You’re helping equip them with the data to solve it, not coding.
If a designer tells you something can’t be done, can you take a step back and try to look at the bigger picture? Can you explore the possibilities together, discuss the potential challenges and collaborate to come up with new ideas? Can you look at the information architecture and suggest changes that could lead to more successful outcomes? By working together, it’s possible to come up with solutions that weren’t previously thought of and find ways to make the seemingly impossible, possible.
The marketing team may claim features are critical: can you look at data to check, & ask the right questions to find it? This shows the difference between knowing how to write SQL and understanding which data to get in the beginning. Even better, do you know what kind of data to look for?
There are countless examples that can be used to illustrate the point, from everyday scenarios to unique and extraordinary ones. In a lot of situations, it becomes clear that the point holds true.
How can you learn to call BS?
To learn how to call BS, observe. When an engineer or designer makes a decision, ask them why. Don’t settle for the surface-level answer; dig deeper (to learn, not challenge), but make it clear that you’re doing so to learn, not to change their mind.
If a certain feature is hard to implement, you could ask how they would go about building it and consider where it might break. Additionally, it might be worth considering what alternative solutions exist, what kind of resources would be required to build the feature, and whether other approaches may be more successful.
Taking the time to reflect on the various elements of the decision-making process can help ensure that the decision is made in the best possible way.
As you observe and learn, you can apply your knowledge in practical ways: ask better questions, provide relevant context during meetings, challenge assumptions, and provide alternative solutions during product design. With practice, you’ll be able to confidently call BS.
It is clear that learning to code, design, and write SQL are all valuable skills, but none of them is necessary to become a product manager. Furthermore, these skills alone will not make you stand out.
You can however decide to learn how to code, design or manipulate data but do so with the knowledge that it is not compulsory for your career.
