Actions
Forum Thread Details
  • Replies 7 replies
  • Subscribers 2559 subscribers
  • Views 1066 views
  • Users 0 members are here
Related

Where Do You Prefer to Post RoadTest Problems to Alert the element14 Team?

rscasny

A program as complex as the RoadTest program is bound to have problems. These problems can range from application-form problems to documentation problems to hardware/software problems. Some of these problems can be resolved by other roadtesters, kind of like a virtual help desk. But there are some problems that require the sponsor's support team to get involved. If you are a roadtester or applicant, the first step in resolving the problem is alerting the element14 team or myself, the RoadTest Program manager.

In the following poll, I would like to get your input on where is the best place to post a roadtest problem so I can help you get support in a prompt, efficient manner.

There are a couple of places to post a roadtest problem. They are:

  • Comments section of the roadtest page
  • Forum of a specific roadtest
  • Community's Feedback and Support page
  • Direct contact (messaging or email)

While I think posting the problem as close to the source (the roadtest page in the comments section) is my preference, I would rather defer you, the roadtesters and members. I want to be as convenient to you as I can.

If you have the time, I would encourage you to vote.

Thanks.

Randall Scasny
Roadtest Program Manager

Parents

  • My personal preference is to go directly to Randall/Sean in private e-mail. Failing that, I have gone direct to company in some instances. There was once where we had PMs between contestants to cross-verify findings.

    This is because, frequently, such issues I encounter are of a complexity and severity that only the manufacturer can sensibly deal with. I would rather avoid publicly revealing such issues until they've had a chance to work through it with me or it has been verified as a non-issue in which case, no disclosure is necessary. This can (in some cases) save the manufacturer some needless public embarrassment and/or protect existing users from having a cybersecurity vulnerability dropped on them with no notice (for example). I ensure I do my due diligence first, before claiming an issue in the first place.

    Minor issues usually won't result in a contact at all - that will merely be noted in the review.

    - Gough

Reply

  • My personal preference is to go directly to Randall/Sean in private e-mail. Failing that, I have gone direct to company in some instances. There was once where we had PMs between contestants to cross-verify findings.

    This is because, frequently, such issues I encounter are of a complexity and severity that only the manufacturer can sensibly deal with. I would rather avoid publicly revealing such issues until they've had a chance to work through it with me or it has been verified as a non-issue in which case, no disclosure is necessary. This can (in some cases) save the manufacturer some needless public embarrassment and/or protect existing users from having a cybersecurity vulnerability dropped on them with no notice (for example). I ensure I do my due diligence first, before claiming an issue in the first place.

    Minor issues usually won't result in a contact at all - that will merely be noted in the review.

    - Gough

Children
  • in reply to Gough Lui

    Same here, I'd rather go the direct contact route as I'd rather not publicly embarrass the manufacturer with something that they could fix "in the shadows". Or I'd rather not display publicly my own lack of knowledge...

    In the past, I've also asked questions on their public forum as it felt the right place to get a better chance of reaching to the product's specialists.