💡

InsightHunt

Hunt the Insights

N

Nikita Miller

SVP & Head of Product

The Knot Worldwide

👥 Team & Culture (1)⚡ Execution (1)🎯 Product Strategy (1)

Key Takeaways

  • 1.While outcomes are critical, output is a leading indicator; teams that don't ship frequently get fewer 'shots on goal'.
  • 2.Define clear 'social contracts' for roles and responsibilities between Product, Design, Engineering, and Data to prevent friction.
  • 3.Data scientists should be embedded in product teams (quads) rather than treated as a centralized service bureau.
  • 4.For distributed teams, solve 'gnarly' strategic problems by meeting in-person for intense 48-hour summits.
  • 5.The PM role is swinging back towards being more technical; understanding data and engineering constraints is increasingly required.
  • 6.Use 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 →