It was a lot of hard work to get here, but the implementation feels great! Response to the modules thus far has been positive. I've had only two constructive criticisms. One was regarding the tone of the modules. The participant thought it was over simplified. Another participant thought that the modules were too long. Neither of these participants were patients. This likely affected their responses.
Prior to implementing with the patients, we had to get permission from the Chief Medical Officer. A reduced presentation was prepared for him. It included just the moudle on ileus and a shorter version of the evaluation. My site supervisor emphasized keeping this presentation short and simple since the CMO's time is very valuable.
There've been very few edits to be made post implementation. Some of the timing could be adjusted a bit and there was a ghost image in a stray frame. But overall, things seem to work just the way they should. Next step is compiling the evaluations.
Monday, November 23, 2009
Monday, November 9, 2009
A Light at the End of the Tunnel
I can actually see the end of this very long phase of development. I've learned that development can be a roller coaster ride. Sometimes things go smoothly and it's exciting to see it coming together. Sometimes things drag on forever or have to be redone. It's been both exciting and frustrating.
During development, I have created five patient education modules. Please take a look at them. There are still a few tweaks to be done, but the end is in sight.
My biggest improvement since my last report is the addition of audio. Audio was an adventure in and of itself. Two issues made audio difficult. First, my site supervisor is about 200 miles away for me, so getting together to do the recordings was not easy to schedule. Second, my site supervisor uses a Mac and I use a PC, so we had to find a middle ground. It was easy to pass audio back and forth using the iPhone, but the file type made it difficult to edit. So we resolved the issue by introducing Dr. Jenkins to Camtasia. He was able to use it to record the audio and send the file to me in as a Camtasia recording file (.camrec). He did record it as one long recording, but I was able to use Camtasia to break it up and save the pieces as .mp3 files.
After on some research on adding audio to Flash, I decided to use action script to call the audio files. This would keep the .swf files from being too large since the audio is not actually in them. From there, the big task was matching the audio to the animation. I haven't found one best method that works but I have counted off a whole bunch of "Mississippi's" and learned how to multiply by 12 (frames per second) up pretty high.
This has indeed be a learning process. My skills in Flash, Photoshop, Dreamweaver and CSS are all improving and increasing. Additionally, I have new found respect for the ADDIE model. I also have an appreciation for the skills of others on a project like this. I've personally experienced how important it is that the content expert and the designer are on the same page before design starts. I also found that an explanation of the ADDIE process and why it works is a necessity for those who are not familiar with it. I have new found respect for those who are skilled in designing graphics. This process could have been easier for me if I had access to someone to assist me in this area. Nevertheless, it is a growing process and I am proud of the work I've done. The modules seem incredibly short for the work that went into them, but they are effective. I'm glad to report that my site supervisor has been pleased with the project. He was so impressed that he asked me if he could share my work with the Chief Medical Officer at the hospital. Of course I said yes, but I haven't heard back on that yet.
My next step is to finish tweaking the modules. I got a list of edits from my supervisor today. Should be implementing before the end of the week . . .
During development, I have created five patient education modules. Please take a look at them. There are still a few tweaks to be done, but the end is in sight.
My biggest improvement since my last report is the addition of audio. Audio was an adventure in and of itself. Two issues made audio difficult. First, my site supervisor is about 200 miles away for me, so getting together to do the recordings was not easy to schedule. Second, my site supervisor uses a Mac and I use a PC, so we had to find a middle ground. It was easy to pass audio back and forth using the iPhone, but the file type made it difficult to edit. So we resolved the issue by introducing Dr. Jenkins to Camtasia. He was able to use it to record the audio and send the file to me in as a Camtasia recording file (.camrec). He did record it as one long recording, but I was able to use Camtasia to break it up and save the pieces as .mp3 files.
After on some research on adding audio to Flash, I decided to use action script to call the audio files. This would keep the .swf files from being too large since the audio is not actually in them. From there, the big task was matching the audio to the animation. I haven't found one best method that works but I have counted off a whole bunch of "Mississippi's" and learned how to multiply by 12 (frames per second) up pretty high.
This has indeed be a learning process. My skills in Flash, Photoshop, Dreamweaver and CSS are all improving and increasing. Additionally, I have new found respect for the ADDIE model. I also have an appreciation for the skills of others on a project like this. I've personally experienced how important it is that the content expert and the designer are on the same page before design starts. I also found that an explanation of the ADDIE process and why it works is a necessity for those who are not familiar with it. I have new found respect for those who are skilled in designing graphics. This process could have been easier for me if I had access to someone to assist me in this area. Nevertheless, it is a growing process and I am proud of the work I've done. The modules seem incredibly short for the work that went into them, but they are effective. I'm glad to report that my site supervisor has been pleased with the project. He was so impressed that he asked me if he could share my work with the Chief Medical Officer at the hospital. Of course I said yes, but I haven't heard back on that yet.
My next step is to finish tweaking the modules. I got a list of edits from my supervisor today. Should be implementing before the end of the week . . .
Tuesday, October 27, 2009
Drafts Nearly Done
Spending lots of time working on my drafts. They aren't quite done. I'm a little behind schedule. However, I built time into the schedule for this event. I should be done with them all by the weekend. I have discovered what may be a more efficient way to build the modules in Flash. I usually add an element and then animate it. Then I add another element and animate it. I continued in this way. Now I've been adding all of the elements that need to appear together. This gives me a good idea that the placement for each element works with the placement of all of the elements before I start moving the objects around. This seems to work a little better for me.
I am getting a little more efficient at Flash. But there is still so much to learn. I think I've pulled out nearly every trick that I know. But it's nice to see it coming together.
I am getting a little more efficient at Flash. But there is still so much to learn. I think I've pulled out nearly every trick that I know. But it's nice to see it coming together.
Monday, October 12, 2009
Making Progress
At last, I feel like I'm making progress. I actually have two of the modules created (drafts) in Flash. Still a lot of work to do, but I'm making headway. I was also able to create some images that I'm proud of and that my site supervisor likes. That was a big hurdle, but I'm beginning to tame (just a little) the beast known as Adobe. I created a report on my progress thus far. I won't rehash it all here, but I would like to record some of the things that I am learning.
1. There are situations in which you can be totally dependent on someone else for content. In fact, most situations are probably like this. That's different from many of the projects that we've created in the program. Depending on someone else means having to wait on them to get the content to you.
2. Not everyone respects ADDIE. I'm finding that ADDIE is a great tool for planning, but you can't always follow it to the letter. When working with others, you have to have some room for flexibility.
3. No matter how long I live, I will never learn everything I need to know about Adobe.
1. There are situations in which you can be totally dependent on someone else for content. In fact, most situations are probably like this. That's different from many of the projects that we've created in the program. Depending on someone else means having to wait on them to get the content to you.
2. Not everyone respects ADDIE. I'm finding that ADDIE is a great tool for planning, but you can't always follow it to the letter. When working with others, you have to have some room for flexibility.
3. No matter how long I live, I will never learn everything I need to know about Adobe.
Monday, September 28, 2009
Design
The past couple of weeks have been spent working out the design for the project. There are two phases for the design. First, the general outline of the webpage (for now) that will serve as the platform for accessing the modules.
The second phase has been the more detailed portion of the design. It includes laying out exactly how each module will be delivered. Here is the process that I followed.
1. I transcribed the audio that my site supervisor provided for me. This took quite a bit of time (even with my better than average typing skills).
2. I sorted out the transcribed notes into eight large categories. From here, I wrote the narrative for each of the modules. This was very much like writing a research paper. I had not anticipated this type of research work. At this point, these narratives are still being tweaked and edited between me and the site supervisor.
3. With the draft of the narrative in hand, I began to outline the frames of the demonstration. One thing that I realized at this point is that I will be able to reuse many of the illustrations that I will create between the modules. The other thing that I had to consider is how to draw attention to various parts of the illustration. I've decided to use thickened lines in transparent colors to do this.
4. While drawing out the storyboards, I discovered that some of the draft modules had too much information in them. So, this helped me to consider new modules for smaller amounts of information.
5. An important decision that I made was to have the audio created ahead of the modules. I think it will be easier to match the images and animatioin to the audio than to match the audio to the animations.
I'm starting to see how this will come together, but it is a lot of work.
The second phase has been the more detailed portion of the design. It includes laying out exactly how each module will be delivered. Here is the process that I followed.
1. I transcribed the audio that my site supervisor provided for me. This took quite a bit of time (even with my better than average typing skills).
2. I sorted out the transcribed notes into eight large categories. From here, I wrote the narrative for each of the modules. This was very much like writing a research paper. I had not anticipated this type of research work. At this point, these narratives are still being tweaked and edited between me and the site supervisor.
3. With the draft of the narrative in hand, I began to outline the frames of the demonstration. One thing that I realized at this point is that I will be able to reuse many of the illustrations that I will create between the modules. The other thing that I had to consider is how to draw attention to various parts of the illustration. I've decided to use thickened lines in transparent colors to do this.
4. While drawing out the storyboards, I discovered that some of the draft modules had too much information in them. So, this helped me to consider new modules for smaller amounts of information.
5. An important decision that I made was to have the audio created ahead of the modules. I think it will be easier to match the images and animatioin to the audio than to match the audio to the animations.
I'm starting to see how this will come together, but it is a lot of work.
Monday, September 14, 2009
Project Update
Things are going well with my internship project. It took a little longer than I expected to get the recordings (notes) from my site supervisor. We had a little problem getting the recordings to upload from his computer. While we were trying to resolve that, I spent a good deal of time trying to build my graphics skills. I found several resources Ai Vault, Bitt Box and Lynda.com The first two were free. I subscribed to Lynda.com for $25 per month. So far, it has been well worth. I can watch videos on whatever I need.
I've divided the notes from my site supervisor into about four or five topics that will become the modules. The nice thing about having him record the notes with the pen is that he's pretty much drawn out what each "lesson" should look like. The drawings are fairly simple, so I feel like with the skills that I am gaining in Illustrator, I'll be able to reproduce the drawings with no problem.
The next thing that I will need to do is finalize the decision about how these lessons will be built. Right now, Flash is the front runner. I think it will be easiest to have the audio created first. Then I can adjust the animation to what is being said.
The next thing to be done is to make some solid decisions about the design of all of this.
I've divided the notes from my site supervisor into about four or five topics that will become the modules. The nice thing about having him record the notes with the pen is that he's pretty much drawn out what each "lesson" should look like. The drawings are fairly simple, so I feel like with the skills that I am gaining in Illustrator, I'll be able to reproduce the drawings with no problem.
The next thing that I will need to do is finalize the decision about how these lessons will be built. Right now, Flash is the front runner. I think it will be easiest to have the audio created first. Then I can adjust the animation to what is being said.
The next thing to be done is to make some solid decisions about the design of all of this.
Monday, August 31, 2009
My Project
This semester, I will be working with a physician to develop some education modules geared towards patients, mid-level caregivers, non-medically trained office personnel, etc. These initial modules will address gynological cancers.
I spent time with my site supervisor learning about some typical modules that might be included such as a definition of cancer and how cancer is staged. I suggested that my site supervisor use a digital pen to record his ideas (verbal and written) about how a module might work. So far this has worked wonderfully since I am totally dependent on him for content. (He's even decided to explore using it with his patients so that they can review the information that they received during their appointment.)
After viewing some of these initial drafts of the modules, I began to think about the type of graphics that might be used: realisitic images, detailed colored drawings, or simple line drawings. I looked for some resources on the best practices in instructional design regarding images. I found some useful information at the Rapid eLearning Blog. I also found two books that I plan to consult, The Non-Designer's Design Book by Robin Williams and Graphics for Learning by Ruth Clark. My site supervisor and I decided that simpler drawings might be better and less intimidating for the target users.
My next decision is to decide on the platform for the project. I am considering developing the modules in Flash since it would allow me to build in user controls.
By the end of the week, we should have identified the specific modules to be developed. Then the real work can begin.
I spent time with my site supervisor learning about some typical modules that might be included such as a definition of cancer and how cancer is staged. I suggested that my site supervisor use a digital pen to record his ideas (verbal and written) about how a module might work. So far this has worked wonderfully since I am totally dependent on him for content. (He's even decided to explore using it with his patients so that they can review the information that they received during their appointment.)
After viewing some of these initial drafts of the modules, I began to think about the type of graphics that might be used: realisitic images, detailed colored drawings, or simple line drawings. I looked for some resources on the best practices in instructional design regarding images. I found some useful information at the Rapid eLearning Blog. I also found two books that I plan to consult, The Non-Designer's Design Book by Robin Williams and Graphics for Learning by Ruth Clark. My site supervisor and I decided that simpler drawings might be better and less intimidating for the target users.
My next decision is to decide on the platform for the project. I am considering developing the modules in Flash since it would allow me to build in user controls.
By the end of the week, we should have identified the specific modules to be developed. Then the real work can begin.
Subscribe to:
Posts (Atom)