Updated:
Published:
May 1, 2023
â˘
â˘
12 min
â
If you were today years old when you learned what the acronym âQSGâ stands for, youâre in good company. We live and breathe all things documentation, and that was a new one for us, too.
We may need to brush up on what the cool kids are calling them, but we love a quick start guide. If youâre in the business of teaching people how to use software and you arenât already familiar with QSGs, prepare to have hearts for eyes.
Since understanding how QSGs differ from other types of documentation can be confusing, letâs take a look at one of their closest cousins.
â
Just in case the distinctions arenât jumping out at you, hereâs a more detailed explanation. đ
You may hear people talk about user manuals, tooâbut those are d-e-t-a-i-l-e-d documents. They usually cover more advanced features that quick start guides and quick reference guides wonât.
Now that thatâs cleared up, weâll give you the full rundown on quick start guidesâincluding their biggest benefits, best-in-class examples, 9 tips to keep your end user front and center, and a checklist to help you whip up one of your own.
A quick start guide is a great example of documentation that punches well above its weight.
Itâs also a choose-your-own-adventure situation, with lots of different types to choose from. đ
Research shows:
Quick start guides go hand-in-hand with onboarding, and we could talk about the benefits of both all day. That saidâsince weâre talking about the beauty of brevity todayâweâll keep it short and sweet.
Here are nine advantages to including a quick start guide in your onboarding process:
If itâs all in one ear and out the other until you see a practical example, this section is for you. đ First, a quick overview on formatting options.
While every company (and creator) approaches quick start guides differently, there are a couple of formats youâll see all over the place. One may strike you as a no-brainer over all others, depending on your needs and available resources. Or you may decide to mix and match a few to create the best experience.
You can approach your QSG through:
To get your wheels spinning, here are five quick start guide examples.
For people with answers to FAQs:
Tango makes documentation easy, fast, and fun by automatically generating how-to guides with screenshots.
When the inevitable âHow do IâŚâ question comes your way, Tango makes it simple to share your expertise, avoid hours of tedious documentation, and help everyone around you get stuff doneâwith fewer impromptu requests to screen share. đ
For people looking for answers to get unstuck:
Teaching people how to use a how-to tool *with* a how-to may be slightly meta, but itâs undeniably effective.
After watching a quick demo and clicking the quick start guide link, new users learn how Tango works in-app, in the flow of their work, while viewing their first Tango. On-screen guidance makes it easy to know exactly what to do nextâwhile saving mental energy and minimizing mistakes. đş
â
Itâs hard to imagine a world without Slack. When you need to help a new employee streamline communication and collaboration, thereâs this treasure trove of information.
Slackâs online quick start guide delivers on its promise. With instructions to download the desktop app, view a short video, and zip through a quick tour, it couldnât be easier to set up your digital HQ.
Asana is a web-based project management software that allows teams to collaborate and manage their tasks and projects more efficiently. (If you havenât tried it yet, it is nothing short of â¨.)
They also take an online approach to their quick start guide, with a structure that accelerates the process of finding what youâre looking for. Their guide uses text, video, and animations, and includes a high-level overview of how their program is organized alongside key things you can do.
Salesforce is a cloud-based customer relationship management (CRM) software that helps businesses manage their sales, marketing, customer service, and other business functions in one place.
Since thereâs a lot to learn, Salesforce has many, segment-specific quick start guides. This one's for small businesses who want to use Salesforce, and covers the basics, how to track customers and close deals, how to manage contacts, tips to resolve customer issues, and a glossary. Thereâs also a chatbot for real-time support, and a call to action to try the product out for free.
Wistia is a video marketing platform that makes it easy to find, engage, and grow your audience with video.
You may not be surprised to learn that their demo video doubles as a quick start guide, with tips for hosting, marketing, analyzing, and creating video.
If the only thing you like better than a practical example is an actionable tip, we can do you one betterâwith a round-up of 9 best practices for creating user-centric quick start guides.
We like personas as much as the next person. But to create a 𤊠quick start guide, thereâs no substitute for talking to customers. Itâs a good idea to connect with both inactive users (to suss out areas for improvement) and successfully onboarded users (to see whatâs working).
Issuing a survey works well for gathering quantitative data. You can ask questions like:
You can also dig into:
To collect qualitative insights, you can take a 1:1 or 1:many approach. User research sessions can be particularly helpfulâespecially if you have people sign up to use your product and/or run through your quick start guide while theyâre on a video call with you. Seeing where people get stuck IRL can be hugely illuminatingâand open your eyes to missed expectations and opportunities.
Is there a discrepancy between how youâre messaging your product (perceived value) and the value your users actually receive in the product (experienced value)? If yes, thatâs a good signal your quick start guide isnât quite hitting the mark.
This one hits home, doesnât it? đŻ Creating a PDF probably wouldnât require support from a videographer or an animator. Hosting a webinar probably wouldnât require a web developer or too much time from your best graphic designer. But to truly take a customer-first approach to your onboarding documentation, you need to think about what would serve your user best.
Ultimately, you want your customers to find successâso understanding what success means to them and figuring out how your documentation helped (or hindered đ) is key.
The average human attention span is 8.25 seconds. We officially have a shorter attention span than goldfish. This means itâs critical to keep your âquickâ reference guide from being too comprehensiveâand difficult to digest.
If onboarding is a path towards value, you want that path to be as direct as possible, with no obstacles in the way. Your goal is to help your users reach the âaha!â momentâwhere they realize how useful your product isâASAP. Every piece of content in your quick start guide should accelerate the movement towards that moment. If it doesnât, cut it out âď¸.
â
The temptation to squeeze in ALL the cool things about your product is real. But to keep your quick start guide from morphing into a user manualâand to keep your end user top of mindâseparate whatâs necessary to know from what can be taught later on. Itâs a good thing if the latter is a long list! That just means you have plenty of ways to add consistent value over time (which will help with retention).
What percentage of non-technical people make up your audience? If itâs anything other than 0%, write as if your reader has no prior knowledge of or experience with your product.
â
Your engineering team likely puts lots of effort into shipping new solutions. And your product team likely puts lots of effort into naming them. It makes sense to want both teams to have their moment in the sun! But if you arenât careful, your quick start guide may start to sound like an announcement of something awesome that you builtâvs. an application that helps users understand how they can solve their problems. Focus on contextual application, or how your product can help to drive an outcome, rather than rattling off feature names.
As anyone who creates documentation knowsâmaintenance is ongoing. And also: not the most fun. That saidâŚyour quick start guide will only be as useful as it is accurate. This is especially true when writing technical documentation since product updates can easily make your QSG obsolete. Work with your product, engineering, marketing, sales, and customer success teams to create a plan to update your guide whenever there are big updates to your product roadmap.
When you pick a format for your quick start guide, think about the things that will help users feel the most supported through setup and beyond. Is that a chatbot on a website? A link out to a knowledge base from an infographic? Or a step-by-step tutorial with a literal âGuide Meâ button?
To deliver on our initial promise to youâhereâs a Notion checklist to help you create a quick start guide in no time.
TL;DR: Itâs hard to overstate the importance of the first interactions people have with your product, service, or software.
â
Potential users shouldnât have to guess or work hard to understand your product. They should be able to understand what it is and why they should use it in a glance. Thatâs where quick start guides come into playâand show that (sometimes) less really is more.
We'll never show up
empty-handed (how rude!).