On this page6 sections
Published November 2, 2026.
The control this growth workflow needs
Growth Experiments is a written control for the growth team. It shows the source, the owner, the exception, and the close.
It matters because a test ends without a decision and the same idea returns next quarter.
What the record must show
Start with the experiment record. Record the source date, the named reviewer, the decision, and the destination evidence.
The specialist prepares and routes the record; the growth lead keeps the decision that changes spend, a customer promise, access, or a published claim.
Where the VA work stops
Preparation is not approval. A clean packet is a reviewed question waiting for the owner who carries the consequence.
Write the boundary beside the queue so it survives volume and staff changes.
Where the handoff breaks
The predictable failure is this: a test ends without a decision and the same idea returns next quarter. Use one status set: ready, exception, approved, and closed.
A status without an owner and a date is only a label.
A worked example
An onboarding test ends. The record shows the result, the limits, the decision, and the recheck date. The record shows the original state, the change, the reviewer, and the confirmation.
A second person should be able to repeat the check without a private conversation.
Close and review
Close growth experiments only when the source, approval, action, and destination evidence agree.
Sample one ordinary case, one exception, and one correction each week. Fix the rule before coaching the same operator again.