Why I love Loom (with Confluence and Jira) as a Marketing Lead

[#1]

I was chatting with a colleague about the kind of teams and processes that really benefit from using Atlassian products, and he couldn’t really list any for Loom.

Hold my beer 🍺

Why I love using Loom

I work from Toulouse, France, but my colleagues are in multiple cities in Europe and the US. Some of my colleagues only work 80% full time, so either have a shorter work day or don’t work one day a week. When I want to share or explain something, finding the a time where everyone is available is hard…. and usually kind of overkill. I don’t really need to call a meeting to share the statistics from a campaign, the new process for updating certain kinds of content on the website, or to remind everyone where to find a template they need to use.

But I probably use Loom even more often when my chat message to someone starts getting to the 4 sentence mark. Then I know I have a bit to say, and instead of sending them a novella by chat, I record a quick Loom. Instead of telling them through text, I actually show them my screen, and colleagues aren’t left wondering how I’m feeling about something because my tone of voice and face are right there in the Loom.

Here are a couple more ways I love using Loom

Adding a Loom to a Jira work item for a designer

When I need one of our designers to create something, maybe an image for a newsletter, the website, or for one of our product pages, I often have an idea in my mind of the sort of thing I want. But instead of typing 3000 caracters in the Jira description and adding screenshots to explain what I mean, I just record a Loom. I can show multiple different tabs or files and comment each one, so it’s actually clear for the designer what I like about each example, and what the most important elements are for the design.

Adding a Loom to an onboarding page

A few months ago, a new content marketing manager joined my team right before I was leaving for Team. I was going to be away at Team for a week, then off a few days with family during her critical first 3 weeks! So I recorded a bunch of Looms, one by topic or theme, showing her how to navigate around our Confluence space, Jira projects, and other resources, as well as explaining processes and expectations. I added them all to her onboarding plan page (in Confluence of course), and she could watch them as many times as needed while I was gone to understand where to find content or how to create a Jira work item.

Making marketing playbooks easier to follow

I’ve been working with my team on building marketing playbooks so it’s easy for everyone to learn our internal processes, for example how to filter for contacts in HubSpot with our particular data structure. And while written instructions are good, and some screenshots too, adding a Loom makes it that much easier for someone to see how you do something.

Presenting on my behalf at a team sync

A few weeks ago I was up in Paris for the Atlassian Team on Tour… but it was the same day as my team sync. I had a couple topics I wanted to remind the team about, so I just recorded a Loom and added it to the meeting agenda page. Since we have a round robin system for hosting the meeting, whoever was hosting just had to play the Loom for everyone, and it’s like I was there! Obviously it’s not exactly the same, but it allowed me to share information during an occasion when my colleagues were already gathered instead of trying to schedule an additional meeting another day.

Hope that inspires you to try out Loom more often.

It's really become my go-to solution working on a distributed team when I need to share something more than 1 or 2 sentences.

[Brittany Soinski]

Fantastic write up, Laura! 👏

[Kristie Riojas]

LOVE this! 

[Thorsten Letschert _Decadis AG_]

@Laura Campbell Great summary. The designer part reminds me of an article on my 'To Write ' list. For us, it was almost the other way around: nearly a year before Atlassian's acquisition, an agency used Loom to comment on their designs - since it was a website relaunch, there was a lot of context for each draft. The added value of the Loom became immediately apparent. We were all the more surprised when the Atlassian announcement came shortly afterwards. I've been a big fan since the first encounter, and I find new use cases every week.