Cap Watkins

VP of Design at BuzzFeed. Formerly at Etsy, Amazon, Formspring and Zoosk. Draws pretty pictures on the Internet all day.

Page 4

Sticking a Fork in Passion

When I was young, I wanted to be a doctor.

Unsurprisingly, my parents were in full support of this idea, buying me a kids’ microscope set, lots of books on the human body and, of course, this fantastic CD-ROM set:


I got into a bit of trouble in elementary school, actually, when I brought BodyWorks printouts of the entire human body (both male and female) to class so I could show off my newfound scientific knowledge to my friends. In my defense, it was visuals of the internals, but I guess that was close enough. Until I was sixteen, I really thought I’d wind up as a physician.

Then, at the beginning of my junior year of high school, I got a failing grade on a paper for my English class. Dr. Granger Babcock was having none of this five-paragraph-essay bullshit and, quite appropriately, let me know that my first essay wasn’t going to pass. He explained in detail the power of the

Continue reading →

The Boring Designer

Whenever I’m looking at a product designer’s work, I find myself continuously asking the same question: which solution is the boring one? Maybe it’s born out of seeing apps choose flash over function, or trying to understand just one too many indecipherable icons-as-buttons. Whatever the case, here’s an ode to the boring designers among us. The designers who…

Choose obvious over clever every time.

If you haven’t read Randy Hunt’s book on Product Design, you haven’t lived. I’m stealing this first one right out of there. When given the choice between hiding things on hover or displaying them right away, the boring designer always chooses the latter. Sure, it might be harder to achieve that perfect visual balance your graphic design teachers drilled into you, but you love a good challenge, right? You value your users’ experience over your own. Maybe you wince a little at the “compromises”

Continue reading →

Experimentation vs. User Experience

Lately, I’ve noticed that I’m following people on Twitter that I can’t recall actually following. Then last evening, I finally noticed that I’d inadvertently tapped that little person-with-a-plus icon in the bottom right with my thumb while scrolling through posts:


Twitter only adds this button to Retweets and Favorites of stranger’s tweets in your feed to make following new folks more convenient. Checking back through my following list, it seems like I’ve done that quite a few times by accident (and I’m not alone). What’s more, it’s a very subtle action. You get only the tiniest indicator that you actually did something (and no animation):


Not hard to miss if you’re purposefully tapping, perhaps. But incredibly easy to miss if you accidentally tap the icon with your thumb. Additionally, undoing that action is a double-confirm. So even if you notice you accidentally followed a

Continue reading →

The Fight

I was giving a talk the other night and, during the question and answer session, a designer described a difficult situation he was facing at his company. After he finished, one of the other speakers told him it was probably time to quit, to vote with his feet. His answer was probably right, of course. I’ve definitely been there a couple of times in my career - exhausted and finding no purchase with my company. That’s how so many tenures at companies end. Frustrated, tired.

At the end of the day, though, it’s not simply being tired or frustrated that leads us to move on. Because, spoiler alert, every job at times will be frustrating and leave you exhausted. The kicker is being frustrated and tired and not believing in your team, the product you’re building or the company itself. It’s a feeling that you can’t change things for the better, or that it’s just not worth the effort. I’ve so

Continue reading →

Should Engineers Design?

Why should I learn to code if engineers don’t have to learn to design?

The last few times I’ve spoken about how Etsy’s product designers are expected to help write the front-end for their features, I’ve gotten that question during each Q&A. And after receiving similar responses on Twitter when I wrote about why designers should code, I’m convinced that the topic seems worth addressing. So, a few thoughts…

That’s a pretty bummer response.

I can’t remember which logical fallacy is being violated by the question, but using a perceived injustice to prevent yourself from acquiring new skills and responsibilities seems like a losing attitude. What other learning experiences are you denying yourself just because you see other people not learning things?

Engineers do design.

In fact, the only way the above question even makes sense to me is if you either a) think design is all about Sketch

Continue reading →

“Good Enough”

This afternoon, I met up with a designer who was in town for a few days. We were catching up and talking shop over drinks, when she brought up an issue near and dear to every designer’s heart (paraphrased).

We ship things sometimes and it’s not how I pictured it. It’s not as great as it could be. We do these two week sprints and people keep saying that it’s good enough, so we ship at the end. But I know it’s not as great as it can be. And we keep saying we’ll go back to fix it, but I know we probably won’t. I look at other products and how well-designed they are and I just don’t see how to reach that level.

We all know that feeling. You’ve got a vision or even a fully-realized design and the end-result that gets shipped seems lacking. There was a corner case that wasn’t totally accounted for and kind of looks weird. A feature that turned out to be more difficult to implement than you

Continue reading →

My Design Process - Part 3

  • Part 1
  • Part 2


You’ve discussed, debated, designed, prototyped and user-tested. Time to build! Yeah, you too. I’ve already written about the real reason designers should code, but here’s another: you’re about to wish you could. As your engineering pals start putting this product together, they’re going to uncover an untold number of corner cases you never accounted for in your design. They’re going to come to you and ask, “Hey, what happens when you have a digital order that’s customized, but also purchased from a Wedding Registry?” You’re going to stare blankly for a second, half your brain processing the request, the other half waiting to see if they’re kidding.

They’re not. Your layout is broken. And while you could sit there and verbally explain every little tweak and fix, life is much simpler and, frankly, happier if you just jump into the code yourself. Some of my

Continue reading →

My Design Process, Part 2

Missed part 1? Read it here.


Time to grab your design tool(s) of choice and get designing. This could mean pencil and paper, Photoshop, Illustrator, Sketch, Balsamiq, html/css, or anything else you prefer. The goal is to get to something clickable as quickly as possible. The great thing about having done all the up front work, is you probably have pretty good ideas for what might be solid directions by the time you get to this step. Try them all as quickly and cheaply as possible. Remember the pros and cons you were listing during the competitive analysis process? Do the same here. Admit where your design is weak and see how that balances with its strengths.

Solicit feedback regularly and consistently. Get eyes on what you’re doing, start tossing what’s clearly a dead-end and iterating on what feels right. Collaboration is definitely your friend at this point. If you’re down a

Continue reading →

My Design Process, Part 1

When I first got into designing products, my first year or two was spent mostly in Photoshop designing high-fidelity mockups a single screen at a time, showing them to my team, iterating and then getting into code. While I had previous experience with critique from my Creative Writing program, my writing process - just sit down and start writing something, anything - left a lot to be desired. And while the results weren’t terrible, they certainly weren’t as thoughtful and holistic as they could have been.

Luckily, I’ve had a few more jobs and opportunities since then to work with more designers, get some experience, add new tools to my skill set and improve my process. Now, I’m finally in a place where I can repeat the same steps and get fairly solid results. The scope and necessity of each step shifts depending on the size and scope of the project. But, generally, I always follow these

Continue reading →

Why Designers Really Should Learn to Code

There’s been a lot of discussion over the years about whether or not designers should be obligated to learn how to implement what they design. This obviously causes a bit of angst amongst the design community because, of course, not every designer has been in a position to learn to write their own front-end code (and that being a requirement is scary). And, hey, some people just aren’t interested in that part of the product process. That’s what engineers are for, right?

On the other side, the common refrain seems to circle around designers becoming more and more independent. If designers know how to code, we can finally be free of engineers telling us we can’t do something. We can implement our vision for the design and not have to rely on anyone else. We can create complex animations, subtle gradients and shadows with pixel perfection. Never have to submit or defend a design spec

Continue reading →