feverishaaron
Joined 18 years ago
Joined 18 years ago
The design should be validated with different users from the same cohort prior to building it. Functional prototypes work well here. Ignoring user feedback here is a huge mistake on the part of the designer. Design is relatively cheap, and it's easy to iterate and check your assumptions with users before anything is set in stone. Correct me if I'm wrong, but this step would have increased trust with your engineering team. Often due to ignorance, some designers don't appreciate how much effort goes into these builds, and how early architectural decisions shape the product in ways that make it difficult to change later.
Acknowledged, that this is a "perfect world" scenario and business pressure might require augmenting the process. An experienced designer would understand how to do this and still get meaningful results.
Companies buy iPod Touches to use as ticket scanners, credit card readers and product catalogs among other things. Same reason – cheap, wi-fi enabled, no contracts.
It was like the Tres Comma club, but tackier.
http://useyourloaf.com/blog/creating-scaled-images-with-pdf-...
-- A designer
If you're a peon, "doing your duty" is a great way to put a target on your back.
[ my public key: https://keybase.io/feverishaaron; my proof: https://keybase.io/feverishaaron/sigs/6-fKby424OTSn1P_h15ApCwa99Lmius1ri8NILKryXE ]