Design Maturity

I am the type of guy that has believed for quite a long time that design drives the development of most of the things Teknision builds and most definitely applications. When ever I speak publicly or post on mailing lists, or even here blogging, I claim this.

There have been those around the community that have chastised my opinion, stating the architects should drive development, and to have it any other way is wrong.

On the other end of this argument, I went into speak at Algonquin College to the Graphic Design students. I told them I started my career as a designer, and still am today, yet I haven't done any graphic work myself in 2-3 years. I claimed obviously that there is alot more to design than graphics.

I just wanted to point you to something interesting, an attempt at defining a concept called Design Maturity. I came across it with Gabor Vida, as we have been doing some research on ROX (Return on Experience).

It can be quite sobering for both those on the design, development, and strategy side when you honestly evaluate yourself or your own organization and it's position on the continum.