Apparently, large images are the way to go. Ryan Battles outlines the how the use of images can affect customer decisions – to buy or not to buy? Bigger images usually meant greater conversions. Saloman, a snowboarding company, increased sales by 40% with these two designs. The above image is the BEFORE – it’s not bad. The above image is the AFTER – emphasis on large graphics.
My recent project involved designing a dashboard/control panel. What I played around the most with was the colors. I changed the header image to a variety of colors.
In his “7 Rules for Creating Gorgeous UI”, Erik Kennedy’s second rule is to start designing in grayscale, so one can focus on the layout and organization of the elements. It makes sense to me. He also demonstrates how when you design in grayscale, you can just add one color and everything looks visually appealing. Here are two of his examples:
I’m considering changing my portfolio to incorporate this concept. It looks really modern, but also photo-centered, which I’m unsure is appropriate for a UX Design portfolio.
Ian Storm Taylor goes on top say “Never Use Black”. It’s unnatural in the real-world – shadows aren’t black themselves. He pushes for saturation and the use of dark greys, playing around with brightness and hues. I remember considering using black in one of my designs and ditched it for dark grey. It looks much better.
Finally, this resource would be definitely helpful for myself. I have to play a lot around with what color goes well with another. I remember showing a prototype to some friends who instantly comment, “that blue and green don’t go well together” – and they don’t, I never thought they did either. Dribble allows you to see what other designers have usedfor color combinations. I looked up the blue color which I tend to gravitate towards, and just realized how good it looks paired with orange. I never thought of that – I tried green and yellow before, but I’ll definitely want to try orange in the future.
Communication and a quick feedback loop will save a significant amount of time, money, and work at the expense of just talking to team members a little more. I can relate this to one experience I had with a startup, who I feel did not communicate anywhere near what I would have wanted, and needed. A big problem was that I didn’t know their design goals clear enough.
I would submit deliverables (sometimes when they didn’t even request it…I just wanted to make their website so much better than it was!) and get replies days after or none at all. When they would reply, I would have wanted a ton more feedback, particularly on every design decision and why it wasn’t implemented. I couldn’t tell whether it was a limitation, a preference, a disagreement on ideas, or what. For instance, I may have raised a flag about a form error and I presented a potential fix (I’m always one to not bring up problems I see without also giving at least a shot at a solution). I got no feedback on it, so I submitted it again (along with other deliverables). Still nothing. I have no idea what they feel about the flag I raised, and it certainly is a reasonable issue. So I was at a loss at that point.
Lesson: to do the best work, designers need to know the team’s goals like the back of their hand. They need to get feedback on every design decision, especially when it is not taken. It can be frustrating to a UX designer when their recommendation, based on cognitive psychology research and standard UX principles, is not taken – it doesn’t make sense to them. The solution is overcommunication. Spend some more time with your team members and save a ton of wasted efforts. It’s well worth it, especially in a lean start-up.