Reminders when using ArcGIS Ideas

825
4
07-05-2023 01:07 PM
DaraBurlo
Esri Community Manager
7 4 825

As stated on the ideas home page, “Your feedback is important to us and we take it seriously. Product team members are subscribed to idea exchanges and labels so that they can keep a finger on the pulse of what you are requesting and build software and services that best meet your needs.” With that being said, I want to offer a few reminders from our Community Resources regarding the ideas program.

 What is ArcGIS Ideas? 

ArcGIS Ideas is a listening channel comprised of a number of Idea Exchanges across Esri Community. Ideas are user-submitted requests for new features and functionality in Esri products. The community can engage with ideas by kudoing/voting or commenting, which helps product teams gauge interest and understand use cases. Ideas are subject to review by relevant product teams at Esri, and we use statuses and comments/moderator notes to provide a response when appropriate.

How are ArcGIS Ideas considered? 

While the amount of votes an idea has garnered is an excellent way for us to understand the demand for specific functionality, there are a wide variety of factors which can play a part in the decision to implement an idea. Factors such as the number of votes the idea has received; the feasibility of the idea within the current product plan; and the impact that the idea will have on other users and existing workflows are among the different factors which impact product teams’ decision making.  Where possible, we will try and be transparent when we communicate back to you about ideas which have been reviewed. We appreciate your understanding that while we love to hear all your ideas, unfortunately not all ideas will be a good product fit or it may take time to implement ideas as they are prioritized among many other development considerations.

How do Esri Staff and Distributors engage with the Esri Community through ArcGIS Ideas?

For each Idea Exchange, some Esri staff will act as Ideas Managers, who will be reviewing ideas and engaging with the community through status updates, comments and more. In addition, other Esri staff members and International Distributors will be able to comment on ideas to ask questions and provide tips or workarounds. Esri staff and International distributors are not able to submit their own ideas, and are encouraged to submit their requests through internal channels.

Idea Submission Guidelines

No questions please.  Idea Exchanges are designed to receive requests for new or improved features and functionality.  They are not meant to ask questions or request help.If you have a question, post it in the appropriate question board to see if other community members are able to help.  If you need immediate assistance with an issue, or are seeking direct communication with an Esri representative, please Contact Us and select the relevant channel (Customer Service, Technical Support, etc.)

No bugs please. Idea Exchanges are not the right place to log software bugs or crashes.  Keep in mind that just because it isn’t the right fit as an Idea does not mean that we aren’t here to help.  Bugs and crashes should be logged with Technical Support.  If working in ArcGIS Desktop/ArcGIS Pro, crashes can be reported by sending an error report.   

What are the idea statuses, and what do they mean?

We value your contributions, and it is important to us that we’re communicating with you about our thinking around specific ideas. We use statuses to communicate updates about ideas back to the community. For more information about the idea statuses and their meaning, please see the ArcGIS Ideas Submission Guidelines. For some additional questions related to status updates, please see Idea Status Changes below.

One particular status I want to point out is the Closed status. Ideas may be closed for different reasons, and we will do our best to communicate and let the community know why this idea isn’t a good match for our current plans. That being said, please refrain from recreating an idea that has previously been closed.

The timing for status changes on idea varies greatly. In some cases, statuses change quickly while in others it may take longer. Remember, just because it is closed right away does not mean that it has not been fully considered. Staff are very familiar with their development considerations and make decisions for the software after reviewing the idea.

Community terms of use

Furthermore, Esri reserves the right to review, modify, delete, reprint or redistribute all content that users contribute to Idea Exchanges. I want to highlight section 2.3 Improper Use of Services. Specifically, the following bullets:

  • Content that is abusive, vulgar, obscene, hateful, fraudulent, or that discloses private or personal matters concerning any person. This includes language, information, or images.
  • Content that is threatening, defamatory or abusive, either between forum members or directed towards a Esri moderator, or a Esri employee or manager.
  • "Rants," "slams," or legal threats against Esri or another company or competitor.

If the guidelines are violated, the post will be removed, and the user will be informed by the Esri Community team about the violated terms of use and the subsequent consequences. For more information, please refer to the Community terms of use.

Thank you again for taking the time to share thoughtful, high-quality ideas.  We truly appreciate your contributions to continuously improving our products and services to help you do your work.

Tags (1)
4 Comments
RandyKreuziger1
Occasional Contributor

@DaraBurlo how are ideas weighted compared to enhancement requests through ESRI support?

LindsayRaabe_FPCWA
Occasional Contributor III

Handy info to have. Thanks for the update. It's good to get a little insight into how things are considered once they hit the Ideas board. 

ChristopherCounsell
MVP Regular Contributor

@RandyKreuziger1 ideas are community driven support. We share ideas and why they would be beneficial, then others can jump on board with kudos and comments outlining why they agree. They can be assessed by votes and engagement. A popular idea that has well-articulated benefits is going to be more considered.

Enhancement requests are a more formal request that is tied to one or more organization accounts. They would be assessed on the business workflow/context, number of users impacted, and $ value of the accounts impacted. A well outlined request, that includes priority/impact, with multiple high-value accounts impacted, will be more heavily considered.

An enhancement request has a section for the community Idea URL, so they can be assessed together.

Ideas can be more lightweight. For example, here's a great one by @alex_mapintel that I don't think quite needs a enhancement request. It's a good idea that we want but don't need:

https://community.esri.com/t5/arcgis-field-maps-ideas/create-a-button-in-field-maps-designer-to-navi...

Here is an idea I made that I also submitted as an enhancement request, as there is more rationale for a business workflow so I think it warrants organizational account support and assessment:

https://community.esri.com/t5/arcgis-survey123-ideas/support-offline-images-in-survey123-inbox/idi-p...

A lot of users create idea but forget to add the workflow or reasoning behind it. A great idea should include why it would benefit you or your business.

DaraBurlo
Esri Community Manager

@RandyKreuziger1 a multitude of factors that go into implementing either an idea or an enhancement. @ChristopherCounsell summed up ideas vs enhancements quite well. In either case, on top of the number of customers requesting the idea/enhancement, the product teams must also consider a few other factors such as; how feasible it is to implement, the business value, the current backlog and time.

If an idea is easy to implement but would only benefit one person, chances are low that it will be implemented. If an idea has provides technical roadblocks or would take a very significant amount of time and/or effort in implementing that too would most likely not be implemented (At least not in the next release or two). If technical difficulties are removed and the business value is high, it would be reassessed. 

Teams also have various priorities within their current backlogs and upcoming roadmaps so they are also weighted against what they can and can't do within a reasonable amount of time. I wish I could provide a magic formula but unfortunately it is not straight forward with all the considerations that the development teams needs to take into account.