![]() ![]() |
Moderator Alumni![]() Group: Hall Of Fame
Joined: 31-August 02
Posts: 15,634
|
Dec 21 2007, 12:49 PM |
|
|
Web 2.0 Can Be Dangerous...
Do too many people who build websites focus too much on building social networks, mashups, and other web 2.0 features to the detriment of their profitability? It's really hard to disagree with this paragraph from the article: QUOTE Before throwing spending money at "2.0" features, make sure that you have all the "1.0" requirements working to perfection. Of the 149,784,002 sites on the Web, maybe a handful can make this claim. Most sites don't even use the customers' terminology in headlines and page titles — if you want one quick action item to improve site profitability through better SEO ranking, more clickthroughs, and better understanding of your services, rewriting the first two words of your microcontent will beat any technology any day. But, there are sites that do the baseline minimum for SEO in page titles, in headlines, and provide a good user experience, and yet don't do much to make their sites engaging, and interactive. A good rebuttal here: Jakob Nielsen on Everyone's Favorite Buzzword: "Web 2.0" QUOTE What's sad about many of today's websites is not the abstract "things" they don't do well (nor whether these mysteries are primary or secondary); rather, that they simply haven't taken the time to understand our [the audience's] needs and plan the experience in advance to ensure those needs are met. Instead, they've been retrofitting Marketing 1.0 into a new medium, just as they have done with every medium that came before it. So, I have some questions: 1. What are the handful of websites that Dr. Nielsen might think are doing all of the web 1.0 things right? 2. What Web 2.0 features are ones that "either hurt users or simply don't matter to users' core needs" that sites add anyway. 3. Are the four trends that Dr. Nielsen points out as defining ones for Web 2.0 really what defines it? Thos would be:
4. Is AJAX too complex for most users? 5. Are most business tasks too boring to support community features, or in other words, is there a way to make most business task interesting enough so that a community will get involved? 6. Are mashups just too confusing when they involve more than one brand? 7. Does advertising only work on web sites when it involves search (like Google) and classified ads (such as eBay and real estate listings), and possibly video? Thought that this quote from Dr. Nielsen's article was funny, but I'm not sure that I agree completely about how he characterizes Facebook: QUOTE Like Iron Chef, Facebook has much drama that makes for good press coverage, but most of its features are worthless for a B2B site that, say, is trying to sell forklift trucks to 50-year-old warehouse managers. Instead of adding Facebook-like features that let users "bite" other users and turn them into zombies, the B2B site would get more sales by offering clear prices, good product photos, detailed specs, convincing whitepapers, an easily navigable information architecture, and an email newsletter. What do you think? Is Web 2.0 bad for the bottom line? |
||
| Offline | ![]() |
Industry Reporter![]() Group: 1000 Post Club
Joined: 19-May 03
Posts: 1,012
|
Dec 21 2007, 02:09 PM |
|
|
By and large, if you aren't doing 1.0 stuff right, you won't get 2.0 right either. And most of 2.0 is 1.0 with a reflective gloss of eye candy. Witness the thread right here about catalyze.org - a purported social site for usability.
Mark my words, Perpetual Beta will be as lame as Under Construction was for 1.0. Based on my experience on signup for catalyze, they're using perpetual beta as a "get out of usability, Free" card. Unfortunately instead of answering each and every one of these questions, they serve as an example in support of Nielsen. 1. Reddit seems to have search working, something Digg has perpetual problems with. 2. Where are the tests? For all the opensource this, and social user-driven that, where is the data? I think the belief is slapping social on it automatically just makes it usable, by default. There is a illusory belief slapping up a comment box will fix all your problems. This despite knowing user feedback is three layers of abstraction away from user observation. Social sites which don't to the social work of user observation aren't social -- by definition they're engaging in social avoidance. As anyone who has been flipped off on the highway can tell you, it doesn't take much distance for the "social' element to devolve rapidly. Autistic, maybe. Not social. Read Autistic Social Software. Check out: The password anti-pattern one of the only discussions on antipaterns in Web 2.0 you'll find. Usability for Rich Internet Applications may be the first and only article people who have read dozens of ruby and AJAX tutorials ever read. And of course there is the inevitable Usability 2.0 discussion. With perpetual beta as an excuse, almost everything should be relabeled 0.2 instead. From the article linked, Web 2.0 is: * Services, not packaged software, with cost-effective scalability * Control over unique, hard-to-recreate data sources that get richer as more people use them * Trusting users as co-developers * Harnessing collective intelligence * Leveraging the long tail through customer self-service * Software above the level of a single device * Lightweight user interfaces, development models, and business models. This shifts the load onto the user, who is now a co-developer. This is decidedly anti-Krugian "Don't Make Me Think" and all that. If you're talking from this point of view, all Web 2.0 is a net negative. From comments (and on the other side, policing comment spam), to voting, it's all additional cognitive load. Customer self-service is as good as your design, but is exponentially harder than static 1.0 types. Your design is as good as your methodology and testing. If you're using the beta badge as a loophole -- you have your answer. What's more usable, full service or self service? User tagging is inherently a chore. The only reason to do it is accuracy. And user tagging isn't all that accurate. Here, again, is one of the few articles which dares suggests improvement: Multi-User Tagging And, if anyone did testing of these apps and widgets, we might know something. Since the user is the "co-developer" the tendency is to not test. 3. Compare that to OReilly immediately above. 4. Most users will never know or care about AJAX. Just like you can make a usable Flash site, the tool is irrelevant, rather it is the culture surrounding the tool which strongly influences how the tool will be used. QUOTE Here’s my working definition of Ajax: The use of scripting to cause portions of a page to refresh without reloading the entire page. That usually happens after the user does something, but it can also happen automatically. -- Joe Clark All this is is time-lag, probably the most machine dependent part of the user experience, and arguably the most primitive usability feature known. With broadband the one thing Ajax had going for it, page refresh, is trivial for actual user experience. Again, most actual Ajax articles stress server load with only a passing nod that the user may get something out of it as well. Luckily the Joe Clark article Build Half a Product: Is Ajax accessible? At all? is one of the few which suggests programmers should have any contact with humans -- ever. Unfortunately he sinks into the accessibility garbage of WCAG guidlines rather than user test. When he does, the findings are applicable for the target group, the blind, numbering 1.1 million people in this country. Fewer actually have a computer and are online, but making this figure any less really makes the whole process of designing for Less Than One Third of One Percent of the people in America a little odd. Because guess what? Just because the blind can access the site in no way, shape or form means they can use it. And even then, you just spent that time on a fraction of one percent of the users. Like the perpetual 800x600 screen resolution debate, how many of your best target customers are on a 486 with 64megs and 800x600? Same question I submit to the accessibility people. Show me the customer database showing the 0.3% of the population you're spending so much time on are your best customers. My guess is Colorlovers spent more time on WCAG guidelines than user testing. The point is there is absolutely no understanding of who the target user is. It's simply assumed that if you make the site accessible for $25 monitors where 800x600 looks about right the user with a $500+ widescreen will be well served. Sorry, but it does not follow. Neither does it follow the 50-year-old warehouse manager is going to provide free Information Architecture with user-driven tagging. Face it, the user making Web 2.0 work is someone with nothing better to do. Usability, in contrast, is for a target user with a lot better to do. In other words the user testing for the roughly 99.7% of users who can fully use Web 2.0 apps might take a while. This post has been edited by DCrx: Dec 21 2007, 03:07 PM |
||
| Offline | ![]() |
|
|
| Lo-Fi Version | Time is now: 9th February 2010 - 05:24 PM |
| Meet our Moderators: | cre8pc : projectphp : sanity : Black Phoenix : bwelford : EGOL : Ruud : rustybrick : AbleReach : swainzy : joedolson: eKstreme: dazzlindonna : SEOigloo: iamlost : RisaBB |