👋 Hello, I’m Lenny and welcome to a ✨ once-a-month-free-edition ✨ of my newsletter. Each week I humbly tackle reader questions about product, growth, working with humans, and anything else that’s stressing you out at the office.

This week’s newsletter is brought to you by…

The Browser is one of my most favorite newsletters. Why? Because every issue brings me joy. How rare is that. I even broke my rule of avoiding sponsorships because I love The Browser so much. Inside each issue, you’ll find a hand-picked selection of the most interesting, best-written, and most get-your-brain-juices-flowing articles on the Internet. Even if you just read the capsule summaries of each selection, your day will be brighter.

Special offer for subscribers of this newsletter: Try an entire month for free, no subscription needed! Click the button below to claim this offer.

Get one month of The Browser free

Q: I’m having a hard time working with the designer on my team. Do you have any advice for working with designers?

When I think about a designer who embodies ideal collaboration and thoughtful partnership with product management, I think of my former colleague Katie Dill. Katie and I worked together at Airbnb where she led much of the product design team. Katie then went on to lead design at Lyft, and last month took on the Head of Design role at Stripe.

I asked Katie for advice on this question, and instead of just sharing a tip or two, she offered to write up an entire guest post sharing specific advice from her experience working with hundreds of PMs. Below you’ll find Katie’s top five tips for building a powerful PM + Design partnership, including:

1. Trust the designer’s expertise

2. Be the conductor

3. Include designers early 

4. Invest in even the smallest of north stars

5. Create shared goals

I learned a ton from Katie’s perspective, and I know you will too. Let’s dive in!

For more from Katie, you can find her on Twitter.

The PM 🤝 Design Partnership

by Katie Dill

Ask a Product Designer what their job is and what you'll hear is likely very close to what a Product Manager (PM) would say about their job: to know what customers need and to deliver it in the form of products that drive the business. This overlap between PMs and designers is a benefit—it means we all want the same thing. But, we often have very different approaches to achieving these goals, which can lead to friction in our collaboration. However, when we embrace our different methods and styles, great things happen! By combining forces—like the Avengers!—we can build much better products.

Below is a quick cheat-sheet for PMs on how to effectively work with designers. By understanding how each other ticks, we can collaborate in more effective ways—leveraging both our differences and similarities—and turn one plus one into three.

Let’s start with a quick reminder of why designers work differently than PMs. While designers come in many different shapes and sizes (e.g., graphic, UX/UI, industrial, service, etc.), generally speaking, all good designers are creative, humanistic, sense-makers, and storytellers. Designers interrogate the present and imagine the future as we aim to create something that is useful, usable, and desirable. These skills are important to your company and are instrumental in driving conversion, loyalty, and efficiency in your business.

Alas, these skills require special conditions to exist, some of which conflict with the default way of doing business. For example, how often are you talking about your customer’s emotions in your QBR? It’s easy to say design and user experience matter, but if you don’t invest in creating the conditions for design to thrive, chances are it won’t.

So what can you do to build a stronger relationship with design? My 5 top tips: 

1. Trust the designer’s expertise

2. Be the conductor

3. Include designers early 

4. Invest in even the smallest of north stars

5. Create shared goals

Tip #1: Trust the designer’s expertise

Creative work is very different from analytical work. It’s non-linear and its value is often difficult to measure. While it’s always good to discuss timelines, goals and expectations, be sure to trust in the designer to know what it takes to do their work well. 

While there are many efforts that are straightforward and do not require reinvention (e.g., industry best practices for a “contact us” page may be just fine ), creative work may surprise you with the time it takes. When something is designed well it often feels simple and obvious. However, the process to get there requires user research, exploration, and a good deal of failure to land on the right answer. Moreover, this time needs to be high quality—uninterrupted—to allow for focus and flow. As Paul Graham notes in his post on Maker vs Manager's schedules, “when you're operating on the maker's schedule, meetings are a disaster. A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.” Designers and other makers on your team require this meeting-free time to get into a creative flow and create. Frankly, you need more of this time, too!

I guarantee there will be times when you and your design partner disagree about something, and they’re not going to be able to validate their opinion (at least not right away). Prototypes and qualitative research can help de-risk decisions. But some design choices are simply a matter of taste. Assuming your company hired well and you’re working with a skilled designer who is well-informed about the user, the problem and goals, you should defer to them in their area of expertise: the user experience.

Tip #2: Be the conductor

If you didn’t know it already, the team is looking at you (the PM) to set up the foundation for collaboration. Great PMs are known for their ability to clarify the context—defining problems, goals, and constraints—and tying it all back to the business. In addition, a great PM is a powerful facilitator that can drive communication and collaboration in and outside of the team. It reminds me of a conductor in an orchestra. The conductor doesn’t play all the instruments, but they have a grasp of what the different players contribute and they help coordinate them such that the ensemble is harmonious.

The best way to coordinate the team and set your design partner(s) up for success is to ensure alignment on the problems to be solved, the mission, and the goals. You have the opportunity to do this in a way that allows the various experts on the team to leverage their own superpowers. Bobby Rasmusson says this well…

Tip #3: Include designers early 

While conducting, it’s important to include folks from the beginning so that you and the team can benefit from their expertise throughout the product development process. When resources are tight, a waterfall approach (ie., work moves assembly-line style from one person/discipline to the next) is tempting but has hidden pitfalls. You’ll get richer solutions, more quickly, if you include your expert partners early.

Doug Collins, a design manager from Western Union states this well... 

There are three major reasons why including designers early can help the organization save time and money: 

1. Designers inform the conversation with a salient voice of the user 

2. Designers catalyze the conversation and drive innovative thinking with creative ideas, visual storytelling and prototypes

3. Designers gain greater context, develop a keener intuition for what’s best and are able to drive higher quality execution faster 

I know it can be hard to add yet another person to the room, but the benefit outweighs the risk. A good example is during planning. I have known plenty of PMs that were eager to rush ahead with a list of features they thought the team should build. However, I have seen these same PMs sing a very different tune after including designers in the planning process. They gained a skillful facilitator, a user-advocate, and a powerful storyteller. Conversations were richer and ideas were more thoughtful. And the designers always got invited back. 

Tip #4: Invest in even the smallest of north stars

I have seen PMs get really worried about "north star" work, fearing that it's superfluous, taking the team's precious time away from completing the obvious and urgent work. All that can be true, but it doesn't have to be. 

A north star is a picture of your future product. It can be low or high fidelity. It can be all-encompassing of the different stages of the user journey, or it can be focused on a particular aspect of the product. A north star is a guiding light that helps align a team on the plan for the product, showing how the pieces will fit together. Without it, you're liable to miss the opportunity to innovate, are likely to neglect the long-term, and are probably turning your product into a disjointed Frankenstein lacking consistency.

We used north stars at Lyft for everything from small improvements to a complete transformation of the rider experience. Lyft started with rideshare, but over time added additional forms of transportation to its app: trains, buses, bikes, scooters, rental cars. This was a big change. To help us do it right—and not cobble things together—we had a multidisciplinary team of designers, engineers, and PMs creating a north star for how the app should be with all the forms of transportation included. The north star covered more than we could do in the short term, but it made it clearer what steps should be taken next so that we’d be headed in the right direction in the long term.

You and your design partner can make sure it's not a waste of time by putting some constraints around the effort as you visualize the destination. Variables to consider:

1. Scope - how much of the product experience to include in the vision? A single screen can be envisioned in a day, whereas a new product can take months. 

2. Fidelity - how robust should this north star be? Consider the audience and how the story will best be understood: in words, in a journey map (like a comic strip), wireframes, or full-fledge prototype.

3. Time horizon - how far out into the future are you planning for? Near-term vision work will include more knowns and be quicker to create, but doesn’t afford you much runway.

4. Buy-in - who do you need to involve to inform and evangelize the work? Feedback cycles take time but are critical when different parties need to be aligned. 

There are no simple answers to these questions. It essentially comes down to how complex is the problem your team is trying to solve? If it's simple, minor, and easily changeable you can likely get away with a short whiteboarding exercise to give everyone clarity. However, if the problem you're solving is complex (e.g., new product, or product overhaul), more formal vision work with ample time and fidelity is essential to bring stakeholders together and provide clarity in the long-term. 

For Lyft to reimagine the rider app in a high-fidelity prototype, it took ~6 months with bi-weekly exec reviews. Whereas a vision exercise for the sign-up flow in sketch-form took less than a week. Again, the best move here is to discuss the timeline and goals with your design partner.  

The best part about a north star is that once the team has clarity on the long-term vision, you can usually break it into incremental steps that are easier to roll-out and measure than the whole kit-and-caboodle. The design work for the near-term will now be much stronger because not only will it account for today’s constraints but future plans as well. 

Tip #5: Create shared goals

There's a dangerous tendency for both designers and PMs to talk about "design goals" as distinct from "business goals." This phrasing undermines the importance of the “design goals” and suggests that designers aren't concerned with what drives the business. Some of the things people call design goals are consistency, usability, accessibility, and delight. Guess what. All of these things drive use, conversion, and loyalty. All things that are critical to the success of the business.

What's going on here is a difference in the level of zoom. For example, consistency of the system is a sub-goal of usability which is a sub-goal of conversion. By talking about how these sub-goals relate to each other and play off each other, you and your team can better define, prioritize and sequence shared goals. This is not only essential to align and focus the team but to ensure everyone is motivated by knowing how their priorities connect to the goals of the team. 

Where this can get challenging is when the designer says, “We need to update the buttons so they’re consistent,” and the PM says, “We don’t have time to do it. It’s not as important as these other things right now.” They’re both potentially correct and perhaps the consistency work will need to wait, but ignoring this work just because its impact is indirect or even immeasurable is not an option. The details are notoriously easy to ignore, however when you think about a product that feels high-quality, trustworthy, and simple you’ll see strong attention to detail. While a user is not going to take the time to report a lack of consistency in the button types, and may not abandon your product right away, these gaps will start to make them wonder about where else you fail—Safety? Security? 

Lean on your design partner to help determine the importance of and sequencing of user experience improvements. Many companies set aside time every quarter and/or require a percentage of the roadmap be devoted to the user experience improvements that contribute indirectly to the bottom line. This is certainly better than nothing, but the more you can get it right the first time, the better! 

—

Many of the above recommendations are good business for any multi-disciplinary team. Collaboration requires empathy, transparency, and respect. The most important thing you can do is have a conversation about how you will work together and check-in with each other frequently. Recognizing our similarities, as well as our differences, makes for a really powerful combination when respected and managed well. 

Lastly, one important recommendation….  stop saying “my designer.” This phrase sets up a false and unuseful hierarchy. While a subtle change, the phrase “my design partner” makes a world of difference that sounds far more inclusive and better enables collaboration.  

Good luck and happy collaborating!

Special thanks to Lenny, Vanessa Cho, and Liv Jenks for editing help. And thank you all for your terrific responses to my question on twitter.

🔥 Job opening of the week: Director of Product at Berbix

Berbix is hiring a Director of Product to lead our product team and set our product direction in service of transforming identity online.

Learn more

Additional opportunities:

1. Product: Clearbanc, Decent, Rocketplace, Transform, Twine, Wrapbook

2. Growth: BasisOne, SpaceX Starlink

3. Design: Ashby, Berbix, Instrumentl, Office Hours, Primer, Runway, Watershed

4. Frontend engineer: Levels, Practice

5. Backend engineer: Driveway, Pogo, Reclaim, Transform, Wrapbook

6. Fullstack engineer: Centered, Emporii, Icebreaker, Iggy, Mem, Runway, Snackpass, Sorare, Stytch, Wrapbook

7. Mobile engineer: Primer, Stytch

8. Game economy designer: Sorare

How would you rate this week's newsletter? 🤔

Great • Good • Meh

If you’re finding this newsletter valuable, consider sharing it with friends, or subscribing if you haven’t already.

Sincerely,

Lenny 👋