-
- August 14th, 2006
- 1 Comment »
- Design
This week in ux-clinic: How to cut a bad, shipped feature
This week in the ux-clinic discussion group:
I’m on young team that has finally admitted to itself that a much-hyped feature of the last release (2.0) is actually quite bad. As in, on one can even figure it out to fully realize how bad it is bad. The problem is, everyone is all thumbs when it comes to what to do about it. The business folks want us to leave it in (the evil feature is still part of the marketing literature), but us UI folks are all for tearing it out – the problem is, how?How do you make the argument to throw away weeks/months of work? How do you message this to customers when something that was there disappears? I need the playbook for how to cut a bad, previously shipped, feature.
- Signed, Cut-less in Chicago
One Response
SCOTT'S NEW BOOK
A provocative collection of behind-the-scenes tales from the life of a successful public speaker, bestselling business author Scott Berkun offers a unique insider's take on what public speakers do, how they do it, and how anyone can do it well. Book Details
OTHER BESTSELLERS
- How I make a living: in detail
Peter says..."Hi Scott, Thank you for sharing this with us. Posts like these are a great motivational source for me. As I’m hoping (and planning) to one day too...' - How I make a living: in detail
Sachin says..."you should consider using ads (at least one small) to increase your income…….there are many good ad networks also where ads do not look bad...' - #41 – Why I left Microsoft
vivek says..."Great! There is always two kind of voices one come from heart and another come from mind. When you passed out of college you listened your mind but at...' - How I make a living: in detail
Elisabeth says..."It’s amazing how many people place so high of an importance on money that they will trade making more of it in exchange for doing a job they...'
Don't miss anything - Free Newsletter
Receive short, near-monthly emails with new essays, most popular posts, and occasional big announcements. Not cheezy - it's good, funny and concise. (privacy policy here)
I’m sympathetic to this one. In an ideal world, you’d find the resources to redesign it and test it.
But given the circumstances (and assuming it’s not a core feature), I’d bury it a level in the UI so that users can’t find it.
And at the same time, put in click monitoring so that for the fourth release, you can demonstrate to the business folks that no one actually uses it.