Scannable Clarity from the First Use
A Concise Guide that Makes Setup Effortless
ROLE
UX Writer / Content Designer
TEAM
Solo — cross-functional collaboration
TIMELINE
Prior to product packaging release
FORMAT
In-box guide + digital companion
DEFINING THE PROBLEM
Users had no idea what their headset could do or how to do it.
The Voyager Free 20 shipped with documentation written for engineers, not end users. Controls were listed in technical tables without context for when or why to use them. Core functions — call answering, volume adjustment, mute, pairing — were buried in dense paragraphs alongside advanced specifications users didn't need in their first ten minutes.
The result was a surge in support contacts asking questions the guide should have answered: "How do I answer a call?" "How do I turn it up?" "What does the button on the side do?" The information existed — users just couldn't find it, scan it, or act on it.
HIGH- LEVEL TIMELINE
Completed prior to the next packaging run so the revised guide could ship in-box with new units and be published digitally for existing users.
MAIN GOAL
Distill device controls and core functionalities into a scannable guide that users get up and running plus feel confident doing so within minutes of opening the box.
THE BIGGER PICTURE
Hypothesis
If users are given a single, scannable reference for the controls and functions they'll actually use — organized around what they want to do, not how the device is built — they will reach confidence faster, contact support less, and feel more satisfied with the product from day one.
Retention
Reduce support ticket volume driven by basic "how do I..." questions that a well-designed guide should preemptively answer.
Logic
Prove that content design — not just product design — drives first-use confidence and long-term feature adoption.
Key goal
Give every user a reference they'll actually reach for, not a manual they'll close after the first paragraph and never open again.
Why it matters: A quick start guide isn't a formality — it's the product's first conversation with the user. When that conversation is confusing, dense, or clearly written for someone else, it erodes confidence in the device before the user has even used it once.
For a wireless headset, the controls are the entire product experience. If users can't figure out how to answer a call or adjust volume without calling support, the product has failed at its most fundamental level — regardless of how good the hardware is.
UNDERSTANDING THE MARKET & USERS
Who we're designing for
The Voyager Free 20 serves users across a wide spectrum of technical familiarity — from IT professionals deploying headsets at scale to first-time wireless headset users setting up their own device. The guide needed to be immediately useful to a non-technical user without feeling condescending to an experienced one.
First-time headset users
Hybrid office teams
IT-managed deployments
Remote workers
CONSTRAINT
The existing documentation mixed essential first-use information with advanced technical specifications on the same page, in the same visual weight. Users had no way to distinguish "I need this now" from "I can find this later" — so many gave up before reaching what they actually needed.
FRUSTRATIONS
Control descriptions used technical naming conventions that didn't map to physical buttons users could find by touch. "Multi-function button (MFB)" told users nothing about where it was, what it felt like, or what a single press versus a double press did in any real-world scenario.
BRAINSTORMING
Breaking down the process
The guide redesign started with a simple question: what does a user need to do in their first 15 minutes with this device? Everything that answered that question stayed. Everything that didn't — moved to a secondary reference section or removed entirely from the quick start format.
1
Audit the existing guide for information hierarchy
Reviewed the full existing documentation and mapped every piece of content to one of three buckets: essential first-use, useful-but-secondary, and technical-only. The audit revealed that over 60% of the in-box guide content fell into the latter two categories — leaving the critical 40% buried.
2
Identify the 6 most common support questions
Worked with the support team to pull the most frequently asked questions tied to first-use. These became the guide's organizing structure — if users were asking it, the guide wasn't answering it clearly enough. Each question became a named section.
3
Rewrite controls using action-first language
Every control description was rewritten from the physical button outward — starting with what the user wants to accomplish, then identifying which button or gesture achieves it, then explaining any nuance (single tap vs. hold). Replaced internal technical naming with plain descriptions tied to physical location.
4
Design for scanning, not reading
Restructured the layout so users could find any answer with a glance — clear section headers, short lines, visual separation between controls, and a consistent pattern throughout. Added a "most used controls" summary at the top for users who needed just the essentials.
MINI STYLE GUIDE
Content principles applied
Task-first, not feature-first
Organize around what users want to do — "Answer a call," "Adjust volume," "Mute yourself" — not around how the device is engineered. Users come to the guide with a goal, not a curiosity about specifications.
Physical language for physical controls
Describe buttons by where they are and what they feel like before naming them. "The oval button on the left earbud" is more useful than "MFB" to a user who has never held the device before.
Scannable over comprehensive
A guide users can scan in 30 seconds is worth ten times more than a complete manual they'll never read. Every design choice — typography, whitespace, section length — prioritizes findability over coverage.
One action per line
Each control entry states one gesture and one outcome. If a button does three things, it gets three lines — not one run-on sentence. Parallel structure makes the guide faster to read and easier to remember.
BREAKING DOWN THE PROCESS
The content transformation
Below are representative examples of how the guide content was rewritten — stripping dense, technical documentation down to clear, action-oriented reference content users could actually use in the moment.
BEFORE - CONTROLS SECTION
Multi-Function Button (MFB) Operations
The MFB provides access to various call and media controls. Single press: answer/end call or play/pause media. Double press: redial last number (phone-dependent). Triple press: access voice assistant (device-dependent). Press and hold (2s): reject incoming call.
Note: Functionality may vary depending on connected device and operating system.
BEFORE - GETTING STARTED SECTION
Initial Configuration and Pairing Procedure
Prior to first use, ensure the device is fully charged using the included charging cradle. Navigate to the Bluetooth settings on your source device and initiate device discovery. Select "PLT_VFree20" from the available devices list to complete pairing.
AFTER - CONTROLS SECTION
Call button (oval button, left earbud)
Tap once → Answer or end a call
Tap twice → Redial last number
Hold 2 sec → Reject incoming call
Tap once → Play or pause music
AFTER - GETTING STARTED SECTION
Get set up in 3 steps
1. Charge for 30 minutes before first use.
2. Open Bluetooth on your phone or laptop.
3. Select PLT_VFree20 from the list.
You're connected when you hear a chime.
BEFORE
AFTER
KEY MOMENTS
Where the content work had the most impact
A quick start guide lives or dies in three specific moments: when the user first opens it, when they have a question mid-use, and when they encounter something unexpected. Each moment required its own content strategy.
First glance — do I need to read all of this?
The visual hierarchy of the revised guide answered this immediately: a "most used controls" summary at the top, organized sections below. Users knew within seconds they could find what they needed without reading everything — which made them far more likely to keep the guide nearby.
01
Mid-call — how do I mute?
The most time-pressured use of any reference material is when a user needs an answer while they're already on a call. Section headers written as tasks ("Mute yourself") and one-line control descriptions meant users could find what they needed in under five seconds without having to read the sentence around it.
02
Something unexpected happened — what does that sound mean?
Audio cues are the device's way of communicating status but only if users know what they mean. Adding a plain-language "What you'll hear" reference section (connection chime, battery warning, mute tone) turned a common confusion point into a moment of confidence.
03
CONCLUSION
Deliverables & Outcomes
Support
Fewer basic "how do I..." support questions as the guide proactively answered the most common first-use queries
Confidence
Users reached device confidence faster — knowing controls, audio cues, and setup steps without needing external help
Adoption
Increased awareness and use of core device features that users previously didn't know existed or know how to access
SUMMARY
Fewer questions. More confidence.
-
Redesigned the Voyager Free 20 quick start guide from the ground up — restructuring information hierarchy.
-
Rewriting all control descriptions in action-first language, and designing the layout for scanning rather than reading.
-
Delivered a final print-ready guide and a companion digital version, along with a content framework for applying the same principles across the broader Poly device documentation suite.
-
The guide became a reference template for future quick start guide production.
Future Outlook
The content framework developed here — task-first organization, physical-language control descriptions, and plain-language audio cue references is device-agnostic and ready to scale.
Open-box experience
Applied consistently across the Poly product line, it would establish a unified documentation voice that users recognize and trust from the moment they open any box in the portfolio.
THANK YOU!
NIKITA KING
