I co-created and co-hosted the Atlassian Ecosystem Podcast at Adaptavist with Ryan Spilken from 2017 to 2022. Ryan and I had worked together at Missouri State University before we both joined Adaptavist, and that existing partnership gave the show a natural dynamic from day one. Over five years and 140 episodes, the show turned dense technical documentation and product announcements into accessible conversations that built a real community of Atlassian professionals. It started as an experiment to fill a knowledge gap and grew into the largest subscriber base of any Atlassian-related podcast, with a devoted following of administrators, consultants, and Atlassian enthusiasts.
The Knowledge Gap in the Atlassian Ecosystem That Started the Podcast
In 2017, keeping up with Atlassian's ecosystem was a full-time job. Product updates shipped constantly. New Marketplace apps launched weekly. Cloud migration was becoming a strategic priority. Jira, Confluence, Bitbucket, Trello, and a growing list of other products each had their own release cadences, documentation sites, and community forums.
The problem wasn't a lack of information. It was the opposite. There was too much information scattered across too many sources, written in too many styles, and aimed at too many different audiences. An administrator trying to understand what a new Jira release meant for their instance had to piece together blog posts, release notes, community threads, and documentation updates. It was fragmented and time-consuming.
I saw an opportunity to aggregate, translate, and contextualize that information in a format people could consume during their commute, their lunch break, or their workout. Podcasts were growing rapidly as a medium, and the Atlassian ecosystem didn't have one that covered the full breadth of tools, practices, and community developments.
The pitch was straightforward: a regular podcast that covers everything happening in the Atlassian world, explained in plain language by people who actually use the tools. Adaptavist supported the idea, and we launched.
Converting Technical Documentation into Engaging Podcast Conversations
Technical documentation exists to be accurate and complete. Podcast conversations need to be engaging and digestible. These are different goals, and bridging them requires deliberate translation work.
Every episode started with research. I'd review the latest release notes, blog posts, community discussions, partner announcements, and even SEC filings – anything related to Atlassian. Then I'd identify the stories that actually mattered to practitioners – the updates that would change how someone administers Jira, the new features that solved real problems, the ecosystem shifts that administrators and consultants needed to know about.
The translation process involved three steps. First, identify the what – what actually changed or happened. Second, explain the why – why does this matter to someone managing Atlassian tools. Third, discuss the so what – what should listeners do about it, if anything.
This structure kept episodes grounded and practical. We weren't just reading release notes into a microphone. We were interpreting them through the lens of working professionals who needed to know whether a particular change affected their instance, their workflow, or their roadmap.
I also learned to be comfortable saying "I don't know" and "this is my interpretation, and I could be wrong." Technical podcasting tempts you toward false authority – presenting every opinion as fact because you're the one with the microphone. Honesty about uncertainty actually built more trust with the audience than pretending to have all the answers.
Year One: Exploring Novel Uses of Atlassian Tools
In the first year, the podcast had a specific editorial angle: we interviewed people who were using Atlassian tools for things other than software development. The conventional wisdom was that Jira was a developer tool and Confluence was for engineering documentation, but we knew teams across industries were adapting these tools in creative ways – project management for marketing teams, service desks for facilities management, Confluence as a knowledge base for HR onboarding. We wanted to surface those novel use cases and show the breadth of what was possible.
We'd bring on guests – Atlassian employees, Marketplace app developers, Solution Partners, community leaders – and have conversations about how they were pushing the tools beyond their expected boundaries. A conversation with someone running their entire non-profit operations through Jira told a different story than the typical sprint planning discussion. A university team using Confluence to manage accreditation documentation showed listeners possibilities they hadn't considered.
Interviews work well for exploring topics in depth. A conversation with an Atlassian product manager about an upcoming feature gives listeners insight they can't get from a blog post. A discussion with a Solutions Partner about a complex migration project tells a story with real stakes and real lessons.
But interviews also have limitations. Scheduling is a constant challenge. Guest quality varies – some people are natural communicators and others give one-word answers to open-ended questions. And listeners who tune in for every episode sometimes want consistency rather than a new voice each week.
The interview format was essential for establishing the podcast's credibility and network. Those early guest episodes connected us with voices across the ecosystem and demonstrated that the show was a serious platform for the community, not just two people speculating about release notes.
Format Evolution: From Interviews to News and Updates Show
After the first year, the format evolved significantly. Ryan and I shifted toward a comprehensive news-and-updates format where we reviewed everything Atlassian-related – all release notes, product updates, blog posts, SEC filings, partner announcements, and anything else we could find – then distilled that into a summary for Atlassian administrators. Every other week, we gave listeners a complete picture of what had changed in the ecosystem and what it meant for their work. We did take breaks for holidays, which is part of why we recorded 140 episodes rather than more over five years.
This change came from listening to audience feedback and watching download patterns. Our regular news episodes consistently performed well. Listeners liked having a reliable biweekly summary they could count on. They treated the show as their primary way to stay current with the Atlassian ecosystem – easier than scanning multiple blogs, forums, and even SEC filings themselves.
Ryan brought a complementary perspective. Where I leaned toward administration and product development, he brought a user-experience and accessibility lens. Our conversations were genuine rather than scripted, which listeners told us they appreciated. We disagreed on air sometimes. We got excited about different features. That dynamic made the show feel like eavesdropping on a conversation between knowledgeable colleagues rather than listening to a corporate content broadcast.
The format evolution also made production more sustainable. Interview-based shows require booking guests, pre-interviewing, coordinating schedules, and dealing with last-minute cancellations. A two-host discussion format requires research and an outline. We could produce episodes more reliably and maintain a consistent schedule, which matters for audience retention in podcasting.
Building Community Credibility in the Atlassian Partner Ecosystem
The podcast didn't just distribute information – it built relationships. Over five years, the show became a known entity in the Atlassian ecosystem. People recognized the podcast at Atlassian Summit events. Partners and Atlassian employees reached out to share news or suggest topics. Marketplace app vendors wanted to come on the show to discuss their products.
This credibility had tangible benefits for Adaptavist. The podcast positioned the company as a thought leader in the ecosystem – not through marketing language but through consistent, useful content that practitioners valued. When someone needed an Atlassian partner, the company producing the podcast they trusted every week had a head start on the relationship.
Community building through a podcast is different from community building through other content formats. Blog posts are one-way. Social media is fragmented. A podcast creates a parasocial relationship where listeners feel like they know the hosts. This creates loyalty that's hard to replicate with written content.
We received emails from listeners who said the podcast was part of their weekly routine. Some listened with their teams. Others used episodes as informal training resources for new hires. One listener told us they'd listened to every episode and attributed their career growth in the Atlassian ecosystem partly to staying current through the show. That kind of feedback doesn't show up in download metrics but it's the real measure of a content property's value.
Making Complex Atlassian Technical Information Accessible
Accessibility isn't just about accommodating different abilities – it's about meeting people where they are. An Atlassian administrator with five years of experience and a new hire who just got assigned to manage their team's Jira project have very different baseline knowledge. A podcast that only serves one group alienates the other.
I developed an approach I'd describe as "explain it simply, then go deeper." We'd introduce a topic at a level anyone could follow, then progressively add detail and nuance. This let less experienced listeners understand the basics and more experienced listeners get value from the deeper discussion.
Analogies were crucial. Explaining Jira's permission scheme hierarchy by comparing it to building security – lobby access versus floor access versus office access – makes an abstract concept concrete. Describing Confluence's space permissions like a library system where different people can shelve, read, or reorganize books gives people a mental model they can extend.
We also made a point of defining terms that seemed obvious. The Atlassian ecosystem has its own vocabulary – "instance," "scheme," "workflow transition," "add-on" versus "app" – and not every listener knows every term. A quick "for those who haven't encountered this before, a scheme in Jira is..." took five seconds and kept newer listeners from feeling excluded.
Five Years of Lessons from Hosting a Technical Podcast
Running a podcast for five years produces a lot of lessons. Here are the ones that I apply to every content project now.
Consistency beats virality. We never had a viral episode. What we had was a show that came out on a reliable schedule, every other week, for five years. That consistency built an audience more effectively than any single breakout episode could have. People subscribed because they trusted us to show up.
The audience knows more than you think. Early on, I was careful to simplify everything. Over time, I realized our listeners were sophisticated. They wanted nuance, not just summaries. The show got better when I trusted the audience to handle complexity and focused on providing context rather than dumbing things down.
Preparation is the difference between good episodes and filler. The episodes where I'd done deep research on the topics were always better than the ones where we winged it. Podcasting feels casual, but good casual conversation requires knowing the material well enough to discuss it naturally. Underprepared episodes sound like exactly what they are.
A co-host relationship is a partnership that needs investment. Ryan and I developed a dynamic that listeners connected with because we invested in that relationship. We debriefed after episodes. We gave each other honest feedback. We discussed who would take the lead on which topics. The on-air chemistry was real, but it didn't happen by accident.
Podcasts are a long game. Downloads grow slowly for most shows. The first six months felt like talking into a void. The audience built over years, not weeks. If you're starting a technical podcast expecting immediate returns, you'll quit before it pays off. The value compounds over time as the back catalog grows and word of mouth accumulates.
The Role of Podcasting in Technical Product Marketing
The Atlassian Ecosystem Podcast taught me that podcasting occupies a unique position in technical product marketing. It's not advertising – listeners would have tuned out immediately if we'd pitched Adaptavist's services every episode. It's not documentation – the format isn't suited for step-by-step instructions. It's not training – you can't follow along with a hands-on exercise while driving.
What it is: a relationship-building medium that establishes trust through consistent, honest, useful commentary. That trust translates to business outcomes, but only if you don't try to force the translation. The moment a content property starts optimizing for lead generation over audience value, the audience notices and leaves.
The best technical podcasts treat their audience as peers, not prospects. That's what we tried to do, and the community response over five years suggests it worked.
FAQ
What was the Atlassian Ecosystem Podcast about?
The Atlassian Ecosystem Podcast covered news, updates, and developments across the entire Atlassian product ecosystem – including Jira, Confluence, Bitbucket, Trello, and Marketplace apps. Co-hosted with Ryan Spilken at Adaptavist from 2017 to 2022, the show translated technical documentation, release notes, SEC filings, and product announcements into accessible biweekly conversations for administrators, consultants, and Atlassian users of all experience levels. Over 140 episodes, it grew to have the largest subscriber base of any Atlassian-related podcast.
How did the Atlassian Ecosystem Podcast build its community audience?
The podcast grew to have the largest subscriber base of any Atlassian-related podcast, built through consistent episodes over five years rather than any single viral moment. The show established credibility by providing genuinely useful information, being honest about uncertainty, and treating listeners as knowledgeable peers. Guest interviews with Atlassian employees and ecosystem leaders connected the show to the broader community, and word of mouth within the Atlassian partner network drove organic growth.
What format worked best for a technical podcast about Atlassian products?
The show started by interviewing people using Atlassian tools for novel, non-software-development purposes, then evolved into a two-host news and discussion format with co-host Ryan Spilken. After the first year, Ryan and I shifted to reviewing all release notes, blog posts, SEC filings, and ecosystem developments, then summarizing everything biweekly for Atlassian administrators. The regular discussion format performed more consistently with listeners who valued a reliable summary of ecosystem developments. The two-host dynamic – built on a partnership that started when we worked together at Missouri State University – provided complementary perspectives and felt like a natural conversation rather than a scripted broadcast.
Related Case Studies
- Building Atlassian's Global Certification Program – The certification program that established Adaptavist's credibility in the Atlassian education space.
- Creating Atlassian University's JIRA Training Videos – Earlier work developing Atlassian training content in a different format.
- Learn for Jira: Building In-App Training from Concept to Sunset – A product approach to the same Atlassian knowledge accessibility challenge the podcast addressed through content.