About

How I hack it all together

tl;dr: ducktape

My Process

Find the fastest way to do the following, then repeat. Looks familiar, right?

 

Build

Workshop a lot of ideas. Prototype or build the validated ones, trash the rest.

Measure

See what users are doing with the new MVP/Feature. Find out why they're doing that.

Learn

Did we hit the success metrics?
If not, why? If yes, can we do better? 

 
 

 

Frequently Asked Questions

No one really asks these frequently. I mean... you get why they're here.

 
 
How did you get into UX design?

Getting my start creating interactive designs for iPad content, I had always wanted to make my designs more effective, more usable and also, used by many more people. At first that meant psychology of design but soon pivoted into user experience design. The gradual exploration and experience in UX design fed back into my visual design, creating better received, better performing projects for my clients. The two worlds have been building each up ever since.

What 'inspires' you?

This is the sort of question that makes me feel like one of those guys commenting on the nutty overtones of an avocado latte. Having answered it so many times though, I think i've boiled it down the most crucial component. It's simple really — users. After shifting around 1px stroke rectangles for hours, nothing breathes life into a project than when users interact with your work for the first time. Moreover, it motivates you to run back and get those changes done before anyone sees it!

 
 
 
What's the difference between good designers and great designers?

A lot could correctly be said here, but in my experience, good designers typically are great at meeting users needs but sort of just wash their hands of the process from there. Great designers meet user needs of course, but they also think about what the business requirements ought to be and how much more value they can bring to a client's organisation (and their own).

Should designers code?

I love sharing wild job descriptions so we can figure out if the expectations should make us feel sick to the stomach or if we should just nervously laugh off the ambiguous skill sets required. "Hey look, this one wants proficiency in Ruby on Rails, 5+ years experience in AutoCAD and Copy Writing is a bonus!".

Short answer, whatever it takes to get the job done. For me, that usually will mean being a code user, and maybe not strictly a coder. I manipulate, copy & paste, research, inspect, find & replace, call up my wizard friend — doing it straight in the browser or in the editor to help me reach my goals faster.

 
 

 

Folks I've designed for