My process begins with user research, interviews and persona development.
I work closely with user researchers to create user personas based on the problem we are trying to solve, and then conduct user interviews and surveys to get clarity on the requirements and data to back up our assumptions.
This is followed by information architecture and wireframing, where I create low fidelity mockups, sometimes creating clickable prototypes at this stage to get a better sense of the user flow.
The next step involves creating high-fidelity mockups in Sketch, which I then put together as clickable prototypes using Flinto or Invision. In some cases, I animate the interactions of these prototypes using Proto or After Effects (old school!).
Getting feedback from key people at each step of the process is critical to the success of any project. Especially important is getting feedback from the engineering team early on so that we can make the best design decisions based on the technologies we are using.
I work closely with engineers to bring my designs to life, providing style guides, image assets, specs and even pair with them while they are coding so that we can work through design details together. I have also jumped into the codebase on occasion, building static pages and editing HTML and CSS.
User testing is usually the next step of the process, I create user tests with 3-4 tasks and questions on usertesting.com or have in-person sessions with users to see how they interact with the app. The sessions are recorded and we watch them several times to make sure we haven't missed anything.
These sessions are invaluable as they allow us to see how the app performs across various devices and internet speeds. We are also often surprised by the reactions that users have to things we didn't even consider.
I work closely with product managers to understand how users are navigating the app, and if they are completing key tasks we want them to complete.
We look at metrics and funnels in Mixpanel, and are able to identify weak points in our user flows. Using this data, we often design alternate solutions and A/B test these different solutions to see whether the changes we are making are headed in the right direction.
7. A/B TEST
Most of the features we build are A/B tested using services like LeanPlum, and we look at the results of these tests to figure out the best solution.
But our work is not done. We continue to optimize the user experience to achieve higher conversion rates, which means our users are able to effectively use the app.
These steps are repeated each time we work on a new feature. Following a consistent design process helps us achieve better results faster.