Sitemap

My Design Process

1.) Define the goal/s of the new feature/product

2 min readJul 11, 2014

--

What are we building? What problem is it solving? What metrics are we trying to improve, if there are any.

2.) Get feedback from users

What might a user want from this product? Are your assumptions about what the user wants correct? Would this new feature/product solve a problem the user is having? I generally talk to users constantly and am always seeing why users use our product, and what problems we solve for them. When I am working on the initial stages of a new feature I start to gather needs, and feedback from users as early as possible.

3.) Competitive analysis

Are there common patterns that have been established for this problem. Are there companies that are doing something different or interesting, why are they doing it differently, what is interesting about their solution? Do the established patterns work in our case?

4.) Define the flow

How does a user get to the feature/product? Where can they go once they get there? What is the user doing 3 minutes before using the feature/product?

Get Greg Mathews’s stories in your inbox

Join Medium for free to get updates from this writer.

5.) Design

Define the hierarchy of the functions you want in the feature/product. Start laying out the screen with pen/paper or with grey boxes. Get feedback. Design something in sketch/photoshop. Get feedback.

6.) Prototype

Prototype interactions that can not be shown with static mockups. I generally use HTML/CSS/JS or Quartz Composer. Get feedback.

7.) User Research

If you have users that enjoy giving feedback go through a prototype with them and figure out what is confusing, and if your solution solves a problem for them.

8.) Build

Build the actual product. I think it is important for the designer to build or have a heavy involvement in the building process to get everything working exactly right. Implementation is the difference between a good product, and a great one. While I am building the feature I generally find corner cases that I might not have found otherwise and can then create solutions for them.

9.) Launch

Gather resources required to launch and push the code out!

10.) View results

Compare the numbers to your initial goals. Improve areas where people are having problems and iterate.

--

--