While I was interning at IBM, I designed intuitive interactions and workflows that were informed by user needs for the IBM Cloud Marketplace. As the visual design lead, I collaborated with a team of 5 (researchers, designers, and developers) to create a concept and present it to executive stakeholders.
Our team’s goal was to rethink the way that IBM handles its financial relationship with Cloud customers. We created a way for end users to get the software they want without the procurement headache. Due to an NDA, I cannot disclose anymore information, but I can present the final product during in-person interviews upon request.
Part of this solution is patent pending.
What do our users' really need?Understanding our users and what they really need was a major focus in our design process. To design the right solution for the right problem, we needed to understand and empathize with our users' pain points fully. Strategies we used included interviews, “hills", empathy maps, and user testing.
How do we get the right feedback?
The design process started with low-fidelity mockups so that we could receive the right feedback on our concepts and iterate quickly. As the concepts became more concrete with user testing, the fidelity of the mockups increased. Strategies we used included user journey maps, sitemaps, and wireframes.
Which feedback do we take?
Getting weekly critical feedback from peers and stakeholders was essential for creating strong, scalable products. We had to be confident in our expertise in order to make important decisions on which feedback to investigate. In order to succeed, we couldn't be afraid of taking risks and failing fast.
For more details on how you can get involved with IBM Design, visit their website at http://www.ibm.com/design/