This blog is my place to share information with others, which I find valuable or others have requested. Also, I use it sometimes as a repository of things I come across that I think are important to me (and maybe others). Topics include social media, facebook, twitter, evaluation, blended, online, clickers, second life, assessment, and more....
How reputable is the company?
How stable is the ownership?
How responsive is the company?
How is their future growth (service -- growth) sustainable?
What are the company values?
What is the companies response to buyouts?
Stock performance if public. Management team. Gartners quadrant. Peer review. Site visits to headquarters & installed sites, etc
You evaluate the company by talking with long-term users (if any), not by talking to the company.
Talk to existing users about experience with the company, contact company directly with questions, look at how long in business
Making sure they have experience from a wide variety of end users, admin., faculty, staff- are they collaborative
Ease of Use/Learning Curve
Integration with Core technologies
Impact on Infrastructure (wireless, email, power, etc.)
Investment (time, money)
Do we really need it and if the answer is yes WHY. All about making sure we aren't duplicating technologies.
I generally am not a big fan of piloting tech just for the sake of piloting. It's nice if some incentive is thrown in, too. :-)
At work, it's mostly risk that I consider first and foremost. Depends on type of work that the org performs, and type of tech.
value added, learning curve, & overall investment (time, money, etc.)
considerations for piloting: sustainability, support requirements and creating expectations for future are big ones
#1 can the budget support it, #2 can it save future budgets, #3 does it have end user support #4 how bad is the learning curve
@dcbphd @phette23 It all depends on *how* the tech is used. Measure impact of teaching choices / methods, not tech. #elifocus