Stuck on a design
After discussing Dribbble and Forrst, and my latest post that looked at criticism in design, I’ve been thinking a lot more about how feedback features in my design process.
When I used to get stuck on a design, from ‘creative block’ or a complete lack of inspiration, I would frantically brainstorm, then browse inspiration sites, then ask the opinions of other designers. Usually the feedback from other designers would form the basis of my amendments, I’d gain inspiration from those changes and continue work from there.
Somehow it didn’t feel right though, I didn’t feel like I was working for myself, asking other designers could feel a bit like cheating. I didn’t like how detached it made me feel from the design when I started to follow the ideas of other designers that have completely different approaches and styles from my own. I decided I don’t feel comfortable sharing work in those stages with other designers as they can be a negative influence on me. Not because they make bad suggestions, but because I work to satisfy them.
No longer craving that kind of approval, I’ve realised that I make extensive use of two new types of feedback, client feedback and ‘boyfriend’ feedback.
So it might sound totally obvious. Inevitably, you will always get feedback from the client at some point. However I’ve found myself doing this at earlier and earlier stages since I starting working freelance.
Lately I’ve been going straight into talking to the client as soon as the design slows down or is coming suspiciously quickly (usually a sign that I’ve jumped on a bandwagon or just acted on my first, badly thought-out idea.) I came to the conclusion that there’s no point searching for answers so far away from the problem. The client is the one person who set the brief and will approve the results, they’re the beginning and the end, so why not involve them more in the middle as well?
Feedback now, polish later
Number one newbie mistake is showing a client a 100% complete mockup (or even live) page design. I’ve done it, and kicked myself for it. Chances are you’ll have really jumped on an idea and run with it. The problem is that the client might not like your angle or approach. You’ve just wasted a huge amount of hours on something that is rejected outright.
You’re designing for the client
There’s no need to be fearful of showing something incomplete. Clients aren’t stupid, and if you explain that the work is unfinished but you’re looking for their input on what you’ve done so far, they’re likely to be grateful that you’re keeping them in the loop.
Unfinished work doesn’t necessarily mean bad work either. You’re not posting your work online for the world to see, you’re sharing progress and developing designs.
The benefits of feedback now
If the client is finding it hard to understand your approach, or flatly hates it, you’ve got time to discuss, justify, rework and whatever else is needed to create something that your client loves and you know will work for the user.
Design is just creative problem solving. If the client isn’t keen on what you’ve shown them and you’ve got some useful criticism, you’re further refining the problem which will help get you closer to the answer.
As a freelance designer, I’m very lucky to have another person around me while I work. My boyfriend Matt works in the same room at home and is an honest critic of everything I do, whether I want his opinion or not!
Non-client and non-designer feedback
Matt is great at giving me reactionary critiques. In this way, he’s far more like a client or a user. He’ll tell me he thinks it’s rubbish, and give a vague idea of why, usually based on reactions and associations such as “it reminds me of X.” Matt’s reasons are never because it’s not on trend, or it doesn’t make use of available technologies. In fact, he often hates the fashionable styles and can convince me to be more reasonable and not succumb to “but this looks pretty.”
One thing that struck me about the discussions about criticism on Dribbble, and the Gap logo, is that the type of feedback a designer gives is totally unlike the thoughts and opinions of clients and users. Those thoughts and opinions are exactly that. They’re not necessarily put in context or very constructive but they are the emotions and associations which are so hard to put into words but have a huge impact on your design’s effectiveness.
Community helps and hinders
I love the amount of apps and tools showing up to help designers communicate more effectively with other designers. It’s fun to share, and it’s fun to have a bit of mutual-appreciation going on. However I think I’m likely to fall into the trap of designing for these communities, for approval of other designers and developers, and totally forgetting the blindingly obvious user needs and client necessities.
Am I the only one? I think it’s hard to tell from the outside. Some people are very capable of creating work that is incredibly satisfying to users, clients, other designers and themselves. The order in which they aimed to please isn’t obvious!