|
by
Will Evans
Member since:
August 31, 2005 The Paris Hilton of Interface Design. The New Gather
July 14, 2006 05:27 AM EDT
(Updated: July 14, 2006 08:47 PM EDT)
views: 148
|
rating: 9.4/10
(5 votes)
|
comments: 57
I logged into Gather this morning to publish my article and was immidiately surprised to see the new Gather User Interface architecture. After the initially pleasing visual - which I wasn't surprised at because Tommy has always done amazing worked. I then set about publishing an article. And got lost. And Frustrated. And Confused. And finally pissed off. First, though, to Kevin who wrote the review of the new User interface -- if I could go back and review your article, I would adjust the ranking I gave you down to a 2 - well, okay the article itself gets a 4 for omotting all the problems, but you truly believed that at least the most glaring issues were going to be dealt with before management moved forward with this nasty turd. Someone should have warned us that there would be significant re-learning of the user interaction for common task flows - I wasn't prepared for the significant decrease in my productivity which someone should have warned me about. And I would give myself a 2 for not finding a way to contribute to the new interaction design. I should have been more engaged - I should not have stood back and trusted the experts. So where does this fall down? I will focus on the two most important things to me - efficient navigation to my articles, and efficient publishing. By removing the DHTML navigation dropdowns, and now have to click twice, compared to once, to get to My Content, which should take me to My Conent -- but doesn't. Now a new top level navigation item is presented in the navigational structure that didn't exist before - right next to the other nav. item called Namespace. This creates cognitive dissonance. You cannot click on a Nav labeled My Content, and then change the label name to Namespace. Second is that I can't view my last five articles, and last five comments. It's been reduced to three. Is there a dropdown preference to change this default to 5? No. But on the upside I can now subscribe to myself... is this useful? No. And - when I subscribe to myself, it goes to a separate page. With no breadcrumbs. The pop-up window was better. Period. Also the subscribe and cancel button don't match - but as I said - we'll ignore visual design and stick with what I know, which is interaction design. But I can click one more time to list my last ten articles. A smaller note: It use to take one click to publish an article. It now takes two. 100% decrease in efficiency. Once inside the publishing workflow, everything is the same. Given how jarring the simple act of just getting here though - I just type in an article title, body, tags. And move on. I go back to Gather home, and then go to preview my last articles in the list. From Gather > My Gather > My Content (whose title changes from My content to Namespace for some very some completely unknown reason). Furthermore -- technically my mouse goes far left- click (My Gather), far right click (My Content), this zigzagging across the screen introduces the likelyhood of user error. Bad call. From my Namespace, I see a list of my last three articles.Can't edit them from here. I used to be able to edit them. I believe this was one of the comments that Kevin brought up with Gather's user experience team? Okay. Let's move to editing an article (and adding a picture to the article) -- click article title > Click Edit. Back into publishing workflow. Upload image > Add Caption, Add tags, click and go. Article image now placed to the right of my first paragraph. Hmmmm. That whole left side is now annoying me. It gives me a list of suggested tags pointing to the right. Does this imply tags suggested for this article? No. These are tertiary navigation items not related the the article. The must be for that huuuuuuuuuge, big, vast empty swatch of unused real estate at the top of the screen. Jesus - it must be, 200 pixels tall, and spans the entire page from the gather logo all the way to infinite. I think it must be a testimony to the emptiness of my soul. I suppose it won't look so vapid, ooops, I mean empty, once a great big flashing, animated Advertisement is dropped there in all its stinking glory, but right now its just wasted empty space and I resent it - because the Tag navigation could have gone there, given me more real estate on the left column, removed the useless tags which are not at all related to my article, and not stuck my damn image right in the middle of my article. If I wanted the thing in the middle of my article, I would have stuck it there. Gather Home Page. No more Editor's pick. No more top ten community picks. No more top tags, sorted. Are there any features? I am writing this as I would for a heuristic evaluation with a mental check list of all the common things I do every morning, and then writing this as immediate reaction. The way a real usability study is supposed to work. I don't think Gather used a persona of an expert user who has a list of 5 common task flows they do every morning. If such a list were used, it would immediately become apparent how bad this interaction really is. So the home page is significantly cleaner. But offers no value. 1 featured conversation, 3 groups, 3 people, 3 images. Sparce, thin, beautiful, and no value. The Paris Hilton of Interface Design. Finally - a business strategy note. When Yahoo! makes this significant change in their user interface design, they allow users the option to switch between old and new. That option is not given. So I guess I am stuck with this. Please, please fix this. I wasted this morning writing this aweful rant instead of publishing the article I wanted to publish. Oh, yeah - Kevin - you no longer get a 2. You should have warned me, but according to our earlier conversation - you did make note of many of these issues and brought them up in a face to face meeting with Gather, including Jim Bostich - who should be the absolute guru of interaction design - and should have taken these comments seriously, and should have fallen on his sword when he was overruled and management decided to go forward with this. Build 5341, "André" I will now refer to from here on out as "Paris."
Tags:
gather,
interaction design,
will evans,
paris hilton,
heuristics,
usability,
ui,
user interface design,
frustration,
interface,
new gather,
gather review,
design
To Group:
improve.gather.com
Please provide details below to help Gather review this content. If it is found to be inappropriate and in violation of the Gather Terms of Service, action will be taken.
You have successfully submitted a report for this post.
|
|
You might also likeMore by Will Evans |
||||
About Gather |
Engagement Marketing |
Make New Friends |
Gather Points |
Advertise on Gather |
Gather Press |
Privacy |
Terms of Service |
Community Guidelines
Books | Celebs | Entertainment | Family | Food | Health | Moms | Money | News | Politics | Spirituality | Sports | Travel | Writing
Books | Celebs | Entertainment | Family | Food | Health | Moms | Money | News | Politics | Spirituality | Sports | Travel | Writing
Version 16836, "Oz"; Copyright © 2009 Gather Inc. All rights reserved.


Comments: 57
For tomorrow's review, we'll focus on the Search engine functionality, lack of taxonomy, and decreased Tagging navigation.
Also, the only article published last night that is NOT about the new Gather that has garnered any signiicant number of comments is one by Jake on WWIII.
I think the points you make are excellent because they are very technical in nature.
Let me point you to my article,
http://www.gather.com/
viewArticle.jsp?articleId=281474976766869
where you may find interesting comment, too, but not as useful in its technical merits department.
I fear a lot of duplication in the new Gather because it is more difficult to find new articles than before.
I agree with your summation that no expert user was used, nor a real useability studey.
It would be good if Gather offered a choice, but it looks like this is the new installation.
I agree the new Gather is much less useful.
Gather threw out the baby with the bathwater - steered away from 'brand' management thinking, created a completely new product, 'fixed' things that weren't broken, and elimineated features and functions that worked and were well liked.
I, too, have not published the article I logged on to write.
I also don't see the new Gather as being more helpful to new viewers - less, actually, because less information is presented.
I'll provide the link to Marina G.'s aritlcle, too.
Jake S.'s article is here:
http://www.gather.com/
viewArticle.jsp?articleId=281474976766868
Mandi G.'s article is here:
http://www.gather.com/
viewArticle.jsp?articleId=281474976766875
I think it is more difficult for people to find articles that have been published. Once an article is a few hours old, it will switch to the previous page and nobody will see it, if it has not been commented upon.
http://www.gather.com/
viewArticle.jsp?articleId=281474976766891
and then you have to click "my Content" to finally get what you're looking for, but then you are isolated from teh world and can't see any activity ongoing elsewhere
so no more pretty thumbnail hopping or quick access to other pages, just a very juvenile layout that's made with the look of a bennig ESL reader in disgusting colors.
and yes KEO, we see your importance in the wold despite all -- but now your little icon shows up headless. and you'll still keep up all the chatter even better than the proverbial headless chicken--
and actually, Paris Hilton would have done a better job, because at least she always looks sleek-- she does understand mass appeal and marketing, and when it comes down to it, is no bimbo because she gets paid for party appearances and retains high rankings over the internet.
s Topic feature.
Also - right now this article has a 10 rating - but I have no idea how many people have rated it. Not that that matters so much - but was it 1 person? 10? Weighted average?
First of all, PLEASE NOTE that my review article was not intended to be a full review, and was solely based on a few times where I was able to see the basics of the design. The primary goal for my article was to communicate that certain negative aspects of the old Gather would still be inherent with the new.
Perhaps it was a mistake to try and strike a balance within my article, and not get into too many details. I also did not think it would be fair, to Gather Inc. or the community, to pan the new Gather too harshly before it gets out of the gate, especially considering that it could be significantly changed when it does, rendering all of my concerns moot. However, in this case, they weren't.
I personally think that the new Gather has significant weaknesses.... far more than you identify in this article, and that extend far beyond the technical.
I'm not one to say "I told you so". But I did inform Gather of my concerns several times, and my issues went unheeded (for the most part). I found this to be very aggravating, as most of my observations should have been obvious to others as well. However, as Tom stated, there were many (hundreds? thousands?) of members contributing to the design of the 'new' Gather. I am but one voice in a chorus.
Perhaps I should have sung louder.
This is much more of a major change than I was used to.
I don't think the Editor's page (new Gather home page) will accomplish much. I don't think it accomplished much before and I don't think that changes.
DId you guys notice Tom commented on his article this morning? He will be hosting a live chat at 1 pl.m. EDT today.
I'll provide a link here to Tom' s article, since I've done that with the others discussing this.
Our heads our chopped. Does my decapitation turn me into Marie Antoinette (since we're discussing celebrities here)?
If so, do I get to say "Let them eat cake?"
KEO: Sorry you lost your head.
He also discusses going live today at 1 p.ml EDT to discuss.
http://www.gather.com/
viewArticle.jsp?articleId=281474976765154
I split the article ID because under old comments, the ID
was too big to fit in one line and would leave off the last numbers, rendering the ID useless.
Yes, I'm aware I can link this ID in a message. I miss having the LINK icon in a comment box that we had in the publishing tool. It's not possible to do that in the comment box, and I'd have to spell it out, which I don't have memorized at this point...I used to have the code memorized a few years ago, but not now. Something for me to do...not difficult, just I have to do it.
Other usability crimes: I went to comment on an article but wasn't signed in. it took me to sign in. then dropped me into my gather. it ignored where i was and what i was doing. that is another break of a golden rule of web page design. If you must navigate a user away from their intended goal for login, BRING THEM BACK where they wanted to go. Duh!
I am actually quite mad. But I also feel bad because i couldn't come to the webex preview last week i was invited to. but it sounds like these points were raised anyway.
Sorry but this violates all the things taught in Web 101 class. They need to revert to old build, then relaunch this with bug fixes and with a choice to toggle between interfaces. I know that will be more costly, but less costly then lost ad views due to frustrated users leaving. Again, web 101. Wow.
How could a site pass QA that chopped off the heads of the most frequent users of the site?
Keyboard navigation keys don't work to scroll articles. That's PRE Web 101 folks.
Having spent 10 years in charge of web site development and design I can't even begin to tell you how I'd react if one of my teams handed me this build. Of course, if done right these issues would have been addressed in the functional spec long before the build was handed to me. So many of the issues I have are not page generation problems, but core design flaws that could never pass muster in a competent web usability department. With that said, I have seen some page generation problems too. Good ole "Page DONE with errors" message from IE.
Enough. I hope we get notified when the old build is reinstated and a plan for launching new functionality with toggling between UIs is hatched.
When I delete a comment I make, the choice is to be 'return to your comments.' Since I don't want that, I click the BACK arrow on Firefox to get me back to my article.
Toggling between interfaces would be a very good idea.
I do encourage people to try out the other articles discussing this today. I'm not plugging shamelessly here, the points are not identical in the articles.
I agree with you Rich about revert to old build...
Tom did say this new version if more extensible...
I wasn't invited to the preview people are talking about.
Was it in my email notifications that I missed? Or, did people think I simply have too many comments and too many views?
Now, why would anyone think that?
Notice that Juliet Capulet is now headless.
You can get to "Today's Topic" by going to the homepage and clicking on the "topic of the day" tag. The Editor's Picks are still there, but they show up one at a time. You can click on "more articles" to see the rest.
viva Andre!
I can no longer see that.
Will, you can see new emails and new invites in top right hand corner. Bill's Spirit informed me of that. It is not intuitive because you are at least the third person who has mentioned it.
I worked on the very first designs -- Alpha and Beta (Cheryl), which was the release before magritte. Magritte was in some ways an improvement over Cheryl, but removed the top level taxonomy (which was very useful, but also had a lot of baggage - specifically in the publishing workflow).
I have been very happy as "a end-user" just like everyone else here. I have no input on the direction of the UI, other than as a user with articles like this.
http://www.gather.com/viewArticle.jsp?articleId=281474976766952
The issues that I have raised here especially the most glaring navigational issue- that input was actually already provided to Gather 'before' they made this release. I can only surmise that that advice and input was not heeded.
http://www.gather.com/viewArticle.jsp?articleId=281474976766953
The average user, knowing nothing about back-end and the true capabilities of the medium, will focus on surface, shallow issues such as:
The font's too small!
I don't like these colors!
I'm confused!!
So the team, in essence, appears to have responded to these types of complaints.
I'm not saying they don't have some merit, but there's not a lot of *improvement* here in terms of the technical functions that might actually make Gather a better place.
I have said for a while I'd like to customize my public Gather home page, so that it's like having a blog.
THAT would be a cool thing for Gather to do. But did they do that? Nope. They spend oodles of time paying some dumb-ass graphic design to create bright orange comment balloons.
Waste of resources, if you ask me.
good...
1. larger pictures
2.
bad
1. gather banner at the top is way too large
2. the font size looks like it was designed for idiot proofness
3. cannot find articles i want to comment on
4. cannot find people who were one click away
5. as a matter of fact, cannot find anything
6. still no ability to sort pics
7. ad space is way too large and intrusive!
8. productivity has dropped exponentially
9. kelly clarkson
10. makes me want to log off and go back to squinting at the last make (why do web designers always feel the need to use verdana for everything!)
Magi
Glenda, I think all this orange is an Irish citrus plot.
Magi
Time to publish my article Zen and the art of application flow. Perhaps people at gather will read it.
The user experience should be:
• Comfortable
• Intuitive
• Consistent
• Trustworthy
The term user experience has been defined and described in many ways, but at Gather we, THE USERS, should define user experience as "the overall perception and comprehensive interaction Gather member's have with the Gather Website. A positive user experience is an our successful and streamlined completion of a desired task." When designing a good user experience it's important for Gather management to remember these four principles, which should be a part of any usability or user experience specialist's toolkit. While these are not the only components of a complete experience, these principles form a solid structure upon which to build a foundation of usability, information design and meaningful Gather Experience.
This site is really bad. It's super slow, always has been. It freezes -- alot.
This build, in my opinion, bodes very badly for the future of Gather. Not JUST because they changed the front page to a bland, sterile, boring piece of crap that must be aimed at somebody's vision of the ideal demographic for this site, but mostly because the other things they did (and didn't do) proved that Gather, Inc. doesn't have the slightest freaking clue what it's doing.
Also, a lot of you seem to think that since everybody's spent the last 24 hours complaining, Gather will immediately do something about it. What the hell do you base that on?
People have been bitching about the editing functions (pretty core, isn't it?) and the rating system ever since I got here and, to date, they have done NOTHING about either of those very basic elements of the site.
They really, really messed this up.
Rich is right about Quality Assurance/Quality Engineering. This version - Paris - and even Magritte - would not pass an acceptance testing and unit testing process. There are two very important aspects here -- does this system allow users to perform tasks in the best possible way, and does the system perform "as expected" within some defined space of how an application should do so.
But these priorities are not set by the application developers. They are set by managers and the person charged with overseeing User Experience. User Experience should care just as much about quality assurance as it does about navigation structures and task flows - and the user experience person should work in lockstep with the manager in charge of QA. These are process and management issues.
All development projects have 5 parameters that can each be stretched or contracted to meet a need. They are often drawn as a baseball diamond. I use such a diagram when talking to my fellow exec staffers, boards of directors, and even explaining decisions to end users. Here are the elements:
Features - the number of features and how deep each one is
Cost - the cost to develop this software project
Quality - how well it works to achieve desired result
Time to market - how fast you can ship it
Partixipant Satisfaction - how badly you will burn out your workers, testers, and users.
You can rush a release to market by cutting features, compromising quality, spending more money, or killing the staff. Each variable can be changed. The magic is getting a company aligned around what choices you are making. For example, all software has bugs, you can't fully empower QA with the decison to release or not. Most software would never ship. Nor can marketing decide the feature set without adequate analysis of cost and hit to time-to-market. If you burn out your staff, quality can suffer, sabotage can occur, and the intellectual capital walks out the door with a middle finger raised. Balancing these elements is the key. Experience is the magic bean to balancing these elements. Each flavor of development has different relationships between the elements. In other words, a web site/service has different interactions between these 5 elements then a shrinkwrap software product. 10 years ago I helped change that for shrinkwrap software when I invented LiveUpdate, which allowed the software to update itself and shifted shrinkwrapped software to a model not unlike a web project. Likewise, I see web projects shifting to be more like shrinkwrap software in ways I cannot discuss due to common courtesy to companies like Gather and Non-disclosure aggrements.
I didn't really get to know any of the Gather execs well enough to really judge their competence. If I was an investor there would be tens of hours more due diligence. Shit, I got a mere 15 minutes with Tom and the CEO is certainly the most influencial person with respect to defining the company's core competences.
What I can do is observe the site's performance and release planning as I have seen it since I first met them when I went to the office's to interview for a position there. During the months since, the site got slower, harder to use, less consistent, and seemed to lose focus on what it wanted to be when it grew up. What I would have expected was improvements in most, if not all, those areas.
With that said, it is a pretty cool site and an amazing accomplishment for such a small team. Although someone out there put up some millions to make it happen and if I was them, and I have been in their position with companies before, I would be asking if the company is moving closer to the stated objectives. Sometimes the stated objectives are exactly the problem. What if the objective was "ship new site design by July 15" rather then "Improve usability for ne users allowing 25% reduction in abandonment rate while increasing productivity for power users by 25% as measure by time to do common tasks." Sadly, the first objective is SO MUCH MORE COMMON then the second, well reasoned objective. I don't know, but given the points rollout and this site push out, I'd almost say some questionable objectives may be the root of the problem.