JV: Have you seen challenges in being a designer at Google, a very sort of technology-focused and -centered company?
IA: It is challenging. I think in a lot of conventional companies, design is kind of a top-down process. Where you think about who are your target users, what’s the market you’re going after, what are their needs. You do requirements-gathering, and then you design the experience around that, and then you tell the engineers to go build. Here, the way products are conceived a lot of times, it’s an engineer has some kind of idea and then starts building it and then — as it gains momentum — a product manager and a designer might become attached to it. So it’s a very bottoms-up kind of process, which is very different to how designers are trained to think about product development. Yet I still think that there are ways that designers can work within that environment and still have products be use-driven and design-driven, but the ways in which you go about getting yourself inserted might be quite different than [at] other cultures, [which] are maybe more top-down, or product- or marketing- or design-driven.
Jeffrey Veen, "Chatting with Irene Au," veen.com, 7 Feb 2007, www.veen.com/jeff/archives/000961.html.
Also listen to a podcast at itc.conversationsnetwork.org/shows/detail1758.html
