Ownership gaps rarely announce themselves. They surface as missed deadlines, duplicated work, or the dreaded phrase "I thought someone else was handling that." The Pre-emptive Ownership Pact (POP) is C2O's answer to these silent failures. It is a lightweight, living agreement that a team creates at the start of an initiative to make role expectations explicit before ambiguity has a chance to cause damage.
A POP is not a contract, and it is not a project plan. It is a shared understanding, typically one to two pages, that captures who holds each C2O role for each lifecycle phase, what triggers a handoff between phases, and how escalation works when the unexpected occurs. Think of it as the team's pre-flight checklist: quick to complete, easy to reference, and invaluable when turbulence hits.
Step 1: Define the Outcome
Every POP begins with a single sentence that describes the measurable outcome the initiative aims to achieve. This is not a project description or a feature list. It is a statement of the change the team wants to see in the world. For example: "Reduce customer onboarding time from fourteen days to three days while maintaining a satisfaction score above 4.5 out of 5." This outcome statement anchors every subsequent decision about roles and phases. If a proposed activity does not connect back to this outcome, it does not belong in the POP.
Resist the temptation to define multiple outcomes in a single POP. If your initiative has genuinely distinct outcomes, create separate POPs for each. Overloading a single agreement dilutes focus and makes role assignment ambiguous. One outcome, one POP, one team.
Step 2: Map Roles to Phases
With the outcome defined, the team maps C2O roles (Drive, Contribute, Enable, Advise, Inform) to each lifecycle phase (Discover, Decide, Build, Run, Adopt). This is best done in a collaborative session, not by a project manager working alone. The facilitator walks through each phase and asks three questions: Who is best positioned to Drive this phase? Who needs to Contribute expertise? Who Enables by providing tools, access, or resources? The Advise and Inform roles are then filled based on stakeholder analysis.
Two rules keep this mapping healthy. First, every phase must have exactly one Drive. Shared Drive is no Drive. Second, the person who Drives one phase should not automatically Drive the next. Rotating the Drive role across phases prevents bottlenecks and builds shared understanding of the full lifecycle. A product manager might Drive Discover and Decide, while an engineering lead Drives Build, and an operations lead Drives Run.
Step 3: Define Phase-Gate Criteria and Escalation Triggers
For each phase transition, the POP specifies what "done" looks like: the deliverables, quality thresholds, and stakeholder sign-offs required before the team moves forward. These criteria should be objective and verifiable. "Stakeholder alignment" is too vague; "written approval from the VP of Product and the Head of Compliance" is actionable. The POP also defines escalation triggers: the specific conditions under which an issue must be raised to leadership rather than resolved within the team. Common triggers include budget overruns exceeding a threshold, timeline delays beyond a set number of days, or scope changes that alter the outcome statement.
Finally, the team agrees on a review cadence. A weekly fifteen-minute check-in is sufficient for most initiatives. During this check-in, the current Drive reports progress against the phase-gate criteria, flags any emerging ownership gaps, and confirms that the POP still reflects reality. If roles have shifted due to changing circumstances, the POP is updated on the spot. This living-document approach is what makes the POP pre-emptive rather than reactive: the team catches gaps before they become failures.
Getting Started Today
The best time to create a POP is at your next project kickoff. Download the Pre-emptive Ownership Pact template from our resources page, block ninety minutes with your core team, and walk through the three steps above. Teams consistently report that the conversation itself is as valuable as the document it produces. By making implicit assumptions explicit, the POP transforms a group of individuals into a team with shared clarity and mutual commitment to the outcome.