OGL Insider: Hotspots - user insights

Preface:

Welcome to another installation of “The Insider”, a peek into the inner workings of the Oracle Guided Learning Product team. Oracle Guided Learning is Oracle’s premier Digital Adoption Platform, designed to help organizations and their users adopt products, policies and processes faster as they transform continually in the cloud.

This series, will give you an insight into the rationales and reasonings for creating some of our premier features and give you visibility into the team behind the platform.

Hotspots – Understand how your users engage with your pages and processes

As part of any design and or configuration process, you will hear many opinions placed on the positioning and integration of any section, component and field on an application. How many times have we heard “I think this would work” or “I feel this is what our users will like.” We often validate this during User Acceptance Testing (UAT) and take our assumptions and learnings and feed that into design.

This also happens when errors occur. There’s a system, process and user experience discussion that cumulate into the “I feel” and “I think” phrases.

While experience and intuition matter, wouldn’t it be nice to incorporate tangible data into the decision-making process? Wouldn’t it be handy to test our hypothesis and validate this end user data?

A key component of Digital Adoption Platforms is the ability to measure insights into user’s behaviours as they navigate applications, processes, and fields. Within Oracle Guided Learning, we call this functionality Hotspots.

What is it? Why did we incorporate this into our product?

A Hotspot is a type of "event listener" that allows organizations/customers to gather critical information on how their users interact with and use the application. Hotspots listen for an event (such as a user click), and when that event occurs, OGL registers that event in analytics.

Hotspots was majorly incorporated in the product to enable our customers to

gain valuable insight into how their users are navigating the application, and even to monitor the key differences between starting a process and not submitting it.

What is available today and how is this being applied?

The image illustrates what the invisible Hotspots would look like on the application and the analytics dashboard after a month of use.

Creating a Hotspot
 

To create a Hotspot:

1. On the OGL console homepage, select Hotspot.

The New Content modal dialog is now displayed.
 

2. Enter the Display Name and the Location URL.

Note:

The following characters are not allowed: / \ | : " < > ?

3. Enter the description for the Hotspot.

4. Select the Create button () to launch the OGL Editor.

The OGL Editor launches in a new tab.

5. Select the desired target element on the application.

6. Go to Step Settings.
7. Set the desired Activation Settings and Advanced Settings.
8. Select Save & Close.
9. Go to the OGL console homepage and activate the Hotspot. Configure Guide Activation settings for this Hotspot, as needed, by selecting Guide Activation in the guide tile.

What have we noticed about the feature's adoption and use case from our customers?

The feature empowers our customers to strategize, plan and to take informed decisions by tracking the usability of the application.

Many of our customers today are utilizing Hotspots for:

• Performing A/B testing on a field, icon and/or infolet during design and configuration stage
• Validating a users’ journey as the application and/or process has gone live
• Identifying errors/points of errors for user design and experience hypothesis

What's next? Where are we going?

In future, we are investigating how Hotspots can be leveraged to be able to display the desired content to the users at the right time upon tracking and analysing the user behaviour data. We are also looking at tangible ways to improve the selection of elements on a page and visualization of data and outputs that come from the Hotspot.