Require business problem, audience, desired outcome, deadline reason, requester, dependencies, and evidence. Reject tactics with no stated purpose.
Prioritize transparently
Score urgency, customer impact, confidence, effort, and dependency risk. Keep a queue for requests needing clarification.
Review flow
Track aging, rework, blocked items, and completed outcomes. The owner sets priority; the assistant keeps the board accurate.
Make intake decision-ready
“Create a campaign” is a tactic. State the problem, audience, deadline reason, evidence, dependencies, and cost of waiting. Return incomplete requests with one focused question.
Keep the queue honest
Use meaningful statuses such as needs context, ready, active, blocked, and accepted. A high-priority item with no owner is blocked. The business owner decides priority and scope. Test a growth operations intake board with a handful of requests from different teams. Require a problem statement, desired decision, evidence link, owner, urgency reason, and next review date before triage.
At the review meeting, merge duplicates and reject requests that have no actionable owner. Keep accepted work visible through completion, and record why deferred work was deferred so the queue remains a decision tool rather than a list of wishes.
