Domo vs Mode: Which is a better fit?

Speaker 1: Hi, my name is Jared. I'm a business development specialist working with Solarium. I'd like to give Domo a rating of three out of five. Prior to using Domo, we were using a service called Pipedrive for our CRM. We wanted to just find something a little bit more dynamic that really was able to work with us and be able to use across platform for all the different agents that worked in our company. We decided to go with Domo just 'cause we wanted to try something that seemed like it was very innovative and new. Domo seemed to be a fresh app out there or a fresh platform out there that really would be able to meet all of our needs and also be pretty similar to what we were using before, but give us a lot more advanced features. Transitioning to Domo was pretty seamless. Our team was able to easily figure out the platform, figure out all the settings and whatnot so we could customize it to our needs. So really the rollout was smooth, nothing crazy, and it was able to get up and running as soon as possible. As far as advice for people who are looking to transition to Domo, I definitely would say to make sure that you have your full IT team and also your project management operations team collaborating on that to make sure that they're all fully understanding what the platform can do for them and how they can best utilize it to help your business grow and advance.

Rohan V.: My name is Rohan. I'm a software engineer at Lyft. And I use Mode Report just for general analytics to understand our data better. And I would give it a rating of a five. I use Mode report at Lyft for different data purposes. It might be for visualizations to better understand our data sets and to be able to get better visibility into the data that we have to understand it. At a higher level, it may be to be able to generate reports, to be able to share with other stakeholders in order for us to be able to better inform them on the data that we do have. Or it may be to even just do playground reporting. Just like being able to investigate data on an ad hoc basis to be able to figure out something on the fly. For all these different purposes, Mode report has been very helpful. I would say that the biggest thing that I like about Mode is just how easy it is to use and how nice it looks. I think the combination of both makes it a very accessible platform to be able to do anything of the use cases that I mentioned before. The fact that visually it has a lot of customization aspects to it, to be able to make it feel how you want it to. And then the fact that all the features are very self-evident, very well documented, and usually pretty intuitive to be able to look at and understand how to interact with it makes it a very engaging solver to use. The two things that I suppose has the most room for growth with regards to Mode that I dislike at the moment is the use of the collections feature and the UI for being able to navigate different data sources. For a collections, being able to organize by maybe teams or purposes is an important feature that I think should definitely be there. But I think the way that I'm navigating it feels not as fluid and not as smooth as the other aspect of Mode. It feels very ad hoc, search driven. Instead of being able to view the collections as a whole, I have to explicitly find it, which only comes from having the pre-knowledge that it exists. And for the data sources, having different engines or different data sources to be able to query data on when I'm using the Python notebooks, or being able to use the data to actually get the sets from, it tends to not have much information about its availability, about if it's actually able to be used with the table in reference. And that tends to mean that you have to have, again, a lot of pre-knowledge on the actual data that you're using to be able to know if the query engine would work for it.