I like the defined boundary of visual design as purely visual (and typographical) in nature, because broad and vague boundaries make for weak definitions (see my response to Russ, above). The idea that design is now “solving problems” is also quite broad.

I try to avoid these semantic pitfalls because I think they distract us from the actual work, whether we are web designers, web architects, UXDs, IAs, EDs or something else.

In any event, it is unfortunate that you hew to such a limited and frankly outdated definition of design (e.g., that which is purely visual or typographical in nature) when both the visual design and UX practices have long since moved toward more of a design thinking definition wherein design as practice becomes focused on solving problems.

“RE: design/architecture, I suspected it was all a matter of terminology as well. I personally do believe the work described in the book is a form of “design,” but so is the minutiae of typography, color and layout which is not covered in the book. To me, “architecture” involves the larger structure and “design” involves the smaller elements that flesh out the user experience.”

You have to take into consideration that “User Experience Design” is pretty common, and pretty well-known. I think that, if you listen to Jesse James Garrett’s (author of “Elements of User Experience”) closing plenary (video: http://is.gd/wJyX transcript: http://is.gd/wJwN) from the IA Summit this year, you’ll find that “User Experience Design” isn’t new–nor is it inaccurate.

Additionally, you need to consider that the title of the book is “A Project Guide to UX Design” and we are pretty explicit about what we do and do not include. We define User Experience Design in the book as:

The creation and synchronization of the elements that affect users’ experience with a particular company, with the intent of influencing their perceptions and behavior.

(We end up stating that we deal with the tangible aspects of that)

Additionally, Wikipedia gives a fair definition: http://is.gd/fiiL

Many of the artifacts and chapters are mentioned:

* Site Audit (usability study of existing assets)
* Flows and Navigation Maps
* User stories or Scenarios
* Persona (Fictitious users to act out the scenarios)
* Site Maps and Content Inventory
* Wireframes (screen blueprints or storyboards)
* Prototypes (For interactive or in-the-mind simulation)
* Written specifications (describing the behavior or design)
* Graphic mockups (Precise visual of the expected end result)

We include the majority of those, as well as a few other key aspects to an overall project. We felt, as practitioners in the field with some pretty solid experience, that we were covering topics that were relevant to those in the field (and validated our ideas with several other practitioners prior to writing).

RE: payment schedules, I think we on the same page that “if it works for you, go for it.” There are many ways to schedule payments and I think we all agree upon the fact that, if an arrangement works for everyone involved, then it’s a good arrangement no matter how it’s scheduled.

RE: design/architecture, I suspected it was all a matter of terminology as well. I personally do believe the work described in the book is a form of “design,” but so is the minutiae of typography, color and layout which is not covered in the book. To me, “architecture” involves the larger structure and “design” involves the smaller elements that flesh out the user experience. Maybe I should study UXD more and see if there is better terminology in the industry.

While reviewing this book, I asked what “architecture” meant to the CEO of a local architecture firm and he considered the word’s Greek and Latin roots, which mean “design,” “building,” and (in Latin’s case) “carpentry.” Maybe design and architecture are one and the same….

RE: Luke Wroblewski’s “Web Form Design,” I actually just finished reading a review copy and will be writing a review shortly. :)

Thank you so much for writing the review.

I wanted to clarify part of what you call out in Chapter 3 on Proposals.

What I say in the book is that the myth that all projects need to be paid 50% upfront and 50% upon completion should be dispelled. In cases where you have a relationship with a client and that can work with you, that’s fine, but over the long term of trying to run a business–particularly if you are an independent or full-time freelancer, that type of arrangement can potentially put you in a dicey fiscal state.

Perhaps I could have been more clear to bring up that if it works for you, go for it. But I do strongly believe that if you want to make a go at being a full time consultant/freelancer, you need to work with a payment structure and schedule that allows you to keep steady income coming in the door.

Additionally, what we talk about definitely is a part of User Experience Design–what you are calling “Web Architecture”, which I do not believe is fully accurate. I’m trying to find a definition of “Web Architecture”–and I think maybe you meant the Information Architecture, which we acknowledge as part of the UX. Usability is a part of User Experience Design, and we do cover off on this in the chapter Design Testing with Users.

There are a number of organizations–UXNET (User Experience Network), Information Architecture Institute, Interaction Design Association, Usability Professionals Association are all great organizations that can give you different insights into the various aspects of User Experience Design.

I’m not sure if you feel that what we do is design–we certainly do feel as if we’re designing a User Experience. And we work closely with visual/graphic designers and developers to ensure that we’re all in-sync and not straying too far from the realm of what is possible and what is required.

Also: If you’re interested in a great book on Form Design, you should check out Luke Wroblewski’s book “Web Form Design” on Rosenfeld Media. http://is.gd/2dSa

Thanks again for the review–it’s really helpful to get an idea as to how things are being presented, and it helps us improve upon things in the event there are future versions.