2024-09: Slack Huddles, MSFT Teams, & Custom Group Naming

Release Date: September 2024

In addition to releasing Calendar 3.0 this month, our product team focused on delivering new insights on Slack and Teams, as well as improving the usability of our custom groups feature in the HRIS upload flow:

1. Slack Huddles

New metrics: slack:v1:huddles:attended, slack:v1:huddles:hours:spent:meetings

Based on popular demand and increased usage we've seen of the Huddles feature in Slack, we've recently added support for key metrics on the # of huddles attended and hours spent in huddles. These metrics can be used to understand the amount of time groups of employees are spending in ad hoc calls and how this impacts workflows and efficiency.

Note: Slack huddles metrics requires a Psoxy version of v0.4.58 or later.

2. Microsoft Teams

New metrics: 20+ Teams-specific metrics

We recently added a large set of metrics that go deeper into Microsoft Teams usage, similar to the detailed metrics we already have available for Slack. These metrics can help teams answer the following questions (and more):

• How much time are employees spending in scheduled and unscheduled Teams calls?

• How many Teams messages are sent as DMs? In public channels? To external parties?

• How long does it take for employees to respond to DM messages?

For more on these metrics and more, please check out our Metric Definitions.

3. Improved Support for Custom Groups

Historically, Worklytics customers have been able to add any number of custom groups not included in our default set of fields as part of the HRIS upload process. These groups are then used to calculate variations on our collaboration metrics and as dimensions/fields in certain data sets.

For example, customgroup1_individual_collaboration_interteam_hours calculates the total time a person has spent collaborating in a week with members of a different CUSTOM_GROUP_1 category.

New this month, we've updated our import process to be able to accept group names for each custom group with the following naming convention: CG_***. For example, instead of CUSTOM_GROUP_1, the group could be called CG_BUILDING_NAME, which is more meaningful.

More detail on this process, along with the latest instructions for HRIS Import are here.