Please reply in the post to this question:
What Communication tasks do eLearning developers do?
So, we’re done with two areas, Quality Assurance and Problem-Solving. We’re moving on to Communication.
Once again, can everyone post at least one idea about the communication tasks that eLearning Developers do? Two would be better! Don’t worry if you want to repeat something that you mentioned in QA or Problem-Solving. We’ll slice, dice, and edit later on.
Do you think we can get everyone’s input by EOD Wednesday?
By the way, here is the eLearning Developers’ competency chart at this point.
We’re moving on. This is the first draft list of Communication competencies:
• Speak clearly and concisely
• Use professional email etiquette
• Provide positive and constructive feedback
• Provide honest, but neutral criticism
• Listen intently to retain information
• Listen to clients’ needs and wants for their visual mock-ups
• Track which files are open, and by whom, when working on the same project with multiple developers
• Relay clearly any issues or hold-ups that are affecting progress
• Be patient and friendly with other developers and ID’s at all times
• Answer IDs’ questions regarding the capabilities of the authoring tools/frameworks
• Ask clarifying questions when necessary, either of clients or IDs
• Lay out expectations of vendors/contractors clearly
Clear and concise speaking;
Professional email etiquette;
Providing positive and constructive feedback;
Intent listening and retention;
Give honest, but neutral criticism.
Keep track of which files are open by who when working on the same project with multiple developers.
Clearly relay any issues or hold-ups that are affecting progress.
Be patient and friendly with other developers and ID’s at all times.
Thanks, othols!
Yes, I think we can get everyone’s input by EOD Wednesday!
Here’s a start:
Listen to clients’ needs and wants for their visual mock-ups.
Answer IDs’ questions regarding the capabilities of the authoring tools/frameworks.
Ask clarifying questions when necessary, either of clients or IDs.
Clearly lay out expectations of vendors/contractors.