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

Provaの成果物

マーケター向けAI Builder Reality Check

最初の本当に使えるAI product sliceを作る準備ができているか、そして今始めたら最初に壊れるものは何かを見極めます。

テンプレート項目

  • User and painful job
  • First useful slice
  • Proof that someone wants it
  • Current artifact or prototype
  • Weakest assumption
  • Data or workflow dependency
  • Review standard
  • Launch risk
  • Next 14-day build commitment

記入例

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

A marketer trying to build an internal campaign QA assistant.

弱い例と強い例

弱い例

UserMarketing team
First useful sliceAI assistant for campaign QA
ProofEveryone says QA is annoying
Weakest assumptionNeed better prompts
Launch riskBugs
14-day commitmentBuild MVP

なぜ弱いのか

  • "Marketing team" is not a user.
  • "AI assistant" is too broad.
  • The proof is hearsay, not behavior.
  • The weakest assumption ignores source data, approval rules, and workflow ownership.
  • "Build MVP" is not a commitment.

強い例

UserPaid media manager checking campaign launch settings before client approval
First useful sliceA checklist reviewer that compares campaign setup notes against required client launch rules
ProofTwo managers already use a manual spreadsheet before every launch; mistakes still reach strategist review
Current artifactOne sample launch checklist, three anonymized campaign setup notes, and one failed QA example
Weakest assumptionThe checklist rules are explicit enough for AI to evaluate without platform access
Data/workflow dependencyClient launch rules, platform screenshots, naming conventions, approval owner
Review standardFlag missing budget, geo, naming, tracking, claim, and approval evidence; never approve launch automatically
Launch riskFalse confidence before a client-visible campaign goes live
14-day commitmentBuild a reviewer for one client and one platform, then test against five past launch packets

なぜ機能するのか

  • The user is specific.
  • The first slice is constrained.
  • Proof comes from an existing workflow.
  • Launch risk is clear.
  • The commitment creates evidence, not just more code.

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

  • Whether the first useful slice is still too large
  • Whether the user is real or imagined
  • Whether there is proof beyond personal excitement
  • Whether the artifact standard exists before the build starts
  • Whether the hard part is product judgment, data access, approval, or implementation
  • Whether the next step should be reality check, build brief, build plan, execution lane, or launch gate

次のステップ

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

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

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

英語版Provaへ進む