Content Strategy Workshop: TC Camp 2016
•Download as PPTX, PDF•
0 likes•382 views
Workshop on how to create successful content strategies with interactive content, structured authoring, and Agile development environments. Delivered at TC Camp 2016.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to Content Strategy Workshop: TC Camp 2016
Similar to Content Strategy Workshop: TC Camp 2016 (20)
More from Gavin Austin
More from Gavin Austin (6)
Recently uploaded
Recently uploaded (20)
Content Strategy Workshop: TC Camp 2016
- 1. Content Strategy Workshop How and Why Salesforce Changed Its Content Strategy Gavin Austin Ted Kuster gaustin@salesforce.com tkuster@salesforce.com @salesforcedocs
- 2. Safe Harbor • Safe harbor statement under the Private Securities Litigation Reform Act of 1995: • This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. • The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. • Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. Agenda 1. Who we are and who you are and why we should all care 2. Why Salesforce moved to more interactive content 3. What types of interactive content we’re creating 4. How we changed our content strategy 5. How we trained teams
- 4. Takeaway If you’re not creating interactive content beyond traditional documentation, you risk losing your customers.
- 6. Who we are Gavin Austin Ted Kuster
- 7. Who are you? 1. What do you hope to learn? 2. Where do you work? 3. Your challenge?
- 8. About your content 1. Which types of content do you create? 2. Do you use structured content? 3. Which tools do you use? 4. What’s the scale?
- 9. What is content strategy? 1. “The analysis and planning to develop a repeatable system that governs the management of content throughout the entire content lifecycle.” 2. “Provides context, so that the organization’s vision can be implemented in an integrated way, to meet business goals and project objectives.” Rahel Anne Bailie, The Language of Content Strategy
- 10. Salesforce’s content strategy Prioritize interactive content over traditional forms of content to give customers the types of information that they want to succeed.
- 11. Your strategy? In one or two sentences.
- 12. 2. Why Salesforce Added More Interactive Forms of Content
- 13. Does this kind of content look familiar?
- 14. What do customers need from content? •“Simplify documentation… It has always been far too lengthy and time- consuming.” •“If I have to leave a page to do research, I am going away… Having it right in the same place increases productivity.” •“There are a lot of videos about what you can do, but they don’t always show how to do it.” •“All documentation focuses on how-to, but we usually start off needing to know when-to or why-to.”
- 15. Why do we write content? Increase customer adoption. Reduce customer cases.
- 16. 3. What Salesforce Added for Interactivity
- 17. What types of content did we create? 1. Walkthroughs 2. Trailhead 3. Videos
- 19. What do our customers think?
- 21. What do our customers think?
- 22. What are videos?
- 23. What do our customers think?
- 24. 4. How Salesforce Changed Its Content Strategy
- 25. How did we change our content strategy?
- 26. Why did we make these changes?
- 27. (1) How has the new strategy improved our help?
- 28. (2) How has the new strategy improved our help? When we write help, we build it according to a structure that provides one bit of info at a time, leading to ever-greater levels of detail.
- 29. (3) How has the new strategy improved our help? When we write new content, we write it to a voice and tone standard that makes it easy to redeploy in any of our content types, including help.
- 30. 5. How Salesforce Trained teams
- 31. How did we train large groups of people?
- 32. Do you practice “Scrum, but”? No one practices Scrum by the book. We all say, “Scrum, but…” This worked t our advantage.
- 33. Do you practice “structure, but”? Probably like you, we’re still working towards a shared view of what “structure” means.
- 34. If there was no “Scrum, but” or “Structure, but”? 1. What would your content strategy be? 2. What do you need to get there? 3. What’s in your way? 4. Can you sidestep?
- 35. Takeaway If you’re not creating interactive content beyond traditional documentation, you risk losing your customers.
- 36. Thank You!
Editor's Notes
- Welcome, brief intro of Gavin and Ted—we’re tech writers--and what Salesforce does for those not familiar. Background----Doc is Dead (LavaCon 2015)! Lofty statement and claim, which we’ll explain. [Doc ALONE is dead?] in that we need new types to address how users learn and interact with our content to get their work done--prioritizing interactive and visually engaging content types because they’re more effective. Same content in a more discoverable, interactive way. In this workshop, you'll learn why Salesforce moved in this direction with its content and content strategy. We’ll also learn about you and your content strategy. As tech comm writers, we’re all in this together and can easily learn from each other. But first…
- Keep the lawyers employed: Salesforce is a publicly traded company, and anything you see or hear in today’s preso might not apply to future releases of the Salesforce application.
- Let’s have a discussion. We’ll share our content strategy, but we want audience to be part of conversation! Disclaimer: this is not a tools talk!
- ‘Doc is Dead’ in that we need new types--re prioritizing interactive content types because it's more effective. Same content in a more discoverable, interactive way. In this preso, you'll learn why Salesforce moved in this direction with its content and content strategy. How many of you create help & 'guides'? How many of you love reading those types of content or feel you get sufficient help from those types of content?
- #1 from the agenda
- Brief intro of Gavin & Ted—we’re tech writers--and what Salesforce does for those not familiar. Gavin – Writers everything from UI text to API reference guides. Preso background. Ultra runner. Ted – Writer and information architect; DITA Maestro. Preso background. Banjo.
- During this workshop, let’s have discussions. Let’s learn from each other. You learned about Ted and me, now let’s learn about you. Ted and I will answer these Qs too.
- To better understand you and the content strategies and challenges you’re working with, please answer these questions. They’ll help us get to know each other better and perhaps solve some of our content problems throughout the workshop. Ted and I will answer these Qs too.
- Before we talk about content strategy, let’s define it so that we all have a reference point. You might not agree with it or like it, but it gives us all an equal place to start from.
- In a nutshell this is the Salesforce Documentation and User Assistance team’s content strategy. Of course, you’ll learn more about it. But notice it’s simple and one sentence?
- Take a minute to think about your strategy, and then share it with us to learn about you and your content better.
- #2 from the agenda, moving on to Salesforce’s journey to adding more interactive content. Break first?
- PM role play (“doc all the things!”): Doc all new features, customer feedback, bugs. Try to keep head above water on an agile/scrum development team. Limited contact with support and marketing to know if content is useful for customers. Follow traditional info model of concept, task, reference, and sometimes FAQ content. Use help, videos, release notes, and guides, tip sheets, workbooks, cheat sheets, etc.
- Do you agree? Different users need content to do different things, depending on their experience level and what phase of the learning process they’re in. These quotes came from extensive user research done by the Salesforce UE team. Due to our PR team, we can’t really share with you the stats or all the customer quotes, but these summed up a lot of the findings, for not just Salesforce!
- A few years ago, due to Salesforce’s massive success and growth, and tons of help content [or as we were planning new content strategy to accommodate Lightning Experience?] we had to step back and ask ourselves this question. We also had to ask it because trust is our number one priority at Salesforce, and we had to ask ourselves if our content was adding to our value/brand of customer trust. Now we ask the Q to you. Perhaps another side of the question is why do you get paid to create content? What’s content’s business value? These were our answers. And based on customer research and data, we learned that we could do a better job of hitting these two targets. The way to hit those targets was not by changing the content so much as its format (“types”), where it’s exposed to customers, and how visual and engaging it is. The interactive content types we’re now using give us these qualities and even encouraged us to better apply these characteristics—info typed, discoverable, visual, and engaging—to the traditional help documentation we continue to write.
- #3 from the agenda, what types of content our team added—interactivity being the most important thing.
- Now, we’ll go into explaining the types. Still use concept, task, reference, and sometimes FAQ--but need it to be discoverable, learn, do. For scale – Plus graphics, minimalism, voice and tone. We make them accessible through the UI and promote them where it makes sense based on how users need to consume the content. We make them more prescriptive (use-case focused, examples) and visual (new graphics specialist). We could give one example of when we'd use a content type other than a walkthrough (a help topic or video, for example) and why a writer would make that choice.
- We can’t give you the exact data, but we can give you some anecdotal….
- Trailhead: >700% growth in active users over 6 months Modules (learning with challenge questions to test your knowledge and make you think) vs. Projects (hands-on practice w/code verification to make sure you’ve followed a set of steps; used for events)
- “Not your typical, boring technical writing.”
- More videos w/ dedicated specialists Embedded in UI Now more interactive with links to additional resources from within video itself
- We’ll get to the reasons why this is, the history.
- Going into #4 of agenda
- Instead of putting most content in help and release notes, we streamlined a pattern based on what our customers ask for; and we prioritize interactive content over traditional content. We have a content menu, if you will. Not all customers want the same types of content. But we can put it where they’re most likely to find it and need it.
- Simplified the number of deliverable types we produce to narrow the options and make content easier to reuse and maintain. Still use traditional help documentation (concept, task, reference, and sometimes FAQ)— but we’re conscious of how we deliver content based on how users might need to consume it (discover, learn, do), opting for more engaging interactive content when possible. What format to use when – walk them through our flow (before/after) strategy
- Optimize traditional help documentation to align with new content standards based on more engaging interactive content our customers love. Highlight how example is: Minimalistic (only the high-value content users need, not everything you can do with a feature) More friendly voice and tone More prescriptive (use-case focused, examples) Visual (new graphics specialist)
- Ted... (aka progressive disclosure.) As a result, much of our help content base has improved in usability and find-ability. (It’s more fun to read!) Also, some of that content has become more easily available for reuse in Trails, videos, walkthroughs, etc. We aim to extend this throughout our help content base.
- Ted… Pass out the printout here
- Agenda item #5. Break?
- shared content plan early on – iterative dedicated trainings with cool themes to make more engaging guidelines: wiki and colorful desk references [add screen shots]
- We’re an agile shop, but we wouldn’t have been able to roll this out if we’d been requiring writers to hey strictly to agile methods. Please try to work the best you can in this framework, making whatever compromises are needed to keep customers happy. Iterative process.
- Ted… Structure can mean different things to different people. We’re evolving.
- Repeat the most important message…if you heard nothing else today of value…
- End of workshop. Thanks for your participation and helping us learn more.
- If we didn’t answer some questions, please contact us on LinkedIn. More Q&A now. Please fill out the survey.