I’m doing a lot of Microsoft Viva work with customers (disclosure) as well as working on a trend report on a related subject, so I am constantly thinking about where this work leads to. The obvious question is what kind of business outcome you are trying to achieve and how do you measure it. This post is to share some initial thinking. Anyone who reads this and is involved in similar work, I’d love your input so I can advance this very quick attempt (hence thought rocket).
So first let me elaborate on the format briefly. It’s just a simple table. I felt it was a nice way to achieve what I wanted. Aside from the structure you can create, it kind of helps to list things out. I wanted to have almost a catalogue that I could capture existing work with but also help stimulate future work (or at least thinking around it). The table below is a combination of those things. Considering there are so many modules in Viva, the structure was helpful to work around them too.
I don’t think the structure and the breakdowns need much more elaboration – they are fairly self-evident. What is much more important is what goes inside them and the references and descriptions I use.
I’ve had to make this generic and I’ve not added specific targets but the clues to what those would be is in the KPI/Outcome column.
As mentioned, some of these are based on real work and some just ideas. As mentioned, would love any input – just add a comment if you have any. This is still very much a work in progress and any work I do or input I receive I’ll progress this perspective further with.