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?
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.
Waiting in a line at DMV. Enjoying an exciting concert. Working on a project with a tight deadline. People perceive time differently in various situations. How would a bit front-end engineering effort make a difference in people’s perception on applications?
I have some learnings from Eli Fitch’s excellent presentation “Perceived Performance”. The quality of presentation is as amazing as the content.
Simplicity is about subtracting the obvious, and adding the meaningful. — John Maeda
Daily UI Design Challenge #25: TV App.
Imagine: Dan is a busy young professional. He spends 12 hours working outside home every weekday. He has been wanting to have a regular work out schedule. The nearest gym is about 7 miles away, and he doesn’t want to drive far to a gym after he gets back home. He started looking for ways he could exercise at home, and eventually decided to purchase a dancing game disk for his Xbox. He’s not an avid dancer, but he would love to try it out. After all, this will make him move around and sweat.
Dan turns on the game console, and selects the dance game. After a few introduction screens, he landed on mode selection. Via Kinetic, his outline is captured and displayed on the screen. He lifts his hand and that gets captured as well. It automatically lands on the Easy mode. “Let’s take it slow for this first time.” He holds the hand still for 3 seconds, and the Easy mode is activated. He’s going to have his first dance.
“Not everything that matters can be measured, and not everything that is measured matters.”