Internal Request Form for Guides

Comments

2 comments

  • Avatar
    Angus Yang

    Hey Joanna Caballero

    Here's an example of what we require internally (through a slack workflow), but of course feel free to adjust to your needs!

    Guide approval request:

    1. Name of Guide - Analytics Walkthrough
    2. Link to Guide - URL
    3. Which Sub or App (Optional)?
    4. What is the purpose of this guide? Guide new users through creating a report in the analytics section.
    5. Desired audience (target segment)? Active Customers
    6. Specific Page or Sitewide? 
    7. Related Product Area - This will determine who needs to review your Guide
    8. Desired publish date? ASAP
    9. Desired publish time? ASAP
    10. Desired expiration? No expiration

    Best,

    1
    Comment actions Permalink
  • Avatar
    Greg Nutt

    The list Angus provided is a great starting point and, as he mentioned, what we use internally.  One addition I like to emphasize when defining this process with my clients, however, is to define the desired outcome for a guide.  What needle are you looking for a guide to move?  Adoption, sentiment, or even just visibility are all common examples of these.  But, with this outcome in mind, you can work with your teams to define KPIs or Goals to track against to ensure the guide is having the desired impact and isn't just 'another distraction' to your end users.

    0
    Comment actions Permalink

Please sign in to leave a comment.