---
title: "What makes a good recommendation?"
url: "https://gleanly.productfruits.help/en/article/what-makes-a-good-recommendation"
language: "en"
last_updated: "2024-07-22T14:07:18.831Z"
---

# What makes a good recommendation?

### Recommendations are what we think we should do with the knowledge. 

The practical result of what came before.

A recommendation looks complicated with 5 different parts, but it's really quite simple and not all parts are always necessary.

![](https://cdn-assets.productfruits.com/56466d96-c598-4774-97f4-86d4b576909b)

So we have…

-   Move the invoice history to the profile settings \[*Action*\] 
-   from the footer \[*Context*\] 
-   so that customers \[*Audience*\] 
-   can find them better \[*Benefit*\], 
-   which will reduce calls to the contact centre \[*Measurement*\].

We want these to be short enough to be consumed in a few seconds and contain enough context to be understood in isolation.

* * *

### **Recommendation taxonomy:**

As well as context we want to give status and prioritisation.

![](https://cdn-assets.productfruits.com/e27bda64-492b-4779-8776-7e28ccf47b66)

Some example statuses include:

-   **Unactioned** if it's waiting for a decision to be made. 
-   If they don't have confidence to make a decisions they might require **More evidence.**
-   With that evidence they might to **Reject** the recommendation.
-   Or they might **Approve** it.
-   This will send it to the blacklog to be **Completed**.
-   And once it is it will need **Retesting**.
-   A recommendation might also be an **Hypothesis** that we are looking for evidence to support or disprove.

Have you understood what makes a good [fact](https://gleanly.productfruits.help/en/article/what-makes-a-good-fact) and [insight](https://gleanly.productfruits.help/en/article/what-makes-a-good-insight)?