Event banner
Event details
- Consistent wording for a smooth landing/transition How do we support end users with this change in name? Is there a consistent 'strapline' / paragraph that the Product team can share on here which really brings to life the value of this change and that we can all start to share from the beginning of March pls?
- New deployments If a business wants to deploy Yammer from as early as March, what is your recommendation in regards to the name, materials, training etc, e.g. go in and launch as 'Yammer' with the disclaimer the this brand name will change completely to Viva Engage by the end of 2023 or go in and launch as 'Viva Engage' from the beginning?
espnguyen
Microsoft
MicrosoftHi Bernie! 👋🏽 Soon we'll be making available rebranding toolkit that hopefully will help with the items you mention above. It will include graphics, templates and other guidance you can use to communicate this change to people in the organization.
For new deployments, I would suggest centralizing on the 'Viva Engage' name but communicating that they might see 'Yammer' and that it will soon change to 'Viva Engage'.
- Hi Bernie and Steve! I've been going back and forth about how to introduce this name change as well. The reason why is because we positioned Yammer as a "partner" to our intranet on SharePoint about two years ago. Then six months later, we added Yammer to the intranet homepage right rail, which has positively impacted new communities, active communities and active users. So I'm debating how I will reposition that relationship with this name change. One tip I read in a blog about this change suggested referencing Yammer as Yammer/Viva Engage, once the change is introduced, which I plan to do.
