In August 2022, I had the privilege of speaking at The Product Dive event on a panel titled “Winning Them Over – How to Work With the Engineering Team.” With over 1,000 enthusiastic attendees, the energy in the room was nothing short of inspiring. It was a powerful opportunity to share practical insights on one of the most critical dynamics in product development: the relationship between product managers and engineering teams.
Working with engineers is both an art and a strategy. When done well, it leads to fast delivery, innovative product solutions, and a deeply collaborative working environment. When done poorly, it results in frustration, misalignment, and stalled progress. During the panel, I broke down the principles that can help bridge the gap and build a truly effective partnership.
- Communication is Your Core Superpower
Communication isn’t just exchanging information—it’s creating understanding.
I emphasized the importance of:
Clarity: Be clear about goals, priorities, and timelines.
Context: Engineers build better when they understand the why, not just the what.
Consistency: Keep communication flowing throughout the product cycle, not just at kickoff.
Strong communication builds trust, reduces friction, and empowers the engineering team to make informed decisions.
- Learn to Speak Their Language
To collaborate effectively with developers, product managers must appreciate the technical landscape. While you don’t need to be a full-fledged engineer, understanding:
basic system architecture,
technical constraints,
development cycles, and
the difference between what is simple and what is resource-intensive
…goes a long way.
Acknowledging technical realities shows respect for the craft and fosters mutual respect.
- Align Vision and Purpose
Product and engineering are often seen as two sides of a coin—but the truth is, they must share a single, unified direction.
During the discussion, I highlighted how aligning vision creates:
better prioritization,
faster decision-making,
more creative problem-solving, and
a sense of shared ownership.
When both teams understand the larger “north star,” every feature, sprint, and iteration becomes part of a bigger mission rather than a checklist.
- Foster a Positive and Supportive Culture
Culture directly affects the quality of the product.
A healthy PM–engineering relationship is built on:
Trust: Allow engineers the autonomy to innovate.
Recognition: Celebrate engineering wins, not just product launches.
Empathy: Understand their challenges, constraints, and workload.
Collaboration thrives when every team member feels valued and supported.
- Tackle Challenges Together
One of my favorite parts of the panel was discussing real-world challenges and how cross-functional teams can overcome them. Whether it’s technical debt, shifting priorities, or unclear requirements, solving problems together —rather than assigning blame—creates momentum and improves velocity.
Great product outcomes are rarely the result of perfect planning. They happen when teams adapt and iterate as one.
A Truly Impactful Experience
Being part of this panel was deeply fulfilling. The engagement and excitement from attendees reinforced the importance of investing in strong product–engineering relationships. It also fueled my passion for contributing to the tech ecosystem, sharing knowledge, and empowering professionals to build with purpose.
For anyone navigating the world of product development, remember:
Winning over the engineering team isn’t about persuasion—it’s about partnership.
Additional Resources
Here are links to some of the highlights from the event:
Product Dive Meet & Greet Recap
(LinkedIn post)
Event Highlights by Rahmat Lasisi
(LinkedIn post)
Applied Skills
Teamwork • Leadership • Communication • Critical Thinking • Creativity
Technical Areas Covered
Product Management • Full-Stack Development • Web • Solution Engineering • Design
0 Comments