# data[].attributes.body
Good: Succinct and clear.

Not so good: Missed a few different types of technology. Didn't go any deeper than clicking on different boxes.

# data[].attributes.body
I like this question:

There is too much technological change coming too fast without enough support for staff.

I think it would be useful to gauge the attitude temperature in a building, but I would follow up with an open ended question about how much/

what kind of support and when it should be offered.

# data[].attributes.body
1. what was good?

- "need more training" as an answer

- breaking down categories of tech use

2. what was not so good?

- no "other" option

- no freewrite box - unable to collect info on new tech/sites they don't already ask about

3. what could use surveying own staff?

- frequencies of use

# data[].attributes.body
Not extensive, but breaks it down to specific areas of technology (email vs. online tools). Would be good for guaging the basic foundation of a staff members familiarity with specific technologies.

# data[].attributes.body
Just a question: I wonder why this survey (and others) are anonymous. Would teachers lie/exaggerate if they had to attach their names?

# data[].attributes.body
Good: covered a lot of territory. diverse technology.

Not so good: Took a while to complete.

# data[].attributes.body
A. I liked how this was laid out better. I liked how it also included knowledge and practice of copyright and internet safety.

B.It was very long and had somethings that were not necessarily school related that could have been left off. Also I think it would be better

if it didn't ask for the name of the person (people are hesitant to put their name on things like this- at least where I work)

C. I would use the lay out and include the questions about copyright and internet safety. I would leave off the questions about Console gaming.

# data[].attributes.body
Can't see; trouble loading.

# data[].attributes.body
Good that it offers a lot of specific options.

Bad that it's clunky and overwhelming in design and offers no chance to collect info on different grades and age groups

# data[].attributes.body
Good:
-Straight-forward
-Quick; doesn't take a lot of time to finish
-Clear, precise questions
Not good:
-Answers are all in list form
-No room for opinions - every answer is in list form
-Would only give an idea of what tech staff needs, not how well they understand it

# data[].attributes.body
A. Straightforward regarding ability to use devices and software/hardware. Felt a bit jumbled and thrown-together without clearly delineated sections.
B. There was no stated "goal" of the survey. What was its purpose? All the answers to the questions are not aligned - this may or may not influence answer selection. Just the off-set nature of how the questions were formatted was a deterrent.
C. Some of the questions regarding online tools and their use could be very enlightening.

# data[].attributes.body
As Jim said, heavy on "what you know"; Good Self-Assesment tool to find where your strengths are and where you need help. Interesting Q on knowing assistive technologies (seems uncommon) Q#7 &#8.

# data[].attributes.body
Seems limited, just asking do or don't you use these technologies, but I do like question 7 that asks which teacher training would be helpful.

# data[].attributes.body
Comprehensive.

Modern.

Asked about application: "How often you use the communication/information

technologies below..."

# data[].attributes.body
Exclusively about what technology is used in the classroom

Does not assess at all pros/cons of different platforms/technologies

Does not cover creative use or how something is used in a classroom setting

Basic tech categories (not as detailed as Survey 1 (for example))

# data[].attributes.body
Did not explain "Why" teachers were taking the survey.

Some "classroom usage" questions.

Heavy on "what do you know?"

# data[].attributes.body
Basic assessment of comfort with and

access to technology; Reviews specific skills as well as general feelings about technology use

Not very helpful when determining ability to effectively use technology as a teaching tool

Had formatting issues (some check boxes were indented, others weren't)

# data[].attributes.body
It was good that it began by asking what grades the respondent works with.

Weird that it makes you choose at least one option on each. What if you don't use any of those things?

# data[].attributes.body
What was good?

-It was very thorough

-Broad spectrum of response options

-Asked about teacher proficiency

Not good

-A bit lengthy

# data[].attributes.body
Good way to gauge the comfort level and proficiency of staff and I liked

the range of "can teach others" to "just understanding."

# data[].attributes.body
A. It was good when asking all of the questions about technology knowledge. One thing I thought that some of the questions could use would be an other option with a space to type in their answer.

B. It was very lengthy and it could have taken some of those questions and laid them out in an easier format. Some of the language was dated.

C I would use the email portions and the application tools (but create a much smaller list of things for them to go through and with updated technology language.

# data[].attributes.body
A. It was fairly comprehensive regarding what skills the staff had in regards to technology. The division of topics was helpful for flow and comprehension. I also thought the short descriptor of the survey at the top was helpful.

B. The at-home questions felt a bit intrusive. Some terminology was misleading/outdated.

C. Seeing as how e-mail is a major form of communication for educators, I would probably use the "E-mail Usage" and "E-Mail Knowledge" portions of this survey.

# data[].attributes.body
1. what was good?

- variety of devices asked about

- range of basic to more advanced skills

- personal and classroom usage

2. not so good

- can't say "sort of" or "incompletely" for some answers

- weird formatting

3. what could y'use if surveying own staff?

- asking what kind of technology and websites staff use in their daily personal life

- asking what basic troubleshooting skills they have (and what they don't I could make an FAQ or something)