angel david lindes archives

“Find the Twin Sumo” or “No, Your Client is Not an Idiot”

You’ve been there. You’ve felt the knot in your stomach. You’ve tightened your grip on your iPad ever so slightly after hearing your client say “You know, on that header? I want our logo to be bigger. Way bigger.” And you think to yourself Great. I just found me another do-it-yourselfer. He designed a newsletter for his student club twenty-seven years ago and now he’s ready to tackle his corporate website. He just needs me to run Photoshop for him.

The world slows down for just a moment. You stare down at your notes, half pretending you didn’t hear and half expecting your iPad to feed you your line or something. But nothing comes. Time picks up its lumbering pace again. The street noise outside your client’s office window wakes you up and you realize now you have to say something; something that acknowledges your client’s statement. Something that isn’t “You wanna do this thing yourself?”

But, what?

Newton, Sumo Wrestling, and Design Iterations

Newton’s third law of motion states that “for every action, there is an equal and opposite reaction.” Of course the guy was talking about the physical world. You know, like the pull of gravity working against your overwhelming desire to dunk it, or the tension of your belt working against the fierce push of your expanding gut. But, of course, we can always twist his words to apply them to design. And it’s fun.

In the “very complicated act of faith” that is design, there are two main forces at work: the problem and the solution. Their relationship is a lot like the one between your beer belly and your belt: they mirror each other. One is the question, the other the answer. They’re twin sumo wrestlers in different-colored diapers, pushing at each other with tremendous force. They’re the yin and the yang: identical, but opposite.

This is a fact that designers the world over use to their advantage. Want to come up with a great solution? Understand the problem. Want to understand the problem? Come up with a solution. If you figure one out, you immediately understand the other.

The design iteration, then, becomes a nice, sweaty wrestle between problem and solution. A designer will do a bit of research on the problem, and then propose a solution. That proposal invites feedback (aka more information about the problem), which the designer then takes into account for the next solution proposal. Rinse and repeat. Slowly, the designer’s understanding of the problem and the solution grow together, until finally, voila! We’ve got ourselves a finished product.

Clients Have Brains Too

As designers, we’re comfortable with this relationship between problem and solution. In fact, we use it to make a living. We’ve come to accept the iterative synthesis of solutions as the best way to come to understand problems. And we love it.

Well, it turns out our clients are often doing just that when they blurt out an unsolicited design suggestion. They may see a problem with our design, but instead of describing the problem by saying something like “You know, the home page just doesn’t feel ours enough. It still feels a little generic to me. I don’t think it reflects the personality of our company quite yet” they propose a solution and say “I think the logo should be bigger. Way bigger.”

This is because clients have brains too, and they understand that problems and solutions are like bellies and belts, like crooked teeth and braces, like moobs and manziers. So, perhaps involuntarily, they blurted out a proposed solution instead of a description of the problem.

So why are the solutions they propose rarely great? Because they’re not trained designers. But that doesn’t mean they’re bad clients. They may be diagnosing a legitimate problem, but because they did so by prescribing a lousy solution, you think they’re dumb.

Take a step back. Breathe.

Find the Twin Sumo

Now it’s back to you in your client’s office, iPad clenched in agony. You need to say something. What to say, what to say, what to say?

Well, if you understand that your client’s lousy design suggestion is really the mirror image of a problem he’s trying to diagnose, all you have to do is find the twin sumo. Take the proposed solution and turn it into the problem you think it was designed to solve. Then shoot it back at your client. Hmmmm…bigger logo…what could he be talking about?

“So, what you’re saying is that you think the current design doesn’t really feel like it belongs to your company, like it’s really you?”

Whew! You made it. Now, relax. Wipe your brow and get rid of the poker face. The conversation is ready to go somewhere.

Did you nail the problem on the head? Maybe so, or maybe not. But when you translated your client’s proposed solution into a diagnosed problem, you did something priceless. You let your client know that his input does matter, but you did it without compromising the integrity of your work, or your role as the design expert in the room.

Now you can work to refine your understanding of the problem the client is trying to diagnose. And your client? Not an idiot. Not a deadbeat. Just a guy with a brain trying to tell you something’s wrong. So listen up. You just might learn something.

posted by davidlindes on Friday, Oct 14, 2011

case study

Lying vs. Simplifying – Ready? Fight!

Lying and simplifying aren’t the same. In fact, they’re not even friends-in-law. They’re archenemies. That’s right. Think Batman and The Joker, Tonya Harding and Nancy Kerrigan, Glenn Beck and Rahm Emanuel. As designers, it’s essential that we understand this, because our lives are spent shooting for simplification. But far too often in our quest for UI Zen, we fall into the bottomless pit of lies, lies, lies.

A comment to my last case study about lying UIs left me with something to think about. Bruno Abrantes, a Portuguese designer and student, wrote the following:

If the UI abstracts complicated facts from users, causing them to make erroneous assumptions about the application that actually makes their lives simpler, then lie at will I say. This is the basis of software such as iTunes and iPhoto (my poster-child examples): … The user is lied to by the interface, since it doesn’t reflect the actual folder/file hierarchy, but the lie makes her life so much easier it’s totally worth it.

This got me thinking “Hang on a second – is lying a good thing sometimes? Is simplification one of its many forms?”

And let me tell you that while Bruno has an excellent point, and one I’ll try to expand on here, I’ve come to the conclusion that lying and simplifying aren’t the same. In fact, they’re not even friends-in-law. They’re archenemies. That’s right. Think Batman and The Joker, Tonya Harding and Nancy Kerrigan, Glenn Beck and Rahm Emanuel.

As designers, it’s essential that we understand this, because our lives are spent shooting for simplification. But far too often in our quest for UI Zen, we fall into the bottomless pit of lies, lies, lies. So how do we know when we’re lying and when we’re simplifying?

Zoom In, Zoom Out

Let’s say I’m trying to figure out where the Rock & Roll Hall of Fame is. Well, Google Maps tells me this:

There it is! I’m so close to it I can see the building’s weird shape, the names of the businesses and streets around it, and I can tell it’s way close to the water. Cool. Now, let’s zoom out a whole bunch – Google gives us this:

The map just got a whole lot simpler and abstract in order to cover a lot greater area, but I still know where my desired destination is. This is because the map remained true to the lay of the land. The Hall of Fame is still in Cleveland, and Cleveland is still northeast of Texas. They still told me the truth. That’s right. Their screen is lie-free, and that’s why I can still get to where I want to go.

Cut the Fat

However, Google filtered out a great deal of irrelevant information. They didn’t tell me the whole truth. Why? Well, because honestly, I don’t need it, and if I had it – all of it, street names and company names for the whole U.S. – the map would become one useless mass of black text. So instead, they presented me with a minimal, but still accurate representation of the info I needed. That’s called simplifying. It’s kinda groovy.

So how do we know what to keep and what to chuck? Google figured it out – they still make the Hall of Fame’s address, phone number, and directions, quite easy to get to. They know why I came to their site in the first place, and that’s essential.

If we know our users, then we can get them what they need and get all the other stuff out of the way. It’s a great way to make friends. If we don’t know our users, the odds of cutting out something essential to them or adding something irrelevant grow quite a bit, and that’s a great way to get your car keyed.

One great example of a man who knew what needed to go is our friend Jared, from those great Subway ads. He knew that,

Now that’s simplification! When we cut the right stuff from our UIs, we can feel the difference, and so can our users. Simplification leads to focus and increased efficiency. Users of good, lean UIs can go farther faster (at least at work) and have more fun while they’re at it.

On the other hand, lying can often begin through a lack of knowledge about our users and their priorities. It takes a whole lot of work to get to the bottom of what users need, and we may be tempted to take shortcuts. Sometimes, in the name of elegance, simplicity and minimalism we can cut some valuable stuff out. Let the following be a grim reminder of the possible results of such reckless behavior:

Only a designer who knows his or her app’s users will be able to successfully discern between fat and vital organs.

The Verdict

Now, let’s return to Bruno’s comment. He’s absolutely right that the decisions Apple made in iTunes and iPhoto make life easier. They abstract away irrelevant information while leaving what matters – the music, the pictures! This is a great example of simplifying.

One of the most important differences between lying and simplifying is their result. Lies are…well, misleading. They misrepresent information that is essential to the user, and that leads to nothing but frustration. Simplifying is different. Though it may not be explicit about every piece of information, it emphasizes the most important ones and leaves the rest out. This enables users to get more done.

The keys to simplifying without falling into a pit of dirty lies are simple. We need to know the underlying truth we’re trying to represent: the information, process, task, etc. If we don’t, neither will our users when they sit in front of out apps. Second, we need to understand our users’ needs intimately. We must know what they want out of their experience with our software. This will allow our solutions to remain both accurate and simple – an elegant, focused representation of the essential truth.

posted by davidlindes on Monday, Feb 08, 2010

Wait, you mean computing isn’t exclusively for designerds? Nonsense.

posted by davidlindes on Monday, Feb 08, 2010

Great point, Bruno. The kind of thing that iTunes and iPhoto do (and the iPad is going to do) I would call abstraction – they keep the user away from information the user does not care about. Hurray for that.

The issue is when a UI misrepresents information that is essential to the user. That’s what I consider lying.

Finally, perhaps one of the greatest pitfalls we face as interaction designers is the risk of mistaking lying for abstraction. Wow, I sense another article coming on…

BTW, the users of the new system are initially unpleasantly surprised by the simplicity of the app. But then the happiness that can only come from software that doesn’t suck settles on them, and we become good friends.

posted by davidlindes on Thursday, Feb 04, 2010

Haha! Wow. All those ESL classes gone to waste!

posted by davidlindes on Wednesday, Feb 03, 2010

My attempt at making a web site look like the logo-plastered walls of any corner store in Guatemala. Also my attempt at Latin Alternative Rock. Listen here.

posted by davidlindes on Tuesday, Feb 02, 2010

case study

UIs that lie & the users who believe them

Interfaces are one of the principal sources from which a person learns about his or her work. That understanding gets turned into diagrams, charts, and maps that, whether accurate or not, come to define the work that person does each day.

My initial meetings with Michael were a bit intimidating. It’s not that he himself was overbearing or anything, it’s just that our conversations eventually filled me with a bit of apprehension – a feeling of “woah, this project could totally kick me around”. See, Michael was a new client who needed a piece of software to help his office do their daily work, and he sat down with me several times to make it clear that their process was insanely complex. Gulp.

Now, I’m a designer, which means I’m supposed to be overly confident about my ability to solve a client’s problems. And at the beginning I was, but as Michael reiterated time and time again how difficult his daily work was, I couldn’t help but believe him, at least in part, and that belief haunted me. With every iteration of the project, as we introduced new functionality and explored additional requirements, I winced inwardly, thinking “here comes the tough part.”

This would be a great time for me to introduce a horrific challenge and then brag about how I beat it to a pulp, but unfortunately that won’t be the case today. It turns out Michael’s project actually turned out to be really straightforward. The logic behind his office’s business process was pretty simple, and as we worked together on a software solution, that simplicity came forward – to our surprise – and made both our lives easier. At first, Michael expressed a bit of concern that we’d overlooked something essential. This seemed too easy. But as he and his staff used the application over time, they became convinced that it was all there. Their work really was that simple.

That got me thinking – why was Michael’s simple process hidden behind so much perceived complexity? How was that confusing layer of muck put in place, and when?

Of course, there are tons of variables involved here, and to say that a single factor was wholly responsible for this counterfeit complexity would be a joke. Even so, as I searched for answers about the origin of a lot of business process misunderstandings, I kept slamming into the office’s previous software and its confusing user interface.

The most dangerous thing I saw in the old UI was a knack for misrepresenting information relationships. Due to confidentiality restraints, I won’t be able to share the actual information that was being turned upside down, but let me give you an example:

Alright, alright, this is an obvious one. The figure misrepresents the relationship between “colors” and the rest of the words. Now, because everyone knows about colors (duh!), the mistake is easy to detect and resolve.

It’s easy for us, a bunch of fully-grown, well-trained professionals, to tell that blue, green, red, and yellow all fit within the category of “colors”. Congratulations. However, what would happen if I taught my newborn about color using the first figure? How do you think that would go? Is there a chance some confusion would ensue?

The UI that Michael’s office was using every day to do their work was teaching them the wrong info relationships over and over again. They’d been using it for over five years, and during that time, they had hired and trained several new employees. Their training had been centered around learning to use the old application. Consequently, they had learned their new job inaccurately in essential ways. Their UI was lying to them, and they were eating it up.

You see, as designers we understand one facet of the knowledge-UI relationship quite well. We depend on our clients’ brains to produce the kinds of info diagrams that can teach us about the design problem at hand, and we hope that this understanding becomes solidified and is eventually projected onto our final UI. That’s how we make software.

However, it had never occurred to me that this relationship could also be reversed until I saw it with my own eyes in Michael’s office. For years he and his staff had looked at their old UI, learned from it, formed elaborate diagrams based on what they learned, and then stored them in their brains forevermore. That’s how we capture concepts.

So there it is. User interfaces are one of the principal sources from which a person learns about his or her work. That understanding gets turned into diagrams, charts, and maps that, whether accurate or not, come to define the work that person does each day.

This brings a new dimension of responsibility to our table as interaction designers. Not only do we need to worry about our interfaces being simple, or elegant, or usable, or accessible; we also have to make sure they’re honest. Do they accurately portray our clients’ processes? Do they faithfully represent the relationships between different bodies of information? Do they tell the truth, or do they lie? Ultimately, whatever they say is going to define how our users think of their work, how they understand it, and how they do it.

posted by davidlindes on Monday, Feb 01, 2010

case study

The Case Against Using Your Head

I’m an amateur singer-songwriter when I’m not at work or asleep (let’s say for now that they’re mutually exclusive), and for the last few years I’ve been writing and performing material with different bands, duos, and on my own. Throughout that time I’ve tried different things to get my songs from pen and paper to studio and stage. It’s a typical creative process – start with an idea, work, work, work, end with a performance or a recording or both. For the longest time, my process for getting from point A (“Mmmm…good idea…”) to point B (“We’re going to play a song for you called…”) was pretty straightforward.

It looked like this:

The whole thing felt a bit tedious from time to time, but overall, it was working for me, you know. I was successfully getting to the record and perform part of things often enough that it was enjoyable.

So a few weeks ago I had this tremendous breakthrough. I had an idea for a song, and it occurred to me that maybe I should just skip all the other steps and just record it. I know, I know, it sounds crazy.

So I started a recording session and laid a bunch of stuff down. I laid down some cajón (Latin percusión standard fare), some Ladysmith Black Mambazo-esque backup vocals, and some wannabe flamenco guitar. I had no idea what words I was going to sing into the mic, but once I had all that textured music goodness backing me up, words just came out of my mouth. I came up with enough material to fill a couple of songs, actually, just singing into the mic over that loop of sweetness.

For a while after that experience, I thought I had just turned the whole process upside down, and I wondered why it had worked so well. That got me to thinking about the process itself and the mediums I used throughout:

I realized that music (the fun part!) wasn’t showing up enough in the process, and most of it was at the very end. I was doing way too much to come up with stuff in my head, and then following that up with too much pen and too much paper. I suppose that’s partly because I wanted to write songs that were well thought through. I wasn’t interested in writing the next “MmmBop”, and so I thought things through and through and through and through before actually making music.

Thinking is not the problem here, trust me. Thinking is too often what’s lacking from popular music. The problem is the medium I was using for thinking. In this case, my target medium was music – guitar, vocals, yelling, whistles, sound samples – and my primary thinking medium were brain sparks and pen and paper.

Not that brain sparks and pen and paper aren’t decent ways to think, you know, they’re great. It’s just that they’re not the most effective thinking mediums if your target medium is something else. In my case, I needed to use music as my thinking medium if I wanted to write a song, and that’s what I did by recording first. If you’re a carpenter, your best thinking medium is wood. If you’re a writer, it’s a Mac. If you’re a lawyer, it’s b.s. and the more you use your target medium as a thinking medium, the more effective your thinking becomes.

The reasons for this are several, but the most obvious is that if your thinking uses your target medium, your thoughts will have the same essential characteristics, restraints, and properties as your final product. Thus, your synthesis will be more accurate. Additionally, your evaluation will be more intuitive because it’s easier to respond to a blown glass object in blown glass form as opposed to brain spark form.

In design we have a word for thinking in non-brain-spark mediums – prototyping. We talk about it, we like it, we love it. But do we do it enough? How many activities are we undertaking with brain-spark power alone? How many more do we limit to the realm of pen and paper? How many of our thoughts actually make it to prototype form?

I think it’s only a select few. And that’s for the same reason that only a select few of my song ideas were making it to recorded format. See, I thought of recording as a way of presenting; a way to say “ah, now that I’ve done my thinking, let me show you all what I came up with” and then attempting to impress. I think too often we regard prototypes in the same way. We use them to show our client some great idea for a solution. We use them to show our team that we bring something to the table. We use them in our portfolios to say “see? I’m good at this”.

Prototyping is a great medium for presentation, and I’m not knocking it in that capacity. All I’m saying is that it’s so much more than a presentation medium. It is our most powerful thought medium.

When we face design problems, we often do so by attempting solutions (Lawson). However, far too often we attempt them only in our minds. We analyze, synthesize, and evaluate using brain sparks. We brain-spark a solution to life and then brain-spark it to death when its weaknesses occur to us. Later, we forget that we had brain-sparked that solution and return to it, only to discard it once again. How many of us have gone through that cycle time and time again in the limited realm of our minds?

Our thinking process would be far more effective if we used prototypes as a medium for thought – without reverence, without censorship, without that little voice in your head that tells you it should look better than it does because you’re going to show it to someone. We should use it as a medium to analyze the design problem, to propose solutions, to make mistakes, to fix them, and to try new things. We should make them an extension of our brains and use them as such: divergently, creatively, exploring the possibilities for a solution. We should let them replace brain sparks as a thought medium as much as possible.

By using prototypes as a thought medium we’re more likely to have a meaningful, fruitful conversation with our own ideas. We are more likely to better identify their strengths and flaws, and communicate those to others. We are more likely to think about our design problem and its solution candidates accurately. In the end, this kind of thinking is more likely to lead to an effective solution.

posted by davidlindes on Friday, Aug 21, 2009

This is a great measuring stick. I know most of these are things we try to emphasize in our design culture here at the Church. It’s nice to know at least one guy thinks we’re headed in the right direction.

posted by davidlindes on Wednesday, Feb 11, 2009

“Be brave enough to live life creatively. The creative is the place where no one else has ever been. You have to leave the city of your comfort and go into the wilderness of your intuition. You [can only get there] by hard work and risk and by not quite knowing what you are doing. What you’ll discover will be wonderful. What you’ll discover will be yourself.”
Alan Alda

posted by davidlindes on Tuesday, Feb 10, 2009