Cs meet up case study nell kauls

544 views
471 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
544
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • About 4-5 months into the blog’s inception.
  • We are hoping that company-wide participation will increase the interest and diversity of our posts. We have 3 employees in Malawi and many consultants in Oman whom I am hoping will follow through and give the blog a whole new dimension really showcasing our international experience.
  • We have a lot of different people on staff with many different talents. All are good writers, but need some guidance in writing for the web. So, we decided to have an editor review all posts.
  • We wanted to give people tools to improve their writing for the web so that the editor doesn’t have an onerous task.
  • Cs meet up case study nell kauls

    1. 1. CASE STUDY: SEWARD INC. BLOG NELL KAULS How content strategy could have saved my web project
    2. 2. THE SITUATION <ul><li>We wanted to start a blog to: </li></ul><ul><li>Tell the world about what we do. </li></ul><ul><li>Tell stories about our international work. </li></ul><ul><li>Build content pages on our new website. </li></ul><ul><li>Drive traffic to our site. </li></ul><ul><li>Have content to share with social networks. </li></ul>
    3. 3. THE SITUATION <ul><li>Things started out really well: </li></ul><ul><li>We met our goal to publish weekly. </li></ul><ul><li>Posts were interesting and timely. </li></ul><ul><li>Pages were indexed and getting traffic. </li></ul>
    4. 4. WHAT WENT WRONG <ul><li>Signs of blog anemia were showing. We were: </li></ul><ul><li>Publishing only every 2-4 weeks. </li></ul><ul><li>Relying heavily on list blogs (posts lacked diversity). </li></ul>
    5. 5. WHAT WENT WRONG <ul><li>Signs of blog anemia were showing. We were: </li></ul><ul><li>Republishing content. </li></ul><ul><li>Relying on a few key people to write posts, rather than company-wide participation. </li></ul>
    6. 6. WHAT WENT WRONG <ul><li>Serial blog posts not so serial. </li></ul>Hey! I made it just shy of a year.
    7. 7. WHAT I LEARNED <ul><li>We were way too informal and casual with our publishing goals. </li></ul><ul><li>You say: Volunteer to write for the blog! People hear: This is optional and not a priority. </li></ul>
    8. 8. WHAT I LEARNED <ul><li>Company leadership needs to buy in to the blog and “encourage” participation. </li></ul><ul><li>Leadership needs to state the business case for the blog. </li></ul>
    9. 9. “ We needed content strategy because without it our blog would have limped along at considerable risk to our reputation.
    10. 10. HOW THINGS HAVE CHANGED <ul><li>Assigned a blog editor. </li></ul><ul><li>Stated the business case for blogging. </li></ul><ul><li>Required company-wide participation, including international employees. </li></ul>
    11. 11. HOW THINGS HAVE CHANGED <ul><li>Created an editorial calendar with dates, topics, and blog ideas. </li></ul>
    12. 12. HOW THINGS HAVE CHANGED <ul><li>Established an editorial process for blog posts. </li></ul><ul><li>Communicated the process to all contributors. </li></ul>
    13. 13. HOW THINGS HAVE CHANGED <ul><li>Gave people access to writing tools. </li></ul>Posted editorial calendar and Seward Style Guide on intranet. Bought copies of style guides for reference.

    ×