Product Managers Don't Need to Do Everything, But They Must Understand Enough
When I first started learning about the role of a product manager (PM), I had a rather naive thought: a PM must know coding, be good at design, understand marketing, and be able to calculate production costs... In other words, they had to be "good at absolutely everything." I floundered around learning all sorts of things, from programming languages to running ads, and ended up feeling exhausted and confused about my true role. It wasn't until I read a lecture about functional areas – the domains a PM regularly works with – that I had my epiphany: a PM doesn't need to do everything, but needs to understand enough to ask the right people the right questions, make sound decisions, and ensure the product stays on track.
My perspective after learning this is: a successful PM is not the person who is the best in every department, but the one who grasps the language, processes, and pain points of each department in order to coordinate them smoothly. If you're self-studying product management – whether you're just starting out, looking to switch careers, or simply curious – understanding the functional areas will help you build a more solid foundation than trying to cram in too many specialized skills without knowing how to use them.
Why must a PM "understand enough" without needing to "do it all"?
Imagine you are the conductor of an orchestra. You don't need to play the flute, violin, or drums as well as each individual musician. But you must know how each instrument produces its sound, when it should come in, when it should stop, and how to make them harmonize. If you're only skilled at the violin but know nothing about the drums, the orchestra will be in chaos. The same goes for a PM. You're not an engineer, a marketing specialist, or a supply chain analyst, but you need to know what they do, what challenges they face, and how your product impacts them.
In a typical organization, a PM works with: engineering, marketing & sales, manufacturing & operations, customer support, supply chain management, project management, and distribution channel stakeholders. Each of these areas has its own language, processes, and priorities. If you don't understand what they're saying, you won't be able to ask the right questions, you won't be able to negotiate, and your product can get stuck between the parties.
One department at a time: what to understand and why?
Engineering: where the product becomes reality
Engineering is the department that gets directly involved in building the product. They are responsible for interpreting and shaping the product vision into code, design, or prototypes. A PM needs to understand software development processes, how to write clear requirements, and – most importantly – the limits of technical feasibility. For example, customers want an app that runs on every device, but engineering says the first version only needs to support iOS. If you don't understand why, you'll apply pressure in the wrong places and demoralize the team.
My advice: learn to read a basic technical design document, understand terms like API, database, and bug triage. You don't need to know how to code, but you should know how to ask "What would happen if we added this feature?" to get valuable answers.
Marketing & Sales: the heart of placing the product in the market
If a product doesn't sell, it has no value. Marketing and sales are the teams that determine how the product reaches customers, through ad campaigns, brand positioning, and pricing strategies. A PM needs to align their vision with the marketing strategy – not just at launch but throughout the product's life cycle. I once witnessed a technically brilliant product fail because the marketing team didn't understand its core value, and conversely, a "premium" product sold to the wrong audience still got criticized.
Learn to read a marketing brief, understand concepts like target audience, positioning, and communication channels. You'll work better with sales if you know what objections they're facing from customers.
Manufacturing & Operations: where the product truly exists
If you make physical products (hardware, packaging, devices), the manufacturing team is your "landlord." They need to know raw materials, fabrication technology, and assembly processes. A PM needs to work with manufacturing engineers to determine which materials are suitable, what they cost, and whether production can scale to large volumes. For example, if you want to make a smart speaker, you need to know which plastic withstands heat well, which battery is safe, and what speed the assembly line can achieve.
Knowledge of tooling and process flow will help you optimize capacity and reduce costs. Don't be afraid to ask manufacturing engineers "silly" questions – they're usually willing to explain if they see that you respect their expertise.
Customer Support: the keepers of the "customer's voice" after the sale
After a product reaches users, customer support is the one who directly hears complaints, questions, and requests. A PM needs a process to listen to this feedback. Factors like documentation (technical writing), training programs, and version updates are all within your reach. For instance, with software, you need to ensure call center agents understand new features well enough to explain them to confused customers. If you neglect this area, no matter how good the product is, it will get poor reviews because of bad support.
Supply Chain Management: the lifeblood of the product
The supply chain handles finding suppliers, negotiating contracts, managing warehouses, and transportation. A PM needs to understand the company's sourcing strategy and know how to coordinate to have the right materials at the right time. I once saw a project delayed by three months simply because an electronic component couldn't be imported after the supplier went bankrupt. If the PM had known how to assess supply chain risks and could have proposed an alternative source, the impact would have been mitigated.
Project Management: the bridge between strategy and execution
Understanding project management principles – like planning, tracking progress, and risk management – helps a PM work better with project teams. You'll be able to make better decisions
Top comments (0)