Welcome to LaunchNotes
There’s a lot you can accomplish with LaunchNotes in little time, so here’s a quick compilation of the most important things we think you should know to get started.
💡 Want to speak with a LaunchNotes pro? Find some time here: Book a Meeting with an expert
1. Customize your hosted LaunchNotes page
Once you get access to your page, the best way is to get it feeling like a part of your brand as you'll be directing your end users to your page with every update. Whereas we have a whole host of customization options (which you can see here), a great place to start is adding your company logo and choosing your color theme to match your branding.
Setting for these can be found under the Project Settings tab on the Admin nav bar > Look & feel
Under the Project Settings tab, you can also change the basic information of your page (under the Basic info tab) to rename your page, add a custom subdomain, and give it a heading and subheading.
💡 Once your page is activated you can choose a custom domain of your choice. If you're interested, reach out to our Customer Success team at firstname.lastname@example.org.
To view what your page looks like after these changes, hit the View public page button at the bottom of the admin nav bar.
2. Add three categories
Categories are the routing system for your notifications. They add a level of segmentation to your updates that ensure your users are only subscribing to, and receiving updates about, the product changes relevant to them. Similarly, on the content creation side, categories help you and your team properly categorize and organize your various work and projects.
Categories can be added and edited under the Categories tab in the nav bar. If you can't think of any categories off the top of your head, here are three basic categories we see a lot of teams using: 'Bug Fixes', 'New Features', and 'UX/UI Updates'
For additional details on how to set up and use categories, please see our KB article on Categories.
On your LaunchNotes page, categories will appear in two places: under each release and along the right hand side nav bar. Users can filter the LaunchNotes page by category by selecting any particular category.
Adding three categories will give you an opportunity to see how easy it is for your users to select and filter your LaunchNotes page to only show information relevant to them. The categories shown in the screenshot above are the categories our team uses, but know that categories are completely customizable to your team structure, use case, release cadence, or however it will be most beneficial to you.
💡 When visiting your public page for the first time, try subscribing to your updates so you can see what the notifications looks like in your inbox, and see what the sign-up process is for your end users.
3. Invite team members
Invite a teammate to collaborate with you on your release. More often than not, release comms involve a few different stakeholders before any messaging reaches users. For example, you might need a designer to drop some illustrations into your release article, or review your overall launch messaging with a Customer Success Manager or Account Manager who are on the front lines with your customers.
You can invite a team member simply by going to the Project Users tab on the lefthand admin nav bar, then selecting + invite user. Here you'll be able to add new users via email, as well as set their permissions.
💡 For more information on user permissions, you check out this knowledge base article on User Roles & Permissions.
4. Create and Publish your first release
Releases represent any customer-facing product change - whether it be a new feature, a bug fix, or even a UX/UI enhancement. These should be created as soon as as you’ve committed to work on a project, and will provide a timeline so internal teams, as well as your end users, can track the project as it moves from planning, to in development, and then live.
Releases also store important supporting information and documentation (e.g., the project brief, Jira epic, support docs, messaging guide, sales collateral, etc.) via Release Links. This way all of the context and information any team member needs on a particular release is in one place and at your fingertips.
Release best practices
Make the name of the release as specific as possible - for example a time period, version number, or feature title
For high priority or tier 1 launches, ensure you create a Release Article to add additional context for your end users (which will drive higher engagement!)
Add teammates as collaborators [link to Users/Subscribers?] so they can stay up to date on where the release is and when it's going to ship
Add the LaunchNotes Slack integration to easily keep your team in the know, at the necessary fidelity, so they're never out of sync with your release timeline
❓ If you have any questions on the above or would like to schedule a walkthrough, as always please don't hesitate to get in touch with us at email@example.com