levitan-brand-ugc

Levitan Brand UGC

Based on Daniel Levitan's public method. Not affiliated with or endorsed by Daniel Levitan.

When to use

Use this skill to turn interchangeable creator testimonials into recognizable advertising formats for a specific brand. It supports creative strategy, creator briefs, short scripts, production planning, and a bounded test plan for TikTok, Meta, or another specified social platform. The deliverable is a repeatable format system with example executions, rather than a disconnected list of hooks.

Apply it when competitors use similar talking-head ads, when audiences cannot identify the advertiser, or when a team needs a consistent way to produce and learn from creator content. Preserve a working UGC control when the task concerns an existing campaign. Treat the provocative German phrase UGC ist tot as a critique of saturation, not proof that every customer video has stopped working.

The public origin is OMR Education episode 283 with Daniel Levitan and Robert Wobst. Their contribution is shared, even though this package is named for Levitan. Read the evidence boundaries in references/method.md before attributing a recommendation. Accessible show notes establish the core direction; related case studies and later public appearances supply supporting context. This package's production fields and testing mechanics are explicitly identified as operational adaptations.

Procedure

1. Set the assignment. Read the intake guidance in templates/output-template.md. Record the product, market, audience, placement, offer, intended action, production resources, and current control. Mark missing facts as assumptions. Ask only for inputs that materially block a useful brief.

2. Diagnose interchangeability. Use rule R1 in references/method.md. Identify which existing opening, testimonial, setting, or claim could belong to any competitor. Explain what the viewer currently learns about the brand and why the proposed change should help.

3. Find the buying motivation. Apply R2 in references/method.md. Connect a specific audience problem to a product capability and available proof. Separate verified features, supplied customer evidence, and invented illustration. Do not invent testimonials or results to make the script persuasive.

4. Define recognition. Follow R3 in references/method.md. Choose a small, repeatable combination of host role, setting, visual cue, verbal framing, and demonstration ritual. Explain why those choices belong to this brand and can survive multiple episodes.

5. Choose the format. Use R4 and its format decision table in references/method.md. Consider a staged podcast conversation, recurring demonstration, or another suitable creator format. Select for the audience problem and production resources; a podcast setup is an option, not the method itself.

6. Cast and brief the creator. Use R5 in references/method.md. Specify the required role, delivery, product understanding, and continuity. Give creators room to speak naturally while keeping factual claims and distinctive format elements consistent. Identify permissions needed for the intended distribution.

7. Write executable episodes. Follow the script fields in templates/output-template.md. Develop an opening, audience tension, visible explanation or demonstration, proof, and relevant call to action. Annotate shots and on-screen text so a producer can execute the concept without guessing.

8. Revise the generic draft. Consult examples/worked-examples.md. Compare the weak and improved versions, then explain which rules changed your own draft. Ensure the improvement contains a repeatable brand idea and product relevance, rather than merely a more dramatic opening.

9. Plan efficient production. Apply R6 in references/method.md. Separate stable format elements from variable hooks, objections, products, or proof scenes. Specify the minimum viable shoot, reusable assets, and adaptation needed for each requested placement. Keep the plan within supplied resources.

10. Design the learning test. Apply R7 in references/method.md and complete the testing fields in templates/output-template.md. State the hypothesis, control, variables, budget boundary, primary outcome, diagnostic metrics, and decision rule. Use client baselines rather than public case-study results as targets.

11. Plan continuation. Use R8 in references/method.md. Describe how to retain recognizable elements while testing new subjects or messages. Explain when to fix the opening, proof, conversion path, or whole format. Treat organic response as input to paid testing, with differences in delivery acknowledged.

12. Review and deliver. Run checklists/review-checklist.md. Repair failures before delivering the completed template. Cite sourced rationale through references/sources.md, distinguish assumptions from evidence, and leave unresolved dependencies visible. Creating a brief does not authorize publishing content or spending advertising budget.

Files in this skill

• SLUG.txt: Package identifier for discovery and naming.
• SKILL.md: Entry point, usage guidance, and procedure.
• references/method.md: Evidence boundaries, principles, decision rules, and edge cases.
• references/sources.md: Fetched public sources, contributions, and access limitations.
• examples/worked-examples.md: Two invented before-and-after applications with rule explanations.
• templates/output-template.md: Deliverable structure and field-level completion guidance.
• checklists/review-checklist.md: Pass/fail checks and repairs for common failures.