Nice collection of design principles, and new to me. Design Principles FTW collects both universal and specific design principles and is curated by Gabriel Svennerberg at Meetod, Sweden.
Design Principles FTW
Blog
How GitHub Uses "Deprivation Testing" To Hone Product Design
Fastco interviewed Chrissie Brodigan, design and UX researcher at GitHub to talk about how they're using deprivation to study people's reaction to removing elements from a product.
The gist of the technique is to work with a set of participants who develop a pattern of use around a feature or design characteristic and journal their experience. After some time, at a point when they've had time to be accustomed to that thing, they take away or alter it, and observe through the journal what the users' reactions are to its removal.
It seems like A/B testing with a greater focus on qualitative measurement. Deprivation could be a powerful factor and tool for assessing value of features on both new and existing products. Designers and developers get to measure the features by removing them, and seeing how upset their users get within a controlled group. Removing features from an existing product is difficult, but the upside in measurement could be that features that have a cost to the user or vendor might turn out to be unnecessary, or the research could lead to improvement.
This is technique is new to me, but I'm not unfamiliar with the pain of having features removed for me, or the backlash you can experience when you change something as a designer.
http://www.fastcolabs.com/3010972/open-company/how-github-uses-deprivation-testing-to-hone-product-design
How to give constructive design feedback over email
I can't imagine email ever being the right way to critique design, or give feedback as a client, but nevertheless it happens, and Julius Tarng, who works on the Branch app, came up with some good advice for those about to give email, and those about to receive it. I think the advice applies for any feedback that's not face to face to face including chat and in comments.
- Get on the the same page
- Talk about what you felt, not what you think the user will feel
- Use past tense, not present
- Question constructively by asking for opinions, not challenging them to convince you
- Try to be specific, and avoid subjective words
- Don’t be dramatic
- Give the design some time, and ask yourself if that email needs to be sent now
Don't just read this list. Read the article at Medium.