# Workflow
## Decide on core topic and type of presentation
* storytelling heavy: pick one core concept I want to communicate
* educational: series of concepts and how they work
## Watch presentations and good storytellers
* Try to find similar type of content/goal
* Gather notes and tangential ideas
* reverse engineer their presentation structure. how are they capturing attention, how are the maintaining it? what is the story arch, what is the conclusion?
## Prepare draft outline and story based on gathered notes
* Ask someone for feedback on core topic and main points related to the topic. potentially arrange them in a specific order
* review and elaborate on story based on initial feedback
## Record audio version of the presentation
* Ask someone else for feedback (higher granularity feedback)
* make adjustments and re-record audio version. ask for feedback again
## Create slides in [pitch.com](http://pitch.com/)
*
## Polish details
* share with more friends
## Create memory palace for script
* read script out loud and capture the immediate images that come to mind when emphasising on specific points
## Rehearse
* over the course of 3 days. sleep well in between
## Present
## Debrief or take notes on the presentation
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.deepwork.studio/teams-departments/awareness/functions/public-speaker/workflow.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.