How to collaborate effectively with product designers


This week, I’m distracted with the first two rounds of the NCAA Men’s Basketball Tournament. As a result, I’m writing this as I wait for the second rounds of games to start later this afternoon.

I’ve had tickets to go to the games in Omaha Nebraska for several months without regard to who was playing here and was fortunate enough that my alma mater, Iowa State University (Go Cyclones!) got seeded to play here.

It’s mere coincidence that this week’s topic is collaboration with your product team, so I won’t try to stretch any analogy between collaboration on a basketball team and on a product team.

Except to say that those basketball teams that make it far in tournaments are those that can work well together and get to where they know where each other will be on the court without looking.

This issue ends up being an extension to the issue on delivery from a couple of weeks ago. In that issue, I shared some perspectives that product people shouldn’t spoon feed their developers priorities and aren’t responsible for the delivery of their product.

If those ideas left you thinking “that’s great Kent, but If I don’t set priorities and drive delivery who will?”

The point that those articles made is you need to share responsibility for moving things forward with the makers on the product team - the engineers and product designers.

Making that happen in practice requires establish trusting relationships with everyone on your product team.

The delivery issue focused on engineers, so in this issue I want to put the focus on working with product designers.

There can be more overlap between product manager and product designer skill sets, so it’s even more important to establish clear expectations about who is going to do what and where you’ll work on the same thing together.

So read on for a collection of tips for building a strong product manager - product designer relationship.


Discount to INDUSTRY Conferences

My friends at Product Collective regularly put on the premier conferences for software product managers. Even better, they put on three in person and one virtual conference each year so you have your choice of where to go.

The conferences coming up are:

New York Product Conference April 18, 2024 New York City, New York USA

Industry Europe June 17 - 19, 2024 Dublin, Ireland

Industry Global September 23 - 25, 2024 Cleveland, Ohio USA

Industry Virtual October 17 Anywhere

Registration is open for all four conferences. Go here for more information.

Plus, if you use the code INSIDEPRODUCT50 when you check out, you get an additional $50 off your registration. (Full disclosure - this is an affiliate offer)

And something else to consider - I’ll be at the New York Product Conference and Industry Global this year. I’d love to see you there.

Register Today!


Advice for PM’s working with Designers

The folks from Aha! shared these suggestions for product managers working with designers.

Don’t throw your designer under the bus. The team owns design decisions, especially when talking with people outside your product team. Succeed or fail as a team in design reviews.

Set the product strategy before your team starts any designs. This helps you build a shared sense of mission with your UX folk.

Provide clear and actionable feedback. If you feel that a design is not what it needs to be, provide feedback that a product designer can act on to improve it.

Romy Misra offers some additional suggestions on how product managers can effectively work with product designers.

The best feedback is about problems, not solutions. Never say “I don’t like it,” without a reason. It’s not “I don’t like this shade of blue,” it’s “I feel like this button doesn’t draw attention enough given its importance.”

One perspective: PM should be an expert in the user, the user’s problems, and the business. The designer should be an expert in user interfaces. - it’s better for PM to describe user problems and business goal, and let designer come up with a solution to address those things

Two cases where PMs should design user interfaces:

  1. You want to create a vision mockup of a new feature or flow
  2. You don’t have a solid visual designer and need to spearhead this yourself

Advice for Designers working with PM’s

Strong relationships are a two-way street, so Adhithya Kumar provided these suggestions to designers on how to work with product managers.

Prioritize tasks - think about engineering needs and business needs to determine the right time to bring up design concerns and to prioritize design decisions. Understand the product status from a broader perspective.

Track UX debt - This is a similar concept to tech debt. Note things you want to come back and fix once you have the initial version released in order to get feedback.

Create a UX test plan - Create a game plan before talking to customers for validation. Work with the PM to structure customer calls so you can address key things you need to make design decisions.

Track actions on the product - A designer, to better inform their design decisions, needs to analyze and figure out what needs to be tracked, why you should track them, and what you aim to get out of tracking them.

Design Skills PMs should have

Remember how I said that there can be a bit of overlap between product managers and product designers? Harish Venkatesan suggested these four design skills that every product manager should have, even if there’s a product designer on the product team.

Advanced user research skills - truly understand your customers and be able to articulate their pain points, desires, and needs to other team members

Basic interaction design skills - describe users’ goals and determine product features based on those goals.

Taste - the best product people have a quality of taste. You need to recognize good design.

Elementary knowledge of visual design concepts - know design vocabulary so you can communicate with designers and understand tradeoffs and design decisions. But, let designers design.

Thanks for reading

Thanks again for reading InsideProduct.

If you have any comments or questions about the newsletter, or there’s anything you’d like me to cover, let me know.

Talk to you next time,

Kent J. McDonald

Founder | KBP.Media

InsideProduct

Hand-picked resources for product owners, business analysts, and product managers working in tech-enabled organizations. Check out the resources I offer below and sign up for my newsletter!

Read more from InsideProduct

For the last few weeks, I’ve explored what prioritization looks like in a variety of different scenarios. This week finished up that series with a look at how you can go about prioritizing a bunch of stakeholder requests. This is a common scenario when you’ve already built software for your company (ie internal product) and you’re trying to optimize or maintain it. A unique aspect for internal products is that most requests for changes come from other people inside your company who may, or...

Last week, we talked about how to prioritize your new product development efforts when you’re trying to get to product market fit. Once you hit that sought after milestone, your product moves into the growth stage of the product life cycle and you switch into product optimization. So it makes sense that optimization is the next scenario I’ll explore on InsideProduct. It seems like everyone is talking about product optimization If you’re not sure what I mean when I say product optimization, go...

Here’s the next in a series of issues on prioritization. This week’s issue looks at prioritization when you build a new product. Some people refer to this as going from 0 → 1. In the world of internal products, you can think of this as what you need to do to enable a brand new process in your organization. The general prioritization approach for new products is very similar to what I described for rebuilding existing products. You decide what features your product will and will not have, then...