# Working with Engineers Working with engineers involves collaborating with highly technical individuals to translate product requirements into a functional product. This requires the Product Manager to effectively communicate the product strategy, business objectives, and user needs to the engineering team. While the Product Manager doesn't need to be highly technical themselves, they should have a basic understanding of the technology stack and be able to ask the right questions to ensure the proposed solutions are technologically sound. The Product Manager should also foster an environment of trust and respect, valuing the input of the engineers and relying on their expertise to guide the technical aspects of product development. ## Example Imagine you're a Product Manager at a social media company, like Twitter. You're working on a new feature that allows users to customize their feed. Your initial proposal involves a complex machine learning algorithm that would predict and prioritize the content that users would like to see. However, during a meeting with the engineering team, the lead engineer expresses concerns about the feasibility of implementing such a complex algorithm within the proposed timeline. They suggest a simpler solution that involves allowing users to manually select the topics they're interested in. As a Product Manager, you might initially be disappointed about the need to simplify your vision. However, you recognize the importance of the engineer's input and their expertise in what is technically feasible. You ask questions to understand the limitations and the proposed alternative solution. After understanding the trade-offs, you agree to adjust the feature to align with the engineer's suggestion. You appreciate the engineer's proactive communication and problem-solving approach, and you make a note to involve the engineering team earlier in the process in the future to ensure technical feasibility is considered from the start. ## Pain Points Balancing the vision of the product with the technical feasibility can be challenging. It's also important to foster a collaborative environment where engineers feel their input is valued and they are involved in the decision-making process. Communication can also be a challenge, especially if the Product Manager and the engineers do not have a shared understanding of the product goals and technical constraints. ## Practical Exercise Reflect on a recent interaction you had with an engineer, technical team member, or someone talking about something that you didn’t understand fully. What was the situation? How did you communicate your ideas and listen to their input? What went well and what could be improved? ## Related Research Topics * Effective communication with technical teams \[ [Google](https://www.google.com/search?q=Effective%20communication%20with%20technical%20teams%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Effective%20communication%20with%20technical%20teams%20in%20product%20management) ] * Building trust with engineers \[ [Google](https://www.google.com/search?q=Building%20trust%20with%20engineers%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Building%20trust%20with%20engineers%20in%20product%20management) ] * Understanding technical constraints in product development. \[ [Google](https://www.google.com/search?q=Understanding%20technical%20constraints%20in%20product%20development.%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Understanding%20technical%20constraints%20in%20product%20development.%20in%20product%20management) ] --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.pmguidebook.com/process-skills/development/working-with-engineers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.