Evidence receipt / preference
Published · transcript-backedKatie Dill: preference
15 Oct 2023 Lenny's Podcast Building beautiful products with Stripe’s Head of Design | Katie Dill (Stripe, Airbnb, Lyft)
“" I really love the multidisciplinary approach, but then when we do the calibration after the team has done these walkthroughs and they've gotten their own perspective and they fill out the scorecard based on our rubric for quality, we will come together in what we call PQR, product quality review.”
Source trail
Everything needed to verify it.
- Speaker
- Katie Dill
- Attribution
- Verified speaker
- Claim type
- preference
- Recorded
- 15 Oct 2023
- Publisher
- Lenny's Podcast
Transcript context
…Yeah. So, I want to try to give people a few more answers to questions when they're probably going to try to do this themselves. Who's in these meetings? Do you join these walkthroughs? Does David join? What do you suggest there? Yeah. For what we're doing for each team is they do them themselves together. At bare minimum, it should be the engineer, product manager and designer doing it together. The reason why we like to see it happen together is, again, as we've talked about before, is that people bring a different perspective to something. Let's say somebody in the room might be like, "Oh my goodness, the load time didn't feel really good there." And like, "Oh, whoa, the way we're stating this is not consistent per page. And that's not on our design system." So, it is really powerful to have folks come together and do it. In fact, David Singleton, who you mentioned, he and I do these things very regularly, too. This is outside the essential journeys program, but he and I walk the store and we'll just pick random flows and go through it together. I can't code, but he can. So, he'll do the code part and I'll be sitting there being, "What? Do they really do that? How can we make that better for them? " I really love the multidisciplinary approach, but then when we do the calibration after the team has done these walkthroughs and they've gotten their own perspective and they fill out the scorecard based on our rubric for quality, we will come together in what we call PQR, product quality review. And they will take us through what they have experienced, and then they'll talk about, "So, this is why we've scored this, a yellow or a yellow green." Then we might have a conversation about that. It's like, "Well, actually, that felt a little worse than you've described it. Actually, I think that we probably need to put more urgency on solving that." Or in some cases it's like, "Actually, that was pretty great. If you think about what we're trying to help somebody achieve at this moment that actually is really hitting the mark." We will debate that there. In those meetings you'll have, yes, myself, David Singleton, Will Gaybrick, who leads product and business, and then various leaders from the organization that might be relevant to that area. We are trying to give people insight to what's happening across. Again, it's a multidisciplinary room. I'm trying to keep it not too large, because obviously it can be hard to have discussion, but it is very valuable to make sure, again, that we have the perspective of product marketing and the perspective of engineering, the expected product in the room as we discuss what our quality bar is. Awesome. Okay. That makes a lot of sense. In terms of scoring, are you scoring individual steps of these journeys or is it yellow for segments? What are you scoring?…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.