When I first read The Rise of Crowdsurfing by Jeff Howe, my gut reaction was that of sadness for the photographer, Mark Harmel, (and those like him) who could no longer charge his normal price for photos. That's his job, his way to make a living. If that's taken away from him, what will he do? What would I do if I were in his shoes?
But after letting it sink in a bit, I realized that that's just the way the capitalist world works. The person or organization who can produce the better product at a lower price typically 'wins' or gets the business. And, there may still be a market for Mark - maybe in art - but for what Claudia Menashe needed, his price wasn't right. When I think about it, I realize that like Claudia, I'm much more flexible regarding what I need in a photo when I am designing/developing an online course. Obviously price is a big barrier because I'm not allowed to bill for expenses, so my options are find it for free or make it myself. Since I'm usually pretty successful at finding or making what I need free of charge, I continue to use this approach.
Still the question remains - how will the internet transform capitalist business in the future? Will I have to pay for all of the online amenities I currently use and enjoy - like a membership on Facebook or Hulu - in order for these companies to stay in the game? CNN Money points out that web 2.0 sites like Facebook, MySpace, and Twitter aren't making money like they would have hoped. Sure, they have ad space, but are you really paying attention to those as you're clicking through a friend's new photo album? Probably not. So, what's their next step? How will these companies boost their profitability and how will this affect me?
Wednesday, July 21, 2010
Tuesday, July 20, 2010
Week 4
How do you judge the value of expertise on the Web? Does it differ from your notion of expertise in face-to-face settings? Why or why not?
Regardless of where I find my information, I take most things with a grain of salt. I do my best to triangulate the information I've found before I consider it fact. However, my approach varies depending on the kind of information I'm looking for. If I'm looking for a recipe or DIY household fix, I'm not going to spend hours looking for supporting information somewhere else. Sure, everyone may make spaghetti sauce a bit differently or approaches a backed up garbage disposal with varying solutions, but I just need one that works. So, I'll search for what I need, try it out, and if it works I'm all set. Otherwise, I'll try something else - no need to make sure 3 chefs/plumbers recommend the same thing.
By contrast, if I'm writing a paper, making a recommendation to a client, or even having a friendly debate with a coworker, I want to make sure the information I'm using is legit. I may browse academic journals (if I'm familiar with them) because I know this information, while not perfect, is held to a higher standard. If I'm searching outside academia, I look for reputable sources and I look for the information in several places.
However, even information from well-respected sources may not be completely accurate. In my Research Methods course in my Psychology program, my professor would bring in articles from the newspaper for us to critique. Many of these articles used statistics to essentially lie - making their claims look stronger. In behavior analysis, we don't use statistical significance - we use social significance, meaning our results are significant when we reach the level that the client would like us to reach. So, a small margin of statistical significance means nothing unless it actually produces desired results as specified by the client. Therefore, I'm wary of statistics and I don't just accept them because someone reputable said so.
I think this is also the case in a f2f setting - I don't take everything that comes out of a professor's mouth as gospel. I also want to triangulate this information before I'm certain of it. I want to see it replicated in various places and sometimes even experience it myself before I'm sold.
Unfortunately, many (not all) of my f2f classes have been structured very much like typical undergraduate courses - tell me what you want me to know, I'll learn it, show you that I've learned it, and I'll pass the course. There hasn't been a lot of room for exploration or translating an assignment to be more meaningful to me and my future (again, in most of my classes - not all). So, I've learned to play the game. I give my professors what they want at the sacrifice of doing something meaningful for me because I've learned that that's the way to get good grades. A semester is short. I can't argue with my professor or work to prove them wrong even if I don't really buy into what it is they're telling me. So, for the purposes of school, I take what they tell me and do what they tell me, but I definitely don't do this blindly. I'm very aware that other perspectives and contrasting information exist and it's my job to analyze all sides and come to a conclusion about what information is most appropriate given the situation. I just may not share that with my professor if I know he/she wants the assignment done a certain way.
Regardless of where I find my information, I take most things with a grain of salt. I do my best to triangulate the information I've found before I consider it fact. However, my approach varies depending on the kind of information I'm looking for. If I'm looking for a recipe or DIY household fix, I'm not going to spend hours looking for supporting information somewhere else. Sure, everyone may make spaghetti sauce a bit differently or approaches a backed up garbage disposal with varying solutions, but I just need one that works. So, I'll search for what I need, try it out, and if it works I'm all set. Otherwise, I'll try something else - no need to make sure 3 chefs/plumbers recommend the same thing.
By contrast, if I'm writing a paper, making a recommendation to a client, or even having a friendly debate with a coworker, I want to make sure the information I'm using is legit. I may browse academic journals (if I'm familiar with them) because I know this information, while not perfect, is held to a higher standard. If I'm searching outside academia, I look for reputable sources and I look for the information in several places.
However, even information from well-respected sources may not be completely accurate. In my Research Methods course in my Psychology program, my professor would bring in articles from the newspaper for us to critique. Many of these articles used statistics to essentially lie - making their claims look stronger. In behavior analysis, we don't use statistical significance - we use social significance, meaning our results are significant when we reach the level that the client would like us to reach. So, a small margin of statistical significance means nothing unless it actually produces desired results as specified by the client. Therefore, I'm wary of statistics and I don't just accept them because someone reputable said so.
I think this is also the case in a f2f setting - I don't take everything that comes out of a professor's mouth as gospel. I also want to triangulate this information before I'm certain of it. I want to see it replicated in various places and sometimes even experience it myself before I'm sold.
Unfortunately, many (not all) of my f2f classes have been structured very much like typical undergraduate courses - tell me what you want me to know, I'll learn it, show you that I've learned it, and I'll pass the course. There hasn't been a lot of room for exploration or translating an assignment to be more meaningful to me and my future (again, in most of my classes - not all). So, I've learned to play the game. I give my professors what they want at the sacrifice of doing something meaningful for me because I've learned that that's the way to get good grades. A semester is short. I can't argue with my professor or work to prove them wrong even if I don't really buy into what it is they're telling me. So, for the purposes of school, I take what they tell me and do what they tell me, but I definitely don't do this blindly. I'm very aware that other perspectives and contrasting information exist and it's my job to analyze all sides and come to a conclusion about what information is most appropriate given the situation. I just may not share that with my professor if I know he/she wants the assignment done a certain way.
Thursday, July 15, 2010
FB > Google

Facebook beats Google as the most visited site.
So, with such a huge presence on Facebook, can businesses really afford not to take advantage of its (and similar web 2.0 tools) capabilities?
I'm thinking 'no'!
There's an app for that!
Just by browsing the app store on your iPhone, you can literally find an app for just about anything you need! A month or so ago, I took a trip to Universal to see a concert. Even though I'd been to the park tons of times, my friend and I decided to go a little early and ride some of the rides. Because we'd be been before, we weren't interested in waiting in line for hours to go on a ride we'd already been on. So, we found an app to let us know the wait times for the various rides. You can check it out here: Wait Watchers. Just as the article says, the app relies on users at the park to update the wait times. We found that they weren't accurate because they hadn't been updated recently enough (try months off). There could be several reasons for this - parkgoers may not know about/have the app in the first place or users may be 'lurking' but not contributing. While this seemed like a great idea for an app, it would probably be more effective if it were updated by the park as the wait times for each line were updated. I guess you could say that this is a case where just lurking could be harmful (or at least not helpful). Thoughts?
Tuesday, July 13, 2010
Web 2.0 in the Workplace
I was browsing the web and I stumbled across this site: Web 2.0 in the Workplace. It talks about how companies can use web 2.0 tools to improve performance. It begins by addressing what is probably a major issue for most - the loss of control over the organization's image or message. Because web 2.0 allows for all parties to contribute, some users may contribute a perspective that is not quite aligned with the organization's, which may concern various stakeholders.
Personally, I believe if many of those stakeholders in a position of power within the organization take a leap and give web 2.0 a chance, they will realize that this is a risk worth taking. By giving employees and customers the opportunity to voice their opinions and give feedback, the company will be supplied with a ton of information that can be used to design a better product or service. Sure, it won't be all positive feedback and that can be scary because who wants to be told they aren't doing an amazing job, but having the opportunity to receive instantaneous feedback from various types of users will help the organization better itself if the feedback is used constructively. This could potentially even help organizations to troubleshoot issues more quickly, while helping to better meet the needs of the consumers.
Can it really hurt to at least try it?
Personally, I believe if many of those stakeholders in a position of power within the organization take a leap and give web 2.0 a chance, they will realize that this is a risk worth taking. By giving employees and customers the opportunity to voice their opinions and give feedback, the company will be supplied with a ton of information that can be used to design a better product or service. Sure, it won't be all positive feedback and that can be scary because who wants to be told they aren't doing an amazing job, but having the opportunity to receive instantaneous feedback from various types of users will help the organization better itself if the feedback is used constructively. This could potentially even help organizations to troubleshoot issues more quickly, while helping to better meet the needs of the consumers.
Can it really hurt to at least try it?
Week 3
What uses might a collaborative wiki or blog have in your chosen (current or desired) work environment? How would they support learning and/or performance? What would be the design and implementation challenges if management tried to do this? What would be the design and implementation challenges of a user-initiated effort?
In my current job at the Department of Highway Safety & Motor Vehicles (HSMV), a collaborative wiki or blog would be very beneficial (in my opinion, at least). This would give our team a means of cataloging various resources, providing tips and tricks we've picked up along the way (perhaps lurking in another community), and ultimately sharing our knowledge and skills with others.
For example (and I mentioned this one on the discussion board), during my first project as an intern, I faced several technological barriers with Articulate. I spent weeks combing Articulate's forums for answers. Finally, after not finding what I needed (and probably because I complained to their customer support so much), I was given a free web conference with one of their best technical support members. I sent him my project in advance, he reviewed it, then I spent a few hours screen sharing with him as he walked me through various issues and their fixes. After that meeting, I knew several work-arounds for 'bugs' in their software, many of which are not intuitive (i.e., to get the wipe animation to complete, add an off screen text box or shape to wipe last, so it will stall out on this object, not the one on screen). Having a team wiki would have provided me with a place to house this information (very knowledge management-esque). Now, it very well may die with me when I leave in a few weeks.
As far as actually implementing this, I see few problems as long as everyone (or mostly everyone) on the team is interested and willing to participate. Our team is pretty close (members and supervisors), so I don't think who this idea came from - management or the team - would be an issue. The only problem I foresee is that of participation, as a collaborative blog would not be useful if no one contributes to it.
Furthermore, since our training is public record, we don't have any security issues to worry about. Additionally, a wiki or blog would not require us to download any software, so I don't foresee the agency's technical support having any issues with us using such a tool, especially since we can speak to the benefits of cataloging information that will allow the team to perform more effectively.
Hmmmm... maybe I can talk the team into starting something like this before I leave...
In my current job at the Department of Highway Safety & Motor Vehicles (HSMV), a collaborative wiki or blog would be very beneficial (in my opinion, at least). This would give our team a means of cataloging various resources, providing tips and tricks we've picked up along the way (perhaps lurking in another community), and ultimately sharing our knowledge and skills with others.
For example (and I mentioned this one on the discussion board), during my first project as an intern, I faced several technological barriers with Articulate. I spent weeks combing Articulate's forums for answers. Finally, after not finding what I needed (and probably because I complained to their customer support so much), I was given a free web conference with one of their best technical support members. I sent him my project in advance, he reviewed it, then I spent a few hours screen sharing with him as he walked me through various issues and their fixes. After that meeting, I knew several work-arounds for 'bugs' in their software, many of which are not intuitive (i.e., to get the wipe animation to complete, add an off screen text box or shape to wipe last, so it will stall out on this object, not the one on screen). Having a team wiki would have provided me with a place to house this information (very knowledge management-esque). Now, it very well may die with me when I leave in a few weeks.
As far as actually implementing this, I see few problems as long as everyone (or mostly everyone) on the team is interested and willing to participate. Our team is pretty close (members and supervisors), so I don't think who this idea came from - management or the team - would be an issue. The only problem I foresee is that of participation, as a collaborative blog would not be useful if no one contributes to it.
Furthermore, since our training is public record, we don't have any security issues to worry about. Additionally, a wiki or blog would not require us to download any software, so I don't foresee the agency's technical support having any issues with us using such a tool, especially since we can speak to the benefits of cataloging information that will allow the team to perform more effectively.
Hmmmm... maybe I can talk the team into starting something like this before I leave...
Saturday, July 10, 2010
Hear a Blog
There are so many amazing web 2.0 tools just waiting to be discovered. Today, as I was skimming a blog I read on occasion, I stumbled across Hear a Blog (http://hearablog.com/) - a site that converts blog posts to podcasts so you can listen to your favorite blog while still being active (driving, running, being outside, etc.). Personally, I'm not an auditory learner and I prefer reading to listening, but I was still very excited about this capability - it's not my only means for consuming the information, just an option. So, check it out if this is something that interests you. You may find your favorite blog in the directory that you can now listen to on the go!
Subscribe to:
Posts (Atom)