Output as Outcome Indicator
by Nikita Miller • SVP & Head of Product at The Knot Worldwide
Nikita Miller is a seasoned product leader with extensive experience in growth and retention. Previously VP of Product at Dooly and Head of Growth & Retention at Trello (Atlassian), she specializes in building high-performing, distributed teams and scaling product organizations.
🎙️ Episode Context
Nikita Miller shares her evolution from focusing purely on outcomes to recognizing the vital importance of output and velocity. She details actionable frameworks for defining cross-functional roles, embedding data scientists into product teams, and managing distributed workforces effectively.
Problem It Solves
Corrects teams that over-index on 'strategy' and 'discovery' but fail to ship software fast enough to learn.
Framework Overview
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.
🧠 Framework Structure
Velocity as Strategy: The more 'shots...
Cycle Time Audits: Routinely ask 'Wha...
Bias for Production: Ideation and bri...
Urgency Maintenance: PMs must instill...
When to Use
When a team is stuck in 'analysis paralysis', spending too much time on documentation/strategy without releasing features.
Common Mistakes
Confusing 'busy work' with shipping; measuring success by the number of documents written rather than features released.
Real World Example
Miller monitors the 'experimentation backlog.' If the backlog is full of ideas but deployment is slow, she shifts the conversation from 'what are we building' to 'why is it taking so long to ship,' emphasizing that output drives the learning loop.
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.
— Nikita Miller