Prova-Artefakt
AI-Builder-Reality-Check für Marketer
Entscheide, ob du bereit bist, den ersten brauchbaren AI-Produktschnitt zu bauen, und was zuerst bricht, wenn du jetzt startest.
Vorlagenfelder
- 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
Ausgefülltes Beispiel
Die ausgefüllten Beispiele unten bleiben auf Englisch, weil Prova eingereichte Artefakte auf Englisch prüft.
A marketer trying to build an internal campaign QA assistant.
Schwache Version vs. starke Version
Schwache Version
| User | Marketing team |
|---|---|
| First useful slice | AI assistant for campaign QA |
| Proof | Everyone says QA is annoying |
| Weakest assumption | Need better prompts |
| Launch risk | Bugs |
| 14-day commitment | Build MVP |
Warum es scheitert
- "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.
Starke Version
| User | Paid media manager checking campaign launch settings before client approval |
|---|---|
| First useful slice | A checklist reviewer that compares campaign setup notes against required client launch rules |
| Proof | Two managers already use a manual spreadsheet before every launch; mistakes still reach strategist review |
| Current artifact | One sample launch checklist, three anonymized campaign setup notes, and one failed QA example |
| Weakest assumption | The checklist rules are explicit enough for AI to evaluate without platform access |
| Data/workflow dependency | Client launch rules, platform screenshots, naming conventions, approval owner |
| Review standard | Flag missing budget, geo, naming, tracking, claim, and approval evidence; never approve launch automatically |
| Launch risk | False confidence before a client-visible campaign goes live |
| 14-day commitment | Build a reviewer for one client and one platform, then test against five past launch packets |
Warum es funktioniert
- 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.
Was Prova prüft, was generische AI oft übersieht
- 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
Nächster Schritt
Willst du Feedback zu deiner Version? Prova startet mit einem kurzen Assessment, damit der Review-Standard zu deiner Rolle, deinem Ziel und deiner ersten Zielgruppe passt. Danach kommst du in den Sprint, der zu deiner aktuellen Arbeit passt.
Prova ist derzeit nur auf Englisch verfügbar.
Vor dem Absenden: entferne Kundennamen, vertrauliche Zahlen und alles, was dein Team nicht in einem Trainings- oder Coaching-System speichern würde.
Weiter zu Prova auf Englisch