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 Thanks so much for this thoughtful reply!
I love how you framed it: not just thinking in terms of personas, but considering where they are in their journey. That really resonates.
It makes total sense to tailor assets by both persona and stage — I imagine it helps avoid generic messaging and drives relevance. I’m especially curious how you map personas across the journey — do you use any specific framework or tools to help with that?
Also, I totally agree on broader content for brand awareness, but once you're aiming for deeper engagement, personalization feels like the way to go. Thanks again for sharing your approach!