How do you tailor messaging for technical vs. non-technical Atlassian audiences?

Elena_Elevatic

Hi Marketing Folks!

I’m curious to learn how you approach messaging when targeting different audiences within the Atlassian ecosystem.

Whether it’s Jira, Confluence, Trello, or other tools, our content often needs to speak to both technical users (such as developers and administrators) and non-technical roles (like project managers, team leads, or executives).

How do you handle that balance in your campaigns? Do you create separate assets for each persona? Or do you keep the content unified and segment your distribution instead?

Are there specific messaging tactics or formats that have worked particularly well (or not at all)?

I’d love to hear your strategies, tips, or lessons learned.

Thanks in advance for sharing!

Elena

Salome ivaniadze

Hi ✨

In my experience, it’s not just about the persona, but about the persona's journey itself.

I always prefer to create individual assets tailored for each stage of the buyer journey and then map out which persona sits where within that journey. That way, the messaging is not only persona-relevant but also context-aware.

As for broader, more general content — I find it works well for brand awareness and top-of-funnel engagement. But when it comes to conversion or retention, segmentation and customisation win every time.