Increase Customer Adoption with Interactive Content

Mar 10, 2016Download as PPTX, PDF0 likes462 views

Salesforce Case Study: Adding Interactivity to Increase Customer Satisfaction Presented at the Intelligent Content Conference on how Salesforce built a framework for interactive content, which led to an increase in customer adoption.

Increase Customer Adoption with
Interactive Content
Gavin Austin & Lila Giuili
Tech Writers, Salesforce
@salesforcedocs
@salesforcedocs • #intelcontent

Salesforce Safe Harbor
@salesforcedocs • #intelcontent
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.

AGENDA
① Everyone’s content problem
② Salesforce’s solution might be your solution
③ Our new help content strategy and next steps
@salesforcedocs • #intelcontent

1 Everyone’s Content Problem
@salesforcedocs • #intelcontent

1. Do you like using online help and user guides?
2. Do they give you a hands-on experience?
3. How do you think your customers feel?
Traditional Content Woes
@salesforcedocs • #intelcontent

Customer Feedback
@salesforcedocs • #intelcontent

Product Feedback
@salesforcedocs • #intelcontent
1. How to improve free product trials?
2. What did potential customers need to see?
3. What was the biggest driver for new interactive content?

User Experience Research
@salesforcedocs • #intelcontent
Customer confusion

2 Salesforce’s Content Solution
@salesforcedocs • #intelcontent

Enhanced Trial Experience
@salesforcedocs • #intelcontent

Walkthroughs
@salesforcedocs • #intelcontent
1. What’s a walkthrough?
2. Who can create them?
3. What do customers think?

Customer Praise
@salesforcedocs • #intelcontent

How Walkthroughs Work
@TwitterHandle • #intelcontent

INTERACTIVE HELP CONTENT
WHERE CUSTOMERS
NEED IT
@salesforcedocs • #intelcontent
WALKTHROUGHS

3 New Strategy & Next Steps
@TwitterHandle • #intelcontent

Walkthroughs’ Impact on Our Help Content Strategy
@salesforcedocs • #intelcontent

Ongoing Challenges
@salesforcedocs • #intelcontent
1. Who’s JSON?
2. What about DITA?
3. How to support writers?
4. How to find walkthroughs?

SECOND MOST IMPORTANT
FORM OF CONTENT
@salesforcedocs • #intelcontent
WALKTHROUGHS

THANK YOU!
Q&A
@salesforcedocs • #intelcontent

Your career, brand, and reputation depend on how well you deliver presentations, both internally and externally. For most people, getting up in front of an audience is a terrifying experience, but it doesn't have to be. By learning a few simple techniques, you can confidently deliver career-boosting technical presentations that won't bore an audience, accidentally tarnish your brand, or limit your career opportunities. Presenting is a craft, not a talent. Those who learn the craft can easily take their careers to the next level.

Content Strategy Workshop: TC Camp 2016Gavin Austin

Doc is Dead! How Walkthroughs Changed Salesforce's Content StrategyGavin Austin

Agile2013 - How Writers Can Thrive in Agile Software DevelopmentGavin Austin

The document discusses how writers can thrive in agile software development environments. It begins by describing challenges writers face with agile practices like terminology, estimates, meetings and context switching. It then provides solutions for implementing agile successfully, including training, templates, clear definitions and hiring more writers. Daily best practices are outlined like asking questions, scheduling documentation hours and organizing documentation blitzes. Team best practices encourage volunteering, speaking up and acting as a shared service. Benefits of agile for writers include more impact, visibility, ownership and clearer communication. The key takeaways are to teach these strategies, emphasize the benefits and reduce costs by supporting writers.

Get Started with Lightning Web Components Open SourceDeveloper Force

With the announcement of Lightning Web Components (LWC) Open Source, developers can now leverage the same UI framework for building applications on Salesforce, and on any other platform. This opens up new possibilities for simpler code sharing, faster application building, and an overall better developer experience. Learn how to get started with LWC Open Source and how to build your first component.

codeLive: Positive and negative testingDeveloper Force

Live Coding with Salesforce Developers: Adding CI to Your Salesforce ProjectDeveloper Force

Live Coding with Salesforce Developers: Decoupling your org with TriggersDeveloper Force

This live coding session demonstrated how to decouple trigger execution from logic using a trigger framework to prevent cross-package dependencies when multiple packages contain triggers on the same object. The presenters built a solution that uses custom metadata and meta programming to dynamically instantiate handler classes defined in the metadata. Key learnings included how packaging can break up a large org but require special handling for triggers due to the best practice of a single trigger per object, and how custom metadata and meta programming can help define trigger logic and execution in a decoupled way.

Rollin' Out Lightnin' Ain't All That Frightenin' by Jon BarlowSalesforce Admins

The document provides guidance on rolling out the Lightning Experience user interface for Salesforce. It recommends educating yourself and your company, planning and executing the rollout, and becoming an expert on Lightning. Key steps include choosing a rollout team, educating users, managing skepticism, planning training, setting a launch date, creating a project schedule, and testing processes. The rollout involves enabling Lightning using the Migration Assistant and monitoring adoption over time. Super users and ongoing education are important for success.

The Proactive Admin: Five Tips to Become an Indispensable Force by Brandon Be...Salesforce Admins

The five tips to become an indispensable admin are: 1) Understand the big picture of how all the data fits together rather than just working in the data, 2) Be proactive in identifying potential issues instead of just putting out fires, 3) Look for interesting trends in the data and share valuable insights, 4) Solicit feedback to better understand challenges and terminology, 5) Build trust by offering insights and then gaining an executive sponsor who can unlock new opportunities. Following these tips can significantly enhance an admin's value.

How to Create Awesome DocumentationSalesforce Admins

The document provides an overview of how to create effective documentation. It discusses the importance of documentation and planning the documentation process. It recommends documenting for users and colleagues. Several tools for documentation are mentioned, including Google Sites, Confluence, and ScreenSteps. Best practices for documentation include planning, writing, revising, and publishing documentation, then repeating the process. The presentation demonstrates setting up a wiki site for documentation. It emphasizes starting with existing resources and dedicating time for updates.

Demystify Metadata Relationships with the Dependency APIDeveloper Force

The document provides an overview of the new Dependency API in Salesforce, which allows users to understand dependencies between metadata in their org. It discusses how the API provides information through the MetadataComponentDependency object about relationships between fields, objects, and other metadata components. The presentation includes a demo of using the API and discusses the current limitations and roadmap for expanding its capabilities and coverage. It encourages users to leverage the API and documentation to help untangle dependencies in their orgs.

Write Powerful Communication to Get Your Stakeholder's Attention by Andrea Ho...Salesforce Admins

The document provides tips for writing powerful communications to get stakeholders' attention. It recommends including the ask in the subject line, such as "[Post to Chatter] Lightning Go-Live". It also suggests including a timeframe, like "[Post to Chatter by Oct 11] Lightning Go-Live" to increase urgency. Finally, it advises putting the ask at the beginning of the message, followed by next steps, importance, and background details. The goal is to get straight to the point and ask to maximize the chance stakeholders will take the desired action.

Introduction to FlowSalesforce Admins

Flow is a declarative development tool that allows users to visually build automated workflows to gather information and update records. The demo showed a flow to automate case management by gathering required details for new user or feature requests, setting decision branches, and distributing the flow through Lightning App Builder. Additional resources for learning more about flow include Trailhead modules, the Success Community, The Wizard News, and the Wizardcast podcast.

Capturing and documenting business processes and rules for agilityMichael Moyal - BPM Consultant

This document discusses combining business process modeling with business rules documentation for increased business agility. It recommends a three step methodology: 1) capture business processes through modeling, 2) identify steps relying on rules, and 3) describe each rule. Benefits include improved communication, responsiveness to change, and automation. A maturity model is provided showing progression from manual to automated processes relying on business rules engines.

Easy No-Code Integrations with External Services and Visual FlowSalesforce Developers

The document discusses forward-looking statements and associated risks and uncertainties. It states that any projections or statements regarding future operations, strategies, products, features or customer contracts are forward-looking. It notes risks including those associated with new functionality, products, business models, operating losses, fluctuations, outages, security, litigation, mergers and acquisitions, market immaturity, limited operating history, employee retention and growth, and larger enterprise customers. Customers should make purchase decisions based on currently available features.

Intro to Apex Testing - Dreamforce 2016Laura Meerkatz

This document discusses best practices for testing Apex code in Salesforce. It recommends writing tests to validate both positive and negative scenarios. Specific areas that should be tested include user access permissions, exceptions, and bulk operations. The document provides guidance on setting up test data, avoiding SeeAllData, and using TestSetup to share data across tests. It also recommends using Test.startTest/stopTest to reset governor limits between tests. The goal of testing is to ensure the code performs as expected and to avoid bugs by systematically validating different situations.

#DF17Recap series: Make apps smarter with EinsteinSalesforce Developers

Einstein Analytics for DevelopersSalesforce Developers

Drive Adoption and Buy-In Using Storytelling by Megan HimanSalesforce Admins

Megan Himan discusses using storytelling to drive adoption and buy-in. She notes that stories should have a purpose, use real people to connect authentically with what people care about. When starting with storytelling, understand the story you want to tell and collect real people's pain points. Tell the story at the right time, frame it for your audience and desired outcome, and use details to evoke emotion by bringing the "why" to life with real people and descriptive pain points. Avoid pitfalls when storytelling.

Salesforce at Continuous Delivery Foundation SummitMark Interrante

How to Write the Trailhead Way by Chris DuarteSalesforce Admins

The document provides tips for content creators on writing in a clear and engaging style for Trailhead. It suggests using fewer words, sounding human by reading writing out loud, using stories to engage readers, taking risks to surprise readers, and embracing feedback to improve work by focusing on the content rather than the author. The document also introduces several Trailhead writers and the modules they have created.

How to Choose the Right Automation Tool by Jonathan Hackworth Salesforce Admins

This document discusses various automation tools in Salesforce and provides examples of how to apply them. It introduces the Salesforce automation suite, which includes Workflow, Approvals, Process Builder, and Visual Workflow. Examples are given such as using Workflow to assign an account owner based on opportunity criteria, using Process Builder to automate a multi-step approval process, and using Workflow or Process Builder to trigger actions like sending a lead record to an external system or posting to Chatter. Tips are provided like starting with Process Builder, testing in sandbox, and keeping automation names descriptive.

Sandboxes: The Future of App Development by Evan Barnet & Pam BarnetSalesforce Admins

Sandboxes are non-production environments that duplicate a production org's metadata and can be used for app development, testing, training, and user acceptance. There are different types of sandboxes that vary in refresh frequency and amount of production data included. Managing sandboxes strategically is important for efficiently building apps. Change sets allow migrating changes between sandboxes and production. Best practices include always testing in sandboxes first, keeping security settings and data consistent, and communicating with business stakeholders.

Become A Formula Writing Guru in 20 Minutes by Mike Martin & Shannon HoweSalesforce Admins

This document provides tips and examples for becoming proficient with formulas in Salesforce in just 20 minutes. It covers the use of IF vs CASE statements, AND/&&/OR/|| operators, TEXT vs VALUE functions, NOW/TODAY functions, CONTAINS/ISBLANK functions, and the CONCATENATE function with examples for each. The agenda suggests explaining six different formula applications in 20 minutes to help readers quickly learn common formulas.

Implementing a Content Strategy Is Like Running 100 Miles: Painful But PossibleGavin Austin

Salesforce Case Study: Blaze a Trail with More Engaging ContentGavin Austin

Build a Bigger & Better Doc TeamGavin Austin

CNIT 140: Flashing FirmwareSam Bowne

More Related Content

What's hot (20)