Difference between revisions of "Documentation in Trainings"
From Competendo - Digital Toolbox
(→Articles, Checklists and Methods) |
|||
Line 4: | Line 4: | ||
</div> | </div> | ||
<div class=teaser-text>The reporting of a well-documented seminar is as easy as pie. Once you have all the learning aims, topics and methods noted down the reporting becomes a matter of incorporating your and participants' observations, feedback and recommendations into the existing document. Also, the more relevant details and insights that you have in the training documentation, the easier it becomes for you to share your experience with the new facilitators that might join your team. | <div class=teaser-text>The reporting of a well-documented seminar is as easy as pie. Once you have all the learning aims, topics and methods noted down the reporting becomes a matter of incorporating your and participants' observations, feedback and recommendations into the existing document. Also, the more relevant details and insights that you have in the training documentation, the easier it becomes for you to share your experience with the new facilitators that might join your team. | ||
+ | </div> | ||
+ | ==Functions of Documentation== | ||
+ | Documentation happens in numerous ways. However, we consider too often only written reports as a tool for documentation, or photos of flipcharts. In fact documentation is much more. It's a post in a messenger group, it can be a drawing, a photo, a video, or a blog. Before deciding for a certain medium and documentation strategy, please remeber: Form should follow function: | ||
+ | <div class="mw-collapsible mw-expanded" data-expandtext="Read more"> | ||
+ | ==Illustrating the Atmosphere== | ||
+ | * the location | ||
+ | * the people | ||
+ | * the style of work or facilitation | ||
+ | |||
+ | ==Evaluating Goal achievement== | ||
+ | * [[Planning goal, topic, method | overall goals]] have been achieved. | ||
+ | * learning goals were addressed like expected | ||
+ | |||
+ | ==Showing the Impact== | ||
+ | * intellectual outcome | ||
+ | * change in behavior and attitude | ||
+ | *gain of knowledge, skills and attitudes | ||
+ | * echo of the activities in the public | ||
+ | |||
+ | ==Collecting Insights== | ||
+ | * new insights, conclusions | ||
+ | * thoughts, questions | ||
+ | * results | ||
+ | |||
+ | ==Meeting of formal requirements== | ||
+ | * grants were used like planned | ||
+ | * the expected target groups were included | ||
+ | * content took place like planned | ||
+ | |||
</div> | </div> | ||
<hr class=boldline> | <hr class=boldline> | ||
==Articles, Checklists and Methods== | ==Articles, Checklists and Methods== | ||
− | <div class="mw-collapsible mw-expanded" data-expandtext=" | + | <div class="mw-collapsible mw-expanded" data-expandtext="Explore, what's inside!"> |
<div class=teaser-box> | <div class=teaser-box> | ||
===[[Functions of Documentation]]=== | ===[[Functions of Documentation]]=== |
Revision as of 22:27, 12 January 2019
Contents
Functions of Documentation
Documentation happens in numerous ways. However, we consider too often only written reports as a tool for documentation, or photos of flipcharts. In fact documentation is much more. It's a post in a messenger group, it can be a drawing, a photo, a video, or a blog. Before deciding for a certain medium and documentation strategy, please remeber: Form should follow function: