Elezea
Requirements. Neil Hunt, Chief Product Officer at Netflix, wrote a good answer on Quora to the question Why doesn’t Netflix offer “Advanced Search” on their site? It’s a great Product Management lesson:
Nothing is purely additive unless everyone uses it. If there’s an affordance to use a feature, the affordance is a distraction to everyone, while the positive value accrues only to the users and potential users.
By Rian, 12 November 2012
Featured
UIE Brain Sparks
Requirements. In today’s UIEtips, I discusses the difference between failed and missed expectations, and how to avoid them. Here’s an excerpt from the article.
When many folks reach into their user research toolbox, the first tools to emerge are surveys and usability testing. However, these are not that helpful with discovering potential missed expectations.
By Jared Spool, 24 October 2012
UIE Brain Sparks
Requirements. Small is good. We love small products. Why not small processes?
Mobile phones used to be big and bulky. Then we found ways to make them smaller and pack more stuff into them.
By Jared Spool, 3 May 2012
ZURB
Requirements. We have written before about the dangers of adding features to your product just to make customers happy. Des Traynor wrote a great article recently about prioritizing the most used features over the marginal utility features that hang around unloved, bloating your app, hogging the UI and adding to maintenance costs.
It's very easy to fall into the trap of thinking that adding features will "add value" to your product.
29 August 2011
Johnny Holland
Requirements.
In my years of reading requirements, I’ve come to loathe the genre. As a written statement, the “requirement” is a somewhat strange and antiquated way to capture what a software system is supposed to do.
By Greg Laugero, 27 June 2011
Johnny Holland
Requirements.
A few years ago, we were working on a complex vaccine ordering website. We never seemed to be able to leave the wireframe stage and move onto development. The “discovery” of new requirements seemed endless.
Here’s how it went as we reviewed the designs for the shopping cart with the client:
Stakeholder 1: What about when the customer realizes they are purchasing using the wrong contract? Can they change it here?
Designer: Not in this design.
By Greg Laugero, 2 May 2011