Methodology

"Design’s fundamental role is problem solver"


Product requirements

Who is the user? Personas? What are the constraints from engineering and product? What are the use cases? What is the problem we're trying to solve?

What is the problem we're trying to solve?


Blue sky

What's the optimal solution? Daydream multiple solutions and see what kinds of cool explorations come of it.

 Map out the workflow and narrow down how it will actually fit in the product. Does it scale?


Wireframe

Mock up promising options from beginning to completion. Add basic user steps. Test! 

Now test!


Test

Create a test (whether it be A/B, usability, etc) and see how the design holds up. Is it causing any friction, if so, where? Are the users accomplishing the vital tasks/do they know what they have to do? Is it easy to do and is it a delightful experience?

Are the users accomplishing the vital tasks/do they know what they have to do? Is it easy to do and is it a delightful experience?


Iterate, iterate, iterate

Take your findings and redesign accordingly. Create actionable and thoughtful changes. 

Connect with your stakeholders again. Has any requirement changed?


Test again

Does the experience make sense now? What has changed that works better now?  Did you change anything that isn't working?

Decide on any necessary next steps


Complete visuals

Refine the details and make sure all use cases (empty states, 1 user, error states) are covered. Prep all designs so they're ready for review from engineering or product.

Prep all designs so they're ready for review from engineering or product.


Finalize specs and review with engineering

Ensure that all use cases are identified. Review with engineering to determine final costs and confirm that there's no miscommunication. Keep the dialogue open throughout development.