Skip to content
すべてのテンプレートに戻る

Provaの成果物

マーケティングチーム向けAI Workflow Audit Template

チームがpilotに進む前に、1つのマーケティングworkflowを整理し、AIが自動化すべきこと、支援すべきこと、守るべきこと、触れないべきことを決めます。

テンプレート項目

  • Workflow stage
  • What AI handles today
  • What AI should handle in six months
  • What stays human and why
  • Ethical or operational risk: low, medium, high
  • Action: automate, augment, protect, decline
  • ICE score for pilot candidates

記入例

下の記入例は英語のままにしています。Provaでは提出された成果物を英語でレビューするためです。

Client reporting workflow for a paid media account.

Data extraction from ad platforms
Metric reconciliation
Anomaly detection
Insight drafting
Strategist review
Client-ready narrative
Follow-up action list

弱い例と強い例

弱い例

Workflow stageReporting
AI handles todayAI writes reports
Stays humanStrategy
RiskMedium
ActionAutomate

なぜ弱いのか

  • "Reporting" is too broad to audit.
  • "Strategy" does not name the judgment point.
  • It does not identify source systems, reconciliation risk, or who approves the client-facing narrative.
  • Automating the whole workflow is unsafe because the work includes interpretation and client trust.

強い例

Workflow stageWeekly paid media variance explanation for Meta, Google, and LinkedIn
AI handles todayDrafts first-pass variance notes from exported spend, revenue, CPA, and campaign-change logs
AI should handle in six monthsFlags likely causes, drafts three audience-specific summaries, and proposes follow-up checks
Stays humanStrategist approves causal claims and client recommendation because platform data can be delayed or misleading
RiskHigh for client narrative, medium for internal diagnosis
ActionAugment, with protected human approval before client send

なぜ機能するのか

  • The stage is specific.
  • Source systems are named.
  • The human judgment point is explicit.
  • Risk differs by use case.
  • The action is narrow enough to pilot.

汎用AIが見落としがちな点をProvaがレビューします

  • Whether the workflow scope is specific enough to audit
  • Whether "stays human" reasons are concrete or just polite language
  • Whether high-risk stages are incorrectly classified as automate
  • Whether ICE scores are supported by operational reality
  • Whether the selected pilot is narrow enough to test
  • Whether the next sprint should be measurement, rollout, or foundation repair

次のステップ

自分の案にフィードバックが欲しい場合、Provaは短いassessmentから始まります。あなたの役割、目標、最初の相手に合わせてレビュー基準を揃え、その後いまの作業に合うsprintへ進みます。

Provaは現在、英語のみ対応しています。

送信前に、クライアント名、機密数値、チームがtrainingやcoaching systemに保存したくない情報を削除してください。

英語版Provaへ進む