Microsoftespnguyen - I categorically disagree with your statement "First, it's important for us to think about how we can add value to end users. End users don't spend a lot of time thinking about whether it's one product name or the other." That may be the assumption from within MSFT, but the reality is that end users absolutely spend a lot of time trying to figure out what it is they're using, getting confused about what to use when (see the recent blog post - published by Microsoft - about the 3 different posters explaining when to use To Do, Planner, and Tasks). You do need to clearly communicate exactly what one solution offers, what its touchpoints are, and where that overlaps other solutions.
FWIW, I'm all for rebranding Yammer. Look at all the other product line rebrands - there are no/few standalone products anymore; they fit under a Purview or Azure or D365 or M365 or Power umbrella. All except Yammer.
If this statement above is true: "Viva Engage will continue to show the same network, home feed, and communities that you see today in Yammer. Any content created in Yammer.com or mobile – including community conversations, storyline posts, and stories – will be viewable in Viva Engage. Likewise, content created in Engage will show up in Yammer native experiences. Viva Engage will also continue respecting any custom branding done for the Communities app. To use Viva Engage an organization must be licensed for Yammer." -- then it doesn't make sense to continue the Yammer brand.
