💡

InsightHunt

Hunt the Insights

N

Nikita Miller

Episode #227

SVP & Head of Product

The Knot Worldwide

👥Team & Culture⚡Execution🎯Product Strategy

📝Full Transcript

11,030 words
Nikita Miller (00:00): And many of the companies that I've either worked with or advised, coached over the past few years, it was all about outcomes. Everyone was, "Outcomes, outcomes, outcomes," which is right. You want to make sure you're doing the right thing with the right goal, and that's fine. And some folks, myself included at certain points, swung way too far on the outcomes train and forgot that output is an indicator of that. So if you have a team that's doing all of the ideation and figuring out 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. Lenny (00:52): Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard one 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 Dooly, 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. (01:51): This episode is brought to you by wealth fronts. Anyone pay...

💡 Key Takeaways

  • 1While outcomes are critical, output is a leading indicator; teams that don't ship frequently get fewer 'shots on goal'.
  • 2Define clear 'social contracts' for roles and responsibilities between Product, Design, Engineering, and Data to prevent friction.
  • 3Data scientists should be embedded in product teams (quads) rather than treated as a centralized service bureau.
  • 4For distributed teams, solve 'gnarly' strategic problems by meeting in-person for intense 48-hour summits.
  • 5The PM role is swinging back towards being more technical; understanding data and engineering constraints is increasingly required.
  • 6Use the question 'What are you optimizing for?' to force alignment on trade-offs across short, medium, and long-term horizons.

📚Methodologies (3)

👥 Team & Culture

A structured exercise where leads from Product, Design, Engineering, and Data explicitly write down their expectations for themselves and each other to create a shared agreement.

Core Principles

  • 1.The Quartet Structure: Move beyond the Triad (PM/Eng/Design) to include Data Science as a core partner.
  • 2.Reciprocal Definition: Individuals write expectations for their own role AND what they expect from their counterparts.
  • 3.Negotiated Agreement: Review the written expectations together to identify gaps (e.g., who handles ticket breakdown) and agree on a 'contract'.
  • +1 more...

"I have them sit down and write [expectations] for each other... and then we arrive at essentially a contract with one another about what we think that looks like."

#cross-functional#responsibility#contract
View Deep Dive →
⚡ Execution

A counter-narrative to 'outcomes over outputs.' While outcomes are the goal, output (velocity) is the necessary leading indicator that predicts the likelihood of achieving those outcomes.

Core Principles

  • 1.Velocity as Strategy: The more 'shots on goal' (experiments/features) you ship, the higher the probability of finding the winning outcome.
  • 2.Cycle Time Audits: Routinely ask 'What did you deliver to production?' and 'How long was the cycle time?' to identify blockers.
  • 3.Bias for Production: Ideation and briefs are necessary, but they are zero value until code hits production.
  • +1 more...

"If you have a team that's doing all of the ideation... but if you're also not shipping a lot of things to market quickly enough, then it just doesn't matter that much."

#output#outcome#indicator
View Deep Dive →
🎯 Product Strategy

A forcing function question—'What are you optimizing for?'—applied to every level of decision making, from quarterly planning to daily prioritization.

Core Principles

  • 1.Define the Time Horizon: Are we optimizing for this sprint, this quarter, or the 3-year vision?
  • 2.Constraint Recognition: Acknowledge that you cannot optimize for speed, quality, and scope simultaneously.
  • 3.Dynamic Re-evaluation: As new data arrives (e.g., Q1 results), the optimization goal for Q2 must be explicitly re-verified.
  • +1 more...

"I ask myself and I ask everyone... 'What are you optimizing for?' ... If that isn't clear, then the trade-offs aren't going to be clear."

#optimization#heuristic#strategy
View Deep Dive →
← Browse All Episodes