I research, document, prototype, test, iterate, design and deliver. Being curious, and a critical thinker person I constantly question the "Whys and Why not’s behind the What is and What ifs."
1. FALL IN LOVE WITH THE PROBLEM
What are the business objectives? What assumptions are we making about our users and the business?
- Business requirements gathering
- Kick-off meetings
2. SEARCH FOR RICH STORIES AND FIND SOME LOVE
Who are the users and what is she/he trying to accomplish?
- Qualitative research to identify user goals and needs
- User interviews
- Journey maps
- Empathy maps
- Discovery maps
3. POV (Point of View)
How does business requirements align with our user's needs?
- Come up with the problem statements
What are some visual solutions? how can the UI satisfy our user's needs?
- Ideation
- Scenarios
- Sketching
- Wireframes
4. SHOW, DON'T TELL. KEEP EVERYONE IN THE LOOP, TO PREVENT BIG SURPRISES.
How quickly I can communicate user research findings with my stakeholders? How can I show the UI flow to our developer teams?
- Workflow diagrams
- Data maps
- Rapid prototypes
5. BUILD TO LEARN.
Is this the right solution? Is this design useful? Is it a simple, intuitive and satisfying experience?
- User testing
How can we make it better?
- Design iterations
- Handover for implementation
- Support implementation