All practice for no stage show? You can build in silence. But you cannot definitely sell\/market in silence.<\/p>\n\n\n\n
A lot goes behind the scene in developing new features for your product\u2014 <\/p>\n\n\n\n
The research your team does, to know what more the users expect from the product. The analysis as to whether or not the feature will bring growth to your product. A great deal of work your design and development teams put in for the new features. <\/p>\n\n\n\n
Doing the right kind of announcement pays off for all these efforts. But new feature announcements are crucial for other reasons as well. <\/p>\n\n\n\n
- Users and markets are like a stream that\u2019s constantly flowing towards the future. To stay relevant<\/strong> with both your product needs improvements and updates.<\/li><\/ol>\n\n\n\n
- Users like the fact that businesses hear their concerns and needs. But they love it when you act on it. New features announcement is one of the ways to re-emphasize that you are user-centric<\/strong>. Also, when users who feel acknowledged and worthy turn out to become loyal customers. <\/li><\/ol>\n\n\n\n
- At any moment, not every user you have is engaging with your product. Some might be inactive. Some might be on the verge of leaving. New feature announcements are the best way to mend the terms. When you offer something new, you can possibly re-engage them<\/strong>. It can prevent churn. <\/li><\/ol>\n\n\n\n
- Many products offer a free trial to people. They keep looking for reasons to subscribe to your product. New feature announcements can add up to it. In short, it can act as a conversion factor.<\/li><\/ol>\n\n\n\n
<\/p>\n\n\n\n
Channels of new feature announcement<\/strong><\/h2>\n\n\n\n
New feature announcements are generally made through these channels. But there are distinctions, owing to which you cannot use the same message everywhere. The way users observe and respond to announcements differs with the channel. Each channel has its way of messaging that\u2019ll prompt them to take action. <\/p>\n\n\n\n
Also, users are accustomed to particular ways in particular channels. Your messaging should be fitting to these norms to yield the best results. To put it simply, you cannot write paragraphs for push notifications. <\/p>\n\n\n\n
Let\u2019s see how each channel works and how you can use them effectively. <\/p>\n\n\n\n
<\/p>\n\n\n\n
In-product announcements<\/strong><\/h3>\n\n\n\n
In-product announcements have more chances of being seen by the users. It is the best way to target active product users. <\/p>\n\n\n\n
You can deliver them in the form of visual highlights, tool-tips, or product tours. <\/p>\n\n\n\n
However, you have to be careful with these announcements as change is aversive for humans. They might be reluctant to accept it. Instead of bombarding them with the changes, introduce such that it\u2019s easy for them to digest. <\/p>\n\n\n\n
Make announcements a pleasant surprise. Make them sound like it\u2019s a valuable addition and highlight the benefits. Only then start with the feature explanation. Look at how Airbnb <\/a>does that,<\/p>\n\n\n\n
<\/figure>\n\n\n\n
<\/a><\/p>\n\n\n\n
<\/figure>\n\n\n\n
Since users are already inside the products, it\u2019s easy to grab their attention. The explanation part can be tooltips, product tours\/demos, or links to the blog. Provide an option where they can learn the working later whenever they like. <\/p>\n\n\n\n
Your in-product announcement should be tuned uniquely for the different user segments. Especially focus on their behavior inside the product and set triggers for announcements accordingly. <\/p>\n\n\n\n
<\/p>\n\n\n\n
Email announcements<\/strong><\/h3>\n\n\n\n
Email is for targeting the existing inactive users of the product. It is aimed at bringing back these users to your product. <\/p>\n\n\n\n
Emails, however, possess the problem of not getting opened. Add the right subject line that persuades and gives them a reason to open. Check out this email subject line. It makes the content interesting by adding \u2018our most requested feature.\u2019<\/strong><\/p>\n\n\n\n
<\/figure>\n\n\n\n
<\/a><\/p>\n\n\n\n
The mail must be effective in making them take action. Add CTAs to take them to try out the feature.<\/p>\n\n\n\n
You can also link blogs here if you think the blog will re-engage them in the product. In the case of email, you cannot use it for meager announcements. Ensure that the new feature is worthy enough to hook the inactive ones. <\/p>\n\n\n\n
You can also target new users with emails. Craft the message such that the new feature becomes yet another reason for their stay\/conversion.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Blogs<\/strong><\/h3>\n\n\n\n
Blogs can be used as a permanent source of information. You can redirect your users from the mail, in-product, and social media here. <\/p>\n\n\n\n
Blogs announcements are long as they explain the feature working in detail along with the reason why. The reason for development is what triggers the reader’s\/users to know more about the new feature. <\/p>\n\n\n\n
Users may not remember your interface. So a plain explanation will not make sense. So, add a lot of screenshots or demo videos, making it easy for the users. You can add CTAs that take them to try the new feature. Make it a detailed guide. <\/p>\n\n\n\n
You can explain different use cases targeting different segments and link them all to one main blog. If you think a single blog will be a cognitive overload, break it into reasonable parts. <\/p>\n\n\n\n
Use blogs in case of significant feature updates. <\/p>\n\n\n\n
<\/p>\n\n\n\n
Social media<\/strong><\/h3>\n\n\n\n
Social media announcements are for significant updates. <\/p>\n\n\n\n
It is targeted at a general audience. You can link to blog posts.<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
New feature announcement framework<\/strong><\/h2>\n\n\n\n
You cannot roll out a new feature without a strategy. <\/p>\n\n\n\n
Well, you can try. <\/p>\n\n\n\n
But its success isn\u2019t ensured. The same goes for the announcement part as well. <\/p>\n\n\n\n
With a framework, you can ensure your announcements can bear the fruit of feature success. It helps you choose the right ways of messaging and channels. It can make you focused. <\/p>\n\n\n\n
- Goal<\/strong><\/li><\/ul>\n\n\n\n
Without a goal, your work might be all over the place. Discuss what you wish for with this feature announcement. You might aim at one of the benefits we mentioned earlier,<\/p>\n\n\n\n
- Reducing Churn<\/a><\/li>
- Improve Conversion rates<\/li>
- Hook to re-engage, etc. <\/li><\/ul>\n\n\n\n
The goal puts you in one path instead of being pulled inside many. The goal of the announcement should match with the goal of new feature development. The most important thing you gotta do is to communicate the goals with your team. It keeps your team aligned to the vision. <\/p>\n\n\n\n
- Target User <\/strong><\/li><\/ul>\n\n\n\n
Not all users utilize a feature in the same way. Their need, usage frequency, and likes might change. That is why we create user personas in the first place, right? So, you need to know the segment of users this feature targets. You can revisit goals and then ask,<\/p>\n\n\n\n
\u2018Who will be benefited most?\u2019 <\/p>\n\n\n\n
When you find answers, you can use them in the messaging and entire targeting process. Again, just like the goal, communicate the target user information to your team. <\/p>\n\n\n\n
- Check feature priority<\/strong><\/li><\/ul>\n\n\n\n
Say all announcements, small or big, go like this.<\/p>\n\n\n\n
We got an important message for you!
<\/p>\n\n\n\n
And you end up delivering an insignificant message most of the time. Users will lose the sense of what is significant and what is not. <\/p>\n\n\n\n
It is why you should gauge the gravity of your announcement, in turn, the feature priority. Depending on it, you can go ahead to decide the number of channels. Remember- More the feature priority, the more the announcement channels. <\/p>\n\n\n\n
- Choosing the channel<\/strong><\/li><\/ul>\n\n\n\n
Different channels are effective for different segments. For example, if you need to add value for existing users, in-product announcements are the best. <\/p>\n\n\n\n
For in-active ones, push notifications and emails are the best option. You can also go with multiple channels depending on the significance of the announcement. <\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
Best practices for announcing new features<\/strong><\/h2>\n\n\n\n
- Visuals<\/strong><\/li><\/ol>\n\n\n\n
When users are amidst the flow of their tasks, any pop-ups can be quite a hindrance. And it has become an involuntary action to close the pop-ups. <\/p>\n\n\n\n
If the visuals aren\u2019t good, they might not want to check it out. Not just the case of pop-ups, this holds true for all visual-incorporated announcements. Make sure that visuals are attention-catchy. You also have to ensure to hook attention throughout the announcement phase.<\/p>\n\n\n\n
- Personalization for different groups<\/strong><\/li><\/ol>\n\n\n\n
Different users look for unique things from your product. So you have to craft personalized messages that can yield the needed response. <\/p>\n\n\n\n
Announcements fabricated with the right users in mind will trigger the aimed action. <\/p>\n\n\n\n
Don\u2019t use the same messaging across different user segments. <\/p>\n\n\n\n
- Copy is everything<\/strong><\/li><\/ol>\n\n\n\n
Your copy plays a significant role here. It\u2019s the base that can elevate the announcement. If your announcement copy isn\u2019t good, the users do go further. Make it precise and at the same time effective in conveying the entire message. <\/p>\n\n\n\n
- Talk benefit<\/strong><\/li><\/ol>\n\n\n\n
Why would a user check out the feature if it doesn\u2019t have a benefit to offer? Conveying the benefits is the right way to get them hooked. Instead of focussing on how the feature works, start with how it is beneficial. Highlighting it can make a big difference in user response. <\/p>\n\n\n\n
- Don\u2019t annoy users<\/strong><\/li><\/ol>\n\n\n\n
When using toolkits or product demos, make them short and precise. Users inside the product are a part of the task flow. These announcements should not take them away from the current flow path. <\/p>\n\n\n\n
Ensure that you don\u2019t make them feel like being caught inside the announcement component. <\/p>\n\n\n\n
<\/p>\n\n\n\n
Great feature announcement examples<\/strong><\/h2>\n\n\n\n
1. In product<\/strong><\/h3>\n\n\n\n
- Gmail<\/strong><\/li><\/ul>\n\n\n\n
Look at the benefit stated here: We\u2019ve made it easier for you to chat and make video calls in Gmail. Also, the visuals are quite eye-catchy as well.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
This is followed by tooltips showcasing the feature along with the benefits. There are also indicators showing the number of features, making it predictable for users. <\/p>\n\n\n\n
https:\/\/www.reallygoodux.io\/blog\/gmails-collaboration-features-tour<\/a><\/p>\n\n\n\n
<\/p>\n\n\n\n
- Feedly<\/strong><\/li><\/ul>\n\n\n\n
Feedly\u2019s <\/a>new feature announcement is a pop-up, with good visuals that convey the message. The users can figure out what the feature does from the visuals easily. The benefits are stated rightly.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
<\/figure><\/div>\n\n\n\n
<\/figure><\/div>\n\n\n\n
Check out the rest here: https:\/\/www.reallygoodux.io\/blog\/feedlys-new-feature-walk-through<\/a> <\/p>\n\n\n\n
<\/p>\n\n\n\n
2. Mail<\/strong><\/h3>\n\n\n\n
- Hinge<\/strong><\/li><\/ul>\n\n\n\n
This mail feature announcement from Hinge <\/a>is minimal and the copy is on point. It brings to light the user problem and introduces the solution as well. The benefit is also stated: \u2018a new way to organize\u2019<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
The mail continues explaining the features,<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
Once all the benefits or updates are mentioned it ends with a CTA<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
Look at the entire mail here: https:\/\/i.pinimg.com\/564x\/66\/ea\/8f\/66ea8fd51f2b8a2c99e536fed2e03e56.jpg<\/a> <\/p>\n\n\n\n
<\/p>\n\n\n\n
- Trello<\/strong><\/li><\/ul>\n\n\n\n
Go Big and Bold creates a mystery factor and the text that follows adds sense to it. The words \u2018Put fun in the functionality\u2019 hook the users to look for more information. <\/p>\n\n\n\n
The features along with the benefits are explained in this mail from Trello<\/a>. There\u2019s also a CTA button. <\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
Look at the CTA of the next feature update. It is action-triggering, right?<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
- Trello<\/strong><\/li><\/ul>\n\n\n\n
- Hinge<\/strong><\/li><\/ul>\n\n\n\n
- Feedly<\/strong><\/li><\/ul>\n\n\n\n
- Gmail<\/strong><\/li><\/ul>\n\n\n\n
- Don\u2019t annoy users<\/strong><\/li><\/ol>\n\n\n\n
- Talk benefit<\/strong><\/li><\/ol>\n\n\n\n
- Copy is everything<\/strong><\/li><\/ol>\n\n\n\n
- Personalization for different groups<\/strong><\/li><\/ol>\n\n\n\n
- Visuals<\/strong><\/li><\/ol>\n\n\n\n
- Choosing the channel<\/strong><\/li><\/ul>\n\n\n\n
- Check feature priority<\/strong><\/li><\/ul>\n\n\n\n
- Reducing Churn<\/a><\/li>
- Goal<\/strong><\/li><\/ul>\n\n\n\n
- Many products offer a free trial to people. They keep looking for reasons to subscribe to your product. New feature announcements can add up to it. In short, it can act as a conversion factor.<\/li><\/ol>\n\n\n\n
- At any moment, not every user you have is engaging with your product. Some might be inactive. Some might be on the verge of leaving. New feature announcements are the best way to mend the terms. When you offer something new, you can possibly re-engage them<\/strong>. It can prevent churn. <\/li><\/ol>\n\n\n\n
- Users like the fact that businesses hear their concerns and needs. But they love it when you act on it. New features announcement is one of the ways to re-emphasize that you are user-centric<\/strong>. Also, when users who feel acknowledged and worthy turn out to become loyal customers. <\/li><\/ol>\n\n\n\n
![\"New](\"https:\/\/lh3.googleusercontent.com\/QOoffWV-T9mEq_7lXIde9cL6cNk_v9VF7UCa-wqVmMUJuxYalfZJAeS9aEPH7dVsth6EofkKWyCLSkSYBwz00oowUgSS0QwcV5WXCmlter_J9kzLF5j79FlVxolDwu-WKhD6xlBk\")
<\/figure><\/div>\n\n\n\n![\"New](\"https:\/\/lh4.googleusercontent.com\/2Mvc623XNU7aQqh1gmpVjh5fM8WkbpoFn-V40Sn7ogWK2DWa_bowJ5Qt5p8BFgdXnYsk2H6aH90UCn1lfeUB91ffryNe1i9jP8S-6wLvTUHDg2U2FSPAeOji5Fn6LqAvWZU9_X4w\")
<\/figure>\n\n\n\n