A couple of years ago while I was working on a project with Kevin M. Hoffman, he related a story to me about his consulting work with an agency on improving presentations to clients. The story centers around a designer who was asked to change his mode of dress. This designer was fond of the goth look, but the agency considered it inappropriate for some client meetings.
Long story short, Kevin told the staff member that he could wear whatever he wanted to, but to consider the situation in terms of his desired outcomes. Clients’ opinions about clothing and personal expression aside, what was more important to the designer: dressing a certain way, or successfully pitching the design direction he was the most excited to work on? The “what to wear” decision then becomes less about the designer’s pride or interest in retaining control, and more about getting what he wants in the situation; acting in his own self-interest to the best of his ability.
Recently, as I worked on an extended project for a client at Bearded, these ideas started percolating through my brain again, but this time with regard to design. Every designer (and really everyone involved in a design) has tendencies and predilections that, like it or not, will be guiding the design process.
Of course we make our best efforts to ground the creative process in research, interviews, and egalitarian decision-making activities (sticky notes and card sorts, anyone?). But no matter what we do, our entire process is filtered through the very fallible, very subjective minds of people.
Let’s talk about your childhood#section2
For a moment, we’ll zoom in from our mile-high view and consider a single person. Let’s imagine a child who grows up under the care of well-meaning but disorganized parents. The parents’ plans and decisions are unpredictable. The child, never knowing what will happen next, grows into a bright, talented young person with an unresolved longing for structure and order.
We might even imagine that this need to bring order from chaos, to sort out the unpredictable, messy parts of the world, is what draws them into a career as a designer.
As they find their professional legs, they mature into not so much the David Carson, Stefan Sagmeister, James Victore, anything goes sort of designer — more of an Erik Spiekermann, Willi Kunz, or Sylvia Harris. They’re not out to tear the design world a new one. To the contrary, they’re focused on sorting out the garbled information before them; smoothing over the rough patches, and slowly rotating their subject’s gleaming, flawless, chrome surface towards the world.
And there’s nothing wrong with this orderly sort of design. In fact, it’s very, very useful to the world. Perhaps even necessary.
Likewise there’s nothing wrong with that wild-eyed sort of design, either. One might imagine (as many do) these types of design as poles on a spectrum of useful approaches. Poles between the qualities of Consistency and Variety.
As it turns out, every project demands to be somewhere on this scale. And it’s essential during the first part of every project (the research, the interviews, even the sticky notes) to figure out which spot on the spectrum is best suited to the project.
Now the extremes of this range are rarely appropriate for any project. An unwaveringly consistent design approach will often seem generic and boring. On the other hand, a design that is entirely committed to variety will make the audience struggle at every turn to orient themselves and parse the information before them.
So it seems fair to say that most designs benefit from being somewhere in the middle zone, balancing between the unhappy extremes of boredom and chaos.
But what happens when our imagined designer – the one who is drawn to systems of order and control – determines through their research that their project requires a design approach that is on the more varied side of center? When the organization, in fact, will benefit from a less rigidly ordered design? This organization, it turns out, needs an approach that may not sing with as much immediate and obvious clarity, but will bring more surprise and thrill to the audience.
And so we find ourselves with a mismatch between impulses (bring order!) and outcomes (show us surprises!). The problem is that the designer’s approach is not in a conversation with the project and its goals; it’s stuck in a very old dialog with the designer’s childhood. If left unaddressed, a successful project outcome will depend on whether or not those old desires happen to match up with the project’s requirements.
If we don’t want to leave things up to chance, this situation requires the identification of both the designer’s impulses and the project’s desired outcomes, and a conscious assessment of their overlap and contradictions.
When I was in a critique at design school, one of my classmates commented on another’s work that they “really seemed to be developing a style.” My professor became suddenly incensed (a rare thing for her), and declared “you’re designers, you don’t have a style! Your style is whatever is appropriate to the project!” In that way design is very different than art. Art stems primarily from the artist’s internal world. But design does not. Design aims to solve problems outside of the designer. Whereas the artist might be seen as a sort of oracle speaking to the world, the designer is more of a tool that is useful in solving problems.
Which is why, in the cases where a designer’s internal impulses and the project’s desired outcomes are not in alignment, the designer must consider adjusting. To be a useful tool, we must recognize that some of our impulses work against the needs of the organization that is employing us, and compensate.
This is no easy task. It’s a process that requires knowing oneself, and questioning our own nature and subjectivity. But it’s only through this sort of rigorous self-assessment and awareness that we can grow beyond our limitations–becoming better designers, and perhaps if we’re lucky, more sensitive and thoughtful people in the process.
7 Reader Comments
Great article! It perfectly describes the design phenomenon I sometimes call “banging my head against the wall” for indeed there is a duality between communicating clearly and opening eyes (and minds).
There’s often a disparity between what a client will accept and what an audience wants to experience, and I think it’s our role to act as advocates. As for style, I’ve always considered it something that happens unavoidably going through a design process, not something nurtured or promoted.
I think Tibor Kalman had some legitimate things to demonstrate about the same quandaries you mention, but it’s possible he ended up so far from the status quo that nobody took him seriously. Personally, I find his blatant adoption of the vernacular a good reminder of who we are really designing for.
Nice wrap up in the article too, Matt. Thank you for sharing your thoughts!
Thank you for the thoughtful response Siebert! And thanks for referencing Tibor Kalman. Always loved that umbrella of his. 🙂
It also brings up the difference between something like being the creative director for a magazine and doing project-based client work—which with its constantly changing goals, is going to emphasize the need for selflessness in design a little more.
One thing that my be useful to consider is that it’s even possible to create great design work that the designer doesn’t (personally) like.
If we start by acknowledging that any design will be liked and disliked by people, then we can also acknowledge that personal preferences (the designer’s or the clients’) can be set aside. What matters is are we communicating what we want to communicate to the people we want to communicate to? And when we do that does it generate the desired emotional resonance? Or, in other words: audience, content, and tone. These things canbe judged independently of the designer and client.
When I look at my own work from over the years this way, I find that there’s a difference between the designs I like the most (what I’d hang on my wall), and the designs that are most successful (which worked best for the client and their users). And what’s interesting is that this outlook, as I get older and internalize it more, starts to change how I view my work.
I find that my favorite designs are now less about what visual details and elements I enjoy the most, and are more about how successful the design was at solving the project challenges. And when both happen, that’s just cake.
On a personal level, I find the effect even more profound. I’ve noticed that over the years I’ve experienced less and less fear and anxiety as a designer about such things as “will people hate the design?” and “what if I’m a bad designer?” Because the success of the design isn’t about the arbitrary liking of it by someone.
Additionally by taking myself out of the design in this way, the design ceases to be a representation of me, but rather simply the work I do. Maybe it’s a minor distinction, but I find it’s much easier to take criticism and learn from that experience when it’s not me up on the chopping block, but my work. 🙂
Thanks for your work here. I am relatively new to design here – but I really want to thank you for putting a sneaking suspicion of mine into words.
Possessing the emotional IQ necessary to “get over yourself” and focus on what is best for the project at hand will surely make for better designs and build trust with clients. If we as designers take the lead in this maybe more of our clients will find the strength to “get over themselves” as well – and together we will reap the benefits of a more selfless collaboration.
As for the example of the child born to “well meaning but disorganized parents” – it reminds me very much of somebody I know.
Thanks for the kind words, Cody!
We have a pre-design-review document at Bearded that basically lays out this concept for clients. I think it’s really useful, as clients are not trained designers, and expecting them to have that experience seems unrealistic. So why not start them with a primer for design reviews?
And I agree with what you’re saying about providing a good example. We can’t very well expect clients to take their personal feelings and preferences out of the work, if we don’t do it first. This approach has certainly saved me from a lot of unhelpful “why won’t the client back off and let designers design?” sort of gripping that you hear so often. The more I can get everyone focused around more objective things (ex. we want the design to be both friendly and scholarly. Is it currently too friendly or too scholarly? What do we all think is making it that way?), the more the design review and revision process becomes about solving a problem together, and the less it’s about an opinion power struggle.
Nice side effect: it’s also a whole lot more pleasant on everyone’s day-to-day lives. 🙂
It’s not easy to let go of my own vision of the project and just do what others expect.
‘Design aims to solve problems outside of the designer’ – that’s a clue!
I always think about that topic and I have a lot of trouble with my boss because of this.
Got something to say?
We have turned off comments, but you can see what folks had to say before we did so.
More from ALA
Personalization Pyramid: A Framework for Designing with User Data
Mobile-First CSS: Is It Time for a Rethink?
Designers, (Re)define Success First
Breaking Out of the Box
How to Sell UX Research with Two Simple Questions