Two Great Teams: Bridging the Gap Between Documentation and Customer Support
-
Upload
neal-kaplan -
Category
Technology
-
view
218 -
download
1
Transcript of Two Great Teams: Bridging the Gap Between Documentation and Customer Support
We can all show up and fill 8 hours.How do we decide what work is really meaningful?How do we prioritize our time?
4
This was an extreme example, but the reality is that if documentation and support are kept separated and rarely communicate then we aren’t providing good service to our customershttps://flic.kr/p/9a6U6Z
14
Ticket deflection?Often named as a goal for docs, but deflection isn’t the right idea…https://flic.kr/p/9xRXiJhttps://flic.kr/p/4gNn2b
17
We don’t want customers to shut up and go awayWe want their feedback!We need to make sure we address their questions where and when they want answershttps://flic.kr/p/8e4gZe
18
Answering your customers’ questions, letting them use your product effectively and get their jobs done makes for happy customersHappy customers renew; happy customers buy more; happy customers say nice things about your producthttps://flic.kr/p/dXEzZp
19
A few years ago, I went to a meetup at a very large company (not write the docs!)There were two presenters, one from customer support, another from the documentation team
21
Why? Why do this extra work? It’s wasting time, and wasting money. How does the customer know where to go to find answers?https://flic.kr/p/4vozZ
27
If you don’t know what your customers are asking about, how they use the product, then you’re creating what you THINK is good documentationMaybe your instincts are great, but after 20 years as a tech writer I’ve learned to NOT trust my instincts; get the data!
30
Customer Support uses your documentation to learn about the productWhy doesn’t the documentation answer the right questions?https://flic.kr/p/4bC5G8
32
Build a relationshipNot just their names, but what they focus on, their areas of expertiseWork with their manager to make knowledge capture a part of the support team’s goals
34
Support ticketing systems support categories; you might need to customize this and add Documentation, as a category or a separate tagHave anything assigned to Documentation (or tagged) automatically send you a notification (or even assign it to you)
36
What’s the level of expertise across customers?What vocabulary do they use? Does this match your terminology, or do you need to change to increase understanding?Remember that support speaks with customers every day
38
Look for the number of Documentation or Question tickets coming inAre there a lot? Is there a trend? New vs. Experienced customers?
39
Do they have a knowledge base? Mine it!Better yet, build ONE source of truth!https://www.flickr.com/photos/multnomahcountylibrary
40
Don’t underestimate them; they communicate with customers much more frequently than you do!Give them creditShow them their information is being used in the documentation, give them a sense of ownership
41
Don’t give them a huge style guide to followOvercome the fear of the blank pageHelps organize their thoughtsEnsures consistencyCustomers see familiar organization
42
Look for change: number and type of “documentation” and “question” ticketsAre the questions getting more complex, more frequent?
45
Your customers don’t care about your company structureSilos don’t help you or your customershttps://flic.kr/p/4vhAFD
46
Build a culture of information sharingYou want people feeding information to you, not having to play detective every dayhttps://flic.kr/p/a9tDjq
47
The more we do this, the better you can prioritize your tasks and deliver docs that really help your customersUse the input from support to set the documentation priorities and build a roadmap for the docsThis will change your prioritiesThis will make more work for youYou are a product owner; your product is documentation
https://flic.kr/p/debvm
48
This is the goal: better, more concise docs that meet customer needsThis is how we prioritize our tasks and make our work worthwhile. Because we don’t want to just move the needle…
49