In this lesson, we will look at a scenario where a story is not performing well for the users who interact with it due to design choices that were made when the story was built. In the following video, we take a closer look at the scenario, why the story isn't performing well at the beginning, the troubleshooting steps, and the steps taken to optimize it.
Using the understand, plan, and build approach, user requirements are gathered to better understand how users interact with and use the story. The Performance Insights tool is used to analyze the story processes in the current story to better understand the performance issues and then, finally, it is optimized to meet the users' needs.
One of the best practices in story design is to start a story with an overview of the data using aggregated data with limited drilldown for a single measure. Using the overview, the user is able to identify the subset of data that interests them, for example, a specific country or company code. By filtering they can define the criteria they are interested in and then view the details where they get the filtered view on a granular level, for example, in a table that displays their filtered data.