Small to Enterprise: Growing Pains in the Content World
•
0 gefällt mir•614 views
In this presentation, I discuss the differences between managing content strategy in a small business and an enterprise business.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Small to Enterprise: Growing Pains in the Content World
Ähnlich wie Small to Enterprise: Growing Pains in the Content World (20)
Mehr von Rhyne Armstrong
Mehr von Rhyne Armstrong (17)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Small to Enterprise: Growing Pains in the Content World
- 1. Rhyne Armstrong From Small to Enterprise: Growing Pains in the Content World
- 2. From Small to Enterprise Growing Pains in the Content World @Ninety7
- 3. @Ninety7 Thank you Rhyne Armstrong @ninety7 Rhynearmstrong@gmail.com Linkedin.com/in/rhyne Facebook.com/rhyne Instagram - rhynearmstrong
- 4. @Ninety7 Aboutme •24 years in TechComm •11 years in Content Strategy. •All in small biz or start-ups. •
- 5. @Ninety7 Introduction I am going to talk about: • What have I gotten myself into? • My attempt at an illustration. • Where are we now? • Learning from my mistakes.
- 6. @Ninety7 Background Story •Small business bought by Cisco. •Small team with basic content strategy. •Defined roles, but no shared content.
- 7. @Ninety7 Expectation •Manage the documentation team. •Improve the quality of content. •Improve the distribution of content. •Improve internal content.
- 8. @Ninety7 Problems •Releases never stop. •Decisions have to be made quickly. •There isn’t a manual. •Platforms may not be compatible.
- 9. @Ninety7 Realizations •Some things are out of your hands. •Your mindset may have to change.
- 10. @Ninety7 Realizations •Some things are out of your hands. •Your mindset may have to change. •Your mindset will have to change.
- 16. @Ninety7 SmallSided • Little to no leadership off the field. • Agile by nature; lots of trial and error. • Small adjustments make big improvements. • Mistakes impact only your team.
- 17. @Ninety7 Players
- 18. @Ninety7 Players •Individual effort is key. •Roles are defined, but don’t matter in the end. •Players are fluid and play all roles. • Field is small, so players can be everywhere on it.
- 19. @Ninety7 Players •Likely have access to all levels of management. •Small-sided is NOT easy (or even easier). •It is just different.
- 31. Arsenal.com
- 33. @Ninety7 The Arsenal Way Arsenal Football Club exists to make our fans proud wherever they are in the world and however they choose to follow us. - http://www.arsenal.com/the-club/the-arsenal-way
- 35. @Ninety7 Asa player… •Know your role. •Adapt as necessary. •Pass the ball. •Know when to lead and when to follow.
- 37. @Ninety7 ManageDoc Team •Hired for coverage, and to increase knowledge and talent. •Improved doc team’s integration in the agile squads by having doc work tracked as a task in a user story.
- 38. @Ninety7 Improve Quality •Convert everything to MadCap Flare so content can be single-sourced and localised. •Put in place a new 2-stage review system.
- 39. @Ninety7 Improve Distribution •Creating new HTML 5 help system that pulls in pre- tagged XML content from a new LMS and Content Distribution System. •Moved internal content to the ISO prescribed content repository (since it is IP).
- 40. @Ninety7 Improve Distribution •Prototyping a new dynamic “playbook” that matches content with security bulletins, troubleshooting, and security procedures.
- 41. @Ninety7 Improve Internal Communication •Working on a new intranet for knowledge management. •Created cross-functional content team. •Streamlining communication tools to help with the overload.
- 43. @Ninety7 Andone more thing… • Started common language initiative. For Stealthwatch and beyond. • Common glossary. • List of terms. • Style and usage guide. • Wiki page for links and discussion of usage.
- 50. @Ninety7 ThingsI learned Content is (or can be) IP.