Process is not a Differentiator
There's a slide from Jamin Hegeman's recent UX week workshop that sparked a memory. He shows a diagram entitled "Interaction Design Process" that consists of four steps: Discovery, Definition, Design and Delivery. Then a diagram next to it entitled "Service Design Process" that consists of the same steps: Discovery, Definition, Design and Delivery. I imagine that it's demonstrating an affinity.But that's also a graphic design process. My first job out of college was at a graphic design studio in Kansas City called D3. The name originally stood for the three partners, but over the years they converted it to "Discover, Define, Design." I also seem to remember "Define, Design, Deliver" floating around the office at some point. Unfortunately it was D3 rather than D4 but the delivery sort of goes without saying when you're dealing with a first-order design studio focusing on print.
The point is, "discover, define, design and deliver" tends to be descriptive of design as a whole and not unique to any particular sub-branch. It's not a stretch to apply it to any of the places I've ever worked; including industrial design studios.
You might almost say that process is not a differentiator.
Posted September 15, 2010
Jeff, I was just exercising some procrastination while trying to work on my thesis, and thought I would check out your site (since I hadn't in some time).
I agree, process is not a differentiator, especially at the most abstract levels. Perhaps it becomes a differentiator the more one subdivides and defines all of the smaller processes that occur within the larger processes, but even then it all depends on specific context, input/output, etc.
However, that's not to say that a well-defined process is not important (and I don't think that's what you're saying at all). Process is important for two major reasons: 1) to study and improve process and 2) to enable collaboration by allowing a team to see what particular phase they are all working within.
If you haven't ever seen this, it might be of interest to you. Hugh Dubberly's expansive collection of many design process models: http://www.dubberly.com/articles/how-do-you-design.html
That's all. Back to work.
However, that's not to say that a well-defined process is not important (and I don't think that's what you're saying at all). Process is important for two major reasons: 1) to study and improve process and 2) to enable collaboration by allowing a team to see what particular phase they are all working within.
CMU Grad Studio