How to drive alignment, urgency, and output across product teams

Executive overview

Product teams obsess over outcomes but often neglect the output that proves progress. Without shipping frequently, strategy and goal-setting become empty exercises. Nikita Miller, SVP of Product at The Knot Worldwide, shares a roles-and-responsibilities framework that creates explicit team contracts, plus hard-won lessons on urgency, remote work, and the evolving PM role.

The core insight: outcomes matter, but shipping velocity is the indicator — and someone has to own urgency.

The roles and responsibilities framework

• Each function — PM, design, engineering, data — writes down what they believe their own role is and what they expect from counterparts
• Teams review these together and arrive at a shared "contract" covering individual, managerial, and cross-functional expectations
• This surfaces conflicts early (e.g. who owns project management after Scrum Masters disappeared) rather than after something falls off the rails
• Revisit when tension or missed delivery surfaces; ideally every quarter or half-year
• The most common gap found: unclear ownership of execution velocity and decision-making speed
• Adding data as a fourth seat (PM, design, engineering, data) removes a chronic blocker and lets data scientists build deep product context

Driving urgency and output

• Outcomes-only focus is a trap: if you're not shipping frequently, strategy doesn't matter much
• PM's job is to drive urgency — remind teams constantly, not through scorecards but through questions
• Useful questions: "What did you ship this sprint?", "What's our experimentation backlog?", "How long was the cycle time on that?"
• Competitive awareness is a practical urgency lever — someone is probably building the same thing faster
• A heuristic for slow teams: track the ratio of optimizations to bigger bets, and watch how long "simple" things sit undone

Remote and distributed teams

• Async communication and strong written/video skills are non-negotiable foundations
• In-person time is most valuable for hard, cross-functional decisions — not routine work
• A tight 48-hour offsite (two nights, structured agenda agreed before arrival, dinner built in) can unblock decisions that weeks of async failed to resolve
• Overlapping core hours give flexibility while preserving real-time collaboration
• Onboard new hires in person for at least one week — cultural and tacit learning is nearly impossible to replicate remotely
• Data scientists embedded in teams (rather than centralised) can spot patterns faster and reduce negotiation overhead

How product management is changing

• PM is now mainstream: ~2 million people carry the title on LinkedIn; degree programs and boot camps exist
• PMs are trending more technical; designers more business-oriented; engineers more product/user-focused — this is converging toward deeper collaboration
• The PM role remains uniquely stressful: expected to be competent across everything, keep calm, and have answers — acknowledge this with your team
• "Balance" is misleading; "optimisation" is more accurate — decide what you're optimising for in this period of your life, and make peace with trade-offs

Getting into product management

• Startups are a strong entry point: broad exposure, fast feedback, no one to teach you the "right" way (the product teaches you)
• Large tech company rotational programs are another proven path
• Technical fluency and data analysis skills are increasingly valuable, even if not required

The one question that drives everything

• "What are you optimising for?" — applicable to product strategy, OKR reviews, personal career decisions, even daily trade-offs
• Forces clarity on priorities before trade-offs can be made meaningfully
• Works at any time horizon: today, this quarter, this year

Working across geographies

• The confusion about what product management is is universal — not specific to any country
• Urgency, goal-setting frameworks, and cross-functional principles translate globally
• Working internationally builds empathy — a core PM skill — by forcing you out of your default assumptions
• Creating space for non-native English speakers to share ideas requires deliberate effort and pays lasting dividends