Thanks to those who attended.

Today we discussed:

• The Four Primary Roles of a Training Initiative and the Interloper Syndrome. This was shared to illustrate the sometimes challenging dynamic between SME and ID.

• The McGurk Effect and how conflicting visual and audio information creates confusion for a learner. This was shared to illustrate the importance of making sure audio narration supports, not conflicts with, the on-screen visuals.
  
  
• Monica also brought up some great points about screen length and how learners can fatigue from too much step-by-step information and a lack of “big picture” explanation. So, we reviewed the 3 components of great formal learning:

1. Context
2. Information
3. Process

I look forward to next week’s discussion.

How do you know how to setup a project file structure that works for everyone? Well, the answer is there really isn’t. The real problem is there is no manual to help setup a file structure, especially one everyone can agree with. I know this because every where I have been the file structure is setup different from job to job and in some instances from project to project. Sure there are resources to look up on the web, some people post their file structures so you can use it as an example. But it’s never a perfect fit for what you need in your own structure.

When we designed our file structure the best fit was to create a structure by client then specific projects. We then took a look at what the client sent us, files we generated (source files) and the finished product (published files). We found out that in this type of categorizing we were able to find a place for every file in an organized fashion and that it would allow people who weren’t on the project to find files as easily as if they were the one who created the originals.

Unfortunately, just having an organized file structure doesn’t mean people will follow it, but that’s a story for another time.