Delivering Product Value Means Delivering Insights

Hello, everyone. I'm Charles Caldwell and I lead product at Logi Analytics. In my career, I've focused on enabling humans to make more effective decisions by delivering data-driven insights.

I think we can take for granted that at this point, software has in fact eaten the world and that applications are a major part of our daily lives, both professionally and personally. And one of the key lessons I've taken away, especially from the early days of internet commerce was that the most successful applications were those that didn't simply facilitate transactions but focused on delivering insights. Insights that helped me make decisions faster, helped me be aware of options that were available to me and help me make decisions that were more effective for what I was trying to accomplish. And the reason applications are so effective at this is because they take generalised technology like analytics and AI, ML, blockchain, geospatial, and they apply those to solving specific problems. An application exists in context of the problem that it solves. And it's got the ability to provide insights in context where those insights have the most meaning and immediate impact on a problem that your end users are trying to solve. Applications are also purpose built and they take on the structure of the decisions to be made and the actions to be taken. And applications, especially with mobile phones today, are often very close to where the action takes place. So, they take those technical capabilities and they're able to translate them into real world value by translating them directly into action.

Now, especially for those of us building B2B applications, I know we're feeling a lot of pressure right now to make our applications deliver the same level of usability that we see in a lot of the consumer applications. And we do a lot of surveys on this at Logi Analytics and I looked at a lot of research in the market on this to keep myself informed. And frankly, every survey that I see, throughout my career, where we ask professionals in an organisation about analytics, they generally come back stressing the same thing, and that is we need more and there's lots of gaps. And we see that today, analytics is increasingly essential to the daily lives of your end users and the seismic shift to a hundred percent remote work that we've all experienced during the pandemic has really served to highlight that this need is true across all types of work. It's not just sort of the knowledge workers in the ivory tower. It's really everyone. And the gaps are still very large, with most workers reporting that they actually spend most of their time just looking for the information, trying to find the information that they need and very often, once they do find it, it's not presented in a user-friendly format that they can take advantage of.

Now delivering insights in your application, frankly, there's a lot of different ways to do it. And today, I want to focus in on three specific ways that you can sort of take away and think about that'll allow you to add value to your application by delivering analytic capabilities within the user experience of your app. I'm not going to talk a lot about traditional reporting today, providing summary and kind of detailed listing of data that is a valuable use case. I think we're probably all pretty familiar with that use case. So, I'm going to admit it but don't necessarily forget about it.

The three that I really want to focus in today that you may not be aware of are first the idea of delivering an insight right at the point in your application where a user is going to take an action. The second one I'll talk about is enabling your users to explore so they can discover options that they may not have previously been aware of. And then the third one I'll talk about is providing recommendations that will enable your end users to take a better or more effective action than they might have otherwise had you not given them that recommendation.

So, let's take a look at the first example and it's one we're all super familiar with from Amazon. So, and really the idea here is if you want your end users to make decisions faster, more efficiently, if you can provide an insight that increases their confidence right at the point of actual. That's going to help them decide more quickly. And Amazon, frankly, has done an amazing job of this when they're providing review summaries that show that summary rating and how many reviews and you hover over and it shows you the distribution of the scores, the review scores that summary is often enough, frankly, to move me from this looks like an interesting product to hit the 'Buy Now' button. In the context of your application, you want to ask a few questions: 'where are users making a decision to take an action?', 'Where are they buying a product or approving a purchase or prescribing a medical treatment, or selecting a vendor or identifying a risk?'

At each one of those points, ask yourself, is there an insight that I can provide right in line within this user experience that will help them know if this is a good decision or not and if they're taking the right action and then utilising very targeted data visualisation within that user interface in close proximity to where the user would take the action, you can deliver that insight.

Now these types of embedded analytics can be really straightforward if I'm building a CRM system and I need to know if I should follow up with a contact based on a recent interaction, something as simple as if their order is on time and how long has left to deliver that order, or if the contract is still unsigned and how long until the plan closed date. These types of insights don't need to be complex in how you're presenting them. They really just need to matter to that end user and helping them decide, should I call this individual? Should I text this individual? Should I reach out to them? Or maybe everything's okay and I can leave them alone right now.

You also get massively improved usability because if I got to this contact screen and was wondering these things, I might have to go of elsewhere in the application to find the information and then navigate all the way back in order to then take the action. So, you can really get a lift on your usability with the right targeted insights embedded in the application itself. Now, there are times when you might not be able to define that perfect targeted insight, and you know that your end user has more open-ended question or they're going to get stuck and want to ask more exploratory questions why questions or good examples of these 'why is something happening.' In that case, your user is moving from a state of having kind of a targeted decision. Am I going to buy this product? Is this transactional risk that I need to flag? And they go more into a browsing mode. They're searching for options or they're trying to explore relationships or they're looking for explanations.

In the example of Amazon, this happens when you don't like the product review, right? You look at the product review that doesn't quite look right and you start reading individual reviews. You start looking at comparison products, you may abandon the Amazon experience entirely, and you may go look at a buyer's guide somewhere to explore the category. Now, this type of decision support, this type of analytics, frankly, can be a lot more challenging than the targeted insight. Because it does start to open up to feature sets and capabilities that are richer and more open-ended self-service data discovery, guided analytics. But again, the place to start from a design perspective is to ask yourself, are there potential relationships in the data that aren't readily apparent from the standard user experience flow of the application. Are they things that the users in the course of using the app wouldn't happen across or be able to see or notice? Is there data that a user should compare that they just aren't normally going to see when working with the application and in those cases, you can start to represent that information or present that information either as a guided flow or open into discovery and in guided flows are much like a consumer reports type website. You arrange the information and to related categories like in this case, we've got a wine CRM and I've got key wines that I'm selling. And I'm enabling my end user to pick wines and then explore the data. What are the income range of the wine buyers? What countries are we selling on? If we're going to run events, what are the weather patterns in the areas where we would run promotional events so that we can schedule those.

I can structure an exploratory experience that can allow an end user to start to ask about options, ask questions, and get more information and start to gain some of the benefit of making those comparisons. Now at the other extreme end, you may just give the user a blank canvas with data and let them go crazy on slice and dice and filter and drill to explore all of the options on their own. And it's really going to depend on your persona and how open-ended their questions are. And of course, what their skills are, how analytically savvy is that individual. Now, again, the trick here is that the feature requests can start somewhat innocently this can look like a pretty simple high-level dashboard with a few interactions but very quickly, and especially as you get into the more open-ended discovery. You do start to get into some very complex feature sets, filtering, changing metrics, drill down cohort analysis there's a lot. There's a lot that can go on there and it can cascade very quickly in terms of complexity. So, you'll just need to balance that as you're thinking about implementing these types of discovery use cases.

Now the final sort of concept that I want to talk about is recommendations and very often both the inline insights and guided exploration, they can feel like a recommendation. And in this category, I generally was reserved for instances in which as a product team. I'm able to generate a recommendation on the end user based on one of three things, either best practice. So, industry or subject matter expertise tells me in this situation, you should do X or Y. Past practice, what has this user done in the past? And if I can, I actually want to say, what is the user done in the past that led to a good result. So, if I've got the data to do that, that's an even better recommendation on past practice, where have we prescribed to a patient and the clinical outcomes were good as an example, that's a good past practice. And the third one is peer practice, and this is also known as benchmark. What are other people doing? What are other organisations doing? And for those organisations that are like me? Are they getting better results or am I getting better results? And if you can help me understand why I'm getting better results or why they're getting better results, it'll help me change my own practices.

Now the presentation requirements here can be very simple we've all experienced Netflix recommendations, and this is actually an example of past practice and its past practice with good result because they know our viewing time. We can rate as well, the movies. So, they've actually got a way of saying. These you've watched these kinds of movies in the past and liked them. Here are some recommendations that we think you'll like in this case you can see; I was spending time watching movies with my daughter and they're queuing up more options for us to spend some quality time together because they know what movies we liked watching together in the past. That's a good example of past practice. The displays or the, the processing can also be much more complicated than this you can do alerts and notifications and benchmark analysis can actually become quite a sophisticated set of analysis. So, it really just depends the level and the types of recommendations that you're trying to make. And frankly, this is where even while the front-end presentation may not be complex, the backend processing on recommendations is where you may need to lean on a technical platform for things like AI/ML capabilities to generate those recommendations.

Now having given you sort of three high level use cases to think about in terms of adding value for your end users using analytics, you definitely have to consider how you're going to get there. And in full disclosure, I'm lead product at Logi Analytics, as I said, and we build development platforms that help application teams deliver embedded analytics quickly. So, you can expect I'm going to be biased and tell you, you should go buy a platform, but I'm actually not going to tell you that need to go buy a platform. Not necessarily.

As you're building out analytic capabilities, there are definitely times to take a build versus a buyer or a partner strategy. And when you have very targeted use cases, the simpler use cases, those inline insights, those absolutely in many cases can be built and maintained using some visual libraries and your dev team cranks out the use case and you're good to go. Also as you're thinking about early POC. So, if you're trying to validate requirements, you, you clearly don't want to over invest before getting some validation. And those are also great times to do some build on your own to validate those initial requirements and get to an MVP where I'm going to suggest you sort of start to have some caution is as you're getting into the more complex and open-ended use cases. And it's a combination of a couple of things, sophistication of front-end requirements. So, how much interactivity, how specialised do I need to define filters and share them? Scheduling collaboration, these types of very interactive, robust front-end features. And then it's also the backend processing. Where do I need AI/ML, more sophisticated data access, search use cases as well as a graph database use cases. These types of complexities are aware of platform is going to start to help you, especially as you're scaling to larger data volumes, larger number of users, as well as more product personas that will start to drive a higher diversity of requirements. Building these capabilities purely out of your development team, frankly, we'll start the swamp, your roadmap.

So, if you analytics starts to become a real key feature set for you, you're going to want to start looking for technology partners either in a by partner type strategy to help accelerate some of this and create some repeatability for you and your dev team.

So, the, the core idea that I want to leave you with today is analytics can be complicated there's a lot going on out there in terms of types of analytics, the algorithms, the technologies are always evolving from a design perspective, it always comes back to value for the end user and the question that I always like to ask myself and kind of reground myself in is if I can help my end user know something that they didn't know before and we'll help them do something different that will create value for them and I can do it right at the point of the action in a very targeted. I can help present them options and exploration when they're in a place where they're confused, they need relationships, they need more options. And when possible, I can give them recommendations to help them be more effective. And if you use that framework, I think you'll find a ton of opportunity to get unmetered from the complexity of the technology and really find opportunities to create. Targeted value for your end users using embedded analytics.

I appreciate you all spending time with me today. I'd love to hear from each of you about the applications you're building and how you think about creating more value in those applications. With data-driven insights, you can find me on LinkedIn.

Love to hear from you. Thank you so much.