Google has dozens of help centers both for external and internal products. Our Technical Writers work hard to keep up with new features, constantly adding new articles, reviewing user feedback and usage metrics to improve existing content. They work closely with Product Managers, Engineers, Marketing and other parts of the company to make sure their content is accurate and in line with the messages Google wants to convey.

The Google Analytics 360 Suite publishes 8 Help Centers, including Analytics, Tag Manager, Optimize, Attribution and others. With so much knowledge being shared, we thought it would be interesting to our users to understand how we produce this content and where our ideas come from. So we decided to talk to one of our Technical Writers, Rick Elliott, who is responsible for content published in the Data Studio Help Center.
Basically, all help content comes from asking the question: what does the user need? We hope the product is intuitive and easy to use so that extra help is not required, but there are always concepts or flows that require more explanation. So that’s the start of a new Help Center article. Depending on the situation, a new article usually stems from 1 of 3 sources:
  1. We launch a new feature and it requires documentation.
  2. We get questions from users on the help forum that can be answered by a new article.
  3. A writer gets a bee in their bonnet and decides we need to document something more fully.
    After that, it’s a process of interviewing the subject matter experts and trying it through lots of sample reports to make sure the flows are right. Once the first draft is done, it is sent out for review and comments, but there may be another round of review and feedback before it gets published. Another big step in the help center content flow is localization: we usually get the translated content out a week or two after publishing the English version. 

    Watch the video to learn more about how Rick developed massive Help sections such as the  chart references and the “warm welcome report”.

    Posted by Daniel Waisberg and Rick Elliott

    p.p1 {margin: 0.0px 0.0px 13.3px 0.0px; line-height: 47.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000} p.p2 {margin: 0.0px 0.0px 13.3px 0.0px; line-height: 20.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000} p.p3 {margin: 0.0px 0.0px 13.3px 0.0px; line-height: 20.0px; font: 12.0px Arial; color: #1155cc; -webkit-text-stroke: #1155cc} p.p4 {margin: 0.0px 0.0px 13.3px 0.0px; line-height: 17.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000} p.p6 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 14.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000; min-height: 14.0px} li.li2 {margin: 0.0px 0.0px 13.3px 0.0px; line-height: 20.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000} li.li5 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 20.0px; font: 12.0px Arial; color: #000000; -webkit-text-stroke: #000000} span.s1 {font-kerning: none} span.s2 {text-decoration: underline ; font-kerning: none; color: #1155cc; -webkit-text-stroke: 0px #1155cc} span.s3 {font-kerning: none; color: #000000; -webkit-text-stroke: 0px #000000} ol.ol1 {list-style-type: decimal}