Trello Review

Kanban-style management that is easy to use and quite stable


What is our primary use case?

We primarily use the solution to organize projects.

Trello is mainly for a Kanban-style of product management. You have a set of tasks and you'll move tasks from one phase to another phase. They won't do anything themselves from the organization's perspective, or from the strategy or the product perspective. A user needs to manipulate the information and set up the processes. If they want to introduce any product, they'll make a different board for that product. Jira, on the other hand, for example, has both a Scrum mode for managing projects and having a toolkit as well as a Kanban-style board.

What is most valuable?

The solution uses Kanban boards.

The solution is very easy to use.

On the features side, it's very stable.

What needs improvement?

There aren't as many tracking tools.

If you use Agile as a methodology, Trello doesn't really fit very well. It cannot run at the speed of the team or show pending tasks and backlogs as well. Those types of features aren't really on Trello. Something such as Jira is much more adept at Agile.

The product doesn't handle heavy loads very well. The information does not load quickly once there's a lot of information in the system. IT needs some sort of load balancer to allow it to take on more information and load more quickly.

For how long have I used the solution?

I used the solution for about three to four years. I used it recently for six months on another project.

What do I think about the stability of the solution?

While the features side is stable, and there aren't bugs and glitches, the solution can get overwhelmed if there is a lot of information on it. In that case, it stops loading quickly and really slows down. It can only take so much.

What do I think about the scalability of the solution?

I'm not confident we will return to using Trello, and therefore likely won't expand it. We've been more satisfied with Jira, as it is a bigger tool and serves our purposes better.

How are customer service and technical support?

I've never reached out to technical support. I can't speak to how responsive or supportive they are. It's not something I can talk about.

Which solution did I use previously and why did I switch?

I previously used a different solution, however, it was difficult to load as you added information, such as images. I then moved to Trello, and now I am on Jira.

Trello isn't as good at tackling Agile development as a solution like Jira would be. It doesn't have the feature sets for that kind of process.

What other advice do I have?

I'm just a customer and end-user.

I use whichever solution the project requires. Sometimes I use Trello, and other times the project calls for something like Jira. I don't use Trello all of the time.

The solution is an online tool.

On a scale from one to ten, I'd rate the product at a seven. The only drawback I see is the loading issues. For a different set of employees, that wouldn't matter much. They can wait five minutes for everything to load and they can do their work quickly, after five minutes of wait time. However, for my role, where I'm directly facing customers, it should be quick to get the information while I'm talking to them to address their inquiries quickly. I cannot say "I don't know." I cannot give such kind of answers to my customer when they're on a call with me. 

For my segment and for the roles I've been in, which are mostly the customer-facing or manager-type roles, it should be quick enough. However, for developers or testers, it need not be.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Trello reviews from users
Find out what your peers are saying about Atlassian, monday, Teambition and others in Project Management Software. Updated: May 2021.
510,204 professionals have used our research since 2012.
Add a Comment
Guest