
Favro is built with a simple and powerful design principle - complexity should be opt-in.
Anyone who has navigated through a JIRA workflow knows how complex doing even something very simple can get as you wander through endless status and resolution types.
The other key feature, which distinguishes this tool from all the rest, is that a card or a board can exist in infinite places. This is much more important than it may seem. It means you can craft the perfect context for any piece of information.
I'll give you a simple example. Say you're working on a feature. Say that feature has a bug. Say you have a board for all work related to that feature, and a board for all bugs on the project. That bug can be seen in both contexts - while doing your feature stand-up, and while reviewing all bugs on the project.
I cannot overstate enough just how important context is to the flow of work on a project. Being able to craft strategic roadmaps for studio leadership, weekly views for feature or content teams and task-level views for individual artists - all while using the same cards and not having to duplicate them - is a feature I now can't live without. Review collected by and hosted on G2.com.
I have no major complaints at the moment, and most small usability issues or feature requests have been taken seriously by the Favro development team and acted on. Review collected by and hosted on G2.com.

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.




