How it Works
Here's an overview of the logic behind Taloflow evaluations.
Last updated
Was this helpful?
Here's an overview of the logic behind Taloflow evaluations.
Last updated
Was this helpful?
The Evaluation is comprised of configurable features and requirements tables, scores (and rankings) for products, a collaborative text editor experience, a questionnaire to help you whittle down requirements and features, and various types of blocks to show the data.
All products are rated on all Requirements and Features.
Features are the components that make up Requirements. For example, a Requirement like "Must integrate with our current stack" could include Okta integration and PagerDuty integration as features.
Requirements and Features have 4 possible priority settings:
Critical
Important
Nice To Have
Don't Care
Products can have the following ratings for Requirements and Features:
Great
Good
OK
Poor
N/A
The weights assigned to Requirement Categories (e.g., Integration) also impact the overall product scores.
The product ranking is a simple order of the products based on their score plus using Critical-rated features as a threshold function. You may get a product ranked higher despite having a lower score due to this.
Impact by Requirement or Impact by Requirement Category are calculated by looking at the standard deviation. You may have 5 features that are Critical but have every product rated the same, whereas 5 features that are Nice To Have could show a lot of variance between products, in which case the Nice To Have's have more Impact.
