Hi everyone,
We recently encountered a challenge: the adoption rate of our newly implemented features isn’t as high as we expected. There could be several reasons for this, but one of our hypotheses is that users may not be fully aware of these features.
I’d love to hear your insights—what strategies have worked best for you when introducing new features? While we do communicate updates within the app, we’re wondering if there are more effective approaches. Would a newsletter, a webinar showcasing the changes, or an in-app recorded demo make a bigger impact?
If you’ve tackled a similar challenge, I’d really appreciate any tips or experiences you can share!
Looking forward to your thoughts.
2 Likes
@GHMahimaanvita @JohannaPichotka @freatt @sopel @Chris_at_DigitalRose @LorenaVargas @MelinaFriebel @ShirleyZhuo @tadler @DaveLiao
I wanted to tag the people who were interested in having a UX/UI designer section here on the Atlassian Community (from my earlier post). I’m really happy that this section is now live, and I’d love for all of us to be active here! 
This is the first post in this section, so please feel free to share your thoughts, especially about how to introduce new features to users. Your opinions will be really helpful!
Looking forward to hearing from you all!
1 Like
Emails are hit and miss, I would say more miss than hit. Something in-app is better.
But is it a major improvement for users?
We have a tendency to think that if something was hard to implement it is major or important. My point is don’t cry wolf. Better to restrict annoying users to things that are significant.
If the adoption rate is low you also have to ask yourself if it is solving a pressing business need and whether the UI is a bad (I always assume it is worse than we think). This could also highlight that it is a minor improvement, niche feature.
2 Likes
Hey, in our case there is definitely some marketing activity around new features. I can’t tell you exactly what channels they use. We also sometimes use Atlassian’s onboarding spotlight. Even if users reject it, they are aware that there is something new. We often combine it with a new-lozenge on the new feature, at least for the beginning. In one app, we also have a “Support and Feedback” dropdown. When you open it, there is a “What’s new” menu item. If there is something new, there will be a pulsating purple dot on the “What’s new” menu item. Maybe that will help you a little.
2 Likes
That is a good point - we need to balance the notifications so that users are not annoyed with them. We inform them about the new changes in a form of a pop-up, where we highlight all the recent changes at once. We don’t show separate notifications for every change.
Regarding the minor/major improvement - it was something that was requested by our clients. We assumed it was major, but maybe this assumption was wrong. We are trying to assess it now. But we had a similar case in another product, where one feature was heavily requested and then not many people were using it 
Of course we ask our clients for feedback, but they rarely get back to us.
1 Like
We also use “What’s new” in our apps. One app uses the Spotlight feature as well. Do you know what performs better in your case? Spotlight or “What’s new”?
1 Like
Hey, unfortunately not. I asked a colleague about the analytics for the “What’s new” section. And she told me that there are hardly any clicks 
I see 
Thanks for checking anyway 