Design Studio Session Overview What is a Design Studio Session? Designers express and explore ideas, generate, and evaluate alternatives to ultimately make decisions and take action. Artists, industrial designers, graphic designers, and architects use Design Studio sessions. Used to: brainstorm, refine, and share ideas, build design skills. Main purpose is to saturate the design space with possibilities, which can be refined. Original Sketch for Flckr
Sketching is a Proven Method for Innovating Innovators sketch to visually think through ideas:
Leonardoda Vinci always sketched a minimum of three times. Scribbles and doodles would sometimes be clustered together, while at other times they were pages apart. (Michael Gelb, 2000)
Thomas Edison sketched the incandescent light bulb in 1879 for his US patent. “No one can doubt the expertise needed to bring a sketch into fruition,” said Charles Batchelor, Edison’s friend and fellow inventor.
On its company website, IDEO, an award-winning design firm, says it builds multi-disciplinary teams that use collaborative sketching to design their ideas.
Sketching is a Critical Process for the 21st Century Sketching is critical for your current success:
Bill Buxton of Microsoft explains over 20 different methods to sketch out user experiences using sketching, cameras, and whiteboards. (Buxton, 2007)
Brandon Schauer of Adaptive Path explains how to make sketching portable with Sketchboarding. (2007)
Dan Roam explains how many of the best ideas are formed literally on the back of a napkin. (Roam, 2009)
Jim Ungar and Jeff White’s presented at SIG-CHI 2008 on how sketching is an agile method. (SIG-CHI, 2008)
JeromeRyckborst’s Five Sketches or Else Method combines the Six Thinking Hats of Edward de Bono with lessons from Bill Buxton. (UPA, 2008)
Bill Buxton’s Design Funnel from Sketching Experiences Buxton talks about a Design Funnel in the SDLC, where the opportunity to saturate the design space with ideas occurs very early. The design space is limited (or goes into a funnel) as projects move in the timeline. Project Timeline
Sketching Early, Prototype Later (Buxton) Buxton explains that opportunities to saturate the design space decrease, as convergence occurs. Concept generation narrows the further you move into the SDLC, but there are still opportunities. Coding limits the design opportunities.
Why Sketches in a Design Studio Session? Why Sketches? Worth a 1,000 words Disposable Quick Cheap No special skills needed No coding needed The goal is to saturate the design space with ideas… Source: Bill Buxton’s “Sketching the User Experience”
Design Studio Session’s Saturate the Design Space Participants produce several rough sketches Discuss and critique the sketches Merge ideas into one design concept Above are Jim and Jeff working on Jewelry.com site (SIG-CHI 2008)
Why are Design Studios Important to You? You should be leading these Design Studio sessions! You are preventing usability issues rather than treating them! You are working on projects from the start, not at the end. RELEVANT
How do make a good sketch? You’re making a rough sketch—Use pen & paper, and colored markers. Don’t use a computer. Use large paper and use the whole page—Write BIG. Draw BIG. Only use fat-nib markers so a roomful of people can see the idea when you present it. “Good enough” is good enough—You’re making a rough sketch. Use only enough detail to communicate your main idea. Only ONE idea per sketch. ANY idea—even crazy or expensive ideas—are OK. Don’t judge your ideas now, just get five on paper. Remember: QUANTITY breeds QUALITY. Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Use 11x17 Paper (Use Big Paper for Big Ideas) Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Don’t Worry about the Details Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Sketch Enough Details to Convey Your Idea Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
You Can Always Refine the Sketch (It is Disposable) Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Provide Annotations in Red for User Actions and Outcomes Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Provide a Title and a Brief Explanation Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
What makes a presentable sketch? Add LABELS and arrows that identify the actions and the results. Number the labels and responses. Always write labels in red, and use red only for labels. (Text in the GUI and title bars is not a label.) Add a SKETCH TITLE to help communicate the idea and to help people remember what it’s about later on. Be able to take about 20 seconds to talk about your sketch. (Don’t worry—it’s enough time. Remember, a picture is “worth a thousand words”.) Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Before you come to the session Do your sketches separately from others on the team. Expect to spend 2-4 minutes on each sketch, but don’t expect to do all your sketches in one sitting. FIVE substantially different ideas—five sketches—for each solution. We need to get out of the common response zone, so five unique sketches, or else (FUSE). Don’t be discouraged if you feel uncomfortable when it’s harder to come up with sketches after doing your third one. This is “the sticking point.” Hang in there! Your really creative ideas need a bit more time to come to the surface. They will come. Talk to other people who’ve done sketching sessions about their experience. QUANTITY breeds QUALITY. We are saturating the design space. Adapted from Jerome Ryckborst’s Five Sketches or Else Method (UPA 2008)
Get Out of the Common Response Zone! You must come with five sketches, or else:- We are wasting our time.- We are staying in the common response zone.- We are not saturating the design space. The sketches must be unique, or else:- You are iterating the same basic idea.- You risk getting committed to one idea.- You are still in the common response zone. Adapted from Jerome Ryckborst’s Five Sketch or Else Method (UPA 2008)
DeBono’s Six Hats—A Structured Path to Decisions De Bono’s Six Hats help team members think about a problem in the same way at the same time, and in a specific progression. This allows the team to complete each step more quickly, and it ensures that all essential details get covered. The hats are ordered in a specific way, so we all think about the designs from various perspectives.
Source: Creative Problem Solving (Don Treffinger, Scott Isaksen, Brian Stead-Dorval, 2006)
Blue Hat: Facilitator or Guide Blue hat: Process (meta-talking). Useful to guide and focus the group. For example: “Now let’s think of yellow-hat thoughts about this idea” moves the group to the next step, and “Can you hold that thought? We’ll look at grey-hat thoughts later” postpones a comment to the right time. Things You Might Hear:- What have we done so far?- What decision have we reached?- What do we do next?- Let’s where a different hat for the next few minutes.- Let’s summarize what we have learned.
White Hat: Neutral, Objective White hat: Factual (state the facts). Seeking objective information, without opinions. Things you might hear:- What do we know? - What don’t we know?- What information is missing?- What questions do we need to ask? - How will we get the information we need?
Green Hat: Creative, Generative Green hat: Creative (ideation). For each problem, sketch five substantially different ideas. During green-hat thinking, do not analyze or judge the ideas; reject nothing; all ideas are acceptable, even “silly” or “impossible” ones. After presenting your sketches to the other design participants, mash up—or re-sketch—to add something new and something borrowed. Re-sketch one of your sketches, and present it. Re-sketch one of someone else’s sketches, and present it. Next, synthesize everything you’ve seen into a few sketches. Present those, and then apply the next two hats to them. Rules of Creativity:
Yellow Hat: Positive, Sunny Yellow hat: Positive. What are the reasons that a green-hat idea may work? Analyze all sketches together, but ask participants to comment on each sketch in turn, so that one sketch never gets two comments in succession. Ask participants to start each comment with the words “This idea may succeed because….” This allows you to probe for value and benefit of potential ideas. Things You Might Ask/Hear:
Black Hat: Critical, Cautious Black hat: Critical. What are the reasons that a green-hat idea may not work? Analyze all sketches together, but ask participants to comment on each sketch in turn, so that one sketch never gets two comments in succession. Require participants to start each comment with “This idea may not succeed because….” This is a good time for a usability expert to identify unusable features in all sketches. If participants get defensive about a comment, refocus them on black-hat thinking (defensive remarks are often yellow-hat), and remind them that one sketch never gets two comments in succession. Follow the black-hat thinking by another round of yellow-hat thinking. After the analysis (yellow- and black-hat thinking), do a further round of green-hat thinking. Use this round of green-hat thinking to address the grey-hat and yellow-hat thoughts.
Red Hat: Emotional, Intuitive Decisions Red hat: Decision. Decision-making based on everything you’ve experienced, based on what you think and feel, using your judgment and opinions. No consensus? You may need to follow the process for another round, starting with white-hat thinking. Although frustrating, sketching is cheaper than having a developer code and then discard (or worse—not discard) a poor design. Things You Might Hear:- I feel like this idea has potential.- I feel like this idea is very unusual.- How do I feel about this idea right now? NOTE: Everyone feels something, even neutrality or apathy. Your Feelings Could Be:
Putting All The Pieces Together Blue Hat (Facilitator) controls the meeting and the hats. White Hat (Group) reviews known facts about design space. Green Hat (Group) creates five initial sketches, which get iterated (re-sketched) during the Design Studio session. Two minute review of each idea at the start of the Design Studio. Yellow Hat (Group) reviews all green-hat sketches, capturing positive aspects of the ideas. Four minute yellow-hat discussion of each green-hat design idea. Black Hat (Group) reviews all green-hat sketches, capturing why ideas may not work. Four minute black-hat discussion each green-hat design idea. Red Hat (Group) reviews and decides on how to move forward based upon each person’s feelings, intuition, and experience.
Design Studio Methodology Design Studio Methodology is not new. Six Hats Method for Software Design was developed by Jerome Ryckborst, who presented at UPA 2008.
White Hat: Understanding the Design Space BRD delivered day before Design Studio. Before the Design Studio Session, we put on our White Hat to determine design space:- Two pages identified—Home and Air Availability pages.- High-level use cases were in the Business Requirements Document.- Affected user personas are Traveler and Travel Arranger. Participants were asked to create five unique designs for the Home and Air Availability pages only.
Tip: Use Brainwriting, If Needed Problem Statements are recorded on top of a page. All problem statements are put into center of a group (3-5 people). Each person gets a sheet and records their initial 3 answers. They return their sheet and get another one. They read the problem statement and other responses. They record new responses (freewheel and piggyback). Goal is 3 statements every 3 minutes, until done. After completing, the team evaluates and votes (focusing). NOTE: Brainwriting has been calling brainstorming on steroids. It captures all data (self-documenting) and you record individual responses (no Group Think). Finally, the group decides.
Blue Hat: What were the Sticking Points? Before looking at any of the sketches, we asked the following question:“What were your sticking points as you sketched?” The answers were similar:- Getting to the 5th idea- Screen real estate- Considering current state- Thinking about the future- General fear (of rejection) For Your Consideration: Ideas and thoughts are exposed in Design Studios, so people can feel nervous. Acknowledging the emotions helps us to move forward. It helps to know that other people has the same sticking points, too.
Green Hat: Individuals Sketch—No Collaboration
Blue Hat: Clustering Similar Designs For the Air Availability pages, we clustered the designs that were similar to make them easier to analyze. Three predominant page designs emerged from the Design Studio session. We still reviewed all of the pages using the Yellow Hat (positive) and the Black Hat (critical). Group 1 Group 2 Group 3
And the winner is….. Red Hat: Decision Point (4 of 4 Pick)
Blue Hat: Debrief 4 Sketchers/1 Facilitator 20 Original Sketches 40 Positive Comments 40 Critical Comments 3 Basic Page Designs Emerge 4 Designs go to 2nd Round Iterate on 2 of 3 Page Designs 4 New Designs for 2nd Round 1 Design Voted on 4-4 2 Hours to Complete Final sketch mashes up ideas from all participants.
Green Hat: Refines Sketch into JPG Rendering Using Final Sketch, a designer can turn the initial drawing into a JPG rendering. Key things to note here:- About 2 hours to sketch- About 2 hours to render JPG- Further down Design Funnel
Some General Numbers Total Energy Used assumes 5000 hours of usage, which is the standard life of an LED bulb.
World Usability Day Site The World Usability Site wants to create a Sustainability program, where users can sign up to get a free LED light bulb. Design Challenge: Create an Energy Calculator to show how changing out a 50-watt light bulb with an energy-saving LED bulb saves money and energy.
Designed the Actual Widget With 40 Designers in 4 Hours
Tips and Tricks Use teams of 6-8 people (too many people is too hard) Stick to the process (use the hats—they work) Do 5 sketches, then 3 sketches, and 1 sketch Vote using a 10% rule:- 30 sketches = 3 votes- 15 sketches = 2 votes- 7 sketches = 1 vote Use mashups for the final sketch. NOTE: It is best to have business requirements defined before a Design Studio, so each person is trying to solve the same problem.
Contact Information Twitter: @BrianKSullivan Email: firstname.lastname@example.orgBlog: http://theusabilitycorner.blogspot.comWeb: www.bigdesignconference.comwww.worldusabilityday.org