Solving What You See

Design is really about solving problems. But how do you know if what you're solving even is the right problem? Or even if its a problem to begin with?

Learning to design is, first of all, learning to see. Designers see more, and more precisely. This is a blessing and a curse—once we have learned to see design, both good and bad, we cannot un-see. The downside is that the more you learn to see, the more you lose your “common” eye, the eye you design for. This can be frustrating for us designers when we work for a customer with a bad eye and strong opinions. But this is no justification for designer arrogance or eye-rolling. Part of our job is to make the invisible visible, to clearly express what we see, feel and do. You can’t expect to sell what you can’t explain.
— Oliver Reichenstein, Learning to See

The eternal issue for designers is how to define the problem they're trying to solve. Go too broad and you won't fix anything, too narrow and you've got the same issue.

Being open to possibilities, listening to people, simply sitting back and observing; these are the real tools we need to be using and developing every day. Better than learning code, or that sweet new version of Photoshop, the ability to clearly and concisely define a problem is crucial.

To top it off, clients aren't to fully understand what their problem is; they may not even know they have one. You'll need to convince them it exists before you can convince them that you've found a way to solve it. Clear, effective thinking and communication are required

So. Start by trying to see. Once you can see, learn to talk. Once you can talk, learn to do.