UIEtips: The Magical Short-Form Creative Brief
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.
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.
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.
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.
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.
The end