bloggers/designers themselves doing not only their
> own visual work, but the IA work *and* the coding behind their blogs. > (I'm still catching up myself in this whole blog thing, having only > gotten started in late December of 2003.) For these designers to learn > the interaction piece as it applies to more robust applications is not > a far stretch, imho. Once they do, they'll have the skills in visual, > IA, interaction and base level coding. That's the new school of > interface design in my view.
Interesting you should mention bloggers, because I am increasingly
convinced of the value of adding excellent writing skills to the pool of
interaction design breadth.
Not necessarily in terms of writing an essay, but rather to take ownership
of inline help text, error messages, and labels. I'd be curious to know
if my experiences are unique, but I have found myself time and time again
working with companies where "copy-writing" is shuffled off to a
department entirely separate from the interaction/visual design studios,
where it is clear that the copywriters have shallow to no knowledge of the
site or application they are writing copy for.
I do a lot of suggested copy revisions (which, thankfully, are usually
implemented instead of the original inappropriate or confusing text), but
am surprised that this practice continues. Maybe I am just seeing
particularly poor implementers of this process?
I am curious - how many of you write or contribute to your own inline
messaging/error messages? If not, do you find the separate of tasks to