Find this guide helpful?
Consider donating
🐼
Product Manager's Guidebook
GithubAuthorDonateContribute
  • Guidebook
    • Welcome
    • Contribute
    • Donate
  • Prelude
    • A Note From The Author
    • How To Use This Guide
  • Introduction
    • Overview
    • What is a Product Manager?
      • Roles and Responsibilities of a Product Manager
      • The Product Mindset
      • Understanding the Product Management Lifecycle
      • Different Types of Product Managers
    • Product Team Structures
      • Stakeholders, Leadership, and the Company
      • Cross-Functional Product Team
      • Differences between Project, Program, and Product Management
  • People Skills
    • Overview
    • Communication
      • Knowing Your Audience
      • Elements of Persuasion and Motivation
      • The Art of Storytelling
      • Effective Meeting Management
      • Delivering Presentations and Demos
    • Building Relationships
      • Collaboration Cadence and Tools
      • Team Agreements and Purpose
      • Understanding Business Problems
      • Managing Expectations
      • Communicating Progress
    • Leadership
      • Cross-Functional Leadership
      • Applied Motivation and Getting Buy-In
      • Giving and Receiving Feedback
      • Aligning Product Mission, Vision, and Strategy
      • Sharing Impact and Outcomes
  • Process Skills
    • Overview
    • Strategy
      • Objective Setting
      • Prioritization
      • Roadmapping
    • Discovery
      • Problem Research and Definition
      • Customer Discovery and Research
      • Solution Design and Validation
    • Development
      • Writing and Using Product Requirements
      • Concepts through Designing
      • Working with Designers
      • Development Execution and Methodologies
      • Working with Engineers
      • Scoping and Writing User Stories
      • Technical Debt Management
    • Delivery
      • Roll-out and Release Management
      • Assessing Assumptions, Risk, and Issues
      • Measuring Product Launch Success
      • Marketing and Communications
      • User Activation
    • Optimization
      • Iterative Development and Learning
      • Streamlining Processes and Experiences
  • Knowledge Skills
    • Overview
    • Understanding the Customer
      • Customer Segmentation and Targeting
      • User Research Methods
      • Understanding Customer Pain Points
      • User Personas Development
      • User Behavior and Psychology
      • Acquiring and Retaining Customers
    • Data-Driven Decisions
      • The Role of Data in Product
      • Data Analysis and Interpretation
      • Identifying and Understanding Assumptions
      • Formulating Your Hypotheses
      • Selecting a Hypothesis for Testing
      • Navigating Signal Metrics to Define KPIs for Hypothesis Testing
      • Testing Your Hypothesis
      • Upholding Data Privacy and Ethics
    • Domain Knowledge
      • Competitive Analysis and Industry
      • Achieving Product-Market Fit
      • Technology and Innovation
      • Aligning with the Company
    • Business Understanding
      • Organizational Values, Objectives, and Priorities
      • Long-Term Planning
      • Business Model Fit
      • Monetization Strategy
Powered by GitBook

Created by Mark Progano • Free & Open Source • Visit the Contribute Page to Help

On this page
  • Example
  • Pain Points
  • Practical Exercise
  • Related Research Topics
Edit on GitHub
  1. Process Skills
  2. Development

Working with Engineers

PreviousDevelopment Execution and MethodologiesNextScoping and Writing User Stories

Last updated 1 month ago

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 [ | ]

  • Building trust with engineers [ | ]

  • Understanding technical constraints in product development. [ | ]

Google
Perplexity
Google
Perplexity
Google
Perplexity