Techno-Stress, Technology & Interfaces

I was not familiar with all of the technology so it was hard to absorb it all at once and learn the differences.

Blogging - not the technology itself; but being able to develop a voice and a focus of discussion

Getting started. The tools that were provided (Blogbridge in particular, and I never did understand what we were supposed to do with Squidoo or delicious) were not plug-and-play or intuitive. I hope that the next project will use easier tools. Our team did most of its work on [name’s] library-provided interactive web tool.

Trying to learn the technologies on my own. Since I work alone, it's tough doing this without anyone else to work through confusing applications.

Trying to combine learning new tools with doing a project. If I were a student, I would have found this to be a fun and creative way of engaging.

… so many technologies, no way to apply them to my association right now and the bad timing.

Not having the right support simply made it more difficult and frustrating, and meant that I didn't learn as much as I wanted about some elements, such as Flickr, podcasting, and RSS.

Needing to download and create passwords for multiple pieces of software with no integration.

I had previous experience with blogging, online meetings, news aggregators and chat, but no experience with Flickr, OPML or podcasting. I did not have to play a lot of catch up luckily with the blogging. I did not care a lot for BlogBridge because I couldn't get it to easily pick up all of the feeds I was suppose to be following. I was using BlogBridge and Rojo and felt like it was slowing me down.