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 illustrations.

Axiom:

To engineer desired...

emotions.

Doctrine:

"Art is all about making questions... 

Design is about crafting

solutions."

From sketching a single Sign Up page to building an app from scratch in code, I always follow the same process. Crafted out of personal experience (a.k.a failures) and some Lean UX principles, it saves me time and from lots of headaches, and ensures consistent results and deliverables.

MY process

how i works             |

01.

What's the problem?

The purpose of this step is to define clearly what is the problem I am trying to solve, gather as much information as I can about the factors that might affect the problem, and establish goals.

MY process

how I works             |

02.

What's the solution*?

Through a Divergence Sprint, I come up with as many ideas as I can that I think solve the problem based on the constraints and data gathered from Step 1. From that, I try to choose the best *solution and then I formulate a testable hypothesis. I should be able to educatedly elaborate how and why I chose that solution and subsequent hypothesis.

MY process

how I works             |

03.

What does the solution feel like? 

Design means a lot more than making something look good. It also has to make sense and invoke positive feelings. It all starts with empathizing with the user. Most of the time, this allows me to  create an experience that delivers the least Cognitive Dissonance and most positive visceral reactions. I find this Step to be the most rewarding and fun since is the the most human. I also usually start thinking about what technologies to use when coding/building and what technology constraints do I have. For this step my tool of choice is pen and paper, a whiteboard and Sketch app.

MY process

how I works             |

04.

What does the product look like? 

At this point, I have a testable hypothesis and a solution depicted through positive experiences crafted in Step 3. This is where you get to validate if your hypothesis is correct. I will usually conduct formal research studies, user interviews, A/B testing utilizing Invision, Axure, or AdobeXD to wire the designs and Flinto, Principle, or Origami for the interaction. Although I enjoy Inivision and Principle the most.

MY process

how I works             |

05.

What's next?

Once I have the results from my testing, I hopefully validated my hypothesis. If I succeed, I go forward with this last step in this iteration and build the solution or feature in code. It is not until I have validated a hypothesis that I even open the Terminal. That way I have data and logic to back my executions in code. After building, I move on to the next cycle of the same 5 steps. These 5 Steps might not be appropriate for every use case but it gives me a framework to go by, and how I feel most comfortable with.

See it in action

Creative Lab

Contact

|                get in touch
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form

OR