anastasiavixen’s posterous

The different sketch styles of the designers at 37signals Jason F. Aug 27

21 comments Latest by MI

Thought it would be fun to share the very different sketch styles of the designers at 37signals. They range from very neat to a mess (mine).

Jamie Dihiansan

Jamie’s sketches are neat, well organized, and readable. They’re fairly high resolution and anyone who’s looking at them can decipher them without assistance. They also often contain supporting materials – ideas, questions, explanations, and goals.

Jason Zimdars

Jason Zimdars’ sketches are also really clean. Nicely organized, consistent, detailed (including shading), and self-explanatory. Everything has its own space. He’ll often iterate a variety of ideas, one after another, on the same page instead of using separate pages for each new idea.

Ryan Singer

Ryan’s sketches trend toward abstract shapes and general ideas, not specific detailed executions. But they’re still neat, logical, and mostly readable. They’re often used as a jumping off point for discussion instead of “this is the solution.” He doesn’t spend a lot of time on drawing, most of the time is spent thinking. The sketches are just a rough way to get an idea into a form that can be shared with others. Ryan almost always uses a thick, low resolution sharpie marker.

Jason Fried

My sketches are generally a mess. Lots of overlapping ideas, text you can’t read, and very abstract shapes, lines, squiggles, and arrows. A page like this usually takes me about 30 seconds to spin out of my head. I just draw an idea without thinking too much about how it looks. They are rarely (if ever) given to someone without explanation or discussion. Like Ryan, my sketches are almost always drawn with a thick, low resolution sharpie marker.

I have no idea if any of this is interesting, but we thought it would be fun to share the different sketch styles of the designers at 37signals.

Looking for a job? Got a position to fill? Check out the Job Board. Over 1 million people use 37signals' simple web-based software to collaborate on projects, track contacts, and organize their business with an intranet.

21 comments so far

Aris Bartee 27 Aug 09

This is interesting. I keep a sketch book of app ideas or layouts that come to mind. I kept it up even during the my “I’m a enterprise developer phase”. Now that I’m back to my design roots and coding my designs, I look over those books to ramp.

The designs are out of context and have no bearing on my current work, but it reminds what is possible.

Greg 27 Aug 09

This is very interesting. I’ve been thinking lately about my process of designing and whether I should use words in my sketches or stick with mostly abstractions in order to focus on structure and layout first then focus on copy in the next iteration. It’s neat to see the different sketch styles you guys have to contrast it with my own. Thanks for posting this.

GeeIWonder 27 Aug 09

I have no idea if any of this is interesting

It is.

Marc Jenkins 27 Aug 09

Definitely interesting stuff. My style probably resembles Jamie’s the most though I like Ryan’s more thinking, less drawing approach.

cd 27 Aug 09

This guy is the business.

Remontti Putkimies 27 Aug 09

Not sure if it was interesting. Mildly bemusing perhaps.

Jason Robb 27 Aug 09

Thanks for sharing these. It is very interesting to see the artifacts, but it would be even more interesting to hear the conversation around them. Do the neat sketches provide more opportunities for feedback? I bet it’s hard to so, or easy to say that it really doesn’t matter. Chicken scratch can be just as valuable as something more refined like Jamie’s.

Here is sketch I made recently:

I’ll be publishing 2 articles about my UX tools for sketching near the end of September with www.uxbooth.com.

Thanks again,

Jason R.

JF 27 Aug 09

Jason: My personal opinion is that really detailed sketches are a waste of time, but everyone has their own way of working.

I don’t impose my sketch style on Jamie or Jason Z., but I do wish they’d “get messy with a sharpie” for a while and give it a try. Sketches are really about exploring, not perfecting. High resolution sketches take time away from basic exploration of more ideas.

It’s like a 10 page proposal vs. a 2 page proposal. We all think we need to send out 10 page proposals, but the 2 pager usually does the job just as well and saves everyone a lot of time.

Just my 2 cents.

Robert 27 Aug 09

I think my sketches would be more effective (and I think I would put more into them) if I was better at drawing. The sketches I create are usually pretty sloppy but tend to get the point across, so I guess I can’t complain.

Jeff 27 Aug 09

JasonF, your sketch looks like Ryan’s sketch, rendered in IE6 !

Jason Robb 27 Aug 09

Agreed, JF. Like your sketches, mine are never a high-resolution representation. The best sketches are done fast, and they’re always kindling for conversation.

Do you sketch on the spot while you’re discussing a design? I imagine the tendency to go detailed happens mostly when isolated from discussion.

JZ 27 Aug 09

I think where Jason F, Ryan, and I differ is that I tend to stick with sketching a little longer than they do.

My initial sketches look a lot like theirs: very loose and more abstract. Those sketches might be a page or two in my book before the one shown in this post.

Where we are different is that I will usually continue to refine the idea on paper, which is more of what you see here.

Many times, I’ll be working in Photoshop or HTML and want to quickly try another idea without doing a lot of work. I’ll then go back to paper and “try” it there before committing to major code or graphic changes. Many times you can work on the idea right there.

The portion of the sketch above where you can see the “email” label in each row was late in the process. I was working in code and really needed to refine that portion. It was faster to go through a bunch of iterations on paper rather than vetting each one in HTML .

It is very interesting to see the artifacts, but it would be even more interesting to hear the conversation around them.

I work remotely so my sketches are 90% for myself — all of the conversation is in my head. For me sketching is a way to record my thinking. When I get stuck on a project, I always return to my sketchbook to make sure I’m executing true to the original idea, or to re-evaluate ideas I may have passed upon. It’s an invaluable tool.

JD 27 Aug 09

Actually since I’ve been working at 37signals I haven’t been sketching as much. I think it’s because at my previous jobs sketches were a form of communicating to non-designers (developers, project managers, etc.). I created sketches to explain where I wanted stuff to go, etc. Maybe there was even an IA involved that created polished wireframes in Vizio.

Now since we don’t have IAs, project managers, and HTML developers (in the Agency typical in-house sense) I don’t need those sketches anymore really. I just get it in HTML and review with Jason F, Ryan, and Jason Z through Campfire (our group chat app). Sometimes others like Jeremy or Jeffrey and even DHH chime in.

The process here is way more fluid because we don’t need to create various official and unofficial forms of documentation. Doesn’t mean this is THE WAY it should be. It’s just the way I’ve evolved my process over the past year.

Luis 27 Aug 09

Interesting or not, the different sketch styles must work because you guys put out great products.

Thanks for sharing.

Matt 27 Aug 09

@JF: It’s interesting and thanks for sharing.

I think it’s just about getting a “flow” going.

I think most would admit that it takes time (1/2 hour or more) to get flow when coding; the proverbial “zone”. Sketching seems to have a much lower time threshold.

Authors use different techniques to break through “writers block”. Some suggestions: open up a word processor and type every thought, even the most mundane…until they achieve flow. (Course, you guys are working on your second book, so you may/may not have had to do this).

Given your (our) mediums are so visual, seems that sketching is quite comparable to this/similar methods…but, the aim is similar.

I guess I’m “lo-res” too; office and home office have of 8×11.5, bond and a box of sharpies. Sketch box for when I travel.

Only bad part about this is method: sharpie hand tattoos (though, sometimes fun too).

Alex 27 Aug 09

Interesting. My sketches are very abstract :-)

DL 27 Aug 09

Thanks for the insight.

It’s nice to see how others go through the “process.” Whether it’s sketching or coding you have to find what works for you and sometimes what works for you only does because you haven’t seen how someone else does it.

I think of these posts as either wake up calls to simplify what I’m doing or validation that I may actually be on the right track.

I have yet to walk away from this type of post without having learned something that will help me with the next design or section of code that I’m going to tackle.

Russ 27 Aug 09

I was wondering if you guys have ever used or or considered using interactive whiteboards.

As your team is pretty spread out it seems like you might really benefit from sketches that could be edited simultaneously and shared seamlessly.

JF 27 Aug 09

Russ: We can share paper very easily. Just drop it in the ScanSnap, it’s saved to the desktop, and we drop it into Campfire or Basecamp where we have all our discussions. It takes about 30 seconds and it fits right into our workflow.

I’ve seen a lot of technology try to replicate pen on paper and I’ve never found it to be even close to the original.

Adam Fitzgerald 27 Aug 09

Jason,

You mention how well scanning and discussing in Campfire fits into your workflow. How do you get around the problem of interrupting people who are buried in code, or do you schedule your discussions on this sort of thing?

Interruptions are a big problem with programmers, so was wondering how you handle it in your team. Maybe a different post :)

Cheers Adam

MI 28 Aug 09

Adam: One of the wonderful things about Campfire is that it’s not in your face unless you want it to be. We generally all reserve the right to completely ignore Campfire if we’re engrossed in another task that we don’t want to be distracted from. As Ryan posted recently, we’ll even take it a step further and go completely radio silent if we really want to be head down on a problem.

If something does require an immediate response, we’re also usually available by IM, SMS , or even phone as a last resort. It’s pretty uncommon for us to have a burning issue that has to be dealt with right this second, though.

Post a comment

Looking for something? Visit the archives.