Released (released.so)

Should you share revenue numbers with everyone in your company? During Atlassian’s early days as a private company, every employee had access to revenue and user metrics. It wasn’t just part of our “Open company… 🐂” value—it made sure everyone knew how we were tracking. 📝 At Released (released.so) we’re just as open. Every month, the whole team gets a detailed update. 📈 MRR, MAU, churn, runway… everyone knows exactly where we are and where we’re headed. To keep ourselves accountable, we’ve put together a simple dashboard in Atlassian #Confluence. Confluence, in my experience, has the best table implementation of any collaboration tool (try using tables in a Google Doc 🤬). Making charts from table data is super easy. ❓Are you sharing your metrics openly? What benefits have you seen? #opencompany #startups #mrr

Impress your boss, excite your customers... create a good public roadmap that keeps them in the loop. 𝗗𝗲𝗳𝗶𝗻𝗲 𝗬𝗼𝘂𝗿 𝗔𝘂𝗱𝗶𝗲𝗻𝗰𝗲 Is your roadmap for customers, internal stakeholders, or the general public? Tailor the content and level of detail accordingly. Customers might need high-level milestones, while internal teams might appreciate more granularity. 𝗖𝗿𝗮𝗳𝘁 𝗮 𝗖𝗹𝗲𝗮𝗿 𝗦𝘁𝗼𝗿𝘆 Begin with a clear starting point, outline key milestones, and show the path to completion. Use fields like target date, product area or flags to highlight important deliverables. Make sure the progression is logical and easy to follow. 𝗔𝗿𝘁𝗶𝗰𝘂𝗹𝗮𝘁𝗲 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀 𝗮𝗻𝗱 𝗚𝗼𝗮𝗹𝘀 Good roadmaps clearly articulate priorities. They explain the "why" behind these priorities and shy away from the nitty-gritty details to focus on the big picture. They are not lists of tasks but representations of outcomes and goals. 𝗘𝗻𝘀𝘂𝗿𝗲 𝗥𝗲𝗴𝘂𝗹𝗮𝗿 𝗨𝗽𝗱𝗮𝘁𝗲𝘀 An outdated roadmap is worse than no roadmap. Set up regular updates so your roadmap always reflects the current state of the project. ------- Want to create the ultimate stakeholder / customer roadmap? Check our our guide here: https://lnkd.in/gWaJAp7K

Your ultimate guide on how to create a 𝗯𝗮𝗱 public roadmap! 𝗧𝗼𝗼 𝗠𝘂𝗰𝗵 𝗗𝗲𝘁𝗮𝗶𝗹 A roadmap cluttered with every Epic, Story and Task is overwhelming. Stick to major features and improvements. You can always provide more detail in a separate document or private roadmap. 𝗟𝗮𝗰𝗸 𝗼𝗳 𝗖𝗹𝗮𝗿𝗶𝘁𝘆 A roadmap that’s hard to understand doesn’t serve its purpose. Avoid jargon and ensure your titles and descriptions are clear. Your audience should get the gist at a glance. 𝗜𝗻𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁 𝗨𝗽𝗱𝗮𝘁𝗲𝘀 An inconsistent or outdated roadmap is worse than no roadmap at all. Stakeholders rely on the roadmap to make decisions, and an outdated roadmap provides misleading information. Regularly update your roadmap to reflect the current state of the project. 👉 Create a great public roadmap with our ultimate roadmap guide. 🔗 Link in the comments below.

Want to increase your customer engagement? Here is how 3 Atlassian Platinum Partners have done it. appanvil GmbH: Embedded their changelog directly in-app, ensuring users stay informed without workflow disruption. Smart move! Mumo Systems: Integrated Released (released.so) into their products, leading to a measurable uptick in user satisfaction and a decrease in support queries. Talk about efficiency! Ricksoft, Inc. : Seamlessly combined Released with Scroll Viewport, streamlining their release note process from Jira to documentation. Innovation at its finest. These companies realized that efficient communication and transparency is not just a nicety—it's a must for building customer trust and engagement, especially in the product-led growth space. What's your strategy for keeping customers engaged and informed? Let's discuss in the comments.

Released is now a bestselling app on the Atlassian marketplace 🎉

We've just launched a super neat feature: 𝙏𝙚𝙭𝙩 𝙝𝙞𝙜𝙝𝙡𝙞𝙜𝙝𝙩𝙞𝙣𝙜 Now, you can make your release notes pop by highlighting the key bits. No more missed important updates – everything you want to stand out will be front and center! Sure, but why? ✦ 𝘾𝙡𝙚𝙖𝙧 𝘾𝙤𝙢𝙢𝙪𝙣𝙞𝙘𝙖𝙩𝙞𝙤𝙣: Important details are now impossible to miss. ✦ 𝙁𝙚𝙖𝙩𝙪𝙧𝙚 𝙨𝙩𝙖𝙩𝙪𝙨 𝙞𝙣𝙙𝙞𝙘𝙖𝙩𝙤𝙧𝙨: Need to call out a beta feature, easy. ✦ 𝙀𝙙𝙞𝙩𝙞𝙤𝙣 𝙞𝙣𝙙𝙞𝙘𝙖𝙩𝙤𝙧𝙨: Communicate that a feature is only available in certain editions. Ready to take your release notes to the next level? Give text highlighting a try and see how it transforms your communication! 🚀 #NewFeature #CustomerEngagement #ReleaseNotes #SaaS #TechUpdates

Create your public Roadmap, straight from Jira. Sharing a roadmap is one of the best ways to keep your team, stakeholders, and customers aligned. It shows what’s coming, when it’s expected, and how everything fits together. But while creating a roadmap in Jira or Jira Product Discovery is straightforward, sharing it—especially a public version—can be a challenge. In today's post, we’ll explore the benefits of sharing your Jira roadmap, the challenges people face today, and how Released makes it easier than ever to share your public roadmap directly from Jira. https://lnkd.in/gf74d4BV #atlassian #jira #roadmaps #customerlove

Is AI killing developer jobs? Or is it more hype than reality? The 2024 Stack Overflow developer survey gives some insight into that question. ◦ 12% of developers do see AI as a real threat to their current job. ◦ 62% are using AI as part of the development process, and a further 14% plan on doing so soon. ◦ 72% view AI as favorable or very favorable ◦ Increased productivity and faster learning top the list of benefits But only 3.3% of developers think that AI is great at handling complex tasks. And therefore we are probably still ways off before AI actually replaces the role of the developer. 👇 See the link in the comments for more insights and datapoints.

This week we have a few more small improvements and bug-fixes for you. To make it a little more fun, Jens recorded writing the release notes this week. Check it out:

Write release notes in 30 seconds ⏱