Knowledge Base

Application Feature Adoption Report

On top of the eight different automated insights reports you can access in YesElf Console, YesElf also offers you extra reports which are custom made by our experts on-demand. If you would like to have this feature enabled in your YesElf Console just contact us. Alternatively, we can send you the custom made reports via email on a weekly or monthly basis.

That being said, let us show you an example of a custom-made report for SAP Concur Application.

Example AFAR

For demonstration purposes, we have made a custom report which includes the application feature usage. Our goal is to help you make your application more successful by making you better understand how it is actually used by your application visitors or users. It’s a report to show the strength of an application by the business functions. Most of our customers have started to pay attention to the fact that there are large parts of the application, which could have been more useful to various kinds of customers. This report gives you a holistic view of your application by the user interactions. 

What this report tells us is:

  • The y-axis represents the number of unique users.
  • The x-axis represents the average user interactions with the application feature.  
  • The size of the circle is defined by the number of interactions, not the number of users. Bigger the size, the more interactions.
  • This graph is divided into magic quadrants. Bottom left (Blue colored circles),  Bottom right (Red-colored circles), Upper left (Green colored circles), and Upper right (Yellow colored circles).
    • The bottom left quadrant (Blue) is showing features that are not adopted yet.
    • The top-left quadrant (Green) shows a well-adopted feature but not as frequently used. That means the majority of the users are aware of these features however use them occasionally.
    • The bottom right (Red) quadrant shows the features which are not well adopted, but once adopted that gets used frequently. These features have potential in them if you can increase the awareness of these features they will be used much more frequently.
    • The top-right quadrant (Yellow) shows the features which are adopted and frequently used .

  • For example, the guide named Fuel Expense was used 2400 times by 338 unique users. Hence the average interaction is 7.10, which finds its place in the bottom right with a red-colored circle. Meaning ‘Fuel expenses’ are added to the expense report very frequently – 7.1 times on average in a month. As this feature is one of the most frequently used but with relatively fewer users, two things should be your focus. One is to find the reason why users are not successfully finishing and the second one how to increase the awareness of the features in the same quadrant so they also will be used by many users and frequently.

  • Another example from the Blue Corner is the feature named Taxi Expense was used 630 times by 252 unique users. Hence the average interaction is 2.5 which places it in the Blue Corner. Meaning each user interacted with the Taxi Expense report 2.5 times within the defined period.

  • Another example from the Green quadrant is the feature named Create Expense Report, which was used 2523 times by 901 unique users. Hence the average interaction is 2.8, which places it in the Green quadrant. Meaning on average each user had created 2.8 expense reports per month.

  • Notice that there is not any circle in the yellow corner for an application feature.   This is important because, ultimately, that is where you want the most profitable, killer application features to be. More unique users making lots of successful interactions. 

This report holistically shows all the interactions with user counts for 30 days. We recommend you keep the beat of changes and nurture what is needed by at least weekly reports. That will give you the edge while evaluating your target market and ensuring you understand their needs and proactively provide solutions.

Tip:  This report is generated from the data of visitor interactions on your application, which are collected by collectors. And are not related to the effectiveness or usage data of the guides that you created with YesElf Editor. In order to have Feature Adoption Report (FAR), you should create, what we call collectors.