Embedded Analytics

Expert Q&A: Empowering End Users With
Embedded Self-Service Analytics

By Yen Dinh
Share on LinkedIn Tweet about this on Twitter Share on Facebook

More than ever before, software teams want to provide end users with enhanced capabilities to do their own reporting and analytics. When you embed self-service analytics in your commercial or corporate application, end users are empowered to get the information they need, when they need it. Rather than exporting data or jumping into another application, users can help themselves to what they need in your software.

We recently sat down with Chris von Simson, Research Director at Dresner Advisory Services, to talk about why user enablement has emerged as the overall theme in today’s embedded analytics market.

>>Related: Logi Composer’s Embedded Self-Service Analytics: The Developer’s Experience and the End User’s Experience<<

Why Self-Service Is Ranked as a Top Priority

According to Dresner Advisory Services, embedded BI is one of the best investments a company can make. Those who aren’t using it are becoming the outliers rather than the status quo. Why? Because an enormous number of organizations that have BI initiatives see very, very high rates of return.

Companies embedding BI see self-service capabilities as a major contributor to overall success. According to Dresner’s survey of software teams, 13 percent of them scored their initiatives as having very high, transformative return on investment at 24 percent or higher. This is the kind of ROI that will transform a company.

The Benefits of Embedded Self-Service

Self-service is not just a flash in the pan—it’s been an important strategic technology for a number of years, along with reporting and dashboards and data integration. But data shows that end-user self-service has had an enormous impact far greater than any of the other technologies. Why?

Self-service means completely different things for different people—but they all find it useful. Let’s look at three different self-service users.

  • If you are an analyst in a big three accounting firm, you will look at self-service as the ability to extract the necessary data from a data set. You’ll investigate the data, look for patterns and insights, and share it with other users. You are a power user whose day job is to work with the data.
  • Next, consider a manager of a car dealership. He’ll look at all the standard reports, such as daily sales volume, and will want to drill down to which specific vehicles in the lot are sold. But unlike the analyst, he’s not digging for insights. He knows what he’s looking for and expects that data to be presented to him.
  • Finally, think about a nurse at a patient’s bedside. The nurse needs to see vital information—heart rate, body temperature, etc.—and may also want to do some drilling to see medicine administered. But she doesn’t need to do grouping or calculations like the analyst and the dealership manager.

Each of these people have day jobs, and each of their jobs require a different level of interaction with data. The reason self-service is essential is because it meets the different needs of every user. And the reason embedded self-service in particular is so impactful is that it’s customized to provide different user experiences to these different users.

Logi Composer’s Embedded Self-Service Capabilities

Logi Composer is an example of an embedded self-service solution that can be configured to match the skill level of your end users, while enabling them to modify and share their own visualizations. By doing so, it allows software teams to avoid the unacceptable trade-off between easy-to-use self-service and control over the end user experience.

Built specifically for software teams, Composer is designed to deliver a complete out-of-the box development experience for embedded analytics. Rather than offering a “one size fits all” approach, it provides flexibility and configuration, including fine-grain configurability over:

  • The user experience and interface
  • Data and usage
  • Functionality, from visual authoring to ad hoc analysis
  • Collaboration and content sharing

For example, when creating an individual visual, you get to decide just how interactive the visual should be. Each visual has its own settings, so you can turn on filters for one but not another. This is a very simple example, but it shows you how you can configure a visual so that your analyst has a different set of options compared to your nurse.

To learn more about embedded self-service and Logi Composer, view our on-demand webinar.

Originally published August 7, 2020; updated on August 12th, 2021

About the Author

Yen Dinh is a content marketing coordinator at Logi Analytics. She has more than five years of experience writing content and is passionate about helping audiences stay updated on emerging technologies.