Suggested by Joanne Anderson – Completed
Questions for VIVA Session
Out of the four VIVA workloads, where should we start the conversation? Answered
How and when should we connect to the other VIVA workloads to ensure that customers are not losing sight of additional VIVA Workloads and are not getting overwhelmed with the amount of information all at once? Answered
What are the excellent scoping questions for a VIVA engagement, especially when the customer approached for a non-VIVA engagement?
- Customer industry
- Current situation and challenges
- Customer Goals
- Success criteria
- VIVA licenses
- VIVA modules deploying
- Deployment approach (pilot group of users/Size)
- Deployment deliverables
- Deployment blockers or risks
- Deployment dates (timeline), constraints
- Scope of work
- Different stakeholders
- Roles and permissions
How to make sure we are inviting the right audience for the conversation?
Usually, the first kikoff call starts with the PM or whomever is leading the project on the customer’s end, including any other team members who would be interested/involved in onboarding process. After the initial call, you’ll have more understanding on the customer’s scope (as mentioned in the previous question) then you can target/include the right audience and technical people from both ends (a Global Admin, a Teams Admin and so on ..)
How is Microsoft approaching Viva Adoption for Customers who already have licenses?
The CSAM/Account team/CSM can answer this question
Can we see a demo or step-by-step approach and prepare accordingly to present to the customer?
The CSM team conducts VIVA Demos prior to the deployment stage. Joanne can work on including you on those demos
Is there an internal push @ Microsoft to send more Viva opportunities via referrals?
Joanne can take care of this question
What are the benefits statements we can use to drive the adoption?
Employee Experience and Engagement | Microsoft Viva
In what ways can we bundle the Viva conversation with other workloads to push for more adoption?
VIVA is built on top of our M365 workloads/services, and this is how you can rely on different VIVA pre-requisites (SharePoint Online, Teams, Exchange Online, Yammer, PowerBI etc.) in order to bundle the Viva conversation with other workloads to push for more adoption.