Forum Discussion
The Future of Delve
We certainly understand and know the pain point. We've been focused on enabling good authoring experience, feel we can offer a good team or executive (CxO) style blog with a dedicated communication site + news approach; esp with coming organizational news. But alas, the personal blog alludes explicit. One can publish news often in many locations (to a team site, to a comm site, to a hub site) and the feed of it goes out to people they are related to, even if the person is not active in the site where it gets published, the Microsoft Graph knows the relations and serves up as best a "feed" it can to each user - without requiring that person to "go to someone's blog." That said, the heads are noodling in these areas for sure. One thing you got me thinking about was a way to present all news someone publishes in all places they can, and seeing the feed through the eyes of what the person logged in has permissions to view. So you would see someone's "blog" but only have visibility to the content you're allowed to view. Just thinking out loud. let's loop in John_Sanders who is our news guru these days to review and possibly add some comments; plus Dave Cohen (US) who owns some of these pieces, too. :-)
Hey gang, I have a post that we published at my company and was wondering what this community thought of it. I'm curious to know how the post -- centered around adoption -- compares to you all's experience. How difficult is it to secure end user adoption? How tough is it to get it to stick? Thanks!
https://www.avepoint.com/blog/strategy-blog/delve-adoption-office-365/
So, I hope this lands constructively, as it's meant to be... I believe "candor is love" in addition to saving everybody time.
That post is not really about Delve adoption, is it? It's about Delve features that may help with O365 adoption. The part about "when and why to go to Delve" is minimal.**
At my org, we see the Delve view now when we use our intranet search and click to a second-level (click on an individual name) in personal search results. That's the only time I ever see it, and is rare indeed; I had to click to an expanded view of my apps to find it, and had a momentary thought of, "did MyCo turn it off?"
And I care a LOT more than the average bear in MyCo about what's in the waffle and how it can make me and my teams and my company more productive. Most others won't be that motivated.
**I will say on the positive side, that from your blog I learned that Delve is supposed to surface content from wherever I stored it in O365, which is a holy grail cut in half.
Why half? Because at MyCo we also have people saving files to desktop, shared drives, blah blah blah. But hey, if their worry is that they saved something in OneNote or Teams Files or OneDrive or Yammer Files and forgot which, this would be one of those "hallelujah choir" things... if I was fully confident that this is what Delve offers.
I'm guessing there are limitations in fine print? After all, Teams Files aren't even a year old yet and we just got Files surfaced in Yammer in my tenant last month.
Anyone who tells me, correctly, "yes really, no fine print" would be my favorite person for quite some time. Because that "find it from anywhere in O365" would offer a carrot I could (and would) dangle in front of my users to indeed, get more adoption of Office365 solutions, AND Delve.
Delve, like Search surfaces information from the "sources" that connects with Office Graph. So, yes, you get content from "all of O365" if connected (that's the fine print). Last I heard, Teams did not connect yet (but it's on their roadmap), so Teams conversation content does now show up in Delve or Search. Files in Teams do show up, because those files are in a group/SharePoint backend that does connect with Graph.
Btw, this is the old "push" vs. "pull" discussion. I find Delve useful in that it pushes information to me when I would not necessarily go find it for myself. Search pulls the information to me.
Now, I too would be interested in finding out more about the future of Delve...