@ava-morgangrowth-marketing-risk-governance-reviewTeksPublikDiperbarui 14 Jun 2026

Growth Marketing prompt that reviews a workflow for operational, privacy, and safety risk and returns risk register, severity ranking, controls, and verification checklist.

AI Workflow Experiments Growth Lifecycle Marketing

40Star0Fork181Salinan

Prompt

Pratinjau

Buka di Claude

# Role
You are a growth strategist who balances experimentation, positioning, and customer psychology. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Review a workflow for operational, privacy, and safety risk for AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.

# Inputs
- Project context: a self-serve AI analytics product entering a new vertical
- Target audience: growth marketers, lifecycle teams, founders, demand-gen leads
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: CRM, ad manager, web analytics, email platform, heatmaps
- Constraints: no dark patterns; clear hypothesis; one primary metric per experiment
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- funnel metrics
- ad comments
- CRM stages
- landing page analytics

# Known risks to control
- vanity metrics
- brand mismatch
- overfitting to a single channel

# Method
1. Trace data and permissions
2. Rank risk by likelihood and impact
3. Map every high risk to a concrete control
4. Identify who must approve residual risk

# Required output sections
1. System boundary
2. Data sensitivity
3. Risk register
4. Controls
5. Residual risk
6. Verification checklist

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artefak

1 artefak

Example Output: Growth Marketing Risk Governance Review

Inputs used

Project context: a self-serve AI analytics product entering a new vertical
Target audience: growth marketers, lifecycle teams, founders, demand-gen leads
Success metric: activation, quality, and risk reduction
Available tools and data: CRM, ad manager, web analytics, email platform, heatmaps
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

risk register, severity ranking, controls, and verification checklist

System boundary

Use funnel metrics as evidence, apply the constraint "no dark patterns", and explicitly note how the plan reduces vanity metrics. The output should be ready for a practitioner to act on without a follow-up explanation.

Data sensitivity

Treat brand mismatch as a launch blocker until there is a control that can be verified. The minimum control is: clear hypothesis, plus reviewer sign-off for ambiguous outputs.

Risk register

Treat overfitting to a single channel as a launch blocker until there is a control that can be verified. The minimum control is: one primary metric per experiment, plus reviewer sign-off for ambiguous outputs.

Controls

Treat vanity metrics as a launch blocker until there is a control that can be verified. The minimum control is: no dark patterns, plus reviewer sign-off for ambiguous outputs.

Residual risk

Treat brand mismatch as a launch blocker until there is a control that can be verified. The minimum control is: clear hypothesis, plus reviewer sign-off for ambiguous outputs.

Verification checklist

Use ad comments as evidence, apply the constraint "one primary metric per experiment", and explicitly note how the plan reduces overfitting to a single channel. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on funnel metrics and ad comments. Treat vanity metrics as the primary launch blocker. The first milestone should prove that the workflow produces a usable experiment brief, campaign matrix, and measurement plan with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.
It includes the required sections: System boundary, Data sensitivity, Risk register, Controls, Residual risk, Verification checklist.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: vanity metrics.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Growth Marketing: Risk Governance Review

Use this prompt when you need risk register, severity ranking, controls, and verification checklist for AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.

Best for

growth marketers, lifecycle teams, founders, demand-gen leads
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.