Documentation

Here are some tips for documentation and a sample.

(These are in addition to the notes I added previously.)

Note the day, module, title and speaker at the beginning of each new section. Sometimes they want the sections in separate files. You'll have to figure it out event-by-event.

They do 1 space after a period, but I'm old fashioned and still do 2. Only Oli notices so now I do it just to bug him.

Of course you need to step up for other roles as needed, but everyone understands if you prefer to review your documentation after each round while your memory is fresh. They love having it immediately following an event so they can do their reports.

If there are other documentors who are not native English speakers, you are invited and expected to correct their work (efficiency) as the native speaker and then give them feedback (effectivness). Wait for the invitation to give feedback. Some welcome it more than others.

You will be asked to review every assignment to make sure the English is correct. This gives you a great entree to join the design process if you don't have one already. Michael, based on what we have told them about you, they expect you to give input on design. They didn't expect me to design when I first came here, but assignments gave me an opportunity to open my big fat mouth and, of course, I did.

Fix the English. As non-native English speakers, it takes some many, many, many words to make a point. Just get the point. They appreciate it. I try to leave in a bit of the speaker's personality...

The well just went dry, I'll upload the final report that the sample (attached) documentation was used in so you can see it.

GAM%20Documentation%20Final.doc