How to Contextualize Your Company’s Learning Data with Watershed and Process Street
A key data point in measuring the effectiveness of a learning solution is checking that people actually completed the learning content. If they didn’t, then the learning certainly didn’t have an impact. Data from your learning systems can tell you whether or not the learning was completed, but might be lacking in painting the full picture of why the learning was not completed. What if training was held back by a step in your onboarding process, or didn’t happen at all because the forms never made it to their destination? Without data to paint the full picture, you can’t hope to intelligently optimize your company learning.
That’s why we’ve partnered with Process Street to create a Zapier integration you can use to feed data from your processes into the same Learning Record Store (LRS) as your learning analytics.
It works by listening for checked off tasks in a specified Process Street template, and then sending rich data from the checklist as an xAPI statement to Watershed.
Let’s dive into a use case to demonstrate how this integration could benefit you.
Example use case: Onboarding
- You gather learning data from your learning systems in Watershed
- You use Process Street to track and structure your employee onboarding process
- You combine data from both learning and non-learning activities that make up the onboarding process in one place
- As an employee is being onboarded, their manager works through a Process Street employee onboarding checklist, recording data and ensuring no steps are missed
- Zapier listens for when tasks are checked off in the checklist, and sends progress updates as statements to Watershed
With a record of when the task was completed, who it was completed by, and other data from the checklist form fields, the L&D team can diagnose bottlenecks in the vital training and onboarding stage and individual line managers have a single place to track their new team member through the complete onboarding process.
How to set up the Integration
To set up this integration, you’ll need:
- A Zapier account
- A Process Street account
- A Watershed account
Setting up the process in Process Street
The first step is to add an employee onboarding template to your Process Street account. You can add the template below to your account as customize it as you like:
Working through the template, you’ll see you can record employee information in the form fields. Here I’ve added some sample information and checked off the “Prepare paperwork” task so Zapier has the information it needs to run a test.
Configuring the Zapier integration
We use the third party automation service Zapier to connect Process Street with Watershed, and over 1,000 different tool in Zapier’s list of supported services. This integration is already built and tested, ready to use when you click “Use this zap” in the embed below:
When you configure the zap embedded above, you’ll have the option to specify template and task you want this integration to run on:
Most of this zap has already been set up for you, so once you have specified the task and template you can keep hitting “Continue” until you get to here:
On this screen, use the “Insert field” button and select “Name”. This sets the task in the Watershed statement to match the name of the checklist item in Process Street.
Complete the zap, and send a test to Watershed.
Now Watershed is logging all instances of the “Prepare paperwork” task being checked off, and storing them as statements for analysis.
Configuring reports in Watershed
Data from Process Street can be used in a whole range of different configured reports addressing questions such as:
- How many people completed each onboarding task?
- What is the average time between completing sequential steps of the onboarding process?
- What time or day or day of week are people more likely to complete certain onboarding tasks?
The most common use of Process Street data in Watershed is for line managers to keep track of where people are in the process. Watershed’s Program report is ideal for this as it can be configured to keep track of a person’s progress through milestones and also display assessment scores for related assessments where relevant. Using permissions, managers only see data about their own people and managers higher up the hierarchy can drop down from their level into individual groups and people.
See Watershed’s Program Report help guide for more details on how to configure the Program Report and the screenshot below for an example of how the report might look.