Domo is a full self-service business intelligence software that combines several data analysis and reporting tools into one platform. It helps users connect to multiple data sources, create robust visual reports, manage their data, send messages in real-time, manage projects, and develop new apps.
N/A
Nintex
Score 8.0 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
I believe that companies that record large amounts of data about their product, service employers KPIs, etc, can make the best out of Domo for reporting and data analysis, but if a company handles little data and is not recording this consistently, it will not be of much use.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Exceptional Transform area of the platform - any/all raw data can be manipulated and combined to create datasources that are very useful for our departments.
Visualization layer is clean and is very business presentable. Its simple but includes depth. Visuals can be created/used by all roles throughout our firm, its not limited to analysts.
Ability to communicate and talk about insights in the data - the communication tool is exceptional. I can @ mention specific users to bring attention to a discovery. I can start a private chat. I can annotate and communicate what I am seeing. I love it.
Mobile experience is excellent. When I am on the road i can actively monitor and engage with my team due to my Domo dashboard on my mobile device. Its amazing to run the business and not worry while away from the office.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
Copying Reports - In Excel or Google Sheets, I like to make copies of similar reports and modify them as necessary for users. In Domo, makes copies of reports (called cards) but all copies are connected. So if you adjust the copy, it changes the original. This means a user has to recreate the report from scratch and then adjust it.
Unforgiving SQL - Domo does allow users to write their own SQL codes, which is great. However, Domo's SQL code is pickier than the other SQL database I've used (Metabase).
Text Alerts - Domo's alerts aren't always the smartest. Some of my dashboards are about the sales teams monthly performance and I get notified when there is a change of more than 20%. I always get notified at the start of the month that reports have changed from 'x' number to zero. This is expected because it's a monthly report and I hate getting texts about it. The only reason I don't term them off so I can be aware if something breaks in the middle of the month.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
Domo is a great up-and-coming product. There are many fantastic features that are extremely compelling to our end users, which makes Domo a great fit for our organization. As with many BI tools, there are items on the wish list that could make implementation, administration and usage easier, but I believe these will be addressed over time as the product matures and evolves. The overall concept and approach of this solution has definitely raised the bar in this area of expertise and I would like to see things advance in giving the enterprise tools that will make decision making easier and more robust in the future.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
The built-in user support and intuitive design of Domo makes it simple to learn and use. I find I can spend hours drilling deep, or else quickly gain an overview in just a few minutes. This is a great advantage since the flexibility fits well with the demands of my role. I enjoy using Domo since I know it will give me comparative data across almost every variable I might want to explore - I look forward to it!
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
Pretty responsive. It took a while to get a response in selecting data points for our particular cards. Might have taken about a month? I am not sure if this was something on our end or Domo's end. But haven't had any other issues yet that required additional support from Domo.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
It is a true web-based application so implementation is much easier and smoother compared to other non-web based BI solutions. Also, they offered consulting services during the implementation process, which was helpful. Also, they provided lots of on-demand training courses and videos, which I liked.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
At the end of the day, end-user adoption and taking the burden of IT to build reports was my goal. Demoing and testing many BI tools, DOMO is the one that allowed both to happen.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
I mentioned a "previously un-analyzable" dataset that we were able to visualize in Domo - the result was business re-alignment for increased productivity, cost savings and ROI.
It's tough to quantify the ability to provide insights that have been desired for years but not possible - we continue to amaze our executives and product managers with the analysis we can provide.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
