In the several corporate UX settings I've been a part of, once consistent pain-point is content. A bit reason for that is that rarely do I see dedicated technical and copy writers on staff who are subject matter experts in content writing.
So what usually happens is it falls into the hands of a mix of business stakeholders and UXers.
Let's assume that this isn't changing any time soon (ie, we're not going to hire a staff of copywriters, unfortunately)...what is your process in terms of handling content and maintenance.
Some specific challenges we've encountered:
- content is written into wireframes and/or prototype
- content is updated post-launch. when it comes time to update wireframes, prototypes, content is now out of sync.
- review/feedback happens in isolation of the broad big-picture. Example: one team changes a term on a microsite, doesn't inform the team handling a different microsite to be in parity.
The question: In lieu of having a proper, dedicated content writing team, what process have you found works for handling content within UX?
At the very least, I'm thinking a separate document should exist outside of the wireframes and prototypes for 'final' content review and authoring, but at the same time, I'm adverse to having yet-another-document floating around.