Is all this written in stone? No. This list gives a general idea of how I work breaking down all the different components. Some weeks or sprints the process might be a lot less or more, it all depends on the the scope and timelines. No matter what these things are involvded.
Apply Empathy, Critical Thinking, Problem Solving, Communication, Visual Design and a Get Stuff Done mindset.
Before I move one-pixel the first step is to listen. I need to understand what the problem is we are trying to solve, what the user needs, and do they have a unique solution that should be created. Also, I need to know what the business needs are and what we are trying to accomplish (the full picture).
Key takeaways:
After I have a crystal clear understanding of the problem that needs to be solved I start to research the competitive landscape and other possible solutions. I also research internal products already created that might have a similar solution so that we do not need to reinvent the wheel. After getting the information needed I generate initial designs in the form of sketches, mockups, or rough prototypes. During this step I am also able to experiment with out of the box thinking first and reduce that down to real-world application.
Key takeaways:
SHARE & PRESENT: It is best to get feedback early. After spending a few hours on rough ideas I use this step to present my “best solution” to the team and or stakeholders to make sure my concept is going in the right direction.
FEEDBACK: I do not take rejection of my work personally! Gather feedback and iterate. [Repeat this step as needed]. Users will give real-world feedback as to what should be improved or is missing. Usability testing is also included here to dive deeper into the needs of a wide range of people, including target users to learn about their motivations, frustrations, and needs which gives a better insight to make a better product. Sometimes experience and best practices are used here based on previous products or simple research on how something should function or be displayed when interviewing and testing is not possible.
Key takeaways:
Final visuals are approved before going to development.
Key takeaways:
This is the phase I collaborate with developers to translate the design into code by producing style guides, delivering assets, and providing any support developers need.
Key takeaways:
Before launching the product into the real world it is best to get the product in front of users. Where I work currently we do A/B test on a small percentage of users for real live feedback.
Key takeaways: