EM-PM Relationship as a Product
This is the second article in a 3-part series of insights from my experience building and supporting strong EM/PM partnerships - read the first article here.
In the first article, we explored how to assess your EM-PM dynamic - where it is today, and where you'd like it to go. Now let’s talk about how to actually get there. Just like your team iterates toward better outcomes, your partnership can, too.
Think of your relationship as a product. You’re not shipping software; you’re shaping a collaboration. That means investing in maintenance, retrospectives, and even the occasional refactor.
Design your relationship
- What is important in your partnership?
- What are the parameters, strategies and values by which you’ll evaluate the work?
- How will you measure success?
You won’t always be in agreement, and that’s OK - that’s the work. When facing a conflict, embrace it. Ask the question: why do I think X is important, while my peer is prioritizing Y?
Use process commentary - describe out loud what’s happening and what you’re seeing. You’ll be amazed by how effective that can be in your interactions.
Iterate and Retrospect
Give yourselves permission to experiment with new ways of working. Take that process commentary to the next level - just like your team improves through agile practices, so can your partnership. Have regular 1:1s, but also schedule “retrospective” time that is focused on how you're working together. Try asking:
- What’s going well in our collaboration?
- What’s been frustrating?
- What’s something we could try differently next month?
Partner on Business Alignment
Remind yourself of the team’s business objectives; make data-driven decisions and continue aligning your team with the “why”. Strive to fully partnering on all decisions and projects coming into your team - model that relationship to your team and you’ll notice how smoother the whole design to delivery process is.
Remember - you're both committed to succeeding - be each other the 10x factor you can be.
