Skip to content
Lenny's PodcastLenny's Podcast

Driving alignment within teams, work-life balance, and the changing PM landscape | Nikita Miller

Nikita Miller is a product leader, angel investor, and advisor. She has built and led product teams at companies ranging from early-stage startups to multinationals, and she is currently SVP of Product Management at The Knot Worldwide. Nikita is passionate about scaling product teams to support high-growth businesses and was a product leader at Trello and Atlassian for five years. In today’s podcast, we cover: • Lessons from building and growing Trello • Nikita’s roles and responsibilities framework • How the PM landscape is changing • Lessons about managing remote teams • Tactics for driving urgency within teams • Why working cross-culturally was such a formative experience — Brought to you by Wealthfront—Make smarter stock investments | Lenny’s Job Board—Hire the best product people. Find the best product gigs | Ahrefs—Improve your website’s SEO for free Find the full transcript at: https://www.lennyspodcast.com/driving-alignment-and-urgency-within-teams-work-life-balance-and-the-changing-pm-landscape-nikita-miller-the-knot-trello/#transcript Where to find Nikita Miller: • Twitter: https://twitter.com/nikitadyer • LinkedIn: https://www.linkedin.com/in/nikitadyer/ Where to find Lenny: • Newsletter: https://www.lennysnewsletter.com • Twitter: https://twitter.com/lennysan • LinkedIn: https://www.linkedin.com/in/lennyrachitsky/ In this episode, we cover: (00:00) Nikita’s background (03:56) How Nikita helped Trello develop enterprise features  (09:41) Trello vs. Jira (10:28) Similarities and differences between building for users at The Knot vs. Trello (15:02) Pro tips for Trello users (15:41) Nikita’s roles and responsibilities framework (21:10) Why scrum masters are disappearing and what shifts are happening on teams (21:56) Why every team should have a data scientist embedded in it (23:27) The proper cadence for the rules and responsibilities framework, and problems around execution (25:27) Outcomes and output (28:34) The importance of urgency, and how to cultivate a sense of urgency (29:52) How to determine if your team is moving quickly enough (31:03) Prioritization between big bets and optimizations (31:29) Questions Nikita asks to understand her team’s speed  (33:30) Changes in the field of product management (36:42) Advice for people who want to get into product (38:40) Why being a PM is hard, and thoughts on work-life balance (43:03) How to manage remote teams and how to do successful, short, in-person meetups (47:59) The importance of having overlapping work hours and onboarding in person (49:09) The advantages of working in different cultures  (52:58) The question Nikita finds most useful (55:07) Lightning round Referenced: • Trello: https://www.atlassian.com/software/trello • The Knot: https://www.theknot.com/ • Jira: https://www.atlassian.com/software/jira • Roles and Responsibilities template: https://www.atlassian.com/team-playbook/plays/roles-and-responsibilities • OKR examples: https://www.whatmatters.com/get-examples • Set goals with OKRs: https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/ • Objectives and Key Results (OKRs): https://www.atlassian.com/team-playbook/plays/okrs • Amp It Up: Leading for Hypergrowth by Raising Expectations, Increasing Urgency, and Elevating Intensity: https://www.amazon.com/Amp-Unlocking-Hypergrowth-Expectations-Intensity/dp/1119836115 • Nikita’s LinkedIn post on working abroad: https://www.linkedin.com/feed/update/urn:li:activity:7039394235304824832/ • You Will Hear Thunder: https://www.amazon.com/Will-Hear-Thunder-Anna-Akhmatova/dp/0821408062 • The Fire Next Time: https://www.amazon.com/Fire-Next-Time-James-Baldwin/dp/067974472X/ • High Output Management: https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884 • Crash Landing on You on Netflix: https://www.netflix.com/title/81159258 • Arc browser: https://arc.net/ • Josh Miller on Lenny’s Podcast: https://www.lennyspodcast.com/competing-with-giants-an-inside-look-at-how-the-browser-company-builds-product-josh-miller-ceo/ Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Disclosure: I am a Wealthfront client and I have received non-cash compensation for the testimonial in this episode.

Nikita MillerguestLenny Rachitskyhost
Apr 6, 202359mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:003:56

    Nikita’s background

    1. NM

      ... and many of the companies that I've either worked with, or advised, or coached over the past few years, it was all about outcomes. Like everyone was outcomes, outcomes, outcomes. Which is right. You wanna make sure you're doing the right thing with the right goal and that's fine. And some folks, you know, myself included, at certain points, like swung way too far on the outcomes train and forgot that, uh, output is an indicator of that. So if you have a team that's doing all of the ideation and figuring out, you know, how to make decisions quickly and getting the right documentation and setting up the right product briefs and design briefs and experiment briefs. All the things that we know go into successful product development. That's great, but if you're also not shipping a lot of things to market quickly enough, then it just doesn't matter that much.

    2. LR

      (intro music plays) Welcome to Lenny's podcast where I interview world class product leaders and growth experts to learn from their hard won experiences building and growing today's most successful products. Today my guest is Nikita Miller. A huge thank you to Camille Ricketts for recommending Nikita and for connecting us. Nikita is senior vice president and head of product at The Knot Worldwide. Before that she was VP of product at Duulip and before that she was head of growth and retention at Trello for over five years. In our conversation we dig into how product managers and people getting married are similar, a bunch of advice on getting into product management, a really cool framework for how to align roles and responsibilities within your cross functional teams, a bunch of advice for working effectively as a remote and distributed team, and the one question that Nikita asks constantly to get the most out of her teams. Nikita is amazing and I am excited for you to learn from her. With that, I bring you Nikita Miller after a short word from our sponsors. This episode is brought to you by Wealthfront. Anyone paying attention to the stock market over the past few years knows it's been a wild ride. Many people who made risky stock bets during the bull market are now facing big losses and wondering how to make better informed investments going forward. That's why I'm excited to tell you about Wealthfront's new stock investing product which is specifically designed to help you make better stock investments. It has all the features you'd expect including fractional shares, zero commissions, and a one dollar minimum. But what sets it apart is a unique feature called stock collections. These are groups of stocks created by Wealthfront's investment team that are designed around unique investment opportunities. You can think of Wealthfront stock collections like Spotify discovery playlists, but instead of helping you find new songs, they help you discover new companies and themes to invest in. For example, some popular collections right now are dividend to blue chip stocks, semiconductor leaders, and rising interest rates. And each collection includes a summary of the opportunity and trade-offs to help you make more intelligent investing decisions. To start investing with just one dollar, visit wealthfront.com/lenny. And note, I am a Wealthfront client and they arrange for me to share this product with you. Important disclosures and details can be found in the show notes. Are you hiring? Or, on the flip side, are you looking for a new opportunity? Well, either way, check out lennysjobs.com/talent. If you're a hiring manager, you can sign up and get access to hundreds of hand-curated people who are open to new opportunities. Thousands of people apply to join this collective and I personally review and accept just about 10% of them. You won't find a better place to hire product managers and growth leaders. Join almost a hundred other companies who are actively hiring through this collective. And if you're looking around for a new opportunity, actively or passively, join the collective. It's free, you can be anonymous, and you can even hide yourself from specific companies. You can also leave any time, and you'll only hear from companies that you want to hear from. Check out lennysjobs.com/talent.

  2. 3:569:41

    How Nikita helped Trello develop enterprise features

    1. LR

      Nikita, welcome to the podcast.

    2. NM

      Yay, Lenny. Thank you. I'm excited to be here.

    3. LR

      I'm excited to have you. So I don't know if you know this, but I'm actually having a kid in a couple months and I've been doing a lot of reading-

    4. NM

      Mm-hmm.

    5. LR

      ... as you do when you're gonna be a parent. And I was reading a lot of stuff on The Bump, which turns out I realized was something that was in your umbrella of products and then I-

    6. NM

      A part of The Knot Worldwide, yeah.

    7. LR

      Yeah. And then I realized y'all have that for pregnancy, you have a site to help you with proposals, you have a site for obviously wedding planning and vendors and, and just party planning in general. And so is the general strategy to ha- like be there for every adulting milestone in life? Is that, is that the plan?

    8. NM

      Yes. That's a nice way of putting it. We talk about it as being there for the big celebrations in life.

    9. LR

      Mm-hmm.

    10. NM

      Like we have these celebratory m- moments that mark adulthood.

    11. LR

      Mm-hmm.

    12. NM

      And so to be part of that journey. We primarily focus in the wedding space, but yes, across the whole journey.

    13. LR

      Feels like the one, the two pieces you're missing are divorce and funerals.

    14. NM

      Uh, right. (laughs)

    15. LR

      Uh, is that, is that, is that the plan or, uh, do you wanna stick to happy things?

    16. NM

      I think we're sticking to celebrations.

    17. LR

      Mm-hmm.

    18. NM

      I think we're leaning on the world needs a lot more celebration right now.

    19. LR

      Okay. I-

    20. NM

      So helping folks do that.

    21. LR

      Hear, hear. Okay, cool. It's a really smart strategy, makes a lot of sense.

    22. NM

      Mm-hmm.

    23. LR

      Like once you get someone, you know, with their wedding and then you kind of expand from there.

    24. NM

      Right. And their friends too.

    25. LR

      Mm. Interesting. Right, 'cause they register on The Knot and they're like-

    26. NM

      Yeah. They register on The Knot.

    27. LR

      ... "Yo, what's going on here?"

    28. NM

      That's right. They register on... Yeah.

    29. LR

      Genius. Well, so we're gonna talk about some of the things you've learned along your time there. But, uh, I wanted to start with your previous gig at Atlassian and specifically-

    30. NM

      Yeah.

  3. 9:4110:28

    Trello vs. Jira

    1. NM

    2. LR

      Got it. Coming back to the question of, like, Trello versus Jira, 'cause I think this might be interesting to people, just, like, if you're trying to decide-

    3. NM

      (laughs) .

    4. LR

      ... should we use Trello or should we use Jira, what's, like, a simple way to think about which way to go as a f- as a founder maybe or as a product team?

    5. NM

      I think that smaller teams, especially folks that are ideating, right, when you haven't landed on what you're gonna build yet, I think Trello is a great product for that, for pulling ideas, for prioritizing them, for, for tracking how we're progressing through, like, discovery. I think Trello is really great for that. For things that have been decided and are ready to go and are really in the breakdown these tasks and assign it to people, then something like Jira is probably a better use case, uh, but I'm sure there are people that'll disagree

  4. 10:2815:02

    Similarities and differences between building for users at The Knot vs. Trello

    1. NM

      with that.

    2. LR

      (laughs) Cool. Building for PMs is what you were doing while you were working on Trello.

    3. NM

      Yeah.

    4. LR

      I imagine that's kind of a bittersweet experience. Uh, I imagine some sense, they're like an amazing market to sell to, on the other, they're probably really annoying. What's like a surprise maybe or a lesson about working on building products for product managers?

    5. NM

      I think you're right, it is a bitter s- sweet place to be. I think I, I less thought of it as building for product managers and just thought about it in the context of productivity.

    6. LR

      Mm-hmm.

    7. NM

      Overall. And productivity software in itself is really what's bittersweet because-

    8. LR

      Mm.

    9. NM

      ... there are a lot of trade-offs. And when you're dealing with a software team, for instance, how you measure productivity or define it for a PM or designer or engineer or a data scientist is probably really different. And so the impossibility of solving for all of those use cases, I think is always what's challenging. And we know that no one product is actually gonna solve all of those use cases no matter what the marketing taglines are out there.

    10. LR

      Mm-hmm.

    11. NM

      And so it was really challenging to figure out, well, what are the core things that a product manager might need to see or a designer or a developer and how do you make sure that that core is there? So, like, you get the 80% and, and then you spend time on the 20% that you know that a very small segment of users are gonna use, but they're probably your core, so, so maybe you spend some time there. But yeah, the answer is no one's gonna be happy.

    12. LR

      Mm-hmm.

    13. NM

      And with Trello, in particular, it was challenging because for a while we were in the, we built a product that was easy to use for everyone, and so then trying to really narrow in on, well, what is a software development use case and what do we really need for that? And that might be very different from what a mom and pop-... you know, shop is gonna need or someone planning their wedding is gonna need.

    14. LR

      That's a good segue to something else I wanted to ask about.

    15. NM

      Yeah.

    16. LR

      You used to build for product managers, now you build for people getting married. I'm curious what is similar about those two groups and what's maybe most different?

    17. NM

      Yeah. Um, a lot of similarity. (laughs)

    18. LR

      Hmm.

    19. NM

      So folks planning their weddings, I mean, think of it as an emotional high-stakes thing that you're hopefully gonna do once, and so the pressure is really there. The pressure and expectations are really high, not unlike product managers or other folks in software. And ultimately wedding planning is this huge project, right? Where you have a bunch of stakeholders, friends, family. You need to manage multiple vendors, and the time horizon for a wedding, once you're engaged is anywhere from like 12 to 18 months, so it is a longtime project. So yeah, I think there's a lot of similarities there. Some of the things that are a little bit different, in terms of how we're building the product is, the amount of decisions probably that need, that go into wedding planning are far more than you would imagine. So one of the reasons being at The Knot is so interesting is we go all the way from planning tools, so actively how do you help people find insbr- inspiration and plan their wedding day to day, to our marketplace, our two-sided marketplace. We have our e-commerce business that's supposed to ... be like registry and paper, and obviously our affili- affiliate businesses and the ads businesses. So it's a little bit different from a SaaS productivity tool, the business that we're in, but a lot of the problems that we're solving for users are actually really similar.

    20. LR

      Hmm. Which one's more, uh, I don't know, stress inducing?

    21. NM

      That's a great question. I think that, uh, I mean, couples, like this is a, uh, it's such an emotional thing for people, for individuals and their families and their friends, so I think I, I personally feel like I empathize with that in a way that I might, that I don't do the same for product even though I'm a product manager because there are many projects and there are always things that we need to manage and that's just part of the gig. Whereas planning your wedding for couples, like this is for many the most meaningful time of their lives, and everyone does this differently. So we have folks that are planning their multi-hundred, you know, person weddings and their 10, 15 closest friends' weddings. But the emotional side of it is the same, and, and you don't wanna let them down because most aren't gonna do it again.

    22. LR

      Yeah. Okay. That's what I would've guessed. Feels like wedding couples are-

    23. NM

      Yep. Wedding couples are-

    24. LR

      ... gonna be more stressed.

    25. NM

      Yeah.

    26. LR

      I just had an idea. Imagine you think about this. Uh, we're doing a baby shower right now and, uh, feels like you're missing a opportunity to do a-

    27. NM

      (laughs)

    28. LR

      ... baby shower invite platform.

    29. NM

      Yes. We've-

    30. LR

      Okay.

  5. 15:0215:41

    Pro tips for Trello users

    1. LR

      One last question about Trello. Do you have any just pro tips for someone using Trello and may not be aware of something they could do with Trello?

    2. NM

      I think the biggest that people probably know about but are often underutilized are power-ups, which is basically our integrations, and power-ups are folks that are usually doing things that are more complex often. But Trello, you know, when you think about it with other products like Asanas, you mentioned Linear, some of what people are worried about is that it's just not, not powerful enough, and power-ups are a way to do that, and there are dozens and hundreds of integrations that you can use it for, so that's worth checking out.

    3. LR

      Awesome. Great tip.

    4. NM

      Yep.

  6. 15:4121:10

    Nikita’s roles and responsibilities framework

    1. NM

    2. LR

      Shifting a little bit and-

    3. NM

      Mm-hmm.

    4. LR

      ... and kinda zooming out, you've worked at a lot of different companies, at a lot of different levels, also a lot of different geographies, uh, and I wanna chat about that last piece. But maybe just broadly, what are a few of your biggest lessons about building teams, building successful and impactful teams?

    5. NM

      This is kind of my jam.

    6. LR

      Hmm.

    7. NM

      It's like- (laughs)

    8. LR

      Excellent.

    9. NM

      Well, that's kind of what I, I spend a lot of time thinking about, and, um, I think every company you go into you approach it slightly differently. For me it usually starts with, um, for individuals kind of identifying very clearly early on roles and responsibilities.

    10. LR

      Hmm.

    11. NM

      Like what are the expectations of a role? So in software for most of us, one of the things that I think I've seen done well or contributed to in multiple companies is the triad: product, design, engineering, data. And what does it look like for these roles and data science that's like other, uh, support-

    12. LR

      Yeah. It's interesting you put data in there. That's cool.

    13. NM

      I'm trying to pull that in. That's my, that is my mission. (laughs)

    14. LR

      That's great. I love that.

    15. NM

      My mission is product design, engineering, data.

    16. LR

      It's not a triad anymore though, but, uh, I love it.

    17. NM

      I know. It's like, uh, yeah, quartet something.

    18. LR

      A quad. It's a chair. It's just a chair.

    19. NM

      Yeah. It's a chair. Great.

    20. LR

      Yeah.

    21. NM

      Um, so, so I think about that a lot, like what are the roles? What do you expect for each of them? And how do you define the responsibilities that we have to each other? I know it sounds kind of maybe, you know, on the softer side, but I think a lot of what we can solve for in creating strong teams is exactly that. And the exercise that I often do is I generally have an idea of what I think the role and responsibilities are and the expectations across these four roles, but the exercise especially with leaders in an org is to have them sit down and write them for each other. So Atlassian has some of this that they do in the form of playbooks, but it's basically I as a product leader, I'm gonna write down what I think the expectations and the role and responsibilities of my engineering manager, of my designer, of my data. And then we look at it together and then we arrive at essentially a contract with one another about what we think that looks like and what that responsibility is to our teams. And from there we cascade it throughout the org. This is very time-intensive, right? As, as you can imagine, and often leads to a lot of debate because depending on the kind of orgs or people's backgrounds, our expectations might differ. But I think that contract early on is really important.

    22. LR

      This is, uh, super interesting. I wanna go two levels deeper.

    23. NM

      Yes.

    24. LR

      So what is it that you're... Like, is there a template that you have? Is there specific questions you're answering? Is it free form?... how do you actually know what to write and sort one of these?

    25. NM

      There is a template. There are templates we can probably share-

    26. LR

      Awesome. Great.

    27. NM

      ... after this to kind of run the roles and responsibilities, and it, it usually comes in a couple of forms. It's what the expectations as an IC, what's the expectation kind of as a manager or with your team, and then what is it to each other, and what are the things that are shared, right? So, you know, when we're running an experiment, like a product manager is likely to write a product brief and go into the details of what that means. The data scientist is likely to help write the actual experiment brief, but we're all putting inputs into it. But then when it comes to data and analysis, my expectation is that both of you are doing that together.

    28. LR

      And is the idea the PM writes, "Here's my, what I'm planning to do?" Is it the data scientist writes on behalf of the PM, "Here's what I expect you to do?" Who's kind of taking the charge in each of these?

    29. NM

      You write your own.

    30. LR

      Mm.

  7. 21:1021:56

    Why scrum masters are disappearing and what shifts are happening on teams

    1. NM

    2. LR

      Mm. Is there anything that you find as surprising about, like, what teams end up taking off the PM's plate or putting on the plate that maybe other companies don't?

    3. NM

      I think a lot of people end up putting a lot on the PM's plate.

    4. LR

      (laughs) Yeah.

    5. NM

      Because of that misunderstanding. And so you end up looking at something as a group and saying, "Well, no one human can do all of those things all the time, so let's, let's talk about what the shared responsibility looks like." And what I think is really powerful about the triad is, is that it's a recognition of, of like there are shared responsibilities, you know? Who's responsible for making sure that everyone understands what we're doing and why? The PM leads that, but evangelizing that is something that would be expected of designers and engineering managers and data scientists as well.

  8. 21:5623:27

    Why every team should have a data scientist embedded in it

    1. NM

    2. LR

      On the data scientist piece, you talked about how you're trying to embed that more and more into product teams. At Airbnb, we, or data scientists were embedded in every team, so I totally get that.

    3. NM

      It's not everywhere. (laughs)

    4. LR

      Yeah, exactly. Uh, what more can you share there of just why you found that to be important and how you're approaching that?

    5. NM

      From my experience as a product manager, it was always a blocker, right? Getting your hands on the data, maybe having someone to troubleshoot with if as a PM you couldn't kind of understand or figure it out yourself. It was just always a blocker. And so then you'd als- then have to go and negotiate with other teams about getting someone's resources to look at this problem. So that's one. The other is just that data scientists, as with most humans, like, we get better the more focused we are and the more in depth we are in understanding the product itself, right? So if you have someone that's dedicated to a zone or an area of the product, then, then it's much easier for them to spot patterns as opposed to attempting to understand what's happening every time a ticket comes in.

    6. LR

      And so the shift you're, you push for is instead of like a centralized data team that you convince to give you resources, you embed-

    7. NM

      Right.

    8. LR

      ... the data scientists-

    9. NM

      Embed them.

    10. LR

      ... in the team.

    11. NM

      Right.

    12. LR

      And do you, do you call them data scientists? Do you call them analysts? How do you think about that?

    13. NM

      That also varies per company. (laughs)

    14. LR

      Mm-hmm.

    15. NM

      That, that depends on the organization and kind of the work. Some teams require data scientists, not all. Some require analysts, right? So that just depends on what the team is working on-

    16. LR

      Mm-hmm.

    17. NM

      ... and what's needed.

    18. LR

      Got

  9. 23:2725:27

    The proper cadence for the rules and responsibilities framework, and problems around execution

    1. LR

      it. Coming back to the roles and responsibilities framework, do you encourage teams to revisit that every once in a while, or is it like, "This team's done this thing and we're good for a while"?

    2. NM

      I encourage them to revisit it, and it's usually because something's fallen off the rails. Like, (laughs) I think if I were really great at it, I'd say, "Every three months or like every six months, let's have a look and see how this is going."

    3. LR

      Hm.

    4. NM

      But often it happens because there's some conflict or tension or something was missed and someone thought it was theirs or not, and we have to do a quick retro. Mm.

    5. LR

      What do you find is often that thing that is maybe missed or often causes tension?

    6. NM

      Execution. It's usually around, uh, execution and velocity.

    7. LR

      Mm. Like not moving fast enough or-

    8. NM

      Not moving-

    9. LR

      ... kicking balls.

    10. NM

      ... fast enough, yeah.

    11. LR

      What do you find often is a, a way to help with that as a, as a leader of teams?

    12. NM

      Well, one, just identifying what the velocity issue is. It's-

    13. LR

      Hm.

    14. NM

      It can vary. So for PMs...... it's often around the velocity of decision-making, right? How long does it take us to actually... From saying we need to do a thing-

    15. LR

      Hmm.

    16. NM

      ... to defining it potentially and then deciding are we actually gonna do it or how. And that, I think, takes a long time for most, most companies, most people. So velocity of decision-making, so I think that tends to fall on the PM most often. The actual execution of it, right, the, the development tends to fall on both PM and engineering. So in engineering, I find that, um, depending on the org, you know, some folks understand like breaking up tickets into small pieces and why that's valuable and how to do it. And that's something that I think everyone in industry (laughs) probably needs a refresher on.

    17. LR

      Hmm.

    18. NM

      On like why that's valuable and how it works, and some of that is also shared by the PM because like if you haven't articulated clearly or well enough what we're trying to do, then it is hard to kind of break that, that apart. So yeah, those are the two things that are on my

  10. 25:2728:34

    Outcomes and output

    1. NM

      mind a lot.

    2. LR

      Is there anything else along the lines of what you've learned about building successful teams? I really love this, uh, roles and responsibilities-

    3. NM

      Yeah.

    4. LR

      ... approach.

    5. NM

      Outcomes and output also-

    6. LR

      Hmm.

    7. NM

      ... comes up a lot.

    8. LR

      Mm-hmm.

    9. NM

      And, and I think that in many of the companies that I've either worked with or advised, coached over the past few years, it was all about outcomes. Like everyone was outcomes, outcomes, outcomes, which is right. You wanna make sure you're doing the right thing with the right goal, and that's fine. And some folks, you know, myself included at certain points, like swung way too far on the outcomes train and forgot that, uh, output is an indicator of that. So if you have a team that's doing all of the ideation and figuring out, you know, how to make decisions quickly and getting the right documentation and setting up the right product briefs and design briefs and experiment briefs, all the things that we know go into, to successful product development, that's great. But if you're also not shipping a lot of things to market quickly enough, then it just doesn't matter that much. So that conversation is one that I think we often have to revisit on teams, on all the teams I've ever been on, that yes, outcomes are important, but also the indicator is around execution and velocity. So if that's not in line, then a lot of the other things don't matter that much.

    10. LR

      And so when you say a outcome, you're saying here's the goal they're achieving or the impact they're having, or is it just the idea, like we know what our outcome will be but they're not actually shipping anything? Like what do... When you say output and outcome, what, what are you referring to specifically?

    11. NM

      The, the outcomes or understanding what the goals are.

    12. LR

      Mm. Yeah.

    13. NM

      And what we might do to get there, right?

    14. LR

      Mm-hmm.

    15. NM

      So OKRs-

    16. LR

      Yeah.

    17. NM

      ... is one, one way to talk about that, great. But embedded in that is, and how are we gonna get there? And the fact is like the more tries you have at it, the likelier you are (laughs) to get it right.

    18. LR

      Mm-hmm.

    19. NM

      So we're not actively monitoring like how fast does it get us, take us to ship things to market.

    20. LR

      I see. So kinda like if I can rephrase it, it's-

    21. NM

      Yes.

    22. LR

      ... a lot of teams like know what they're sh- what... talk about what they should be doing. They have a strategy, they have a goal. But what you're finding is that there's just not a lot of action a lot of times and there's like a huge opportunity just to like get a team to actually ship-

    23. NM

      Yeah.

    24. LR

      ... more often and move faster.

    25. NM

      There's... Yeah. There's not a lot of, um, like understanding of our role in urgency like-

    26. LR

      Mm.

    27. NM

      ... right? It's urgent. And, and software in particular, probably can't forget that 'cause someone else is likely doing something similar or better and faster.

    28. LR

      Makes me think of, uh, I think Frank Slootman is his name, uh, the-

    29. NM

      Hey.

    30. LR

      ... Snowflake CEO. He wrote this book called-

  11. 28:3429:52

    The importance of urgency, and how to cultivate a sense of urgency

    1. LR

      that. What have you found helps in creating that sense of urgency and continuing to increase output?

    2. NM

      Mostly reminding people often.

    3. LR

      Mm-hmm.

    4. NM

      Right? And I don't think that this, the question of like, "Well, show me a list of everything you shipped." That's never gonna work. (laughs) Well, that doesn't make people feel good about the work that they're doing. But, but, you know, let's talk about our experimentation backlog, like what do we have in there? How quickly are we getting those things out? Those are the kind of conversations that I think help. Um, I think that having a good pulse on competition helps-

    5. LR

      Mm.

    6. NM

      ... as just a friendly reminder.

    7. LR

      Hmm.

    8. NM

      You know, that there are others out there doing this and thinking about things very similarly possibly to what we're, how we're thinking about it. So how do we differentiate ourselves? And, and a lot of that is about like how quickly are we getting many ideas to market. Small tangent. The, um, the competition side is interesting to me because I've been... I've worked at a few companies where I've ha- worked with founders who are like, "We don't have competition. Like we're the only ones doing this." And, and then fast forward a few years and you're like, "Here are all the companies-"

    9. LR

      Mm-hmm.

    10. NM

      "... that were your competition that you didn't recognize then that are, are shipping great product now."

    11. LR

      Mm.

    12. NM

      So.

  12. 29:5231:03

    How to determine if your team is moving quickly enough

    1. NM

    2. LR

      This might be a tough question, but I think there's always like a sense of we can move faster. Like it's rare that like, no, we're moving fast as we can. Do you have any kind of heuristic or, I don't know, kind of gut feeling of like knowing and sensing like where this team's doing fine versus this team isn't moving as fast as they can?

    3. NM

      How much time do we spend on what I'd consider optimizations versus like bigger bets?

    4. LR

      Mm.

    5. NM

      Right? Like and how long does that... does it take for that to happen? Right? Because I... You know, you, you've talked to the folks or been in the companies where-... where you talk about something that, by most measures, is pretty simple. Like, you know, someone goes heads down for a week or two and gets it done, and you talk about it, and then, you know, two quarters later, someone mentions it again. And you're like, "Oh, okay." So what are all the things we did in between that time to now why that thing, seemingly simple thing, didn't get done? And I think that's hard to say as a product manager because everything we do is all about prioritization, and I'm sure there are a bunch of other things that were prioritized. But they're like these little things that come up periodically, or bug fixes. Like, something is broken, you know, how long does it take us to recognize it and actually fix it?

  13. 31:0331:29

    Prioritization between big bets and optimizations

    1. NM

    2. LR

      Do you have a heuristic, and speaking of big bets versus optimizations-

    3. NM

      Yeah.

    4. LR

      ... of just how much time/resources to put into each bucket?

    5. NM

      Unfortunately, the answer is it depends.

    6. LR

      Yeah.

    7. NM

      Right? If you're working on a business that is 30 years old and has many acquisitions or is very different from a startup, right, or a growth stage company, I think it, it just varies.

    8. LR

      Yup.

    9. NM

      Yeah.

    10. LR

      That's often what I find.

  14. 31:2933:30

    Questions Nikita asks to understand her team’s speed

    1. LR

    2. NM

      Uh.

    3. LR

      One last question along these lines that was-

    4. NM

      Yeah.

    5. LR

      ... on my mind as we're chatting. When you're finding that a team is not delivering as much output as you would think, what have you found works in helping them recognize that and not get defensive and not, you know, have all these excuses for it's happening, just like help them see what you see?

    6. NM

      I'll tell you what I do. I don't, I don't know that I think s- folks might get defensive sometime.

    7. LR

      Yeah. I think-

    8. NM

      But, um-

    9. LR

      Yeah, certainly.

    10. NM

      ... I'll tell you what I try.

    11. LR

      That's, that's good.

    12. NM

      Uh, for me, the, the biggest thing is just, you know, if, if folks are working on a sprint, it's very simply like, "What did you deliver this sprint?" That's it.

    13. LR

      Just asking questions.

    14. NM

      Just ask a bunch of questions. "What did, what did you deliver?" And the more questions, "Okay, fine. But what did you deliver to production?"

    15. LR

      (laughs) .

    16. NM

      "Great. And how long have you been working on that? Like, how long? What was the cycle time?" So these questions that are, that are really just, I think, seeking to understand, because I understand complexity, right, and so that exists everywhere, but maybe helping folks see that as they're reviewing their own work or their team's work goes a long way.

    17. LR

      Yeah, and it comes back to your, your approach of just focusing on the output, not like-

    18. NM

      Yeah.

    19. LR

      ... what they're planning to do, what they've actually done. This episode is brought to you by Ahrefs. You probably know Ahrefs as one of the leading all-in-one SEO tools used by companies like Facebook, Uber, Shopify, LinkedIn, Pinterest, and thousands more. But Ahrefs is not just for big companies. With their new Ahrefs Webmaster Tools, you can optimize your personal website like a professional for free. You can scan your website for over a hundred common SEO issues that might be hurting your performance in search engines, plus get advice on how to fix those errors. You can have it automatically browse your website's internal and external links and get actionable insights from your backlink profiles, and you can learn what keywords your website ranks for and see how you stack up against your competitors. Visit ahrefs.com/awt and start improving your website's visibility. That's ahrefs.com/awt.

  15. 33:3036:42

    Changes in the field of product management

    1. LR

      Shifting a little bit, you've been a PM for a long time, since 2010, I believe.

    2. NM

      Yeah.

    3. LR

      Uh, and a lot of people kind of move out of PM, and so it's really cool to talk to someone that's been in the field for a while.

    4. NM

      (laughs) .

    5. LR

      What have you seen in terms of how product maybe has changed, the role of product management, the role of product leadership, and also maybe other functions like designer, engineering?

    6. NM

      Yeah. I think the biggest change for product, kind of macro, is how, um, mainstream it is-

    7. LR

      Mm-hmm.

    8. NM

      ... that I, I still find fascinating, the getting degrees in product management and going to business school to transition into product management and, like, the whole discipline and there's a whole business, honestly, around the business of product management, which I find really fascinating and didn't exist. And I think, for better or worse, that comes with a lot of good, and in some ways, I think might have removed some of the quirkiness and creativity that probably is required of product. Uh, but that's probably a different podcast (laughs) . So that's one, just macro. In terms of the roles, I think that what we were talking before about roles and responsibilities and, and defining those, for product managers, I think product managers are increasingly, I think, a bit more technical, or expected to be. I think there was a moment where they were technical and then it was, "No, no, we're all generalists," and now I think we're going back to PMs need to be more technical. I think designers, the expectation is that they'll be more business oriented.

    9. LR

      Mm.

    10. NM

      Right? Design as a, as a means, honestly, to an end. I think that's trending and probably for the better. I think the best designers I've ever worked with are also, like, exceptionally savvy business people. And I think engineers are, are increasingly becoming what I, more product focused, more user focused. So, you know, product engineers was something Trello, I think, did ex- really well. This idea that great ideas can come from anywhere in the org and any function I think is really magical. So as you're seeing PMs becoming more technical, I think designers becoming more business oriented, engineers are becoming a lot more product, user focused, to me, that's amazing because it means that we're getting closer to what I'd consider, like, really deep collaboration. And it's not to say that we're not experts. Like, there are expertise within that that we expect of folks, but that care for other disciplines, I think is where a lot of magic happens.

    11. LR

      That's really interesting. When you say PMs getting more technical, what is, when you're hiring, interviewing, what kind of, what are you looking for? Like, do PMs need to learn to code? How technical do you find they need?

    12. NM

      I don't think so, necessarily. I think a lot more PMs are. A lot more PMs are taking boot camps or-

    13. LR

      Mm-hmm.

    14. NM

      ... coding classes, which I think is all to the good. I don't know that it's a requirement, but there is more of that and I think it is very helpful. Similarly, a lot more PMs are taking more, you know, classes or digging more into data analysis, also really valuable. So...Yeah, I don't think it's a requirement. Uh, I am not, like, a technical PM. I don't have a tech background. I think I've been doing it long enough at this point to, to, you know, do okay. But I think it's a benefit.

  16. 36:4238:40

    Advice for people who want to get into product

    1. NM

    2. LR

      You said that, that the PM is becoming more of just, like, a thing with training, classes and courses like that.

    3. NM

      Yeah.

    4. LR

      I did a search once on LinkedIn for how many product managers there are. Uh, guess how many PMs there are in the world, uh, that have the title PM in their LinkedIn profile?

    5. NM

      (laughs) A lot. I'm guessing a lot.

    6. LR

      Two million.

    7. NM

      (laughs) That's wild.

    8. LR

      That's wild.

    9. NM

      Yeah.

    10. LR

      And, and there's 800,000 just in the U.S. and so-

    11. NM

      Wow.

    12. LR

      ... it's like a, a large, a large group that I didn't expect, uh...

    13. NM

      That's huge. Yeah. Back in my, um, ed tech days, a friend of mine, her kids were in school and she came in one day, her son was in grade school at the time, in elementary school, and he had a, like this, you know, match to w- careers, what you see, and they had a person at a computer, this image, and it was product manager. There was a, an option for product manager and that's when I knew. I was like, "Okay. This is, this is mainstream. We're about to become consultants."

    14. LR

      Yeah. I always used to joke no one grows up and is like, "I wanna be a product manager when I grow up," but I-

    15. NM

      Yeah.

    16. LR

      ... think that's starting to actually be a thing.

    17. NM

      It's starting. It's a thing, yeah.

    18. LR

      Yeah. While we're on that topic, I imagine people often ask you for advice on how to get into product management. Do you have any advice there for folks that are listening that maybe wanna get into that?

    19. NM

      There are many ways now (laughs) . I think there are a lot of the, the typical programs that a lot of the big tech companies have, I think is one way. I think getting into startups as a product manager-

    20. LR

      Mm-hmm.

    21. NM

      ... is a pretty awesome way to get into product, because it's just a lot of problem solving. The problem with that is you don't have anyone to teach you the right way, but the product will teach you the right and wrong way if, you know, you're with a team that, that is moving quickly. So yeah. I still think that s- working on smaller products and companies is a way, great way to get into product management, in part because you'll get to touch all of the functions that are kind of required parts of the product discipline, and I think it's hard to get that experience otherwise.

  17. 38:4043:03

    Why being a PM is hard, and thoughts on work-life balance

    1. NM

    2. LR

      The PM role, we haven't talked about this, uh, it's just, like, very hard and very stressful-

    3. NM

      Yes.

    4. LR

      ... and mostly sucks in many ways.

    5. NM

      Yes.

    6. LR

      And we could talk about that if you want. But, uh, it was more of a segue to, um, work/life balance, which I know you have some strong opinions about.

    7. NM

      Yeah. Mm-hmm.

    8. LR

      So I don't know. You could take it either direction, but just, like, thoughts on work/life balance/how hard the PM role is?

    9. NM

      The PM role is really hard. I feel, um, especially now that I'm managing a lot of teams, right, and PMs at a lot of lev- different levels, I do find that periodically I, I remind them with, like, the core of my (laughs) being that, like, I know this is hard, right? Like, it is hard. There are a lot of expectations. You're expected to be competent across many areas all the time. You're expected to have an answer and you're expected to, like, keep your calm and, like, not lose your shit. And that's really hard. It just is. It's stressful, right? So I think I spend quite a bit of time with my team, my PMs, like, helping them understand that I understand that, and so when we're problem solving, let's probably not solve for everything. Let's, like, focus on one of many things that are expected. So yeah. It's really hard. On work/life balance, as I mentioned to you of, like, think about this a lot, I am currently a mom, and as you can imagine, like, that's a lot to, to manage at any given time. And so recently when I think about work/life balance, I don't, I don't use the word balance. I use optimization. (laughs)

    10. LR

      Mm-hmm.

    11. NM

      Right? It's this question of, like, what are you optimizing for right now, whether it's today or this quarter or this year, with the understanding that I don't think you can have it all at the same time all the time. And so I'm, like, increasingly coming to peace with that. Where that's been interesting over the course of my career, I was chatting with my husband about this yesterday, just thinking about it, was early in my career I remember when we had big releases, like, folks would just work nonstop for a couple of weeks. We would stay in the office late. We would come in early. If it was international, we just probably wouldn't sleep because we wanted to make sure we QA'd everything before we released it. Like, and that was an expected part of the product development life cycle, and those were the lot of my early product years and I, and I just did it and it was very exciting and I quite enjoyed it. But even then, the flip side of it for me was I also, I was a runner back then, so if I was training for a half marathon or a marathon, then, like, you know, the next week I'd probably do my long run in the morning and not start work until 10:00 AM. And, like, that was my version of balance. Right? And I think we're all lucky enough, many of us, excuse me, are lucky enough especially in tech that a lot of companies kind of get that form of flexibility. So now fast forward 13 years, it's, it is very similar. It's like I don't, I don't do all of the drop-offs and pickups for the kids, but you know, there are some weeks where I'm like, "This is the week I'm gonna do all of the drop-offs and pickups," or, "This is the day." And that's felt much healthier for me than this expectation that I'm somehow gonna balance it all and everything is gonna be equally great or cared for all the time.

    12. LR

      I think what I'm hearing is, uh, essentially, which I really like and agree with, is, like, sometimes you're just gonna have to go sprint and go hard and work really hard and go long hours, and then that doesn't need to last forever. And then when it's not, enjoy that extra time and kind of, like, buil- rebuild and recharge and do the things you gotta do.

    13. NM

      Yeah. That's, that's about right.

    14. LR

      Yeah. I find the same thing. I find that just, like, working hard is very, uh, correlated with success (laughs) and a lot of times it's just a lot of long hours and sometimes-

    15. NM

      Yes.

    16. LR

      ... you can't balance it-

    17. NM

      Right.

    18. LR

      ... for periods of time.

    19. NM

      Right.

    20. LR

      Yeah.

    21. NM

      And it can also be, you know, at different points in your life.... right?

    22. LR

      Right.

    23. NM

      So right now, at this particular moment in my life, I'm probably not gonna go hard at a super early stage startup, right?

    24. LR

      Yeah.

    25. NM

      Because I believe that you probably need to be in person, and working really hard together for long periods of time. And not everyone feels this way, I know that. (laughs) Like, I've had these conversations with lots of friends and colleagues, but... So personally for me, that's probably not the decision I would make at this moment in my life.

    26. LR

      Yeah, I get that.

  18. 43:0347:59

    How to manage remote teams and how to do successful, short, in-person meetups

    1. LR

      Another area I wanted to touch on is remote work and distributed work. I believe most of your career you were remote or you worked with remote teams and distributed teams, and that's such a on-trend, uh, thing now, where a lot of teams are working hybrid, working remotely, working with distributed teams. What have you learned about being successful working with distributed and remote teams?

    2. NM

      Yes. That's, uh, my entire career has been with remote or distributed teams.

    3. LR

      Wow.

    4. NM

      That's right. Um, when I started, early in my career, I, I lived abroad for a while, I lived in Shanghai, had a core team there, but also worked with a distributed team in Europe and Latin America, which meant all kinds of crazy hours and lots of sprints like we just talked about. Um, things that worked well, one, like documentation, it's a thing. Asynchronous communication, everyone just has to get used to it and better at it. And so increasingly just being better communicators, whether it's on a video or written, I think that's just really important, and everyone building up that muscle is really important. For all of the roles I've been in, this, um, this notion of what does it mean to have really meaningful and valuable in person time that can sustain you for the remote and distributed time is really important. I think a lot of what's happened now in COVID and even now, a lot of teams are, have never met their coworkers. Like they don't onboard in person, they don't have events or off-sites as frequently, and, and I think flexibility is really great, but I think that really, that makes it really hard, and to me what I've figured out, I think, is that it especially makes it hard to solve hard problems.

    5. LR

      Mm.

    6. NM

      Like, solving a hard problem remotely with folks that you haven't spent in person time with, that you haven't broken bread with, that you haven't, like, disagreed with in person and built that trust is just really hard. In fact, it's much harder. So some of the things I've done even here at like The Knot Worldwide is, periodically when there's a really gnarly problem, I like wave the flag and I say, "Hey, everyone, why don't we try and get together for two days and like hash some of this stuff out? And then we can go back to our remote lives." And I think folks have been maybe unsurprisingly very open to that, 'cause I think w- they see the, like not only the efficiency, but the camaraderie that can happen there as opposed to what was happening potentially on, on a, you know, Hangouts or a Zoom call.

    7. LR

      What does that event look like? Like, where do you do it? What's ro- roughly an agenda?

    8. NM

      One, the agenda is pretty tight before we get there. (laughs)

    9. LR

      Mm-hmm.

    10. NM

      Right? Myself or someone else, we're responsible for making sure that that's an, um, a well-articulated agenda that we all kind of agree on before we even get there. So I think that's one. I think 48 hours, two nights, right? And that's important to me because it is the, tends to still just be hours in a conference room or a meeting room during the day, but you do need to build in the, "And let's go have dinner."

    11. LR

      Mm-hmm.

    12. NM

      "Since we're all in person anyway." Or, "Let's have an extended lunch and maybe an extended day." I think that's just really important and even early in my career when I was working more internationally, the company I worked for was pretty amazing because two or three times a year, the entire company globally came together for a week or two. And it made a, a huge difference and many of the folks that I worked with there are still, you know, friends and mentors.

    13. LR

      Are you able to share what was the challenge you were trying to overcome in one of these times?

    14. NM

      Yeah. I, I, I can speak about it generally, which was just-

    15. LR

      Yeah.

    16. NM

      ... we had a change in strategy and we needed to land a couple of core decisions about what we might build, and there were lots of documents and lots of conversations and the, back to the velocity of decision making, like remotely, that can be really hard because with time zones, someone sends a doc, you comment on it, you get to the other day by the end of the week, and so days and days have passed and we still haven't landed it, and people have really strong opinions obviously about something that big. So it was like, "Nope, okay. Great." Wave the flag. And not everyone could make it. Most people could, and the folks who could not were, were yes, on a screen.

    17. LR

      Was there anything specific in that off-site that helped you get to a resolution?

    18. NM

      In that particular one was one very cross-functional-

    19. LR

      Mm-hmm.

    20. NM

      ... and the, the unlock there was giving the data person-

    21. LR

      Mm.

    22. NM

      ... (laughs) the space to educate all of us. That was it. It was like, "You have the floor. Educate."

    23. LR

      Yeah, I find that's often the solution is people just don't have all the same information that they're-

    24. NM

      Yeah.

    25. LR

      ... ba- basing their decision on, and so make sure everyone starts with the same foundation.

    26. NM

      Right.

    27. LR

      Awesome. And it comes back to your, uh, push to get data integrated into every team and make that part of the four quad triad.

    28. NM

      That, (laughs) that chair. It's the chair.

  19. 47:5949:09

    The importance of having overlapping work hours and onboarding in person

    1. LR

      Anything else around remote work or distributed work that you found to be incredibly impactful or important?

    2. NM

      Well, the flexibility of it, that I'm sure we've, you've talked about with others, that is really important. I do think that the Trello! and Atlassian I think did this really well, is having standards around a couple things. The biggest one I think was overlapping work hours. So everyone had general flexibility, but there were some set of hours where everyone needed to be online at the same time for the most part every day, and that made a big difference.

    3. LR

      Mm-hmm.

    4. NM

      Onboarding happened in person.

    5. LR

      Mm-hmm.

    6. NM

      I think that in-person onboarding for new folks is really important.... especially for, for everyone. For any new person or an organization, I think how we work culturally, having a contact that you can reach out to, all of that I think is really crucial. I'm definitely of the so much of my early learning was in person, and I have no idea how we're gonna replicate that in a non-office setting. It's just really hard.

    7. LR

      How long do you try to have that person in the office for onboarding? Is it, like, a week? Is it a few days?

    8. NM

      A

  20. 49:0952:58

    The advantages of working in different cultures

    1. NM

      week. A week.

    2. LR

      Awesome. Shifting a little bit, just a few more questions.

    3. NM

      Yeah. Okay.

    4. LR

      You mentioned you worked in China.

    5. NM

      I did.

    6. LR

      You also worked in the UK for a while. Obviously in the US now. What have you found to be some of the biggest differences in maybe the product culture or just culture in general working in these different areas?

    7. NM

      The confusion around what product management is-

    8. LR

      Mm-hmm.

    9. NM

      ... (laughs) is universal.

    10. LR

      (laughs)

    11. NM

      That's, like, not specific to, to US I think, and the fact that it's changing, that I think was the same. Um, I don't know that I found that many differences in terms of kind of the, the, how we approached goal setting, all very similar, the need for urgency. Like, all those principles, I think this, are the same no matter where you are. Part of what I experienced when I started in Shanghai was the feeling that the product managemer- manager was expected to have all the answers.

    12. LR

      Mm.

    13. NM

      Which as you can imagine was really overwhelming. And so, I remember because I was young and I didn't know that much about product management, and I definitely did not have all the answers, I spent a lot of time helping the team help me find answers. (laughs) And that was a little bit of a culture shift in our team at the time, and I actually think that's kind of carried me through my entire career, right? Which is trying to figure out how to share the product management load so, like, we're, like, equally responsible for what we're building. So, so that was a good, good, like, unintentional learning that I think has been really important for my career. I think that part of that learning that I've had obviously here and, and in London as well was the figuring out how to make room for creativity.

    14. LR

      Mm.

    15. NM

      So in Shanghai and, and also in London at the time, this was a decade now, so many things have changed since then, there just didn't seem to be as much room for ideas to come from anywhere, which I think is also related to what I was saying before.

    16. LR

      Mm-hmm.

    17. NM

      So, like, making space for people across functions to share ideas and then across geographies to share ideas, especially in companies where English might have been the primary language, but most of the employees were not native English speakers. Like, there was a lot of time I think that I felt that I, I wanted to spend and I did on just creating space for people to, like, comfortably share their ideas honestly. And, and that for me was really formative, because I think it's been... Yeah, it's, it's really impacted how I've approached my entire career, and I don't know that I would have had I not had those experiences.

    18. LR

      I was, uh, browsing through your LinkedIn post and you said something just like that, uh, on LinkedIn of just, like, how formative that experience was for you.

    19. NM

      Yeah.

    20. LR

      I know it's not something people can just like, "Hey, I'm gonna go to China and work for a startup," but-

    21. NM

      Serious- Yeah.

    22. LR

      ... it sounds like you recommend working at companies of different cultures, 'cause it feels like it kind of, like, is a lens.

    23. NM

      Yeah. I do. I, I also think, you know, my, I am, um, my family, I'm Jamaican. I'm a Jamaican immigrant.

    24. LR

      Mm-hmm.

    25. NM

      And so all of our experiences inform, like, how we perform our jobs and how we think about problems and, and being able to, to s- to expand that is... Yes, I would recommend it to every and anyone that gets the opportunity, and I think it's really important as product managers, because I think it's really hard to be a product manager if you cannot empathize, right? With the people and problems that you're solving for, and being out of your comfort zone obviously is, is one way to learn empathy. (laughs)

    26. LR

      I love that. One final question. Is there, before we get to a very exciting lightning round, uh, not to, not to not count that,

  21. 52:5855:07

    The question Nikita finds most useful

    1. LR

      those questions, are there just any, like, frameworks or processes or methods that you've found to be very valuable in your career as a product leader that you would wanna share?

    2. NM

      The question I ask myself and I ask everyone (laughs) in my life probably either whether it's on my team or when folks, friends talk to me, I always ask, "What are you optimizing for?" Like, that's the question. It's, "What are you optimizing for?" And it's, you know, the short, medium, long term in product, but it's the what are you optimizing for today, this quarter, this year, whatever time horizon. And I think that can be just a really illuminating way of thinking about obvious- honestly, like, just how are you spending your time? And I think it works for product as well. Like, every time we talk about OKR or goal setting, ultimately it is what are we optimizing for for some period of time? And I think that always for me, whether personally or in product, is very illuminating.

    3. LR

      I love that. I'm pretty sure I've asked that question a thousand times myself. Uh, one thing I find though is people get annoyed with you just like, "Okay, you're such a, such a PM." Just like-

    4. NM

      I know. (laughs) But it worked.

    5. LR

      It does work. (laughs)

    6. NM

      But it worked.

    7. LR

      What are some instances where you deploy this question? Like, is it in a meeting where someone's asking a question or just like, "What are we optimizing for here?"

    8. NM

      I mean, I ask this question, like, all the time.

    9. LR

      Mm-hmm.

    10. NM

      I ask this question to my husband. Like, "What are we optimizing for?" (laughs)

    11. LR

      Yeah. I'm sure, I'm sure he loves it. (laughs)

    12. NM

      He was a PM too, so he gets it.

    13. LR

      Okay. Okay. That's helpful.

    14. NM

      He gets it. Um, I ask this to my five-year-old honestly.

    15. LR

      Wow.

    16. NM

      (laughs) ...five-year-old. Um, it's, uh, we talk about it a lot. Like, now we're going to quarterly planning, all of us, right? And, and now we have information from Q1, so, so let's look at it and say, "Okay. Given what we know now, what are we optimizing for?" 'Cause it might not be the same thing we did before with new information, or it may be. And that's usually just a...... just then helping us get better at figuring out, obviously, how we're doing trade-offs, right?

    17. LR

      That's awesome.

    18. NM

      Because if, if the first point isn't clear, then-

    19. LR

      Yeah.

    20. NM

      ... the trade-offs aren't gonna be clear.

    21. LR

      Yep. The other question is what, what problem are we trying to solve here?

    22. NM

      Yeah. (laughs)

    23. LR

      I feel like I need to make mugs and put these-

    24. NM

      Yes. (laughs)

    25. LR

      ... uh, put these on some mugs for product managers.

  22. 55:0759:19

    Lightning round

    1. LR

      Well, with that we've reached our very exciting lightning round. I've got six questions for you. Are you ready?

    2. NM

      Uh, yes. I don't think I prepped this, but I'm ready. Yes.

    3. LR

      Okay. Well, it'll be the most fun then. What are two or three books that you recommend most to other people?

    4. NM

      These are not product books. I recommend, uh, Ana Akhmatova's You Will Hear Thunder, a book of poetry that is excellent. Um, I recommend almost anything by James Baldwin. The Fire Next Time, I most recently re-read. And on back to software, High Output Management.

    5. LR

      What are some favorite movies or TV shows that you've recently watched that you really enjoyed?

    6. NM

      Um, I'm really into K-dramas right now, and actually, um-

    7. LR

      Is that a Korean drama?

    8. NM

      ... Korean dramas right now. (laughs) Um, Crash Landing on You is, you know, it's great. It's a love story.

    9. LR

      Wow.

    10. NM

      It's wonderful.

    11. LR

      Cool. Very out of the box. I love it.

    12. NM

      (laughs)

    13. LR

      What's a favorite interview question that you like to ask?

    14. NM

      For product managers, if we think about product in the context of artist, scientist, general, general manager, where do you spike?

    15. LR

      Artist, scientist, general manager. Interesting.

    16. NM

      Mm-hmm.

    17. LR

      And is there one you ideally look for the answer, or it depends on the role you're hiring for?

    18. NM

      It totally depends on the composition of my team.

    19. LR

      Interesting. Cool. I like that. A different triad. What's a favorite product you recently discovered that you love?

    20. NM

      Arc-

    21. LR

      Mm-hmm.

    22. NM

      ... by The Browser Company. I think they're a product that's clearly having a lot of fun, and you can feel that in the product. They, when I first opened it, they have an unveiling experience, which isn't something you'd expect of a browser, and there was something really delightful about it.

    23. LR

      Yeah. I imagine you've heard the, uh, interview with Josh.

    24. NM

      I did. (laughs)

    25. LR

      What a guy. What a cool product. I love it. We have a whole hour and a half on it, so-

    26. NM

      Yeah.

    27. LR

      ... check that out if-

    28. NM

      (laughs)

    29. LR

      ... anyone wants to learn more about Arc. What is something relatively minor you've changed in your product development process that has had a tremendous impact in your team's ability to execute?

    30. NM

      Helping product teams triads, product design, engineering, and data, understand their shared roles and responsibilities.

Episode duration: 59:19

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode 4PhfAbRQpbI

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome