I'm Kaye Mao, a third year Interaction Design student from Toronto.
I revel in dissecting complex problems and crafting elegant solutions that integrate seamlessly into a person's life. Solutions that make a positive impact on people's lives by having a holistic understanding of the way a person thinks and acts. I am especially intrigued by design that incites behavioural change, particularly within the healthcare, dating, finance, and productivity space.learn more
If you’re going to love something it needs to be the process of coming up with a solution. If you’re going to love two things, the other one should be that you’ve actually solved the problem. If you’re going to love three things, love the people you’re trying to help.
— Mike Monteiro
Before I 'do' anything, I outline my goals and break down the project into general steps. Then I plan out my process; taking into consideration time, resources, and scope.
Designing solely for the end user* is naïve and impractical. Design should understand and balance the needs of the business, the users, and the people building it.
Next: Research. The people who will be using the product, the competition, other designers, tutorials, anything and everything. I learn as much as I can about the problem space.
At this stage I define my context & design problem; potentially creating design artifacts to help me empathize and understand the target users.
Research and thoughts become mind maps & brainstorms. Ideas are scribbled down and sketches are small and drawn in rapid successions.
Concepts are reviewed, evaluated, & tossed. A few rough gems of concepts are selected as the seed for further ideation until a final concept is chosen.
Work smart instead of hard. This means having an awareness of and choosing the most efficient and effective tools for the job. Be it photoshop, code, or pen and paper; the idea dictates the strategy and tools.
Design is never finished; it merely becomes good enough to solicit feedback. Sharing, critiques, and user testing provide feedback that is used to fuel ongoing design iterations.*note: I think that 'user' is a single faceted term to refer to the people using a product. However, I use this term for conciseness.