[READ BEFORE POSTING] MyVR Community Rules
In order to foster a thriving and helpful community, we have created a few guidelines. Please adhere to these rules to keep the conversation on point and useful in the MyVR Community. To help all members feel safe and supported, posts that break the following rules will be removed. Accounts that are repeat offenders will be deactivated. While we hate to remove content and prevent participation, we believe enforcing these rules is essential to having a healthy community.
This is an excerpt from the MyVR Community Code of Conduct. You can find the full document here.
Do Not Spam
Please do not post spam in the MyVR community. Spamming the community includes the following behavior
- Posting advertisements, including promoting competitive services
- Posting solicitations
- Rapid posting
- Repeated posting of similar content
Do Not Post Offensive Content
Do not publish anything to the community that contains the following
- Threats of violence or other forms of harassment
- Racist, derogatory, or discriminatory comments
- Profane, vulgar, or sexually explicit language
- Sexual or violent imagery
Do Not Share Others’ Personal Information Without Consent
Do not share the personal information of others without their consent. Personal information can include a person’s name, address, and contact information.
Do Not Violate the Law or Copyright
You may not post content that violates any local, state, or federal laws. You also may not post content that violates the copyright, trademark, patent, trade secret, or other intellectual property right of another person without explicit consent.
Do Not Post Bug Reports, Feature Requests, or Product Complaints
Do not post bug reports, feature requests, and product complaints in the MyVR Community. Please send all of these concerns to MyVR’s support team at myvr.com/contact/. If you post a bug report, feature request, or product complaint in the forum, we will remove the post and forward your concern to our support team when a response appears appropriate. If only part of your post violates this rule, the offending content will be removed
Awesome idea. Glad to see MyVR providing a proactive community for VR's.
re: Do Not Post...feature requests...
I'd actually LIKE to see the ideas for feature requests posted here too! Once forwarded, why delete the post? You may find support (or not) for the idea, and it may also generate further ideas for the growth of MyVR. Just my two cents
@Jenny-Oest Thank you for the feedback. We are definitely interested in getting input from our users. We are working on some ideas for how to best leverage feature request from the community, so stay tuned!
For now, we are welcoming feedback in the Sneak Peeks room of the community. There, MyVR will post descriptions of potential new features and links to early versions of new features. You gain access to that room once you achieve the Advisor Rank.
@Jenny-Oest It's a great question, so let me be open and honest about our reasons for wanting to handle feature requests outside of the forum:
OUR COMMUNITY HAS A SPECIFIC FOCUS IN MIND: GETTING HELP USING THE PRODUCT
The community was launched to provide a way for users to answer each other's questions about how to use MyVR, and we can't guarantee that MyVR will answer every question (though we will certainly moderate and participate in some threads). Users are obviously not in a position to respond to questions about the company's product road map, so it doesn't really fit within the purpose of the community..
THE FORUM IS THE WRONG TECHNOLOGY TOOL FOR THE JOB
We have a process for collecting, processing, prioritizing, and working on feature requests that we're investing in and maintaining, and the community forum doesn't provide much structure for that - it's just open-ended Q&A format and doesn't do the things we need it to do to manage feature requests.
WE PLAN TO SHARE OUR ROAD MAP IN A MORE SCALABLE WAY
While today we engage with users to prioritize feature requests periodically, there are improvements coming to our feature request process where we'll be regularly sharing more insights into the features requests we receive at MyVR. We also plan to include what we are currently working on, and that's all more scalable to do with the process we're investing in then repeatedly answering one-off questions on feature requests.
WE PLAN TO ADD TOOLS FOR VOTING ON FEATURE REQUESTS
Once we start sharing the most commonly requested features as I just mentioned, we plan to also provide the ability to vote on the feature enhancements that you want most. This is something we do ad hoc these days periodically (via surveys and interviews), and we'll be investing in a broader and more automated process around this. This will be a better and more scalable process for prioritization than free form discussion.
USERS CAN SOMETIMES OVERWEIGHT THEIR OWN FEATURE REQUESTS
It's human nature to place the most emphasis on the things we want, and then get upset when they're not delivered. MyVR is building for a broad audience of users and must prioritize based on the collective needs. There are tons of things we COULD build, and thus there is an endless list of questions we'd need to answer, and then potentially explain/debate why we're not doing a particular user's request right away.
This all takes us away from actually building the product, so we'd like to have a better way to make our plans clearer to our users and let them have a voice. If a feature doesn't get worked on, it will be because it didn't get enough momentum from the broad base of users who are telling us what they need to run their business via their votes on features. This will be easier to grasp when you have the ability to vote on features then it would by just reading forum Q&A.
TIMELINES CAN CHANGE
Sometimes, road maps change, and so giving feedback on new features or updates about when they're coming just cannot be done effectively or in a scalable manner through Q&A. Let me give a specific, real example. We got approved this past spring by Airbnb to integrate with them. It wasn't scheduled on our road map because it wasn't under our control as to when they'd allow us to integrate with them, but once approved, we had to jump on it immediately, given the feedback we'd gotten from our users about the importance of an Airbnb integration. So, we had to push back some other items which were lower priority than Airbnb.
Communicating these changes in real-time can be really difficult, particularly to a user who personally doesn't want Airbnb and wanted the feature that got delayed so that we could integrate with Airbnb. We're going to need a scalable way to manage this and share updates with users, and just Q&A doesn't work and timelines can end up being fluid. Anyone who has worked in product or engineering for a software startup knows this well.
THE (RESTRICTED) SNEAK PEAKS FORUM SECTION WILL BE WHERE NEW FEATURE DISCUSSIONS HAPPEN
As outlined in the forum overview documents, there's a room that is not immediately available to all users, but can be earned by our members who add the most value to our community. This room is where we plan to share more granular details around what's coming, screen shots, and potentially beta testing so that we can get user feedback.
So in short, since we have another process in place (and being further developed) for this, feature requests don't make a lot of sense in the forum. Since we want the forum to be a place where you can expect to get answers from others or from MyVR, and feature requests will likely go answered (and potentially be a distraction away from the process we WANT users to engage in for this), we feel that having a bunch of unanswered feature requests in the forum will negatively impact the user experience.
p.s. I'm even taking a little bit of a risk sharing the process we have upcoming around soliciting votes on feature requests, as I know that is still at least a few months away. So bear with us and submit your feedback via the feedback form in the product as we continue down this path!
Thank you for all of that insight. You've clearly thought through all of the right things, so I support your direction 100%.