Gather and understand information

Before building, I need to understand the requirements of the product. For startups, this means I spend time with potential customers. For client projects, I review user behavior, interface with the team, define requirements, and consider business objectives.

Unite on an approach

For ill-defined projects, I start with the lowest fidelity representation of the product—wireframes. Once the project is better defined, I begin exploring how key screens may look in Sketch or in the browser (HTML and CSS). This step is complete once everyone agrees that early designs are the right approach.

Create the style guide

I now build a style guide that will determine the look and feel of the product. Any common element is defined and built out in HTML, CSS, and javascript. I then test the style guide against two or three key screens. If the resulting pages are simple to build and provide an intuitive and beautiful user experience, this step is complete.

Build the product

The style guide provides me the HTML, CSS, and javascript to build production-grade screens. I build out the rest of the product, making slight modifications as needed. As I finish each screen, backend developers lay business logic behind the interface. Following QA, the product is ready to be launched.

Revise & Polish

The solution is never perfect, so I track user behavior and identify opportunities for enhancing the user experience.