Are you new to Nintex Analytics and looking for quick insight out of the box? Created your first Usage Lens dashboard and now want to do more?
Well, you’re in luck!
In this post, I’ll cover how you can take the next step and spin up a basic Process Intelligence Lens (dashboard) quickly to get foundational runtime insight for a particular process: how many times it has run, did it complete or was there a fault, how long does it take on average, who is involved, and more. You get all of this from a pre-built dashboard embedded in Nintex Analytics.
*Note: If you haven’t already, activate Nintex Analytics(or sign up for a trial and connect your Nintex data sources.
Here Are The Steps:
First, in your Nintex AnalyticsTenant, select “Lenses” in the top menu and then “Create Lens.” When the icons below pop up, click on “Process Intelligence”:
Secondly, search for the workflows you want to add to this Lens. For this example, we’ll gather insight on “Leave Approval by Manager” across our SharePoint 2013 and 2016 environments, so simply use the keyword “leave” to search for the relevant processes. You’ll see two instances of “Leave Approval by Manager”; click the “Add” icon next to the workflow, then click “Done.”
Finally, you’ll need to choose how you want to visualize or consume the data of this workflow (numbered in the screenshot below). You have three main options:
- Create a standard Process Intelligence Lens with the pre-built dashboard in Nintex Analytics
- Use a Power BI Online connection to push the Nintex data to Power BI.
- Use the OData connection to surface the data in another analytic tool (such as Microsoft Excel)
For this example we want the first option (utilizing the pre-built dashboard); when we click that, Analytics automatically creates the process intelligence dashboard for Leave Approval by Manager.
Insight We Gain From the Out-of-the-Box Dashboard:
The first tab provides an overview of runtime Process Metrics:
- The leave approval process has run 415 times, resulted in 396 tasks, and has faulted 15 times (hover mouse over bar graph)
- 66 leave approvals currently running, handy if there is system maintenance, so workflows are not interrupted or lost.
- Peak times when leave approvals are requested throughout the year (helps with staff planning and scheduling)
- Who made the most requests (helps with planning)
- How long it took. See how it took 2 days this year versus almost 5 last year? That insight helps monitor process productivity, making sure the number of days doesn’t creep up again.
The second dashboard tab is Process Participation, which focuses on employee engagement. A couple of things stand out.
The workflow has only been published twice since 2014 – a sign that it may be due for improvement.
- The process has 14 participants, but there are 20 people in the team. This may signal that six of my staff are disengaged from the process, or have not submitted a leave request for the past few years.
- Outcomes of the leave requests, as well as employee engagement with the process over time, can also be tracked.
The final tab looks at the process’s Return on Investment (ROI). This tells us how Nintex Workflow had business impact through processes automation.
ROI is calculated in three areas:
- IT productivity: Did it save time, so IT can work on higher-value tasks?
- End-user productivity: Did it save time for the end user, who can do other things?
- Development cost savings: Did Nintex Workflow save money through reduced custom development costs?
These calculations are based on an ROI framework developed by Forrester Research. To read more about the framework, follow the link in the dashboard.
That’s it! In five minutes you’re an insight hero. And you can take the same approach to all of your top processes. Imagine what your executive team will think of those insights!
And this just scratches the surface of what we can do with the Process intelligence Lens in Nintex Analytics. We’re queuing up blogs that demonstrate the deeper value of instrumenting your automated processes with Beacons (which are signals that emit data from a particular point in a workflow) and of connecting to Power BI desktop to create custom dashboards.
We’re also going to show you an in-depth example of how best to use a Process Intelligence Lens (using Beacons) to surface data with more business context. As you’d probably guess, different businesses have different goals, so this approach takes more consideration around the questions your unique business wants to address.