In the various online content strategy discussion groups, a recurring theme has been about seeing examples of content strategy – not the processes but actual deliverables. My immediate response of wanting to help out gets tempered with the reality. First of all, sharing a document without the context is relatively useless, and most work is done under NDA. No one who wants to protect their reputations and their clients would expose that kind of work , and particularly in a public forum. As well, there may be some reluctance to give away intellectual property – in other words, if someone comes up with a particularly clever way to deliver value, that becomes a consultant’s competitive advantage. Giving it away is, in effect, giving away earning potential.
There needs to be a balance, though, between self-protection and sharing and support. This is the first in a series of posts that will share some of the generic deliverables that make up a part of a content strategy. However – and this is a big however – these deliverables are to be taken with a grain of salt. They are not offered in any sort of context. Some deliverables may apply to certain situations, and not to others. These are simply my way of doing things, and may not bear any remote resemblance to the way that others create their deliverables.
Building deliverables on common sense
If you were thrown off a boat into a lake, you would figure out how to swim. For the pioneers of content strategy, this was certainly the case. We reasoned out the processes and deliverables based on what we needed to accomplish by the end of the project. It’s still that way, for much of the practice. It has to be. You need to respond to existing situations, and work within the infrastructures and plans in place. It’s basic consulting practice: understand the current state, anticipate the future state, find the gap, and figure out how to fill it. Other consultants do that with finances, staff, and processes. We’re the consultants who do that with content – and what you create is what you need to get the job done.
With this in mind, over the new few weeks I will show examples of some basic deliverables. As always, feedback and suggestions are welcome, and I’ll add to the list as I get suggestions.
- The increasing relevance of ebooks and other epublications
- All I learned about book publishing comes from The Book
- Content Re-use and Narrative Flow
- 2012 in Review – a Content Strategy Retrospective
- Two weeks, four events, eight observations: insights from the conference circuit
- Content Inventories, Audits, and Analyses: All part of benchmarking
- Working on the City of Vancouver website
- Occupying a unique content strategy space
- Move over, Big Data. It’s time for Big Content.
- Setting a context for a content strategy vocabulary
- Content classification and findability
- Content development
- Content management
- Content strategy
- Information design and usability
- Professional development
- Social media
- User experience
Tagsaccessibility ann rockley books career development CMS content as asset Content convergence content lifecycle Content management content strategy convergence deliverables DITA Duo Consulting experience design Flash integration intelligent content interaction design Management marketing mentors open standards plain language politics processes Professional development ROI search section 508 single-sourcing Social media STC structured content syndication taxonomy TechCraft translation Twitter usability user-centered design user-generated content User experience value XML
- rahelab: Need more #contentstrategy business side arguments? I'm making them at the NYC meetup, June 10th: http://t.co/TlAeEF8IBA
- rahelab: .@eaton I think that when the two sides come together and pool their technical and editorial resources, the results will be awesome!
- rahelab: RT @RayGallon: My guest post on @gathercontent blog: Your Software Needs a Content Strategy, Too! — http://t.co/MOCuTfpTFa #contentstrategy…
- rahelab: RT @JRoTweeter: @rahelab ♪♫♫ From Paris to Berlin ♪♫ in every disco that I'm in ♪♫♪ you know it's Content I love… ♫♪
- rahelab: .@angelacolter not to mention country/language differences. E.g wi-fi in Spain, Germany is pronounced wee-fee. DITA is DEETA or DITTA.