The Cross-Functional Responsibility Contract
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
Resolves ambiguity and friction regarding who owns what (e.g., project management tasks) in a cross-functional team.
Framework Overview
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.
🧠 Framework Structure
The Quartet Structure: Move beyond th...
Reciprocal Definition: Individuals wr...
Negotiated Agreement: Review the writ...
Periodic Renewal: Revisit the contrac...
When to Use
When forming a new team, when a team is missing deadlines, or when there is visible tension regarding task ownership.
Common Mistakes
Assuming generic job descriptions are enough; failing to clarify 'invisible work' like sprint management or QA.
Real World Example
At Atlassian/Trello, Miller found that 'Scrum Master' roles were disappearing, leaving a void in project management. She used this framework to clarify that Engineering Managers (EMs) needed to take ownership of sprint goals and delivery, rather than dumping it all on the PM.
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.
— Nikita Miller