IxD 2011 Designing Advanced Design Workshop

Saturday February 12 10:36

Wednesday February 09 16:16

The problem that occurs when a clever, *advanced idea is inserted into a machine that is already optimized for itself — for efficiency. Just because it’s bright and clever and has colors doesn’t mean that it can find a place to fit in a process that is either (a) already humming along or, (b) unwilling or unable to change and adapt its workflow to allow something to drop into place. From my perspective, this means that it requires either a crisis which *forces the machine to stop and change itself — which is painful — or the machine needs to be changed from the outset to accommodate advanced design that does not come from left field but is accepted as something that is routine and part of the machine itself.

Some notes from Mike Kruzeniski‘s workshop at IxD11 on the topic of Designing Advanced Design. This is a fascinating topic to The Laboratory and equally fascinating to hear it from and participate with Mike, who is a good friend and former colleague at Nokia, of all things. Mike’s now at Microsoft so, like..now it might be like we’re colleagues again! At least partners in doing fascinating and unexpected things in the realm of design and technology.

Anyway. There were a number of highlights that I think are relevant. I’ll start with the general structure of the workshop, which was a workshop. ((Parenthetically, I’m a bit confused by workshops that are more someone presenting than people getting their hands a bit dirty, or going out in the world, or ignoring their iPad/iPhone update status checkers. I would even say that I don’t get the real-time twammering in a workshop. Either be there, or don’t be there. Bring a notebook. Sharpen your pen. Listen, do, speak. Okay, rant over.))

Wednesday February 09 15:06

Wednesday February 09 15:00

Wednesday February 09 14:45

After introductions by Mike and a bit of a discussion about what advanced design might be ((I mentioned I was also quite interested in *advancing design in the sense of moving it closer to the locus of decision making, alongside of the business-y types)) Mike presented the workshop exercise. We were to build boats. Little boats. Made of plastic bits sort of like Legos but, as we would find out later — subject to subtle variations in how they can be assembled, even much more than the typical Lego brick. ((* Update: via @rhysys — they are called Stickle Bricks! *)) The group was broken up into several roles — customers, customer liaison, builders, suppliers, plant managers, quality assurance. Each group played the roles you would expect in the construction of to-spec boats. Customers would place orders which would be relayed to the operation. I was a builder so I basically tried to assemble boats as quickly as possible, making horrible but not-obvious mistakes which resulted in boats being delivered…and then rejected. Each round was broken up into 10 order cycles that ran for a short, fixed amount of time. In that period we’d try to assemble the requested amount of boats, which the customers could reject for flaws. Flaws were sent back to be disassembled so we could try again, but things moved quickly. At the end of the round ((which consisted of a number of order cycles)) a tally was made to determine the per-unit cost based on factors such as — number of workers, number of delivered boats, quantity of raw materials left over, etc. All the things you might understand to influence the cost of a boat. At the end of each round, there was a short amount of time to reconfigure the whole “plant” — increase builders, rearrange how materials moved from source to assembly, break apart assembly into multiple steps, fire people, etc. This was all in order to decreate the cost per boat. We actually did really horribly the first time — target cost: $15. our cost, like..$2500. miserable. We got better over two more rounds, but still only got down to about $30+ or something.

Some insights from this exercise, which is derived from a familiar MBA exercise. First, designers don’t seem to want to fire anyone. Second, MBA people are more than willing to fire workers (based on Mike’s description of when he participated in the exercise at a sort of MBA program). Third, companies that make things — even a few of them and not in the millions of them — are optimized for themselves to be efficient. Change breaks that kind of optimization, resulting in less efficiency, higher costs, etc.

((That third point is one reason I guess we here at the Laboratory prefer small refinements that make big impacts. Making something just a bit better, or refining it with such tenacity — simple, small, thoughtful refinements — that the consequences can become significant without significantly challenging the need for efficiency.))

In the lead-up to this exercise, Mike introduced a few simple yet important tenets surrounding advanced design. There are two basic ways for a company to compete: (1) It can be cheap; (2) It can be different (be something else.) And he introduced one of these curious “Laws” that we here at the Laboratory had never heard of: Parkinson’s Law which basically states that work expands so as to fill the time available for its completion. Or, stated another way: The demand upon a resource tends to expand to match the supply of the resource. ((And yet another way that the Laboratory’s Bureau on Time Management uses as an operating principle: If you wait until the last minute, it only takes a minute to do.))

So then we can think of advanced design as those resources set aside for other activities, which sort of means that it can get a bit out of control if we apply Parkinson’s Law. So — how does one do advanced design? What are some models and approaches?

For the workshop, Mike looked at three case studies of advanced design studios: Nokia, Microsoft and Nike. Each has somewhat different approaches to advanced design, which he laid out. ((I may get the details of the case studies slightly off, but the substance is what I recall and what I think is the significant points.))

3 Approaches to Advanced Design

1. The Outlier
This is the advanced design studio that thinks about “what if?” scenarios, and explores to the side, looking at perhaps total departures from the conventional wisdom. Real out-there stuff that challenges and provokes. He offered three examples of The Outlier: BMW’s Gina Concept car from 2008; Nokia’s Homegrown project; Xbox Kinect

2. The Pantry
A bit like squirreling things away in the pantry for when the weather goes all awry and you’re trapped and can’t get out and don’t want to starve. You do things even if they’re not assigned to go to market. The case study Mike offered was Nike who’s design studio maintains an active bit of work exploring, researching new materials and the like. In the case study, Nike was outdone by Under Armour sports kit who created an intense following amongst various gladiator sports like Football and the like. They broadsided Nike whose marketing people went to design and said, like..help. Design did not start a specific program from scratch to address this, but went to their “pantry” and put together a package from the existing “advanced design” material to create a bit of sports kit that made Football’rs look super scary..like robotic gladiators. Plus, presumably — it worked as equipment. One intriguing thing Mike mentioned was that some folks had been doing some studies on motion and the like with sports folks and found out that feet and hands move the most, so they highlighted feets and hands by bringing out these intense dayglo colorations to the materials used in gloves and sneakers so the players *look fast. I found this fascinating.

3. The Northstar
This is where design works towards an advanced goal, but it’s more an aspirational target that is steered towards, perhaps indirectly. This might best be described as evolving a vision, refining from what’s out there. This I think captures to a certain extent what *vision work does, although sometimes vision work is basically just a nice thing to look at without the tectonics that could activate design work. The challenge is to avoid just creating something that’s cool to look at but doesn’t give enough to make it start becoming material.


1991 Audi Avus Quattro Concept Car

The example Mike offered in this case was Audi Avus concept car that (I know nothing about cars except how to drive them, sorta) that provided some radical new lines in 1991. It became a sort of objective point in a way — guiding the evolution of their surfacing and configurations so that over time Audi cars begin to take on the features of this Avus concept over time. The Avus provides the “Northstar” for the design team. Now — whether its stated expressly as in a lead designer saying..in 20 years lets get *here, or if it is less formal perhaps does not matter so much. Its more that this vision becomes quite tangible over time, an evolution of the car DNA.


Audi Rosemeyer

Audi R8

What I find most intriguing about this sort of vision-y Northstar case of Audi in particular is that they are able to stay on course. Twenty years is a long time — even, it seems to me, in the world of automobile design where things change exceptionally slowly because of the momentum and levels of commitment necessary for manufacturing and tooling and all the rest. Yet somehow they are able to keep their eyes on this objective that must’ve seemed quite radical at the time, especially if you consider what Audi looked like in 1991.


The 1991 Audi 200 Turbo

Some random insights that came up during the workshop.
* The Apple model isn’t reproducible perhaps because it is quite driven by the owners themselves and their personalities and abilities to drive change.
* Advanced design is about change. The instinct of a company is optimization; reduce risk and costs; it will reject change.
* Our role as advanced design is to help companies *prepare for change rather than execute it. In other words, be there when things go badly and people around you start losing their head and blame you while you keep yours, and you continue to trust yourself when all those around you doubt you — in other words, when panic and confusion sets in, advanced design can lead at those moments of epic, systemic change.

What is advanced design?
Let’s take this from the perspective of “advancing” design. The “advanced” moniker seems quite old fashioned. Advancing design, or advanced designing seem like useful semantic word play. The semantics help me think about design as something that can move forward (advancing design), rather than designing something in advance of something else (as advanced design would imply), or designing in a way that is different from what is designed today (or what is thought of as design today). In that way, advancing and poking and provoking means more than differentiation. It means more than using advanced techniques.

Some notes/thoughts about what advanced/advancing design or advanced designing might be:

* working through ideas differently
* designing the way of designing always, for each and ever
* iteration, refinement — put it up, strip it back, put it back up again
* communicating tangibly, materially
* storytelling — film, prose, language
* design fiction – actively suspending disbelief. making props and probes and prototypes.
* proto-typing – making stuff, in the shop, at the bench, learning by making and doing
* photography – way better than clip-art and it forces a different kind of conversation and moves things away from *only working at the screen in Illustrator

Why do I blog this? Because I went to the workshop; it made me think of a few useful things; I’ve been sitting on this in draft state for almost two months.

One thought on “IxD 2011 Designing Advanced Design Workshop”

  1. Thanks alot for sharing Julian!

    Wanted to be there to participate but didnt manage passes in time. This really helps fill in the blanks somewhat.

Comments are closed.