Design Process

Use your brain not just your eyes.

Design isn't just about making something look great, it's about making it work well and providing a great solution to a difficult problem.
Below is my typical approach to a product design problem. It is flexible enough to remove or add further steps depending on the project. 


Business Needs
Talk to stake holders about desired time frames & budgets
Development Resource
Understand what tech knowledge is available within the team


User Needs
Understand what the user needs are from
direct dialogue, or by reading any existing user profiles
Research the competition in the market place
Rough Ideas
Sketch out some initial thoughts and ideas



Look at established UX Patterns that will be needed
User Stories
Write user stories to help keep focus and validate ideas against
User Flows
Create user flows to help visualise how the product and features will work
Edge Cases
Uncover edge case and decide which should be considered
Develop wireframes (thinking in terms of components)
Secondary States
Understand further states that will be required (errors, empty states)
Test & Prototype
Build interactive prototype using a service such as InVision or Marvel and
share them for testing with users and stake holders


Visual Design Patterns and frameworks that will be needed
Look at existing guidelines or design patterns if applicable
UI Kit
Generate a consistent UI Kit with reusable components
Animation & Motion
Define and ensure a consitent approach
Developer Guidelines
Either generate a guideline for developers or use a service such as Zeplin