How to make a quick start guide, with a little help from your friends at Tango.

<aside> 👌🏼 If following a checklist feels like the ideal level of hard, you’ve come to the right place.

Just duplicate this doc to get started. ****

</aside>

The groundwork

Before you start

<aside> 🔎 Who are you trying to help, and what are you trying to help them do?

</aside>

• [ ] Identify your target audience.
• [ ] Determine your objective(s).

<aside> ❓ Is a quick start guide your best bet?

A quick start guide (QSG) is a concise set of instructions to help users get started using a product, service, or software application. If your goals go above and beyond that definition, you may want to consider a different deliverable.

</aside>

• [ ] Validate the need for a QSG internally.
• [ ] Pinpoint your primary focus (product, tier, etc.).

<aside> 💬 Have you talked to users and/or customers?

What’s even more important than validating the need for a QSG internally?

• Confirming your community has a pressing need and/or desire for this kind of content.

• Understanding common pain points.

• Taking a data-driven approach to what you do (and don’t!) focus on. </aside>

• [ ] Create and circulate a survey for quantitative feedback re: what it’s like to get started with your product.

• [ ] Form a focus group for qualitative feedback re: preferred learning styles, sticking points within your product, popular use cases, favorite features, wish list items, and more.

• [ ] Set up 1:1 interviews with successful and unsuccessful users.

• [ ] Comb through support tickets to find common pain points during onboarding.

• [ ] Look at product data to uncover key actions that correlate to quicker satisfaction.

• [ ] Analyze Net Promoter Score (NPS) results to understand where you’re hitting a home run (and striking out).

• [ ] Confirm the perceived and experienced value for your product are one and the same.