The Anatomy of All Digital Interfaces
Hola! šš¼ mi nombre es
Iām a Design Technologist and User Experience Designer. By day I design + <code /> digital products and also craft Design Systems. By night I enjoy hand lettering, making moss art and doing illustrations.
About /oscar@oskrhq.com / Github / Codepen / Medium / Dribbble / Instagram
SkillShare class
Should Designers Code?
Empathize
Understand
It's not me. It's you. Begin by understanding what motivates and discourages the user and the business. Like my mom used to say when I was a kid; "do not judge a man [design for a user] until you've walked a mile in his [his/her] shoes."`
Define
Understand
What's the problem? Combine the research and observations from Step Uno, begin highlighting opportunities for innovation, and define the problem clearly. Helps to step back and look at the picture from 10,000 feet and ask yourself; "Why is there is this a problem in first place?"
Ideate
Explore
What's the solution? Come up with as many crazy ideas as possible to solve the problem, choose one solution, and formulate a testable hypothesis with it. A Scientific Method always helps. See? I learned something in science class... Oh, and don't forget to collaborate on this one! You don't know everything.
Prototype
Explore
How does the solution feel like? Create an experience for the solution you chose that delivers the least Cognitive Dissonance and most positive feelings. Resist the temptation of going Hifi too fast. Remember, Pixel Paranoia is expensive. Chill, and go old school first. Start with a pen, pencil, a big eraser and gallons of coffee. Show concepts fast guerrilla style if necessary. Oh and before you test, do yourself a favor and show the prototypes to the PM.
Test
Materialize
Learn. Learn. Learn. The primary goal is to learn. The secondary goal is to validate assumptions and your hypothesis. Remember, there is no failing nor passing. There is only learning. Every iteration and test you perform gets you closer to the optimal solution.
Implement
Materialize
Move on or go again? Depends on the results of your tests. Prepare for another run through the process, or if the hypothesis was validated, implement the solution and go get drinks with the team.
āš½ Important: Remember to invite the boss.
