Latest Tweets

What We Do

| 06.19.2009

diagram

I recently sketched this diagram to explain what we do and wanted to see if it resonated with people. Is this too high level? Does it add a layer of understanding?  Basically, we work with clients on all levels of product design including feature definition, interaction and visual  design, user research, and specification. The only thing we don’t do is the final code. Thoughts?

Share with

6 Comments

  1. I think this is a standard model for many, but for the last 5 years or so, I think many agencies and definitely many internals are also idea generating arms of the process/organization. And by this I mean that design research is generative in nature, and helps or informs the creation of ideas.

    further, I think “code” should be substituted with “engineering & production” so that it can include non-software environments of interaction design as well.

    — dave

    posted by Dave Malouf at 12:08 pm on 06.19.09
  2. I really admire the basic simplicity of it, and I get what you’re trying to convey (being at the converging heart of it all), but I always keep coming back to the Eames venn diagram which pretty much sums it up for me and is frankly very difficult to improve upon IMHO:

    http://www.ghostinthepixel.com/?p=103

    Of course, substitute his words with “engineering” and “QA” and “Biz Dev”, etc. all those various parties of competing/conflicting concerns. But what I really admire about Eames’ is the note Eames wrote that these areas are not static but always growing and evolving (hence the organic, sketchy nature of his diagram) Also, his point that “adding more clients add to the relationship in a positive and constructive way” which is vital IMHO.

    posted by Uday Gajendar at 12:21 pm on 06.19.09
  3. I just created something similar at my organization as I was trying to convince upper management to start a UX team. As I iterated through the process, I realized there is a 4th sphere. As UX professionals our goal is not just to help the product side to understand what they need to create but mainly to represent the end-user in all parts of the product development.

    We don’t want to get pigeon holed into thinking as a product owner. We are there to stand up for the end-user in the entire process. The user is the 4th circle and UX is what brings users, product owners & coders together.

    posted by Pradeep Nayar at 12:41 pm on 06.19.09
  4. I’m part of a team of 6 with a product manager and a community manager. Often I find that my job requires me to generate new ideas from conversations with users in the market, design parts of the product (the visual and interaction sections) based on those ideas and being a developer also contribute code to that feature. I would probably put myself in a box that spans both the circles, however i don’t know what my title would be. Any ideas?

    posted by Disha Al Baqui at 12:42 pm on 06.19.09
  5. I might add one / two more bubbles on to that “Strategy.” An experienced UX person can provide strategic insight into what direction a companies product should be headed,

    Maybe think of strategy as a big circle surrounding the 3.

    posted by uidesignguide at 2:38 pm on 06.19.09
  6. Why ‘product design’ rather than ‘interaction design’? To me the latter is more to do with physical rather than digital (even though Kim Goodwin suggests otherwise). If you’re aiming more at digital then Ixd + coding, otherwise Product Design + Engineering (as Dave suggested).

    posted by Vicky Teinaki at 7:36 pm on 06.19.09

Leave a comment