On unpleasant, good, great experiences and why you should care about them.
Here’s a presentation I gave to my coworkers in a brown bag session. It’s a while ago, but still holds true. My goal was to help all of us better understand accessibility, its impact for users as well as how we could better build our software for users who have disabilities.
Behzod shared a 4-step research framework on how to decide on what/how to research: DECISION -> EVIDENCE -> DATA -> APPROACH.
Out of all the different types of card sorting I’ve learned, this modified Delphi card sorting method is the most interesting one.
As designers, our intuition and judgement take a big part when it comes to evaluating our own design ideas.
Sometimes, I kill ideas when they’re still in my head.
The problem with that is several fold.
How to expand your design explorations? How not to explore just “safe” design options?
As we walked away, I was thinking. Human connection is such a wonderful thing that gives you wonderful feelings.
If someone asks you to make a tool lighter so it’s not too tiring to use, is “lighter” the real solution?
Daily UI Design Challenge #26: Subscribe.
Imagine:Jamie works busy city life. She hardly has time to cook dinner these days. Going out every night costs a lot, she discovered that, sadly, as she jots down numbers for recent months’ spendings on food. $15, $20, $17… it doesn’t seem much per meal, but it’s a lot when all adds up.
She starts researching cheaper and convenient meal solutions. Instant ramen noodles? $2 per bag, but no, too unhealthy. Meal ingredient delivery services? No, too much work. Cooked dinner delivery service? Hmm. How much is it? $9.99. Recipes look good and healthy. A 30% off deal for first week’s subscription. Not bad.
Jamie wants to give it a shot. She inputs her credit card, reviews dinner choices and ready to subscribe to the service.
Trained academically as a computer science student, I was used to/still sometimes evaluate feasibility too early. When a solution appears, my mind starts asking “is this feasible” very quickly. That’s the downside of having an engineering mindset: you may run “feasibility evaluations” for your design solutions your head too early, rather than putting all the solution options onto the table, and waiting for your engineering partners’ expertise. This resulted in eliminating certain solutions prematurely. When you care about “what is feasible” too much too early, you stop going an extra mile to add a level of star experience for your users.