80 Works for Designers

Find Out For Yourself

"If you want to study something, it's better not to know what the answer is."

I was reading the essay "Find Out For Yourself" by Shunryu Suzuki today when I was struck with a sudden thought: we can be better designers when we don't know what we're doing.

Many of us were attracted to the field of design specifically to make art. Then, somewhere along the way -- especially after having so much energy placed in making artifacts, not art -- our perception of what it meant to be a designer broadened. We became competent in creating specific kinds of artifacts. We mastered specific domains of expression.

But that didn't mean that we designed better artifacts. It's human insight that grounds and infuses design work that creates meaningful change in our society.

Making is not a direct substitute for generating meaning in design. But the process of making can lead to meaning, and our minds must be open to receive it. I've heard this described as "abductive" design thinking -- which in plain English boils down to being able to extrapolate solutions from limited information.

You can seek out that insight before creating your design, if you have the tools. If you don't, then you can start designing. But if you want to use your time wisely -- not efficiently, mind you -- you should practice agile design.

How Designers Can Think Strategically

Last class, I made good on my promise to describe how to properly frame a design problem. And while all of you said that what I was describing wasn't "new" in any sense of the word, there was some good dialogue about what does and doesn't fall into the realm of a designer's control when you're working through a project.

One of the last things I touched upon in our discussion and drew on the board was a rudimentary version of the following chart:

When clients meet with you to discuss their needs, they're often thinking solely about tactics. However, good designers know how to rise above the tactics and describe how their actions impact business goals and marketing goals beyond making a good logo. These designers get a seat at the table with the CEO and are more likely to retain their clients in the long term -- provided that their design work is well-executed and on brief.

If you find this topic of interest, feel free to read further in this 6-part series from last year on ChangeOrder.

Sustaining a Sketchbook Practice

Where do you keep your ideas?

While we've been discussing the different kind of design challenges you might face through a varied career, and I've provided you with various methods and tools to come up with solutions to those ideas, we haven't talked much about where you store those ideas and reference them in the future. Keeping a sketchbook is the best way to capture both ideas and the processes by which you iterate those ideas into a coherent form.

I saw a lovely presentation by Tim Wood of the company Effective UI on this topic a few weeks ago, and he had a few great points about keeping a sketchbook that I thought would be helpful for you.

Work 45 / Touch Screen of (Deaf) Rock: Student Prototypes

A few weeks back, I took a class taught by Dan Saffer and Bill De Rouchey about designing gestural and touch user interfaces. Within the class, we had an hour to prototype a "music store interface of the future." When we were working on the exercise, I couldn't help but wonder what kind of experiences we could create with similar technologies for people who are disabled.

Two weeks later, I'd crafted the following exercise for our 80 Works class:

"The Experience Music Project (EMP) would like you and your big brains to create a novel exhibit experience for their Music Lab that lets deaf people feel different kinds of music. You have 45 minutes working together as a team to create a paper prototype AT SIZE that defines this experience. We’ll test your interface in a walkthrough, and then you'll get 15 more minutes to refine the interface for a final test."

With only 45 minutes to get a first rev of a paper prototype into place, Mark Notermann, Meg Doyle, Claire Kohler, and Donnie Dinch jumped into action! Let's look at their interface and see how they revised it on the fly to make it sing.

Precisely Rough Sketching

When I was at Interaction'09 last week, I had the luck to attend a 4-hour "Drawing Ideas" class with Mark Baskinger, a professor in the design program at Carnegie Mellon, and William Bardel, an information designer. They have a book coming out later this year on this topic, and in their class, they shared a number of tips and tricks on how to render your conceptual ideas with a certain level of fidelity.

I can't give away the crux of what they shared -- they want you to buy the book! So let me point out some tips and tricks that helped me out... especially because they align with the previous discussions and posts we've had about sketching design ideas.

Work 22 / Dry Diapers: Student Designs + Case Study

About four weeks ago, the 80 Works class was tasked by me and Jill Vartenigian, an instructor at Seattle Central, with the following challenge:

"In 30 minutes, brainstorm ideas for a name, logo, and form factor for a brand of diapers that can be marketed to urban parents. These diapers need an edge, a hint of sly humor or cool that make them stand out from the boring 'ol diapers you can find pretty much anywhere.

Boy, did the class rise to the challenge. The following is a case study of how the class took this seed idea and executed it as a design concept.

Work 21 / Mr. Blue: Student Designs

The most common color? Blue. And yet there are so many variations on this hue... Can you design a masthead for a new magazine that’s solely about the topic of blue? This includes its name, suggestions for art direction, and what kinds of articles you think the editor should include.

 

True Blue by Mark Notermann

 

BLUEMAG by Meg Doyle

 

Blue by Donnie Dinch

Collaborative Design Methods: Group Critique

This is one of the hardest skills for any designer to attain. It is a lifelong practice. And you will discover, as you move from agency to agency, that there are varied points of view to how to approach a critique. I am going to share with you some guidelines that we can use for the rest of our class. This is what I'd like to call a positive method for discussing design concepts, as opposed to the "shooting gallery" approach I've seen at other shops.

Collaborative Design Practices: Choosing Your Tools

Whether you're using a camera, Adobe CS3, or a stone tablet with an awl, you need tools to make a designed artifact. Those tools could be anything physical beyond your brain and hands, really: torn paper, a sponge, an 8-color Heidelberg press, or code that will be compiled into a Flash SWF.

Knowing which tools to select and when you apply those tools while you're making a design can have massive implications on how long it takes to execute a project. Beyond coming up with a strong idea and knowing how to manage your design role and tasks, improper tool selection can hurt you more than any other decision in the design process.

And when you're working in a team of designers collaboratively, not clarifying what tools will be applied in advance can be deadly. This is why in agency settings, we default to whiteboards, pencil and paper, and other simple methods of working through design problems.

This post will talk through some of the reasons why we stay low-fi so far into the design process, and what rewards you can reap from the result.

Collaborative Design Methods: Simple Sketching

There are plenty of books and tutorials out there that describe how to draw things well. We spent a lot of time in school learning how to draw things beautifully, in all sorts of photorealistic ways. This is considered a hard skill and in many cases a cost of entry for being a commercial artist.

So please excuse the rudimentary nature of this post. I suck at drawing with a pencil. But that has never gotten in the way of putting out solid design work and sketching ideas for buy-in by my peers.

Collaborative Making, Part 4: Role-Setting

This past Thursday, I provided the following structure for developing a working process for your first collaborative assignment:

1. Set your intent, deliverables, and timeframe.
2. Establish individual roles.
3. Consider methods of critique. A.k.a. form the braid, set rules around idea-sharing.
4. Schedule touch-points.
5. What's your contingency? (Sick, late, timeframe or budget changes dramatically)

This structure dovetails with the "Forming the Braid" post from last week and blows out some of the action steps you'll need to take to work effectively.

In this post, I wanted to focus on #2, "Establishing individual roles," since we only got a chance to talk briefly about role-setting for our class teams. I've been wrestling with how to simplify this discussion, as it's proving to be deceptively complex. Let me take a stab at it.

Type Alphabet from Marian Bantjes

I stumbled across this piece by Marian Bantjes tonight. I can't believe the timing worked out so well; it's the perfect post to follow our own type alphabets. (Although, as inspiration, it may have been better a week ago...) I only wish she had given more details about how she crafted the alphabet.

Anyways, I just think her work is really cool, inspirational, and unusual. It's great to see how she uses her amazing talents as an artist and designer to make a living. It turns out there is demand for the kind of meticulous, off-beat, incredibly versatile artwork she's known for!

Detail:

Work 05 / Easy as ABC: Winter 09 Class Alphabets

Here are the found alphabets from our first take-home assignment! Everyone did great work and took a completely different approach to this project. Click on each letter to see the full alphabet on Flickr.

 

Denim Alphabet by Donnie Dinch

 

Circuit Alphabet by Meg Doyle

 

Liquid Alphabet by Claire Kohler

 

Shoestring Alphabet by Mark Notermann

 

Pin Alphabet by David Sherwin

Collaborative Making, Part 3: The Need for Self-Critique

When you're working in a team setting, it can be tempting (and very easy) to ask your peers for regular critique as part of your braid pattern. However, this is a slippery slope. On the one hand, you trust your teammates and want their opinions; on the other hand, you can sometimes get a little bit lazy and overlook obvious blunders. It's very important to have your own methods of self-critique to keep the work evolving.

Here's a link to a piece I wrote last year about setting up your own process of self-critique. Even when you're leaning hard on your teammates to help you through a tough project, running down this list can really help you nudge a good design into great territory when you've factored in the feedback from your team.

Glenn Sakamoto, a great designer, added a few questions to the above list that you should also consider: Does it draw me in emotionally? Does it have significant contrast? Does it communicate clearly? Does it transcend fashion, fads, or trends? All good stuff!

Looking forward to seeing you all in class on Thursday!

Collaborative Making, Part 2: Forming the Braid

Many years ago, I worked at a very fast-paced agency, and I just couldn't keep up... or so I thought. I would keep showing work in review and getting smacked down. There were a lot of late nights and rework. But there didn't have to be.

One day, my art director pulled me aside and drew the following two illustrations on the board:

Collaborative Making, Part 1: Workflow

Next week, we'll be having you embark on your first take-home assignment that requires collaborative making, as opposed to how you'd work through every aspect of a design problem on your own. With this in mind, I wanted to get you oriented to how this process would play out in the setting of a design firm, and get you the tools you'd need to manage your time effectively to work in similar constraints.

I drew this sketch to show how, once you've got a solid idea nailed down for your project, you've got to enter into the actual "design process," using whatever tools are at hand to create a visual comp. After you've iterated through the design process to the point that you feel that your work can be shared with others, you bring the work into review with your peers. They provide their feedback, and you re-enter the design process or, if the work is very tight, you move on to present it to the client. This is verboten at any design firm, and you've lived through this kind of process a number of times in school.

WORK 13 / Class 2: Book Report

Pictured above is a screen capture from a great resource for you to research current trends in book cover design, The Book Cover Archive.

The assignment from class: Bring in a book that you really like that most people probably haven't read. Each of us will give a brief talk about the book and why we like it. Your book will be randomly assigned to another designer in the class. You are now the book designer at Knopf assigned to create the cover for the new paperback edition. (Let's ignore that Knopf doesn't regularly do paperbacks.) Come up with an idea for the cover design + a single chapter page/spread of the interior. You may not read any part of the book other than the back cover/inside jacket flap.

Since we'd run out of time in class, we didn't get to do what I hoped, which was for us to give a very short talk about why we loved the book so much that we'd brought in. Because of that, I'd said that you could check out the book reviews on Amazon.com to try to get that kind of emotional flavor regarding the text. On reflecting upon it, I'm going to open up things here so that we can share a paragraph or two about the book we brought in. I'll start with my book, Veronica by Nicholas Christopher. Feel free to leave comments to this post with your brief blurb about your book as well!

The following text is from Nicholas Christopher's Web site:

On a snowy night in February, at the improbable point in lower Manhattan where Waverly Place intersects Waverly Place, Leo meets Veronica for the first time. Starkly beautiful, mysterious, aloof, she leads him into a world where illusion blends seamlessly with reality -- a luminously transformed city where powerful underground streams crisscross beneath the streets, a city of dragon-points and Tibetan mysticism, where real time is magically altered. Ten years have passed since Veronica's father, the famous magician Albin White, disappeared while performing a dangerous feat of time travel before a packed theater audience. White's disappearance was no accident. He was sabotaged by his apprentice Starwood, who interfered at a critical moment and sent him hurtling into the past, free to explore other eras but with no means of returning to the present...

I'm going to cut this quote off here, because any more would just give the whole plot away...

The thing that I love about this book is that it flows from moment to moment just like memory. And just like how we fall into a reverie when remembering something potent from our past, this book becomes deeper and more intuitive as you dive into it. After reading it, I realized that this book is crafted almost like you're falling down into a well -- but instead of hitting cold water when you reach bottom, you are left gasping as you stare up into a frigid, starry sky.

Collaborative Concepting, Part 3: Sharing your Ideas

Finally, let's explore #3 in the chain -- sharing your ideas with your CD/account team.

After you've concepted out a series of ideas and roughed them into a form that's palatable to share with your larger team at work (or the client), the fun truly begins. That is, the fun of actually making your ideas into tangible artifacts. But first, you have to sell your ideas in. If you just start designing stuff willy-nilly without conceptual buy-in, you're going to be burning a lot of time on the computer that would be better spent making sure your ideas are salable.

And when ideas get shared with others, a funny thing happens... as the idea broadens to envelop others, they grow in ways that you can't anticipate and control. Shaping that change is a critical tactic of group ideation, not enforcing things exactly as you see them in your mind, but as they can be shared en masse to create a more powerful meaning. You've all got to drink the same kind of Flavor-Aid. After group review, you may need to tweak, retrofit, or otherwise reconcept material if it isn't fit for execution.

Here's some governing principles for presenting your concepts to the overall team:

Collaborative Concepting, Part 2: Brainstorming/Concepting Meetings

Let's talk about #2 in the chain -- the concepting meeting with your peers.

Unless you're leading a brainstorm, chances are you're going to have to conform to the team's working process. But I can tell you that even if they aren't rigid in how the session is set up, it's going to probably conform to the following template. In a one-hour session, it will likely break down as follows:

Collaborative Concepting, Part 1: Overview + Project Inputs

In class, I'd drawn a chart similar to this on the board:

If we start to question every link in this chain, then we have an opportunity to increase our speed from idea to artifact as teams without sacrificing essential qualities of our practice. Or, to think about it another way: we need to be who we are as people through the process, and preserve that through any method that we consider taking on as a group. Genuine creative sparks should fly, not those of frustration.

In these next few posts, I'm going to talk about the first link in the chain: getting to a great idea through collaborative brainstorming. Please forgive me if this seems on the surface to be a bit rudimentary. There will be plenty of nuance we'll be exploring in class and in our take-home exercises that will require the structure I'm outlining here.

Let's start by unpacking how creative ideation occurs in an agency setting, and how to jump into what seems like boiling water with a confident dive -- or a cannonball...

Say Hello to the Designers

As part of the egalitarian spirit of 80 Works -- in the sense that myself/the teacher and the students are in it together, designing 80 projects on top of everything else in our busy lives -- I'm opening up this blog to posts and designs from the students.

Through the life of the class, we'll be putting up links to resources that are related to projects in process and in-class discussions, as well as work that we're excited about that comes out of the class itself.

So say hello in the next few weeks to Donnie Dinch, Meg Doyle, Mark Notermann, and Claire Kohler as they start posting in this space!

About the artwork: The image shown above, "I am Walter Gropius" by Claire Kohler, is from a warm-up exercise that we did in our first class period called "Bauhaus, Baby." Students had 15 minutes to place a square, circle, and triangle on a sheet of paper. They then passed that paper to another student, who had 10 minutes to write a headline that gave explicit meaning to the rudimentary design.

WORK 07 / Class 1: Lost in Translation

Here's another one of the works we'll be kicking off in class today: "Lost in Translation."

Exercise: Choose one of the provided ads and redesign it with text you’ve written in English. If possible, do not adjust the layout. What will help this ad make sense?

I've selected 11 ads from various sources around the Internet. All of them are in foreign languages: Japanese, Russian, Hebrew, Arabic, French, Spanish, and so on.

Download the foreign-language ads here.

WORK 05 / Class 1: Easy as ABC

One of the first take-home exercises we'll do for 80 Works is one I'd written about a few months back, "Easy as ABC." Here's the final version of the exercise we'll discuss in class:

The exercise: Assemble a 26-character alphabet using only found objects or environments. Letters may be documented for presentation to the class through collage, photography, photocopying, digital illustration, and other appropriate mediums. You may not merge examples of computer typefaces out in the wild, document elements of existing signage, or pull in anything that may be considered a finished letterform.

There are a million number of ways to approach this exercise. Here's a few examples I've seen around the Internet that pay it off, though it looks like these designers spent a good deal of time executing these alphabets. (And the second example had a tad of Photoshop to get things to line up right...)

Hooks Alphabet by Jeffrey Tribe. From SwissMiss.

Type the Sky by Lisa Rienermann. From Mirage.Studio.7.

I'm excited to see what ideas we'll come up with!

Winter 09 Class Overview and Syllabus

Hello 80 Works'ers for Winter 09 --

Here for your downloading pleasure are the 80 Works Class Overview and the 80 Works Syllabus as PDF files. I'll include the overview here as well.

Class Overview

The class has two types of exercises:

Foundation exercises will give us a taste of collaborative working conditions and potential roles that we may fulfill in a fast-paced design agency. It will also allow us to experience the challenges inherent in client-designer dynamics in a controlled and constructive manner.

Stretch exercises. These assignments are meant to cover a wide range of deliverables that a working designer would create across most of today’s prominent design disciplines. They are also meant to give us a taste of the range of approaches we need to take in order to find appropriate design solutions quickly. A small number of these assignments will be revisions of class-created materials, while others will require working in small groups outside of class.

You will not be provided with a full syllabus of assignments for the entire course, as we may be tempted to work ahead a few weeks. A luxury of time is rare in the world of design.

You will help create the class

Many of the 80 Works have been created by me or derived from classic exercises that are required in design school. The rest will created by you. This will allow you to try your hand at designing things that you’ve always wanted to create, but never had a suitable assignment to tackle. Every Thursday after Class 01, each designer will be required to bring an exercise to the class on a range of provided topics. Your teacher will assign at least 20 of those exercises to the class over the life of the seminar. (They need to be challenging, but don’t come up with something too diabolical.) Please craft your exercise within one of the categories shown in the 80 Works Class Overview PDF.

80 Works expectations

1. You should fulfill every assignment and bring it to class, no matter what. Work fast. Turn your editor off. Take as many risks as possible. The greater the risk in the work that you’re attempting, the more important that you bring it to class. You shouldn’t have time to sit around and think about whether what you’re doing is good.

2. Everything gets shown to the group, no matter what. Each assignment will get a quick group critique. Listen to how other people view it, and what they think it can become. This is invaluable input. Don’t defend what you meant to accomplish in the time frame, but just didn’t get there. This class is about possibilities, not finality.

3. Failure on some of the projects will happen, no matter what. Keep notes on what works and what doesn’t work. Learn to fail faster. As we get to the end of the class, we’ll focus on what can be extracted from your best works over the life of the class. When you have some free time, you can start thinking portfolio and polish.

For a good starter on working agile as a designer, take a look at a recent article on Ideas on Ideas.

See you on Thursday! Please be sure to fill out the class questionnaire as well... it's critical for our first class assignment.

Book, Class, and Blog Launch

Here's a quick update of what's going on with 80 Works for Designers...

The Book. I've signed up with HOW Design Press to write a book for working designers! The book will be based off the 80 Works classes I'm teaching these next few quarters. You can get the full story here.

The Class. The first 80 Works for Designers class starts this Thursday, and there's still space for one or two more designers. Read details about the class here and contact me at dksherwin at msn.com if you'd like to participate. Work on certain exercises in the class will be considered for inclusion on 80Works.com and in the book.

The Blog. There's now an 80 Works blog that will let you follow along with the class week by week. You can read it at http://www.80works.com/ and watch how things develop! I'll also frequently post questions for discussion and class exercises for the community to take part in, as well as calls for submission for contributing to the book.

To keep ChangeOrder's focus on business and design process, I will only include news about 80 Works for Designers here as stubs, while 80works.com will contain frequent postings about the class and the book.

Thanks to everyone who's helped support this idea since the very beginning... it's turning into quite a journey!