Working with Engineers is Product Management

I think the first thing, and this applies to any relationship, not just product managers and engineers, is mutual respect.

Marc Abraham, Chief Product Officer at Settled, shares how he collaborates with engineers and designers and his approach to product roadmapping.


There are few standardized career paths for becoming a product manager, but Marc Abraham’s story is particularly unique. Marc is a former corporate lawyer turned Chief Product Officer based in the UK. After working in business development and project management, he transitioned to product management so that he could work on the entire product lifecycle.

Marc has gained a deep understanding of how to facilitate productive collaboration. He learned that in order to develop and maintain a healthy working relationship between product managers and engineers, product managers and engineers need to have mutual respect and understanding, and clear roles and responsibilities.

Product managers liaise between customers and the business, engineers and designers, to come up with the answer to “what we are trying to achieve and why?” Engineers are able to turn those ideas into viable products. In other words, product managers are responsible for the “what” and “why,” and engineers are responsible for the “how.”

Marc also shares advice on collaboration with designers. Everyone has an opinion on design, he says. That’s why he recommends that product managers facilitate conversations with key stakeholders by providing context and explaining the “why” behind decisions.

Marc says that good product managers value all the information and viewpoints, make a decision, and take accountability. However, while it’s crucial to make sure everyone has a say, it’s easy for this to lead to chaos. To this end, Marc says to set parameters so that people don’t go too far off on a tangent.

Marc shares two helpful frameworks for making product decisions: Cost of Delay and RICE.

Cost of Delay forces teams to consider what would happen if they stopped working on A and started working on B instead. In other words, teams consider the opportunity cost of a given project, calculating how much effort is need to bring the product to market but also what alternative uses of that time would look like.

RICE, Marc’s second framework, is an acronym that comprises four important factors when making decisions:

RICE boils down to evaluating the feasibility and benefits of a given project both in terms of money and time costs.

You’ll learn a lot from this episode about how to collaborate with engineers and designers and prioritize ideas.

Here are the highlights:

Marc Abraham

Chief Product Officer at Settled

Marc’s Recommended Resources on Working with Engineers

What Marc is Listening To Right Now

Marc’s Favorite New Products Outside of Work

Subscribe to receive the latest episodes and exclusive resources

Related Episodes

100

Perfecting the Kickoff Meeting is Product Management

Katie Guernsey, Product Manager at STRV, shares how to influence key stakeholders with a compelling presentation and align product teams to execute on a vision.

Listen to Episode
60

Rallying Stakeholders is Product Management

Joe Lalley, Digital and Social Strategy Director at PwC, shares how to align stakeholders and make the case for key product decisions based on his experience building PwC’s homepage.

Listen to Episode
4

Hiring is Product Management

Will Cole, Director of Product at Stack Exchange, illustrates how to transition from a company that goes out to find talent into a company that attracts talent, how to source and screen innovative product people, and how to build rapport with engineers.

Listen to Episode

Alpha is the fastest way to learn about your future customers.

Learn More