Now, about nine months later, Microsoft Delve is taking a circuitous route to success, to say the least.
While it was designed to be a business intelligence (BI), Enterprise search and collaboration tool wrapped into one, it has yet to make good on that vision. Delve was intended to be able to search users' documents, email messages, meetings and more, then serve up relevant content and messages to them based on their content and activities. At one level, Delve has failed because it hasn't been as comprehensive a search tool as it was billed. At another level, users have significant concerns about their privacy, given the scope of documents and activities Delve is designed to scour.
As BI and SharePoint expert Scott Robinson notes in this podcast, Delve was intended to be much like Edwin Jarvis, butler and human search tool for Iron Man's Tony Stark. But Delve ain't no Jarvis, Robinson said.
"Jarvis ... [is] always there at Tony's elbow, giving him what he needs even before he knows he needs it. Delve wanted to be Jarvis," Robinson said.
"Delve wanted to be a product that anticipated the user's needs, that understood the user inside-out, and followed the user's behavior patterns and personal workflow, and understood what the user did day to day, so that everything was there at the user's elbow."
But according to Robinson, Microsoft failed in articulating the return on investment of Delve and in being able to roll out a tool comprehensive enough to have ROI.
"The truth is, the product didn't cover in terms of breadth or depth enough of the user's work, documents and content to make a real difference. So, it was off to a rocky start from the beginning. The people who were using it didn't really understand what it was doing, and it wasn't doing well enough to make a good impression. Now, that's bad news all around."
For more, check out this podcast above.
At Ignite, Delve takes the stage
Office 365 tools get reined in
Office 365 roadmap is rocky