Comments on: Transcribing the spoken word

By: Friday content strategy: installment 3 « new media mentality

Friday content strategy: installment 3 « new media mentality — Fri, 28 Aug 2009 18:03:26 +0000

[…] Transcribing the spoken word, by Richard Ingram […]

By: Richard

Richard — Wed, 12 Aug 2009 12:00:25 +0000

Thanks Destry. Simplicity was certainly a consideration! It’s all food for thought though.

There are many roles and responsibilities I toyed with promoting on the model; one being the ‘Marketer’. They would have lightened the branding/advertising load on the copywriter and could have provided another helpful link to the marketing elements of SEO.

A ‘Translator’ would indeed be an interesting addition. I too would like to hear how they see their position within this and other models of this ilk.

By: Destry Wion

Destry Wion — Tue, 11 Aug 2009 18:51:18 +0000

Now that I think about it. There’s probably two levels of accessibility that suggest two kinds of roles. The accessibility embedded in markup is what I was talking about earlier and suited to a skilled integrateur these days. But transcription is a whole bigger thing outside of the Integrateur’s domain, and thus, like the Translator, could be another required role in the model. Question, I guess, is when do you stop for the sake of simplicity?

I love your model, by the way, and enjoy playing with it.

By: Destry Wion

Destry Wion — Tue, 11 Aug 2009 18:33:23 +0000

Another great article, Richard. Nice to see someone making the bridge between CS and accessibility. However, this would seem to make clear a gap in your positioning model from “They’ll thank you later”.

What seems to be missing now is the “Integrateur” role on which things like graphic charter, prototypes, markup, accessibility (transcription?), scripting, etc would be attached. I would say HTML = page templates if your talking about the markup kind, so that would be something to clear up with the Interaction Designer role too, I would guess.

The Integrateur role would certainly be linked between the Interaction Designer and the Programmer, and the Content Strategist would be linked to the Integrateur via the prototypes and accessibility halos, at least.

“Translation” (or Localisation/Internationalisation) is another halo that might at least have a dotted halo as many web projects are international these days. Whether that’s added to the Information Architect role or not, I’m not sure, but I’m going to have some translators have a look and let me know because I’m quite curious now what they would think. They’ll probably claim needing their own role in red, of course. LOL!

Cheers!