Prototyping Q&A with Victor Saad
The following question and answer discussion comes from Victor Saad. It resulted from a prototype experience I called, “27/7,” in which I asked seven questions about prototyping to 27 people I know or know of, admire, wondered about, and otherwise respect. The intent of the experiment was to understand better what the terms “prototype” and “prototyping” mean to a wide orbit of design professionals, with outcomes hopefully helping a book I’m writing about… prototyping. This discussion is the first in the series of content resulting from that experiment.
A few notes about Victor:
Victor Saad is the creator and curator of the Experience Institute (“Ei”). The work of Ei has introduced a reframe in and around a conventional college trajectory by making experiences a source material for learning and credentialing outcomes. Victor experiments with new work and executes new concepts all the time. From afar it’s not always clear which is which because it always seems intentional. His responses illuminated that very thing: his intentionality with what he does. I am grateful for his willingness to share his time and corresponding thoughts.
Questions 1 and 2: “Prototype” has a literal definition and has lots of implications — what do you think it communicates well? Where is it a total miss?
Victor Saad: Prototype communicates imperfect. Minimal time. Few resources. Little cost. It says, “I just need to show you something to help us both understand if there’s something worth continuing here.”
I think some people take it as half-assed or thoughtless. That’s a shame.
I also think it can sometimes lead to moving forward even though there’s NOT something worth continuing. As in, “we made this prototype, so let’s keep going.” But prototypes should help decide whether or not to continue… not just how to continue.
Q3: How does prototyping show up differently in your personal versus professional life? (… or your recreational life or experimental life?)
VS: Personally, it feels like lower pressure and more fun. I can prototype a new routine or apartment layout or wardrobe and it feels fun and useful. It’s for me or those around me.
It’s hard to feel that same levity with work prototypes. I feel greater pressure to have a prototype lead to something important. I’m on the clock and I’m working alongside smart people who are working hard. It’s harder to say, “I tried a prototype and it didn’t work out,” because we also need to get that proposal out, and write that talk, and plan that board meeting, and 1,000 other things.
No one places that pressure on me — I just feel it.
It can be hard to decide when a prototype is needed and when you should just do the thing.
Q4: Thinking of a recent project in which intentionally you used a prototype — whether a challenge or a breeze — what were ways you knew if the prototype was going well or poorly?
VS: When we were building our new deck of cards, we made several prototypes. Mostly hand written and with blank cards purchased from amazon. We hosted lunches, house parties, and office events. At the end, we always asked for feedback and people loved sharing their ideas. Typically, people were excited and wanted us to continue. That’s a good sign, but that’s also not super helpful in deciding what to change. So sometimes, we waited to ask questions — just an extra day or two — and asked what they remembered about the experience? Whatever they remembered became a helpful clue for what we should continue doing.
Q5: What’s a go-to prototyping tool you use most regularly? (Please feel easy interpreting “tool” loosely — object, state of mind, constraint, whatever…)
VS: No tech.
Usually paper and sharpie.
Sometimes tape on the floor to create mini “rooms” where people can enter to “experience” a module or state of mind.
Q6: What’s missing from the discussion of prototyping?
VS: Taking inventory.
I wonder if it would be helpful if people took inventory of what things they already have to begin prototyping. In class, we often provide cardboard, construction paper, etc etc. But that innately communicates that we need to give people the things to prototype. It would be interesting to not provide anything and let people look around and reach for whatever is in their midst. Or ask for what they might need.
I’m not always sure how long a prototype should last? How do you determine when a prototype is finished? How many iterations are enough before you say, “Let’s ship!” or “Let’s stop!”
Q7: What’s a change in how you think of prototyping *now* contrasted to how you may have thought/acted in the past?
VS: Shorter, faster, less resources.
Some of my biggest mistakes came from getting too far down the road without getting unbiased feedback.
Get it out of my hands.
Sometimes, I shouldn’t even be the one leading the prototyping. Someone who has less of a stake in the idea needs to lead it to come to unbiased next steps.
I’ve learned prototypes don’t have to be so serious. Help the people interacting see the levity in this. Let them tinker, add on, break it, etc. I’m much less interested in protecting my prototypes. I want people to play with them!