Mar 14
3 min read
Product manager’s key stakeholders
Those who are not into product management or sometimes naive Product managers (PM) may think that a Product Manager interacts only with tech and customers to ship the product. To clear their misconception, this post covers the list of stakeholders and the purpose of the interaction.
- User/Customer: To understand the problem statement. Once the user is converted into the customers then you’ll have two different personas.
- Business: To understand the business goals that are aligned with the solutions provided to the customer
- Designer (UX/UI): To design the experience of the solution and interfaces which will be used by various users of the product.
- Frontend(FE) developers: To develop Mobile/Web App based solutions. It’s important that PM provides the list of events and properties to be traced via Firebase, Amplitude, Mixpanel, etc…
- Backend(BE) developers: To develop BE systems that further interact with FE or external APIs. To empower BE, PM bridges the interaction with FE and external parties. If the events and properties need to be tracked directly from BE then it should also be provided by PM.
- Business analyst: To prepare various reports such as business and product metrics.
- Tester/Delivery: To ensure that the prepared product is up to the mark as per the design references given by PM. The design references can be given in the form of a PRD or click-through prototype.
- Infrastructure: To ensure that the solution prepared by BE should have low latency and up for the customer whenever they need it. During integration with a third party, it’s important that inbound and outbound IPs are whitelisted with SSL so that secure communication can take place.
- Information Security: To ensure that internal systems are not vulnerable. If the system is interacting with external systems then they will make sure that the required protocols are adhered.
- Compliance/Legal: To ensure that the developed solution is fully compliant with the measures defined by the respective authority. When any third party is being onboarded then this team will ensure the required Service Level Agreement (SLA).
- Risk: To prevent fraud and malicious activities performed by the customer.
- Operation: To make sure that all tasks that are not automated are carried out by the team with a proper Standard operation procedure (SOP) and handholdings.
- Customer Support: To make sure that what the customer is conveying about the product reaches you so that you can further improve it. Also, empower them with a set of information so that the customer’s questions can be answered.
- Sales and Marketing: To make sure that they understand the product well so that they can sell/communicate better.
- Content writer: To prepare write-ups for the website, PR activities, and knowledge base.
- Trainer: To amplitude the product sessions for the internal stakeholders.
- Finance: To ensure cash inflow and outflow of the product are known so that they can better manage cash flow. Apart from that, the vendor’s quotations and invoice clearance are also managed by them.
