Not actually a toilet

7 Reasons to No-Hire a Product Designer (Part I)

Julie Zhuo
The Year of the Looking Glass

--

Imagine I walk into your house one sunny afternoon with a plate of cookies and a box of tea for our Sherlock marathon (hey, no judging.) You're not there to greet me at the door. Instead, I find you in the bathroom amidst a battlefield of tools—pipes and bolts and gears and instruments-I-don't-know-the-name-of-but-kinda-look-like-devices-of-torture. Your brows are furrowed in a deep V as you hunch over a gigantic, pipe-wrapped mass of brass and wood and porcelain sitting where your toilet used to be.

"Uh, whatcha doing?" I ask.

You frown. (Apparently, you expected more out of my powers of deduction after all that Sherlock-watching). "My toilet broke," you say, "So I bought a bunch of stuff at Home Depot to fix it." You wipe your hands on your jeans, step back, and crank a lever. There is a loud gurgling sound as the machine rumbles to life, then burps silent. "It works," you say with some satisfaction.

"Wow," I say. "It's…impressive."

And it is. It looks like an invention from the days of airships and steam engines, all polished metal and criss-crossing pipes and clicking, whrring gears. I'd never seen anything quite like it before. I point to a dial where a thin, red arrow trembles between a bunch of numbers. "What's that for?" I ask.

You say: (surprise! This blog post just turned interactive!)

A. "Isn't it the sickest? Bet you've never seen one of those dials before on a toilet. Nbd, though. It’s just a little thing called innovation."

B. "Ah, glad you asked. It's necessary to understand the hydraulic pressure locking mechanism I built. You see, the numbers here correspond to the joules needed for the proper functioning of the lumbar pipes…" <answer continues for another seven minutes as you pull some pencil diagrams out of your pocket, walk me through your alternative ideas, and eventually end with three pages of mathematical calculations for why this works>

C. "Oh, I was watching Youtube videos on how to fix a toilet and this one guy has a whole channel called Pimp my Loo and he always throws one of these suckers on."

D. "Hmm, good question. I can’t recall, but I’m sure it was important at the time..."

Cut scene. The bathroom ripples and fades away (a pretty trippy animation, if you ask me.) Suddenly we are designers, sitting in an interview room, and your steampunk toilet has morphed seamlessly into an example your past design work. I have just asked you why you decided to use a list view to showcase a bunch of photos on one of your interfaces.

The correct answer is B, obviously. The others are insta-No-Hire answers. Ludicrous scenario aside, you wouldn't accept a plumber doing stuff to fix your toilet without some very clear, rational purpose, and you shouldn't accept a designer doing so either. Making stuff look good is not a goal in of itself. Neither is striving to be innovative. These are byproducts of doing the thing that actually matters, which is, namely, solving a problem.

So. It’s very simple. The first reason to No-Hire a product designer is if they don’t have intentionality. What does that mean? See if they fail these exercises:

1) Point to some part of their design and ask them why they made that decision. (Why is that button chartreuse? Why does your navigation resemble a flower petal? Why'd you decide to build the Instagram of Dropboxes in the first place?). They should have good, compelling and thoughtful explanations that ties back to the problem they were trying to solve.

2) Pitch them an alternative design idea to what they showed. (Have you considered magenta buttons? How about shaping your nav to resemble a young sapling? What do you think of repositioning your product as the Dropbox of Instagrams instead?) Either they’ve already considered it (all the better if they bust out old mocks or sketches), or they can respond on-the-spot with deep, critical thoughts about the tradeoffs.

3) Ask them why they think another product was designed the way it was. A good designer should have plenty to say here, because they assume that, like them, other good designers also make intentional decisions.

4) Look at how they use common design patterns. Do they blindly accept such patterns as Truth? Or do they analyze whether using a common pattern actually works for the problem they’re trying to solve?

5) Look for hints of random decision making. Good designers do not do things randomly, or for the hell of it, or just because it seemed cool.

Even if a steampunk toilet does seem pretty damn cool.

Read more: Part 2 · Part 3

This is Part One of a series of seven (or five or nine or eleven, who knows when I'll run out) reasons to No-Hire a designer, culled from doing hundreds of design interviews over the past few years. Stay tuned for fresh new installments. (Or, if you've already pwnzored this whole interview thing and are looking for a new gig, why don’t you get in touch?)

--

--

Julie Zhuo
The Year of the Looking Glass

Building Sundial (sundial.so). Former Product Design VP @ FB. Author of The Making of a Manager. Find me @joulee. I love people, nuance, and systems.