SIGMA

My main use case for Sigma  is to check on the status of our accounts, my accounts, and my programs. I love using a tool where I can analyze the return visits of leads that we've already sent to customers.

I use Sigma  for analyzing those return visits by loading it, setting the fields for a particular account of mine, and I can see the leads that we've sent. In analyzing, I let Sigma do its magic and can run another report that tells me every time one of those lead accounts has returned to PeerSpot to continue their research. This has been an invaluable resource for me to share with some of our customers to help them understand the value of our audience in showing how their leads are continuing to visit and do their research, which provides our customers with great intelligence for their account scoring and lead handling.

I'm using Sigma to check on all the programs. That was one of my favorite use cases, but to see how many leads have been delivered, to see how many reviews have been collected, to see how many review interviews have been set up, how our outreach center is contacting prospects for leaving reviews. There are a lot of different use cases for Sigma.

Having those dashboards set up in Sigma has made things easier for me and my team because it's just going into one report. There are a couple of different tabs in the same report rather than opening multiple different dashboards and reports from Salesforce , and that just speeds things up and saves some time.

Sigma has positively affected my organization by saving us time in accessing information, which ultimately gets us to complete projects faster.

I understand the value and would say I get through tasks 25% faster using Sigma.

Sigma can be improved in terms of speed; it would be great if it could process the data even faster. I think it's more of our use of it that I'm not responsible for in getting the Salesforce  data into Sigma. Sometimes I can't find what I need or the data isn't quite uploaded correctly, but I think it's a problem of the entry into Salesforce, not getting it over to Sigma. It would be nice if the reports also included more graphics and were more visually pleasing or compelling rather than just data.

We started using Sigma as a company about a year and a half ago.

I think Sigma is stable.

I haven't used customer support at all.

Before Sigma, we used a different solution, but I don't remember what it was called. I wasn't involved in the decision to make the switch, so it's irrelevant. Sigma is a good choice.

I have seen a return on investment with Sigma; we already said that it saves about a quarter, it gets me to answers about 25% faster.

When it comes to pricing, setup cost, and licensing, it has nothing to do with me.

I don't know if my team evaluated other options before choosing Sigma.

I'm not doing any customization with Sigma. The ease of use is there. It takes a little while just to get used to it. Sometimes when I'm running an estimate for leads, in my haste, I try to get the answers, but I need to wait for it to finish processing all the data, which is totally reasonable. But it's pretty easy to use.

My advice for others looking into using Sigma is to make sure you set up the reports and the dashboards in the most efficient way. Ask for feedback from your teams if multiple people are going to be using it. Because once it's set up, it's a very powerful tool. But if not all the perfect data is in there, then it's just not going to do its job.

On a scale of one to ten, I rate Sigma an eight.

The project I worked on with Sigma  involved creating a migration assessment tracker. We fetch all the data from the Tableau server and the cloud through the metadata API or the REST API. Then our data engineering team puts that particular data through the Alteryx  workflow, refines all the components, and pushes the data into Snowflake . We then connect Snowflake  with Sigma . With that report, you can compute how much time it will take to migrate a particular site, how many workbooks exist, how many tabs are in Tableau, the duration required, and the complexity of the workbook based on the calculations.

The report also shows if any workbook is associated with upstream workflows or how many published data sources exist. We brought this information onto Sigma and created our report accordingly to estimate the migration time.

It serves the marketing team by ensuring that when receiving a project involving migration from Tableau to Sigma, they can estimate the time required. It estimates all efforts based on these complexities, the size of the Tableau server, and the number of users involved.

Compared to other BI tools, each tool has its own capabilities. Sigma has excellent features, such as lookup tables where you can easily bring data that are not interrelated or at different granularity. Because in Tableau, you can see various LODs. To create those same functionalities in Sigma, we generally use lookup tables and replicate that functionality there. It has multiple good controls such as segmented controls. It also provides tab options with the inbuilt feature in the interface itself. If you need to create a similar thing in Tableau, you need to create separate sheets or buttons. Sigma provides several cool features. You can create multiple visuals, and the maps functionality is very good in Sigma. We explored all the charts that Sigma has provided in its interface. Although Sigma is introducing some AI capabilities, that has yet to be explored from our side. We have explored the interface part, creating dashboards, and managing data sources with joins and relationships.

As we are exploring multiple features in Sigma, I think Sigma can add more functionality. As Power BI gives multiple modeling options in its interface with the query editor, those features can be added in Sigma for intuitiveness or for making the data very clean. From the dashboarding perspective, it performs well. However, from the modeling perspective, it requires more capabilities that can be added in Sigma.

The main improvement needed is in data modeling capabilities. If they add those features in the near future, it would be very helpful for us to implement the same or do the data cleansing part in the Sigma tool itself.

I have almost eight years of experience working with Tableau and Power BI. For Sigma, I have been working for the past two years.

I am not sure if my company purchased Sigma through the AWS Marketplace .

We did not face typical errors during our project with Sigma. In the near future, if we receive support from Sigma, that would be more helpful. There are multiple teams in my organization working on Sigma projects. We have not connected with Sigma support yet. In the future, I can provide more detailed reviews.

If data is substantial, in Sigma's case, the data is always live. It is not a kind of extract, whereas Tableau provides both live and extract functionality.

On the scale of 1 to 10, I rate Sigma an 8.5 because there are multiple tools whose setup needs to be done, and the servers are also on physical machines such as Tableau server for maintaining all those components. As Sigma is a cloud platform, you do not need to do all that maintenance work. Regarding visualization and data modeling, as mentioned earlier, they can improve on those aspects. The functionality and interface have improved significantly with their latest versions. Previously, all options were on the left-hand side, and now there are floating themes at the bottom where you can easily select all options and create a good dashboard.

In Tableau, you have filter actions where you can select any particular sheet, click on that particular button, and the data is filtered accordingly. You can do a similar thing with the help of actions in Sigma. You can even change the dynamic axis. If you want to change the X-axis and Y-axis, you can do it with the help of controls, the segmented controls, and with the help of actions.

Setting up Sigma is not complex. If you know all the components through their documentation, you can easily implement it as the documentation they created is comprehensive and contains all the necessary information.

As we are a hybrid team, operating from India as well as the US side, we do the development part and our US team connects with the clients and deploys all components in the environment. We are primarily developers, but we can also manage the publishing and other tasks.

Regarding the differences between Sigma and Tableau, for visualization, Tableau is the best tool I have worked with because you can change the visualization accordingly by creating different calculated fields. Sigma could add more visualizations. In Tableau, you can do forecasting with the help of the analytics tab. If Sigma also adds these features, it would be beneficial. In Tableau, there is a smoothing model you can select to do forecasting, create good trend lines, and add effective reference lines while creating trends.

I prefer to remain anonymous. Based on my experience with Sigma, I would rate it 8.5 out of 10.

We use Sigma  for all of our data visualization and reporting. It works off of Snowflake , so it pulls in data from Salesforce , NetSuite, our website, and Google Analytics . Via Snowflake , we're able to have unified, single views. Sigma  serves as the visualization and reporting front end.

Sigma is widely adopted across our organization for creating dashboards and reports. The solution feels more modern than Tableau , and it's not as sales-oriented, offering a more generalized approach. The visual appeal of Sigma stands out, as the graphs and charts look visually nicer compared to Tableau . The use of Sigma in decision-making, presentations to customers, and reporting to investors showcases its value in handling data-related tasks.

I would love to be able to create my own reports in Sigma, as I can do in Salesforce . Either we are not using it properly, or the software is too complicated. It would be great if there was a way for me to create reports without relying on a data analyst. I'm interested in the upcoming AI co-pilot to enable natural language generation of visualizations and reports. Also, the marketing materials did not match what I feel we've received. Regarding pricing, Sigma's pricing doesn't allow more people to have the ability to create their own reports. We have very few admin or report creator licenses, while everyone else is on a view-only mode.

We have been using Sigma for around a year and a half.

We previously used Tableau. We found Tableau to be a less modern solution, and we hoped Sigma would be more self-serve. However, it's not more self-serve than Tableau.

I didn't perform the initial setup. The migration from Tableau took quite a bit of time, indicating that it could benefit from being more straightforward and easier.

While I don't have specific metrics, Sigma is integral to our business processes. We use it in decision-making and for customer and investor presentations. It's essential for everything data-related within our company.

The pricing of Sigma is a concern, as it restricts our ability to provide more users with report-creating capabilities due to the high cost of admin or report creator licenses. Most users have view-only access.

I did not participate in the evaluation process, but our data analysts considered other solutions besides Tableau and Sigma, though I can't recall which ones.

Determine your requirements carefully as there are many data visualization tools available. Each has pros and cons, so ensure Sigma fits your needs. Additionally, I rate Sigma an eight out of ten because it meets our needs, but there are some disappointments with the software.

Our primary use case for Sigma  is reporting.

The most valuable feature of Sigma  is the detailed reports. These reports offer a lot of details and have positively impacted our ability to generate better reports for the organization.

Sigma could have better reports.

I have been using Sigma for a year.

I use Figma for UX wireframes. My UX team creates the actual UI and prototypes to demonstrate UI behavior. Afterward, we collaborate with the PO and PMs to refine further. Once finalized, the UI wireframes are used as a base for developing the actual UI, leveraging CSS provided by Figma for consistency. During testing, Figma serves as a reference for checking alignment, font sizing, color, and behaviors.

Figma offers the ability to extract CSS to ensure consistency between the design and the actual UI. Overall, Figma facilitates many collaborative uses along the project pipeline, enhancing teamwork efficiency. The top two features are collaboration and commenting. Multiple users can view and interact with designs simultaneously, much like Miro. The CSS extraction feature ensures that the rendered page matches the design, reducing discrepancies.

There is room for improvement in Figma's versioning capabilities. I feel there is a lack of change tracking, which affects clarity in collaborative environments. Implementing version history similar to code repositories would aid in tracking design evolution. Additionally, Figma lacks adequate structure for organizing designs. Implementing features for better grouping, labeling, and categorizing would enhance usability.

I have used Figma within the last few months.

Figma is a stable product without notable breakdowns or bugs.

Previously, I used InfinityForm or a similar tool, and I find Figma much better than that.

I was not involved in the initial setup as it was managed by a different team.

If I were to add a feature to Figma, it would be versioning to aid collaborative teams in tracking design changes over time. I rate Figma a six out of ten due to the need for better structuring and labeling of diagrams and the absence of versioning.