Pretend you are the growth ops lead and force the experiment package to survive questions about who can kill a running test, how referral fraud spikes are timed, and which lifecycle email caps still lack a named owner when marketing wants volume.
This seat sits between the live experiment tools and the growth claims leadership will actually quote. It asks which kill thresholds invent completeness the staffing map never measured, which fraud responses look crisp on a slide and soft in the live sample, and what happens when an email cap skip lands because ownership is incomplete. A green growth board does not answer those questions. The review needs the kill map, fraud calendar, email cap sheet, and the named person who can freeze a growth path.
Build the brief the seat can attack
Hand over the experiment tools in use, kill threshold draft, referral fraud spike plan, lifecycle email cap packet, last growth incidents, and one recent case where a delayed kill hurt a member or a board narrative. Include which product promises still bypass the same review. State the decision: clear the growth change, revise specific controls, or hold until a freeze owner is named.
Boundaries matter. The growth ops lead can challenge untested kill trees, fraud windows that ignore measured restore time, email caps without a kill switch, and override paths without logging. Product outcome ownership stays with the product lead. Creator or partner payout ceilings belong in the same packet so a quiet invoice does not hide a brittle growth path.
Force concrete answers
- Which critical experiment class still lacks a tested kill path with a measured age-out, and who owns the gap?
- What must hold before a referral fraud response can promote into a lasting rule, and who can waive it without a written reason?
- How does a declined email cap ask become visible to the requester within the claimed window?
- What is the measured time from a failed fraud finding to a human with freeze authority?
- Which shared override can ship many lifecycle sends without failing a single growth health check?
- Who has authority to pause experiments or force an email rollback at week end without waiting for the marketing owner?
Require observed, inferred, or unknown labels. Observed claims need a source. Unknowns become owners and due dates. When two teams claim the same growth authority, force one named decision before the next experiment change starts.
Turn objections into ship gates
Run the role in Pingpong with the same exhibits the growth team will use. Have the home team answer each objection in writing. The useful output is a short growth ledger: approved experiment classes, blocked classes, fraud windows, and the person who can call a freeze.
For kill timing, pair this seat with an experiment kill threshold review. For fraud risk, add a referral fraud spike stress test. Email caps often need a lifecycle email cap review. Adjacent seat work lives in the growth PM seat. The war-game decisions hub has more seats. Before approving the package, make the growth ops lead write the exact freeze and experiment check that will decide whether the change continues.