If you’re a content strategist, you have likely heard a lot about the importance of being part of designing and customizing content management systems. But if you’re a developer, you may not have the same perspective.
On a recent project, I witnessed this firsthand. While I made a point of creating content templates, identifying content types, and designing governance practices with an eventual CMS customization in mind, the (external) development team was not prepared for the same level of collaboration. They looked at my deliverables as options, and when my ideas didn’t fit, rather than open a discussion they unilaterally made decisions. Unfortunately, the result was a CMS that didn’t fit the content needs or the editorial team’s abilities.
Content Strategy vs. Content Engineering: The Emerging Role of The Content Engineer, by Cruce Saunders
A content tragedy: They intended to personalize, to reuse content, to have a great taxonomy. In reality, the developers couldn’t do it. The project was a failure.
What could they do to improve this for next time? They asked some questions. Continue Reading
Last week I met up with a UX designer who is fairly new to the field. She has an insatiable thirst for knowledge, and reads everything she can find on UX, IA, content strategy, user research, and design in general, which is a sign to me that she’ll be going great places.
She confessed to me that she’s often overwhelmed by the amount there is to learn. “I often feel that I’m barely sticking my toe in to this huge lake of knowledge” she said, and I confessed (to her chagrin) that after 6 years in the field, I often feel the same way.
To be honest, I don’t think that feeling ever goes away. There’s too much new research, too many new books, too much being produced and discovered every day. Instead, I think we learn to sift through the information and categorize it into one of two areas: base knowledge, and trends. Continue Reading