Death to Lorem Ipsum & Other Adventures in Content
by Kate RutterIn May 2008, Kristina Halvorson, Founder of Brain Traffic spoke at Adaptive Path’s Queens of Content event. Her presentation “Content Strategy: The Mania, the Myth, the Method” shed light on current perceptions of content strategy in user experience, and provided great fodder for further exploration.
I was particularly intrigued by what Kristina had to say, because while I agreed with the overarching message, I felt compelled to debate some of the finer points. So we did.
The result is a conversation that starts with content basics and closes with a bold challenge. Along the way you’ll read about standard-bearers, the infamous “seat at the strategy table,” why lorem ipsum should be DOA, 3 things every UX project lead needs to consider, typing monkeys, and hear wisdom from Winston Churchill.
Check it out in our Essays: Death to Lorem Ipsum & Other Adventures in Content
This entry was posted
on Wednesday, June 25th, 2008 at 2:48 pm and is filed under Content Management, Content Strategy, Conversations, Experience Design, Experience Strategy.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
This post is licensed under a Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
July 2nd, 2008 at 3:29 pm
Julie H. is a seasoned UX consultant, and she sent these comments along via email, and I think they add to the conversation:
I completely agree about importance of content to be considered early on, produced early on and iterated, along with the design work; and the importance of preparing the clients for review responsibilities. Copywriters are core members of UX teams I’ve managed and copy is a key deliverable. Copy briefs would include nomenclature, page, button, link, help, error, alt tag text and I’ve needed copywriters to understand SEO and, at the beginning of a project, to work out which organizational legacy nomenclature doesn’t work for users and what opportunities we, as a UX team, have to change it.
Thanks for the insights, Julie!