Biomedical education
Create a drug development process explainer video
Create a drug development process video by selecting the stages and decision points in your approved overview. Paste their descriptions into AutoScribble and define whether the lesson covers a general process or a documented example. Review the draft so the sequence explains the source without implying a fixed timetable, automatic progress or approval of a particular product.
Audience: Biomedical educators
Keep decision points visible in the development map.
Map selected development stages
Draft a 120-second landscape whiteboard lesson for [learner group] using my approved drug development overview. This is a [general process or documented example]. Cover these stages: [stages], keeping the source's decision points and any branches explicit. Use a process map rather than implying fixed elapsed time. Do not invent dates, costs, success rates, trial results or regulatory approval, and do not add a successful ending absent from the source. Finish at the stated boundary of the material, with a recap of the key decisions. [Paste your source material here]
A straight timeline can make development look simpler and more certain than the source describes. Your production task is to preserve the important decisions while keeping the overview understandable. Decide which stages belong in this lesson, what moves the explanation between them and how the video should represent a branch, revision or stopping point.
Distinguish a general map from a product story
Put that choice in the first line of your brief. A general overview should use the stage labels and boundaries from the chosen source. A documented example needs its own factual context and status. Do not borrow an outcome from one example to supply a reassuring ending for an otherwise generic process animation.
Represent decisions as decisions
List the evidence question or decision described at each selected transition. Use a clearly labelled branch or pause where the source requires one, rather than an automatic arrow to the next stage. Equal spacing on the screen should organise the explanation, not imply equal durations, probabilities or costs across the development process.
End at the source's stated boundary
A final trophy or approval stamp can overstate what the lesson establishes. Choose an ending that names the last stage actually covered and points to the next source where appropriate. Avoid invented timelines, success rates or regulator claims, and review the generated visual sequence for an unintended promise that every candidate completes the same journey.
Illustrative storyboard
A possible scene sequence
A process map introduces selected development stages and their source-defined decisions.
- Scene 1
Visual
A scope card identifies a general overview or documented example.
Narration
This map covers the process scope stated in the supplied material.
- Scene 2
Visual
The opening stages appear with brief source-based descriptions.
Narration
Each stage answers a particular question in this overview.
- Scene 3
Visual
A labelled decision point interrupts a simple straight arrow.
Narration
Progress depends on the decision described here; it is not automatic.
- Scene 4
Visual
The map ends at the last source-covered stage without an approval stamp.
Narration
Our explanation stops where the source material stops.
Example storyboard; your generated video will vary.
Questions
- Should every stage have a duration on the timeline?
- Only use appropriately sourced timing with its context. A process map can show explanatory order without making the spacing between stages look like a fixed development timetable.
- Can I include a named medicine's development story?
- Use a documented source for that example, including its actual status and relevant limits. Keep the product-specific story separate from claims about what every development programme does.
- How can the ending feel complete without approval?
- Return to the learning objective and recap the decisions covered. A clear explanation can end at a defined process boundary without inventing a successful outcome for the story.
Review the generated wording and visuals before using your video. See pricing and credits.