Driving alignment and urgency within teams, work-life balance, and the changing PM landscape | Nikita Miller (The Knot, Trello)
Lenny interviews Nikita Miller, SVP and Head of Product at The Knot Worldwide, about her insights on product management, building high-impact teams, aligning roles and responsibilities, and effective remote work strategies, drawing from her experience at Trello and The Knot.
Deep Dive Analysis
18 Topic Outline
The Knot Worldwide's Strategy and Adulting Milestones
Trello's Ideal Users and Evolution
Growing Trello's Enterprise Business
Deciding Between Trello and Jira
Building Products for PMs vs. Wedding Planners
Pro Tips for Trello Users: Power-Ups
Nikita's Roles and Responsibilities Framework
Shifts in Team Roles and Project Management
Importance of Embedded Data Scientists in Teams
Revisiting Roles and Responsibilities: Execution Challenges
Balancing Outcomes and Output for Team Success
Cultivating Urgency and Measuring Team Speed
Changes in the Product Management Field
Advice for Getting into Product Management
Challenges of the PM Role and Work-Life Optimization
Successful Strategies for Remote and Distributed Teams
Advantages of Working in Different Cultures
Nikita's Most Useful Question for Teams
4 Key Concepts
Product Triad (or Quad)
This framework defines core roles and responsibilities within a cross-functional product team, traditionally including Product, Design, and Engineering. Nikita advocates for expanding this to a 'quad' by embedding Data Science, recognizing shared responsibilities and distinct expertise across these functions to foster deep collaboration and shared understanding.
Outcomes vs. Output
Outcomes focus on achieving the right goals and impact, which is crucial. However, teams sometimes overemphasize outcomes and neglect output, which is the actual shipping of features and ideas to market. Output serves as an indicator of progress towards outcomes; without sufficient output, even well-defined outcomes may not be realized.
Work-Life Optimization
Instead of aiming for a constant 'balance,' this concept suggests consciously deciding what to prioritize (optimize for) in different periods—whether it's a day, quarter, or year—understanding that it's not always possible to give equal attention to all aspects of life and work simultaneously. It acknowledges that sometimes intense work sprints are necessary, followed by periods of recharge.
Progressive Disclosure (Trello)
Trello's design philosophy where the product starts with simplicity and gradually reveals more sophisticated features as users' needs evolve. This allows for easy onboarding for new users with small problems, while still growing with them as their use cases become more complex, contrasting with products that begin with inherent complexity.
10 Questions Answered
The Knot Worldwide aims to be present for all major adulting milestones, specifically focusing on celebratory moments in life, primarily within the wedding space, but expanding across the entire journey from proposals to pregnancy.
Trello is ideal for smaller teams, especially during the ideation and discovery phase of a project, for pulling ideas, prioritizing, and tracking progress. Jira is generally better for tasks that have been decided and are ready for breakdown and assignment to specific individuals.
Teams can improve clarity by having each member (e.g., Product, Design, Engineering, Data) write down their own role and responsibilities, as well as their expectations of their counterparts. These documents are then reviewed together to form a shared 'contract' on team responsibilities.
Outcomes refer to achieving the right goals and impact (e.g., OKRs), while output refers to the actual shipping of features and ideas to market. While outcomes are important, sufficient output is a critical indicator of execution and velocity, as more attempts increase the likelihood of success.
Leaders can cultivate urgency by regularly reminding teams of their goals, discussing experimentation backlogs and shipping speed, and using competition as a friendly reminder. Asking questions like 'What did you deliver this sprint?' and 'What was the cycle time?' helps teams reflect on their velocity.
The PM role has become more mainstream, with formal education and a dedicated industry. PMs are increasingly expected to be more technical, while designers are becoming more business-oriented, and engineers more product/user-focused, fostering deeper cross-functional collaboration.
Instead of 'balance,' Nikita suggests 'work-life optimization,' where one consciously decides what to prioritize for a given period (day, quarter, year). This acknowledges that it's not always possible to give equal attention to all aspects of life and work simultaneously, allowing for periods of intense work followed by intentional recharge.
Key strategies include strong documentation and asynchronous communication, building muscle in written and video communication, and having meaningful in-person time. Short, focused in-person meetups (e.g., 48 hours) are crucial for solving hard problems and building trust and camaraderie that sustains remote work.
In-person onboarding helps new employees understand the company culture, build initial contacts, and learn how the organization works culturally. This foundational in-person experience is crucial for integrating into the team and navigating a remote work environment effectively.
The most useful question is 'What are you optimizing for?' This question, applied to short, medium, or long-term horizons, helps clarify priorities, understand how time is being spent, and make better trade-offs in both personal and professional contexts.
25 Actionable Insights
1. Co-create Team R&R Contracts
Clearly define roles and responsibilities for cross-functional teams (Product, Design, Engineering, Data) by having each leader write their own role and expectations of counterparts. Review these together to create a shared “contract” that cascades through the organization, preventing conflict and clarifying expectations.
2. Balance Outcomes and Output
Ensure teams balance focusing on desired outcomes with achieving sufficient output (shipping things quickly). Prioritize execution velocity, as high output indicates progress towards outcomes and increases the likelihood of success.
3. Optimize, Don’t Balance
Shift from striving for “work-life balance” to “work-life optimization,” acknowledging that you can’t have it all simultaneously. Recognize that some periods will require intense effort and long hours, which should then be followed by times for recharging and focusing on other priorities.
4. Value In-Person Time
For remote and distributed teams, prioritize meaningful in-person time, especially for solving complex problems and building trust. Regular offsites or events where team members can meet, collaborate, and socialize are crucial to foster camaraderie and efficiency.
5. Offsite for Gnarly Problems
When facing “gnarly problems” in remote teams, convene a 48-hour in-person offsite with a tightly articulated agenda agreed upon beforehand. Ensure time for both focused work sessions and informal social activities like dinners to build camaraderie and facilitate problem-solving.
6. Educate for Shared Understanding
When making critical cross-functional decisions, ensure everyone operates from the same information foundation by giving experts (e.g., data scientists) dedicated time to educate the entire team. This shared understanding can be the “unlock” for resolving complex issues.
7. Embed Data Scientists in Teams
Embed data scientists directly within product teams, dedicating them to specific product zones or areas. This removes data access blockers for PMs and allows data scientists to develop deeper product understanding, leading to better pattern recognition and insights.
8. PMs Drive Urgency
Product Managers should actively drive urgency by frequently discussing experimentation backlogs and shipping velocity. Regularly remind teams of competition to foster a sense of differentiation and motivate faster market delivery of ideas.
9. Question Output, Not Effort
To address low team output without defensiveness, ask specific, probing questions about deliverables. Focus on “What did you deliver this sprint?”, “What did you deliver to production?”, and “What was the cycle time?” to help teams self-reflect and understand their execution velocity.
10. Ask “What Optimizing For?”
Consistently ask “What are you optimizing for?” (today, this quarter, this year, etc.) in both personal and professional contexts. This question illuminates priorities, guides decision-making, and clarifies trade-offs, especially during goal setting and OKR discussions.
11. Ask “What Problem?”
Always clarify “What problem are we trying to solve?” This fundamental question ensures focus, prevents misdirected effort, and aligns the team on the core challenge at hand.
12. Establish Overlapping Work Hours
For remote teams, establish a set of overlapping work hours where all team members are expected to be online simultaneously. This standard, while maintaining general flexibility, significantly improves real-time collaboration and communication.
13. In-Person Onboarding is Key
Conduct in-person onboarding for all new hires, ideally for about a week. This is crucial for new team members to understand company culture, establish initial contacts, and facilitate early learning that is difficult to replicate remotely.
14. Share PM Load
Actively share the product management load by empowering and involving the entire team in finding answers and taking responsibility for what is being built. This fosters a culture of shared ownership and reduces the burden on individual PMs.
15. Foster Idea Sharing
Intentionally create a safe and comfortable space for people across all functions and geographies to share their ideas, especially in diverse teams where language barriers might exist. This fosters creativity and ensures valuable insights are not overlooked.
16. PMs Develop Technical Skills
Product Managers should increasingly develop technical skills and delve into data analysis, even if not required to code. This enhances their effectiveness and understanding of product development and performance.
17. Designers Need Business Acumen
Designers should cultivate a strong business orientation, viewing design as a means to achieve business objectives. The most effective designers are also savvy business people, integrating commercial understanding into their creative process.
18. Engineers Focus on Product
Encourage engineers to become more product and user-focused, recognizing that valuable ideas can originate from any function. This fosters a collaborative environment where engineers contribute beyond just coding, leading to more impactful products.
19. Cultivate User Empathy
Cultivate strong empathy for the people and problems you are solving, as it’s crucial for effective product management. Stepping out of your comfort zone is a key way to develop this empathy.
20. Start PM Career in Startups
To break into product management, consider working at smaller companies or startups where you’ll gain exposure to all facets of the product discipline. This broad experience is invaluable for developing a comprehensive understanding of the role.
21. Use Trello for Ideation
Use Trello for smaller teams, especially during the ideation and discovery phases of product development. It’s effective for pulling ideas, prioritizing them, and tracking progress before solidifying what to build.
22. Use Jira for Execution
Opt for tools like Jira when tasks have been decided, are ready for execution, and require detailed breakdown and assignment to individuals. This is more suitable for managing the development of established plans.
23. Leverage Trello Power-ups
Utilize Trello’s “power-ups” (integrations) to enhance its capabilities for more complex tasks. This helps overcome concerns about Trello not being powerful enough for sophisticated use cases.
24. Revisit R&R Regularly
Revisit and review team roles and responsibilities, especially when conflicts, tensions, or missed tasks indicate a breakdown in understanding. This helps address issues and clarify ownership.
25. Use The Knot Marketplace
If planning a wedding, utilize The Knot Worldwide marketplace to find and connect with wedding vendors. It offers a comprehensive platform to build your wedding team, including access to cool small businesses.
6 Key Quotes
If you're also not shipping a lot of things to market quickly enough, then it just doesn't matter that much.
Nikita Miller
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.
Nikita Miller
I don't think you can have it all at the same time all the time.
Nikita Miller
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.
Nikita Miller
The more tries you have at it, the likelier you are to get it right.
Nikita Miller
No one grows up and is like, I want to be a product manager when I grew up. But I think that's starting to. It's starting. It's a thing.
Lenny Rachitsky
2 Protocols
Roles and Responsibilities Framework
Nikita Miller- Each individual (e.g., Product, Design, Engineering, Data) writes down what they believe their own role and responsibilities are.
- Each individual also writes down their expectations of their counterparts' roles and responsibilities.
- The team reviews these documents together to identify differences and arrive at a shared 'contract' or understanding.
- This contract is then cascaded throughout the organization.
- Revisit the framework periodically, especially when conflicts or execution issues arise.
Effective In-Person Meetups for Remote Teams
Nikita Miller- Identify a 'gnarly problem' or a change in strategy that requires deep collaboration and decision-making.
- Set a tight, well-articulated agenda that everyone agrees on beforehand.
- Gather the cross-functional team for approximately 48 hours (two nights).
- Dedicate focused time in a meeting room during the day to hash out the problem.
- Build in time for social activities like dinner or extended lunches to foster camaraderie and trust.
- Ensure that key stakeholders, like data personnel, are given ample space to educate the team.