Monday, August 17, 2015

Business Process – the missing element from Delve?

Microsoft Delve is an interesting new cloud product that attempts to bring together the many information sources a typical enterprise business user is interested in so that they can make sure they know what they need to.

It is often simplified to talk about finding people through content, or content through people.
image
Leaving aside the similarities with stalking work colleagues, it does seem to offer some value. One potential use case I heard of was finding all presentations presented to me in the last 12 months.
Delve is based around the Office Graph, which gathers data from across Office 365 and other tools (even eventually ones from ISVs). The idea seems simple enough:

The two relationship types they currently support are “Trending Around” (content related to a specific person) and “Working With” (people working with a specific piece of content). Graph edges are relationships and the nodes can be people or content (documents or conversations).

Clearly this could be very useful, but I think the missing element is business process.

Now traditionally we have represented the business process in a number of ways. perhaps it was the location (e.g. a Virtual File), a piece of metadata (e.g. project name), or just when it occurred (e.g. Collaborate 2015). These are all fairly imprecise, and one of the issues with business process as an idea is that you can have more than one present at a given moment in time.

For instance, this weekend I ended up paying $36 for internet access at the hotel my employer had our annual conference at. I am planning on expensing that amount on Monday. There are three business processes this involves:
  1. The expense reimbursement business process.
  2. But the expense was only necessary because we were offsite at Activate 2015, so it was part of the Activate conference.
  3. The internet access was required because my flatmate at the time needed to upload a user research prototype for our Connect product.
I would expect that the expense reimbursement could show up any one of these three. Either a query about all employee (or my specific) expense reimbursements, a query about Activate 2015 activities or a query about the user research for the next phase of Objective Connect.

In a graph we could add business process as another node, but that doesn’t involve it in the relationship between person and content the way we would want to. However, custom content types are going to be added soon, so the API would allow us to add a business process node easily enough. But would we link the piece of content, or the person to it?

We could make it an attribute of relationship, but that might limit our ability to query it (or not – see the idea of looking for content presented to me). Given there is a potential one-to-many relationship between a given edge (relationship) and business processes, it might requires changes to the Office Graph from Microsoft to give us that functionality.

There is another technical problem, which is how do we capture the relevant business processes that are involved in these person/content relationships? Do we ask users to act like lawyers and specify at every minute of the day what business processes they are involved in? Do we merely make them hashtags and allow people to tag everything they do, if they choose to do so? Is there some automated process that will prompt people to classify their content based on the meaning detected in the words they use?

Personally I think there is some real value in using hashtags – but they must be understood in the context of that person’s role, activities and context. So I might have tagged that expense reimbursement with these hashtags:
#expense  #Activate2015  #ConnectUX
But they way those might be interpreted might vary by context. For example, #expense will be associated with the sort of expenses I am allowed – perhaps “discretionary travel expenses”. Further to that, #ConnectUX will be regarded due to the time period as relating to the Connect user experience research being conducted between the 10th and 21st of August.

Those context variations to the hashtags require some rules, some intelligence, be applied to my hashtags in order to derive a better set of processes. That is hard, and that is where I would expect an app might want to call out to <handwave> (Cortana and the Office Graph?) to find info that would help solve the problem. We would also want other apps (CRM, ERP, etc) to support this sort of tagging, so their content could be properly understood as well. It sounds improbable, but interesting I think …

More info about the actions available as edges.

No comments:

Post a comment