Hi Ron... thanks for the thoughtful response... ... I would agree. I did not mean to imply that schooling is where respect is earned, but I think it helps toMessage 1 of 118 , Dec 5 2:43 PMView SourceHi Ron... thanks for the thoughtful response...On Dec 5, 2009, at 2:45 PM, Ron Jeffries wrote:I would agree. I did not mean to imply that schooling is where respect is earned, but I think it helps to clarify the level of background and education. There are a lot of folks trained in graphic design working in the software field. It is not appropriate to lump them in with IA's and UXA's that have deep HCI and interaction backgrounds. Much like the difference between power and authority... one is given the other earned... respect must be also be earned on a personal level. More over I was speaking about the respect for design as a practice.My other point being that an open process of collaboration does require not only respect for the players but also respect for specific discipline. While I may know a lot about project management and even how I might code a project, as a user experience designer I know my place. I would never pose to tell someone how they might do their job unless they were outright failing. But for some reason, we are all designers, we all have opinions and many feel compelled to 'help' the designer. I often ask folks to tell me what the problem is... and yet it is easier for some to prescribe the solution, even when outside of their expertise.I was speaking more broadly to product design... and that includes services and software. I have yet to see really successful software design and production. Granted most of my experience has been in startup mode - proof of concept companies, but it is a very young field and very complex. I think the book dreaming in code does a nice job of documenting this. I think agile is an interesting approach. I do not think it is a mature metoid, and I doubt if it, in its current state, ultimately becomes a standard (but that is probably foder for a different and much larger conversation.There are many components of agile that are worth. Amongst them scrum style meetings and quick, iterative launches. Part of is probably prone to the iteration because as a designer, I have used quick iterations a short hand prototypes for over twenty years, as havemost of us.I was not trying to say anything specific about you Ron. But all of use understand the tendency to be less than open regarding our process when the scrutiny is lacking respect.Its always easy to lay blame, but completely unproductive. I have found that the larger the organization, the more aggregate the solutions and end products. Compromise is quality is hard for everyone.
I ve been called pedantic on occasion. I m ok with that ; )Message 118 of 118 , Dec 10 2:47 PMView SourceI've been called pedantic on occasion. I'm ok with that ; )On Sat, Dec 5, 2009 at 6:56 PM, Jeff Patton <jpatton@...> wrote:
On Dec 6, 2009, at 12:22 AM, mark schraad wrote:For me separating different kinds of design starts to get a bit tedious. When you think about it, it's like night and day - which although you can tell me to the second when sunrise or sunset is, it's a pretty academic discussion when it's still light outside. OK, bad metaphor - my point is that all design decision run together. They just do. Giving precise definitions for one type or another doesn't seem to help people make better decisions in practice.Reading "the oatmeal" has put me in a strange mood. Yes I am the mother-f**ing pterodactyl: http://theoatmeal.com/comics/ptero