Getting everyone on board with a new initiative or tool is hard—even in the best of times.
These days, many teams are now remote, and there are plenty of world distractions on top of normal business activities. But by knowing where to look and how to help your team, you can start realizing the value of tools like Litmus faster. Once you’ve learned the keys to using Litmus in your workflow, you might end up like VSP, who saves 100 hours per month building emails.
In our recent webinar, How To (Finally) Get Your Team Using Litmus, Justin Lieberthal, Solutions Engineer at Litmus, shared tips on how he’s coached hundreds of companies getting started on the platform. We’ve also asked Lyla Rozelle, our Customer Marketing Manager, and Jaina Mistry, the Litmus Email Marketing Manager, to share their personal insights into helping teams make the most out of their Litmus account.
Here’s what we learned.
Personalizing the Litmus experience for each role is the key to success
Yes, Litmus is an email marketing tool. But it goes beyond the technical aspects like Litmus Builder. Litmus offers a single point of collaboration that empowers teams to get feedback faster. However, the sticking point is that you need your team members to be in there to give you feedback.
Lyla Rozelle shared,“You have to create a process for everyone to follow that meets them where they work.”
When it comes to getting your team to use Litmus consistently, you can’t take a one-size-fits-all approach. Instead, Lyla recommends being specific in what you show each team member and tailor their experience to their role.
To get started, use these four tips to help different roles make the connection between their current workflow and Litmus.
Team leaders can take stock of skills to set up permissions
There’s a LOT you can do on Litmus. While this means you can improve most of your workflow with Litmus, it also means someone signing on for the first time has a ton to take in. It’s like walking into a restaurant with a ten-page menu—there’s something for everyone, but you might need help finding your way.
This is where user privileges and roles come in. When administrators or team leaders set up your team’s accounts under specific categories, such as code editors and account holders, they streamline what everyone has access to.
As a result, the options team members have when they log in are simplified to the tools they need to use. With a few clicks, you practically attach a flashing arrow sign to the only part of the workflow each person needs to pay attention to.
With these different user permissions and roles in mind, let’s explore tips that help specific team members.
Designers and developers should tailor their process depending on where source code lives
If we had to break the different workflows we see users employ, one of the most obvious divisions is around where the “source of truth” for email code is. The two paths to choose between are building inside of Litmus and building outside of Litmus.
These are some workflow tips depending on how your team works.
If your team builds inside Litmus:
- Sync each new email to your ESP as soon as you create it in Builder. Any changes made to a synced email in Litmus update in your ESP. Setting it up first means you don’t need to worry about it later.
- Build out your design library. The design library houses your team’s templates, partials, and snippets. Teaching your team to use these will save precious time.
If your team builds outside Litmus:
- Emphasize using test email addresses. Test email addresses are how you’ll send emails into your account for quality assurance testing, so using the right test email address will make everyone’s life easier.
- Use a Wiki to document email files and templates. If your team doesn’t use Litmus as your primary design library, you can still link to Litmus in your documentation. Jaina Mistry noted that, “We use Confluence as our main source of documentation of our templates, snippets, partials, and how they’re implemented. Adding links raises Litmus’ visibility in the team and shares how exactly we’re using it.”
Editors and reviewers need to understand (and use!) Litmus emails for testing
Email client apps update about every two days, so testing every email is essential to make sure expectations match reality with every message you send. For most teams, sending a test email to yourself, your team, or your shareholders is a given in their workflow. Team members who provide the final check and seal of approval on an email can quickly get overwhelmed with scattered versions and comments.
With Litmus, each account has designated Litmus email addresses to send test emails to. Instead of creating a new email in Litmus, your team can send an email draft to the Litmus test address to add the email to your account.
There are a few test address types your team needs to know:
- Personal test email addresses. Each user has an email address, which is useful for tracking who created and sent which emails.
- Project-specific test email addresses. Projects and folders keep everything in your Litmus account organized, and each has a designated Litmus email address. Sending emails to these addresses automatically sorts drafts into the correct spot.
- Checklist and Proof test email addresses. If you’re testing and editing a single email, send a test with the address for that message within Checklist or Proof. That way, the new version will overwrite the previous version instead of having multiple copies of the same email floating around.
Litmus test email addresses help your team get emails into Litmus and maintain organization for projects in process. Ensuring everyone understands how useful they are, and when to use each, allows the workflow to run smoothly.
Everyone benefits from Litmus visibility in your project management software
Sometimes team interaction will be limited or sporadic. If that’s the case, there are a few methods and integrations to make Litmus easier to use alongside your favorite project management and communication tools.
The easiest way to incorporate Litmus into your team’s project management software is with links. We even have free Trello email workflow templates. Attaching Litmus links to a particular task makes it easy for everyone to get to the right spot in Litmus while providing context from the rest of the project. You can also choose to send portions of your Checklist with links highlighting particular issues.
If you go this route, make sure to adjust the sharing settings on your links. Jaina shared that “while most of the team does have access to our Litmus account, we make an effort always to generate public share links if we want to share Checklists/Builder files/Proofs. That way, no one’s left asking, ‘I can’t see that link. Did I get the right link sent to me?’”
Jaina also relies on the Litmus and Slack integration to know which Proofs need her urgent attention. “Because we generally live in Slack, it’s the best place for me to get visibility on projects currently at the Proofing stage,” she said.
Finding the perfect workflow is an art and a science, and don’t be too hard on yourself if it takes a little time for your team to hit its stride. Your quest (should you choose to accept it) is to help everyone understand which parts of Litmus they need to narrow everyone’s focus.
If you want to hear more about the tips covered today, check out the full webinar How To (Finally) Get Your Team Using Litmus. When you’re ready to implement what you’ve learned, log in to your account, or start a free trial.