Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Establishing Harmony between Product Designers & Product Managers

Establishing Harmony between Product Designers & Product Managers

Tactical tips for developing healthy, collaborative and high-functioning relationships between Product Designers and Product Managers. (Originally presented at Designers + Geeks NYC, June 28, 2018).

Deepa Subramaniam

June 28, 2018
Tweet

Other Decks in Design

Transcript

  1. We spend more time with our colleagues then we do

    with our own friends & family. ✨We should enjoy work.✨
  2. How can teams be productive while also having fun, maintaining

    a healthy culture, and collaborating well, despite different roles, different goals and the realities of startup life? 3
  3. Make the implicit, explicit: Proactively translate for each other Regularly

    clarify roles & responsibilities Partner on Research Spend time to gain alignment at the start Openly discuss your working styles Join forces, lead by example 1 2 3 4 5 6
  4. Discovery Design Development Testing & Deployment Post-Deployment & Iteration Framing

    the problem, opportunity & approach Based on the problem, identify solutions Build feature reliably, securely & w/ quality Test & ship the feature Based on how the feature is doing, decide what’s next?
  5. Seamless collaboration requires clarity. Who does what, when? “Well, That’s

    not my job.” “Wait, I already did that.” “Uh, who was supposed to do that?”
  6. Product Manager owns the story of “what” & “why” Product

    Designer ∩ Product Manager Responsible for the success of the product ∩ Product Designer owns the story of “how” and “when”
  7. Product Manager owns the story of “?” Engineering Lead owns

    the story of “?” Product Designer owns the story of “?” PM ∩ PD ∩ EL: Responsible for the overall success of the product ∩
  8. Discovery Design Development Testing & Deployment Post-Deployment & Iteration Framing

    the problem, opportunity & approach Based on the problem, identify solutions Build feature reliably, securely & w/ quality Test & ship the feature Based on how the feature is doing, decide what’s next? Partnership is key, determine your focus!
  9. Good questions to ask • What is the user-facing problem

    we’re trying to solve? • What evidence do we have that this is a problem? • What is the business-facing problem we’re trying to solve? • How does it affect different parts of the business? • What evidence do we have that this is a problem? • Who is our target user? • What do we know about them? • Who are we not targeting? • What do we know about this audience of users (their motivations, their needs, their friction points, etc) • What are the user goals of this project? • What are non-goals for this project? • What does success look like?
  10. What you expect of them? What they expect of you?

    When and in what medium? Strategy Feedback Project Management Help/Support [Adapted from Lara Hogan’s worksheet here (larahogan.me/resources)]
  11. When the broader team sees you both coordinating and holding

    each other accountable, they will follow suit.
  12. Make the implicit, explicit: Proactively translate for each other Regularly

    clarify roles & responsibilities Partner on Research Spend time to gain alignment at the start Openly discuss your working styles Join forces, lead by example 1 2 3 4 5 6
  13. Q&A