Atlassian Everything Podcast

Alex Ortiz (Dr. Jira) is BACK! In this exclusive sit-down, we go beyond the official documentation to uncover what’s really happening inside the Atlassian ecosystem. From the "wild west" of Jira configurations to the aggressive corporate chess moves being played by competitors like Asana, Alex and Josh pull back the curtain on the world’s most powerful productivity suite.🔥 This episode is brought to you by GitProtect - our go-to backup solution, trusted and recommended to every customer who takes their security seriously 🔗 https://links.gryd.io/hORtOkG Inside This Episode:• The Jira Paradox: Why the "best and worst thing" about Jira is that there’s no right way to use it—and how that leads to chaos in most companies.• The License Wars: A look at Asana’s $250k "unlimited" strategy to steal Atlassian’s lunch and why Jira desperately needs a "Stakeholder License."• Enterprise vs. Innovation: Is Atlassian moving too fast for its own good? We discuss why moving a single "Status Button" can cause a meltdown in a 100,000-person company.• The Origin Story: For the first time publicly, Alex shares the "exclusive" story of how he actually became Dr. Jira (it involves an HVAC company and a lot of eggs).•The Future of Work: Has Atlassian peaked? We analyze the next 5 years of AI, the data center void, and the startups waiting to take the crown.Takeaways• The beauty of Jira lies in its flexibility.• Every team has a unique way of using Jira.• There is no one-size-fits-all approach to project management tools.• Using Jira effectively is about finding what works for your team.• The cooking analogy highlights the importance of adaptability.• Success with Jira depends on the team's specific needs.• Different teams can achieve success with different methods.• Flexibility in tools can lead to innovative solutions.• Understanding your team's workflow is crucial for effective tool usage.• Coaching teams on tool usage requires understanding their unique dynamics.Chapters: 00:00 – The "No Right Way" Problem: Why zero overlap between teams is dangerous.10:44 – EXCLUSIVE: How I became "Dr. Jira."24:54 – ABS vs. Team '24: Why tactical, community-led events are winning.40:36 – The Enterprise Pivot: Is Atlassian leaving small teams behind?54:54 – The Stakeholder Problem: Why VPs hate logging into Jira.01:03:25 – Big announcements for the next major event.

In this episode, we sit down with Michael Kuhl — former Manager of Growth Analytics at Appfire, one of the biggest players in the Atlassian ecosystem — to unpack what’s really happening in the Marketplace right now.🔥 This episode is brought to you by GitProtect - our go-to backup solution, trusted and recommended to every customer who takes their security seriously 🔗 https://bit.ly/4pHDXyg If you build Atlassian apps, work as a Solution Partner, or run services around Jira/Confluence, this conversation is a massive wake-up call.We break down:🔥 Why the “old app era” is collapsing🔥 Why tiny feature apps are dying and won’t survive🔥 How Atlassian’s enterprise shift is reshaping the ecosystem🔥 The truth behind Marketplace distribution and why it no longer works🔥 Why Atlassian is absorbing top app ideas into the core product🔥 The new winning strategy: Solutions + services + defensible IP🔥 How AI will turn Jira into a backend and change how devs work🔥 What the F1 sponsorship really signals about Atlassian’s direction🔥 Why solution partners MUST own their own IP in the futureMichael also shares insights from Salesforce, Facebook, Amazon, OpenAI, and the broader “distribution channel evolution” that every platform goes through — and why the Atlassian ecosystem is no exception.Whether you’re building apps, running consulting, or just curious about the future of Atlassian…This episode will change the way you see the Marketplace.

Why do so many teams keep switching tools — and still fail?Jira. ClickUp. Notion. Monday. New platform, same chaos.In this episode, Gray MacKenzie (ClickUp expert, ZenPilot) and Josh Golosinkiy (Jira expert, GRYD.IO) break down the uncomfortable truth:💥 It’s not about tools.💥 It’s not about features.💥 It’s about habits, process, and discipline.We go deep on:• Why teams switch from Jira to ClickUp (and back again)• The hidden cost of tool fatigue• Why “flexibility” often creates chaos• How AI is exposing — not fixing — bad workflows• The difference between process maturity and tool addictionContrarian POV:“You don’t need a new tool. You need new habits.”If you’ve ever felt like your tech stack is growing but your output isn’t — this one will hit hard.

Jira was never designed for the average user. Chris Cooke saw that — and turned user pain into product gold. In this no-holds-barred episode, he breaks down how he bootstrapped Custom Charts into a $10M business, why most Atlassian apps still suck, and what happens when you zig while everyone else zags.No fluff. No corporate polish. Just raw lessons on UX, app strategy, and building for the 99% of users who’d rather burn the manual than read it.

Think JIRA is just a tool for techies and micro-managers? Think again. In this episode, we dive headfirst into all the myths, mistakes, and mindset shifts that make or break your team’s productivity, with special guest “Fun Man” Andy - yes, the real deal from Fun Inc.🔑 Takeaways:・ Reinventing the wheel in JIRA is a common issue.・ User experience can be negatively impacted by constant UI changes.・ The terminology used in tools like JIRA can affect user adoption.・ Non-technical teams can benefit from using JIRA with the right approach.・ Agile methodologies are essential for evaluating tool effectiveness.・ Making work fun involves aligning people, processes, and products.・ Regular retrospectives are crucial for continuous improvement.・ Content quality can be assessed by the creator's credibility and following.・ Metrics should inspire actionable change to be relevant.・ Integration of tools should focus on where teams naturally work.✨ Perfect for: JIRA admins, Atlassian power users, Enterprise managers, Agile teams, HR and Marketing leaders, and anyone ready to challenge the status quo.