Digital Ambassadors – 3. Gauging existing expertise
Post 3 of 7
Every school has experts in multiple areas, and technology is no exception. For every expert there will be a number of people who don’t feel so comfortable using technology. It is important to gauge the school’s overall level of expertise, and where pockets of expertise exist. This will help shape the Digital Ambassadors programme. In this post, I share some techniques to make that happen.
Using online survey software, such as Google Forms, is a great way to gather a high volume of data quickly and efficiently. Using the basic tools provided, it is possible to get an overview of responses extremely quickly.
Using such tools, it is very easy to branch questionnaires so that specific questions are only asked to specific groups of users (e.g. parents, teachers, students, etc.). If that option is not suitable, surveys can easily be duplicated, modified and administered to different audiences.
The following questions may be of use:
- How would you describe your overall level of comfort using technology? (scale from 1 to 5)
- Self-assess your level of expertise with the following tools (grid: rows = tool, columns = scale)
- What tech tool do you feel you need the most help with? (list of tools to choose from)
- What tech tool(s) could you provide training for? (list of tools to choose from)
- Briefly explain one thing that you did in a lesson, which was highly successful.
The list above is by no means exhaustive, but I have found that shorter surveys get far more answers than long surveys.
The members of the IT team (or tech team, helpdesk, etc.) usually have a pretty good idea of who the experts may be, and also which skills users need the most. It may be a good idea to ask them to draw up a list of who they consider to be experts and a list of the most obvious needs.
Mentors (or tutors) tend to know their students very well, and I have had success asking mentors to name 2 or 3 students in their groups who may be good candidates to become Digital Ambassadors.
In the next post, I will discuss how to actually build the programme.