Free form diatribe on Kristina’s afternoon workshop.

  • (technical difficulties)
  • (she already has the room at her fingertips)
  • the discussion of content is a very organic process that involves all of us to participateĀ  (and she will steal our ideas)
  • pseudo empowerment to site editors.
  • putting the onus on us. We need to help drive the content strategy discussion.
  • Too often we react to content, it’s a critical biz asset
  • need cs to develop message hierarchy
  • CMS cannot define and refine workflow
  • Governance outlines helps you get funded
  • Content Development falls down when people don’t track what content they are creating.
  • Ask the who what why where when how and cut your content in half
  • Quicken example – sell boxes mint – see myself everywhere.
  • Out there, nobody cares. Make content strategy relevant to the business.
  • Structure = IA
  • CS/IA kinda two sides of the same coin
  • We are lacking case studies big time
  • (Kissing hands, shaking babies. I think I got that right.)
  • content is spread all around, not just on your website.
  • Rolling inventory – inventory that never ends. (yay!)
  • Identify where you can have the biggest impact with the least amount of money and go with it.
  • In need of a spidering tool (look to Norway)
  • You can manually audit up to about 2000 pages.
  • Project charter is part of the content delivery – biz objectives
  • (Break time! 10 minutes people, hustle hustle!)
  • Not every project needs content strategy
  • Don’t shove it down people’s throats. Play your cards carefully.
  • Ecosystem – the environment the where the system live.
  • context, content, users – IA framework
  • Content strategy needs user research.
  • competitor site audits are tricky because it isn’t about keeping up with the jones, but more about discovering your niche.
  • As a strategist you need to listen and let them keep them talking
  • Pain points (we need to do a better job at promoting these to the right audience)
  • Sign off is very important.
  • Doc needs to be easy to use, makes informed decisions, facilitates smart decision making, docs action plan, troubleshoots implementation. Be sustainable.
  • Your one second is driven by visuals, graphics, load, etc. call to action
  • page template vs page table. Page table is not lorim ipsum
  • Gap analysis is a key component of CS
  • workflow can help eek out inefficiencies
  • some websites have become poor business properties
  • empowerment needs to happen or else we are just followers.
  • We so even remotely done. Yes, we’ve been doing this for years, but just now generating buzz.
Advertisements