Understand the reference before adapting
Record the source and the role of each segment: opening, context, proof and ending. Separate a creative structure from the reference creator’s words, footage, music, identity and product claims. A public reference does not automatically provide permission to reuse any of its assets.
Build from your own verified facts
Write the intended viewer task, your actual feature and the product action a recording can show. For a fictional notes app, the supported planning fact could be that a call note contains a next-step section. A reference about automatically sending follow-ups cannot be copied into this product concept unless that feature genuinely exists.
| Reference element | Your adaptation | Evidence |
|---|---|---|
| Sequence | Reaction then product action | Record your own footage |
| Feature claim | A next-step section | Verify your application |
| Third-party asset | Use only with permission | Record the license or approval |
Write an original adaptation
A hypothetical new sequence might be “wait, the next step is right here,” followed by an independently recorded note and a readable section. Write original words, use your own footage or properly licensed assets, and verify any conditions. This is a concept plan, not an analysis of a specific permissioned reference or a finished asset.
Document the real transformation
Before treating the article as an example, provide a permissioned source, a source analysis, a verified product brief and an approved original final asset. Check exact copy, private data and rights. Do not promise that your adaptation will reproduce another creator’s results.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Audience and task: __. Verified product fact: __. Planned words and action: __. Asset source and permission: __. Actual review observations: __.Browse the founder guide library for the next task in your workflow.