This link has been bookmarked by 19 people . It was first bookmarked on 16 Jun 2009, by Sharon Elin.
-
30 Dec 09
-
29 Dec 09
-
14 Jul 09
-
12 Jul 09
-
01 Jul 09
-
If you lose your job, you could be flushing a lot of your work down the drain. One day you’re happy at work and the next you’re out on the street with no access to your projects or the tools used to build them. For these reasons, it’s important to maintain a portfolio.
-
Instructional design: Do you have examples of different approaches to learning and course design
- 7 more annotations...
-
-
Graphic design: While everyone talks about instructional design, I think an equal consideration is the visual design.
-
Present diverse projects: Don’t show me 400 courses that all look the same. If that’s all you get to work on, then spend some time on your own and build out other examples. They don’t need to be complete courses. Build out an interaction or a scenario. Take one topic and try it three different ways.
-
you should understand how to manage a project from start to finish.
-
Project management:
-
Writing:
-
How well can you write to document procedures and provide the right level of guidance? On the other hand, some projects are not technical and require a more conversational tone. As Cathy Moore would ask, “Can you dump the drone?”
-
- Build a case study for each project. It doesn’t need to be overly fancy. Describe the project objectives, what you did, and the results. If you have examples add them. If not, at least try to add some screenshots.
- Create a blog to document your learning. Use it to capture what you’re doing and thoughts you have during the production process. If you need ideas to get started, look at some of the demos in this blog. Take one of the ideas and play around with it.
- Network with others. A portfolio’s no good if you have no place to show it(your blog) or share it (your network)
-
-
-
20 Jun 09
-
Ruth HowardMany elearning developers face two common problems. All the work you do is proprietary so you can't share it with outsiders. Or the organization's expectations are lower than your skills.\n\nToo many people told me that they couldn't share what they were working on. This makes sense for the organization, but not for you. Don't allow their content to make your skills proprietary, as well. In the same sense, don't let their lower expectations define your skills.
epf eportfolio eportfolios e-portfolio e-portfolios virtualportfolio virtualportfolios digitalportfolio digitalportfolios onlineportfolio onlineportfolios lifeportfolios lifestreams personallearningspaces personalonlinespaces digifolios careerportfolios
-
19 Jun 09
Allison MillerMany elearning developers face two common problems. All the work you do is proprietary so you can’t share it with outsiders. Or the organization’s expectations are lower than your skills.
Too many people told me that they couldn’t share what they were working on. This makes sense for the organization, but not for you. Don’t allow their content to make your skills proprietary, as well. In the same sense, don’t let their lower expectations define your skills.epf eportfolio eportfolios e-portfolio e-portfolios virtualportfolio virtualportfolios digitalportfolio digitalportfolios onlineportfolio onlineportfolios lifeportfolios lifestreams personallearningspaces personalonlinespaces digifolios careerportfolios
-
18 Jun 09
-
17 Jun 09
-
16 Jun 09
-
Christy TuckerBenefits of a portfolio plus tips on what to include and what to do if everything you do is proprietary
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.