Hubbl Process Analytics is the only Salesforce-native process mining tool.
Addressing your Security Concerns by Being a Managed Package on the Salesforce Appexchange.
How to get started with Hubbl Process Analytics, from installation and configuration to a walkthrough of the first steps to value.
There are two simple ways to configure Hubbl Process Analytics in your org.
User guide on the first steps you can take to get value out of Hubbl Process Analytics.
Hubbl Process Analytics is a powerful tool that helps you gain insights into the efficiency and effectiveness of your business processes. It serves as both a discovery and coaching tool.Â
As a ‘discovery tool’, it provides objective insights into the current state of a process, helping to identify systemic issues.
As a ‘coaching tool’, it allows you to benchmark the performance of individuals, teams, or products against your organization's average or the best-in-class standards.
As a ‘hypothesis testing tool’, it enables you to evaluate the effects of system or process changes by comparing processes before and after, for even minor changes.
Hubbl Process Analytics starts by visualizing your process using Salesforce field history logs. It creates a flow diagram that displays the times and frequencies of each path taken through the process, also known as variants. These variants can be further analyzed. For instance, you can explore the fastest path through the process, paths with the most steps, or paths followed by specific products. These analyses can be done manually or automated within the product.
Hubbl Process Analytics simply requires access to Salesforce field history logs, which are available once the tool is installed in your Salesforce organization for analysis. You can specify the object, date range, and attributes you need, and an easy-to-use wizard takes care of the rest. Additionally, event logs from other applications can be imported into custom Salesforce objects for analysis.
The primary output is an interactive process visualization that can be customized with filters. Additionally, you will receive a series of observations about the process, leading to actionable business insights.
Business Process Mining, as defined by analyst firm Gartner, refers to tools designed to discover, monitor, and improve processes by extracting knowledge from events captured in information systems.
These tools provide continuous visibility and insights into your processes. Business Process Mining tools accelerate the application of data science to business processes. They are typically system-agnostic but may require data preparation and data science expertise to operate effectively.
In developing Hubbl Process Analytics, we aimed to address the challenges associated with traditional process mining, particularly for smaller organizations. The key distinctions are as follows:
Data Preparation: Hubbl Process Analytics focuses on radically reducing the need for extensive data preparation. Traditional process mining often requires significant data preparation efforts, which can be time-consuming and resource-intensive.
Time to Insight: Hubbl Process Analytics is designed to deliver insights quickly. It prioritizes minimizing the time it takes to gain valuable insights from your processes, making it more efficient than traditional process mining.
Cost Efficiency: By streamlining data preparation and accelerating the time to insight, Hubbl Process Analytics helps lower the costs associated with process mining projects.
Hubbl Process Analytics is tailored to serve as a tool for both end-users of Salesforce applications and Salesforce administration and implementation teams. It is specifically designed to cater to the needs of these groups within your organization.
The ideal amount of historical data for analysis depends on several factors:
Volume of Records: Ideally, you should have hundreds or thousands of records (instances of the process being executed) to conduct meaningful analysis.
Annual Cycles: To capture a full year's process, approximately 14 months' worth of history is recommended.
Process Lifecycle Time: Consider the duration of your process lifecycle. For instance, if your sales cycle spans 12 months, aim to use 18 months of data for a comprehensive view. If a service ticket is typically resolved in one day, then three months' worth of ticket data should suffice if there's a significant volume.
Process Analytics and Business Intelligence (BI) serve different but complementary purposes:
Business Intelligence (BI): BI is valuable for identifying metrics and trends. For example, it can tell you that sales last quarter were 20% greater than the same quarter last year, with products A and B as the main contributors. However, BI doesn't provide insights into why product C's deals are taking longer to close this year compared to last year.
Process Analytics (Process Mining): Process analytics excels at pinpointing specific process-related issues. It reveals exactly where in the process problems are arising. For instance, it can identify that product C's delays are due to a lengthier contracting process. Process analytics complements BI by diving deep into process efficiency and effectiveness, offering insights that traditional BI may miss.Â
The frequency metric in Hubbl Process Analytics indicates the number of occurrences of each completed activity. For instance, in an opportunity process visualization, if you see 'Customer Evaluating' with a frequency of 762, it means that 762 sales opportunities have passed through that specific stage.Â
A variant in Hubbl Process Analytics represents a unique path through a business process. For example, different customer support cases may follow various sequences of statuses. Each path is a variant, and the most common ones have a high record count. Find out more here.
In the settings panel on the right of the visualization tab, you'll find a listing of each process flow variant. Each time an opportunity, case, or object completes a variant, it counts as a record. The activities column indicates the number of activity steps in that particular variant.
The line color and thickness in the visualization tab are explained in the key at the bottom left. These colors represent relative times for all line segments in the process being visualized. For instance, red segments might take longer, but it doesn't necessarily indicate a problem. Context matters; for instance, a red segment after sending an email may simply reflect a customer response time.