Forum Discussion
The Future of Delve
- Jun 05, 2018
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. :-)
I always liked Delve, but struggled to identify the trigger, in terms of either situation or need, "when people would reach for it."
I remember at one Ignite conference keynote, listening to Julia White positioning Delve as where she starts her day, in order to get a feel for the context of her projects, team and the organization, before diving into any direct messaging. But clearly that didn't take root, as I never saw that again.
From my (admittedly incredibly limited) point of view, the Delve team has not been highly aggressive in its messaging around "when and why" so much as "what it can do."
I have a strong bias against feature-oriented analyses of tools for exactly this reason. Features are rarely unique, unless they're dependent on exclusive integrations or some other special sauce. As I've written elsewhere, a breakthrough this week is a checked box next quarter, as platforms and tools converge.
Focusing on "when and why," on the other hand, is always germane. Consider Teams and Yammer, where the feature overlap is epic. But...I reach for Teams when I need to work with my team on a project with a PowerBI dashboard (inner loop). I reach for Yammer when I want to leverage a company-wide PowerBI group of thousands, for help or ideas or updates (outer loop).
Backing away from the soapbox now, and waiting on people with much better creds to tell us what's going on behind the curtains.
Thanks Melanie, as always,for your thoughtful and considered reply..
I agree with your analysis on features yet this is exactly where I’ve been caught out and I suspect others have too. Both boards and blogs are features that need to be developed and roadmapped either inside or outside Delve in Office 365.
I’ve been genuinely impressed with the improvements in the Microsoft Graph of which Delve was most definitely the poster child. It is inevitable on an initiative as large as Office 365 that some ideas grow and others do not. I’d appreciate a mature response from Microsoft, as considered and insightful as yours, outlining their plans.
Delve shone brightly and helped shape Office 365. Let’s recognise that and retire the product in clear support of customers.
- Stephen BoothAug 27, 2019Copper Contributor
John Wynne wrote:Both boards and blogs are features that need to be developed and roadmapped either inside or outside Delve in Office 365.
Yes, most definitely. Killing those would be galactically stupid IMHO.
Maybe I'll just have to move my content to Blogger or Wordpress?
- RobOKJan 28, 2018Bronze Contributor
John Wynne wrote:Both boards and blogs are features that need to be developed and roadmapped either inside or outside Delve in Office 365.
Agree!
I’ve been genuinely impressed with the improvements in the Microsoft Graph [...]
I don't doubt this, but how has the Graph improved?