Create instructor-guide.md

Author: valentina-s

resources/organizing/instructor-guide.md

@@ -0,0 +1,39 @@
+## Target Audience: 
+Please specify the target audience for this tutorial. What does the audience need to know to be able to benefit from your tutorial? Can you eliminate unnecessary prerequisites? 
+
+OceanHackWeek participants come from diverse technical backgrounds: while some may have basic scripting experience, others may have built complex applications within their domain, and still may be completely unfamiliar with libraries used in an adjacent domain.
+
+## Learning Objectives: 
+Please provide a few measurable learning objectives for your tutorial: those should be short statements of what participants will be able to do immediately after the tutorial. Consider learning objectives of varying complexity: some expect participants to be able to execute simple tasks, while others expect them to be able to develop new approaches to address a problem. You can use the [Bloom’s Taxonomy categorization](https://www.unmc.edu/facdev/_documents/teaching-docs/bloom-taxonomy.pdf) to structure your objectives. 
+
+**Example:**
+
+After the lesson the learners will be able to 
+* Outline elements of ML pipelines
+* List major differences between types of ML methods, and steps to proceed to evaluate their performance
+* Identify contexts where deep learning can be useful
+* Organize labeled datasets in a format expected by ML libraries
+
+Think about the balance of how this tutorial can be helpful to participants during the hackweek vs. afterwards throughout their careers.
+
+## General Tips:
+Think of ways to engage the audience during the tutorial. That can also set the right tone of how much detail you need to provide. Remember the more experienced participants may be the more vocal ones so think of ways to hear from everybody without making them feel uncomfortable for not knowing a concept. Anonymous polls can be useful (such as [particifi](https://particify.de/en/)). 
+
+Although the content of your tutorial may not seem a lot when presented as stand-alone, the participants are going through a sequence of tutorials during the week, and are also learning a lot of new things for their projects. 
+
+* If using notebooks/code, be explicit whether you expect people to follow along running the cells/changing code on the fly, or they can just follow your demo, and dive into the notebook later.
+* Scrolling through notebooks/code can become pretty confusing, so consider having sections in the notebook and hiding the code cells, only to reveal it when talking about a specific section
+* Add a few key points after a section
+* If there are steps for which participants need to navigate to specific places on a website, consider saving snapshots and circling the places they need to click to avoid them missing crucial steps after which they cannot navigate the lesson; pause to make sure people are at the right place
+* Look through the tutorial and see what jargon/acronyms you are using:
+  * Remove the ones not crucial for the tutorial
+  * Spell out the ones that the participants need to know
+  * If some are not important, be explicit that they are not important right now, and they are just there for future reference
+ 
+## Tips for Use Case/Workflow Presentation:
+
+* While preparing your presentation, identify which of its components generalize outside of the use case; state those explicitly to help listeners focus on what can be relevant to them
+* Share lessons learned: what worked well, what did not
+* Did you have to pivot the project?
+
+