1. Define the job to be done
In a ad slots program, define the job to be done before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
2. Map users and permissions
In a ad slots program, map users and permissions before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
3. Inventory data inputs
In a ad slots program, inventory data inputs before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
4. Design workflows
In a ad slots program, design workflows before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
5. Specify integrations
In a ad slots program, specify integrations before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
6. Set controls and approvals
In a ad slots program, set controls and approvals before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
7. Validate reporting
In a ad slots program, validate reporting before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
8. Pilot with bounded scope
In a ad slots program, pilot with bounded scope before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
9. Monitor exceptions
In a ad slots program, monitor exceptions before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.
10. Review total operating cost
In a ad slots program, review total operating cost before advancing. Document the hypothesis, responsible owner, input evidence, accepted output, deadline and stop condition so the decision can be reproduced.
The output of this ad slots step should be understandable to a reviewer who did not create the campaign or page. That discipline reduces hidden assumptions and improves future iteration.