What do you use to explain design?

Interested to see what resources people use when trying to explain the design process to non-designers. Particularly those in which you’ll be working with on a project.

Anything - Websites, books, case studies, images etc throw them up here.

1 - Your portfolio, which should have the process
2 - That IDEO shopping cart video on YouTube?
3 - I think IP’s firm put out a DVD called ‘the brief’ expressly for this purpose - I would check that out too.

As cheesy as the book is to some, The Art of Innovation by Tom Kelley gives some pretty good insight into how designers think for the non-designer.

That IDEO shopping cart video on YouTube?

I’ve used this before - Surely there’s something similar out there a little more up to date.

2 things.

First i typically present a compelling pitch deck showing what I’ve done, how, and why it is relevant and the philosophy behind it.

Then I usually make a very detailed document stating exactly what will be done when. I use past work examples to show exactly the level of fidelity I am thinking for what points and call attention to key decision points where there concise feedback and firm decisions will need to be made otherwise the whole timeline gets screwy.

3 things.

Discovery - What is the customer saying? What can the manufacturer do?

Strategy - What does the discovery mean?

Implementation - Make the strategy real.

A video of that would be mighty helpful.

A well thought out phrase.

if that doesn’t work…

Smoke and mirrors :slight_smile:

Boogey Man -
I try and use a simple case study that focuses on two things - identification of insights for design work, and how that insight translates into physical objects, features, etc.

This is a great point Yo, and something that I have been having my design agencies include recently on quotes where there are inexperienced team-members. I find that the images make it much easier for people to understand how the fidelity of prototyping can progress as the confidence grows that a concept is resonating with users. We tend to use alot of words for prototypes (roughs, sketch models, form studies, appearance models, works-like, looks-like, proof of concept, proof of principle, etc. not to mention the myriad of RP types), and those new to design get confused very quickly.

nice succinct way of putting it. frog’s variation is this:

You want the recipe to the secret sauce too? :wink:

Questions like this always get me back to the need for a different kind of design education. One based on what you need to know vs over acadmic-ization. One where a professional can take a class on pitching and proposals as a brush up when it is needed.