Two things stand out to me about Hyperfish: first, they take meeting productivity seriously, and second, they offer an incredible tool for directory accuracy and profile information. On meeting productivity, they don’t allow the use of technology for distraction, which means:
At Hyperfish, we only allow meeting organizers to have laptops in meetings. This really prevents people not paying attention in meetings.
On the tool side, its namesake offering ensures that directory and profile information is up-to-date and complete, and works with Active Directory on-premises, with Azure AD in Office 365, and supports hybrid environments too.
Here’s the back story as I heard it from an early employee. Nintex, a workflow automation tool for SharePoint, relies on Active Directory for name lookup, manager lookup, and the lookup of other relationships between people in order to do its routing and escalations properly. However, very few organisations have a “perfect” Active Directory; more likely, the quality ranking is at the other end of the scale, the result of inattention, complexity, frequent changes of role and location, mergers and acquisitions, and all sorts of other directory atrophy. In other words, the lack of good directory information compromises the ability of workflow tools to work properly. That’s an opportunity. So one of the co-founders of Nintex teams up with some ex-Microsoft contacts and goes to work on how to solve this problem – creating a new product and revenue stream in its own right, but more strategically laying the foundation for greater usage and adoption of Nintex (and other workflow tools too).
Enter Hyperfish. The basic goal is to ensure directory details and contact information for everyone are up-to-date. There are two basic pathways for getting there: ask the person, and connect with other authoritative systems:
Approach 1. Ask the Person
Each individual in an organisation should know their work phone number, email address, mobile number, current job role, office location, etc. By asking each person when directory information is missing, Hyperfish can populate the directory with validated data. Hyperfish can use an email alert or a chatbot interaction to prompt the individual for whatever information is required.
Here’s the flow as Hyperfish illustrates it:
With Microsoft announcing Microsoft Teams as the strategic universal client for real-time communications (not Skype for Business), we can expect to see Hyperfish creating a bot that works in that environment.
Approach 2. Connect with Other Authoritative Systems
In my Office 365 book I say “don’t ask for dumb data” (page 105):
Employees should not have to fill in “dumb data,” which is data that is already authoritatively stored and known from other systems. First name, last name, email address, phone numbers, office location, manager, assistant, and similar data should not be requested from employees when filling in their profile; those details are well-known and should be auto- populated. In some cases an employee will need to correct the data (which should be done in the kingpin system and then flow through), or an employee may not want particular data broadcast across the entire firm. In the latter case, having the ability to add security permissions to data elements is a useful system capability.
Hyperfish does this in spades (yay!), allowing the creating of mapping and update rules between authoritative systems holding directory and profile information and Active Directory. Here’s the example Hyperfish provides:
In the above case, rules have been created to pull specific information from Workday and SAP into the directory, precluding the need to ask an individual for those details. And since the rules can be scheduled, when the data changes in the authoritative system, it will be reflected promptly (not immediately; depends on the schedule frequency) in Active Directory too. Talk about directory goodness!
There are lots of other cool things (read: important functional capabilities that address valid business needs) in Hyperfish too, such as attribute approval, profile picture validation (no cat pictures), attribute presentation rules, and directory scoping (for a phased implementation).
I like what I see.