AVOS’ Delicious Disaster: Lessons from a Complete Failure
1–10 of 70 posts
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#2There is no freaking lesson here, at least not so soon. Because they refuse to revert back, they possibly don't even know how to revert back. It's a major screw up in the history of Internet. Delicious has been doomed for long but people still use it, because browser bookmarking just sucks.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#3I can understand why hardcore lovers of the old Delicious are upset at the "changes". Change can be really tough if you've stuck with a site through that many years. But in the end, the old Delicious isn't changing - it's dead. What now exists is an entirely new site under the delicious coat of arms. What users dont understand is that there is no "going back". It's upsetting that your beloved site is dead, but mourn and move along - any attempt to revive it is folly.
AVOS is ultimately at fault here. They didn't want to hurt the feelings of the Delicious old guard, so they made it sound like everything was ok. But everything -wasn't- ok with the product those users fell in love with, it was being obliterated. The best thing AVOS can do now is help users come to terms with the present reality.
Ultimately, the re-launch was the right move - the delicious of 2004 cant survive in today's web. But AVOS's communication around the transition just wasnt frank enough. They should have just held a funeral.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#4I'm not referring to the new Delicious changes but the actual release itself, users still cannot login or retrieve passwords (including myself).
I've been over at the beta blog trying to get answers and judging by the amount of major issues, this does not look like a well planned release: http://deliciousengineering.blogspot.com/
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#5I can understand why hardcore lovers of the old Delicious are upset at the "changes". Change can be really tough if you've stuck with a site through that many years. But in the end, the old Delicious isn't changing - it's dead. What now exists is an entirely new site under the delicious coat of arms. What users dont understand is that there is no "going back". It's upsetting that your beloved site is dead, but mourn…
I use delicious on a daily basis, and I feel that the problem it solves is very much alive. Maybe I am a bit of a power user, as I search and tag (and love the automatic tag suggestions) all my delicious links from a FF plugin.
But I believe it is still a solution for a very persistent problem, and as long as it solves it, it will be able to survive very well in today's web.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#6This debacle is what made me finally switch to Pinboard. Well, that and I like the Pinboard guy's developer blog. http://blog.pinboard.in/
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#7A live and public website in use for a long time by so many people, goes back to beta and breaks everything. In an offline world, a service like that would possibly call for lawsuits all over.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#8I think this needs a little more thought. Think about this: Delicious doesn't really have a successful business model (if any). Yahoo! was about to kill it.
Now AVOS picks it up. Why would a startup pick it up? There is no way they can make a successful business out of the current state of the site.
But Delicious does have one thing: a big set of users and their bookmarks. Information.
It is obvious that AVOS was going to have to change the system enough to build a business model to experiment with. These changes are doing exactly that. They very well could be experimenting with the features, to see if their business model (hopefully there is one) works.
Now I agree with experimenting, I am EXTREMELY disappointed with the execution of it.
There are things that you just have to do right. Experimenting with features is fine, and since I get Delicious from free, I am willing to experiment. But if the site FAILS most of the time. That is unacceptable. I don't care if Eric Ries says "EXPERIMENT", use the "SCIENTIFIC METHOD". This is no excuse for doing a poor job with your tools and your subject of experimentation.
Unfortunately for them, and I do feel for them, I don't think the site will recover from this. The trust is gone. At least with me.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#9I'm not referring to the new Delicious changes but the actual release itself, users still cannot login or retrieve passwords (including myself). I've been over at the beta blog trying to get answers and judging by the amount of major issues, this does not look like a well planned release: http://deliciousengineering.blogspot.com/
And they're still blaming losing god-only-knows how many accounts entirely on the users. "Missed the opt-in emails" my arse.
Re: AVOS’ Delicious Disaster: Lessons from a Complete Failure
#10I'm not referring to the new Delicious changes but the actual release itself, users still cannot login or retrieve passwords (including myself). I've been over at the beta blog trying to get answers and judging by the amount of major issues, this does not look like a well planned release: http://deliciousengineering.blogspot.com/
And they're still blaming losing god-only-knows how many accounts entirely on the users. "Missed the opt-in emails" my arse.
[deleted]