Designing easy-to-use, valuable and well-crafted UIs is one of the main goals of every Digital Product Designer. Two years ago, I started my journey with no real formal design background (Computer Science & Media). This post summarizes some of the insights I learned along the way as well as advice, that would have been helpful at the start.
The productivity of a Digital Product Designer is defined by the amount of good work he/she is able to put out into the real world together with the team. This is the place, where you get real feedback to learn and steer your product in the right direction. Unnecessary chaos in the midst of a development cycle often stands in the way of this goal. Sometimes developers find edge cases, which make the design unusable. Other times, a developer messages you asking for missing assets. A frustrating and time-consuming problem. However, there are tools to deal with those types of problems upfront.
This blog post was initially published on the HdM Computer Science and Media Blog and was written in cooperation with Malte Vollmerhausen.
Imagine you are going to a supermarket. You spot a pyramid of Campbell’s tomato soup cans. They are off by 10%. You take a bunch of cans and buy them. As a study shows, you statistically would have bought around 3 cans. Let’s sit into our Dolorian, go back 30 minutes and enter the supermarket again. You’re again seeing the pile of Campell’s (with the 10% discount), but now there is one little addition: a sign saying “Max. 12 cans per person”. As the study states, this time you would bring 7 cans to the cash-point. You made a completely irrational decision, because the sign should in no way have an effect on your decision making process – yet it does. As you can imagine, this problem is also present when facing security decisions.