element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
RoadTests & Reviews
  • Products
  • More
RoadTests & Reviews
RoadTest Forum 2 Roadtests, 4 Reviewers, 0 Reviews: When A RoadTester Does Not Complete a Review
  • Blogs
  • Forum
  • Documents
  • RoadTests
  • Reviews
  • Polls
  • Files
  • Members
  • Sub-Groups
  • More
  • Cancel
  • New
Join RoadTests & Reviews to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 54 replies
  • Subscribers 2760 subscribers
  • Views 7118 views
  • Users 0 members are here
  • scasny
Related

2 Roadtests, 4 Reviewers, 0 Reviews: When A RoadTester Does Not Complete a Review

rscasny
rscasny over 7 years ago

Recently, I selected roadtest applicants who were both new roadtesters  and have not participated much on the community, primarily because I have had some other members tell me that I am using experienced roadtesters too much. (This is never my intent; I select the best applicants. When I roadtest writes only a 1-sentence application, I don't have much to go on and these folks usually don't get selected.)

 

I had to report roadtest results to 2 sponsors. Well, the results for these 2 roadtests were not great: 4 roadtesters haven't done their reviews, they haven't logged in for 3 to 4 months, and they have not responded to all our follow ups that we do for every roadtest. Before I selected these 4, I contacted them and they agreed to commit to delivering the review in 60 days.

 

Now, 2 roadtests is a fraction of all roadtests. For many roadtests we get 100% compliance. I'd say overall we are getting a compliance rate in the upper80s/lower90s, which is good and a far cry from where we were 2 years ago when we were at the sub-20% level.

 

Speaking for the sponsor and myself, we understand that in some situations people will be unable to complete the review. After all, people do get ill and emergencies do arise in everyone's lives, so I never expect to have 100% compliance for every roadtest. I recall someone who had a tree fall on his house in an ice storm. That's a major tragedy in my book. Of course I would not expect a review. But these instances are atypical and very few compared to all roadtests and roadtesters I deal with.

 

While we give the official roadtesters the kits and the shipping for free, someone does pay for these things. Typically, the sponsor pays for the kits and element14 pays for the shipping costs to the roadtesters. But we are more than happy to do this because we value our roadtesters' opinions and we are happy to absorb the costs when the reviews are published.

 

But the question comes to mind: what happens when a roadtester doesn't complete the review:

 

1. The sponsor does not receive all the feedback he is seeking when he enrolled in the roadtest program as a sponsor.

2. Someone who does not complete the review prevents someone who could have done the review from doing it.

3. It prevents our members from learning about the product.

4. It damages the credibility of the program.

5. The delinquent roadtesters prevent themselves for being considered for a high-priced product. If I can't reliably use someone for a $35 US roadtest, how can I expect them to do the review for a $3500 US roadtest!

6. I am placed in the embarrassing situation to explain why 4 people I selected did not do their reviews.

 

There are other reasons but 6 reasons is enough to make my point.

 

It is my responsibility to get the required results for both our sponsors. My bosses also have expectations and expect that I will solve problems. I want people to use the RoadTest program to have fun with technology,  and get some products or equipment that they may not have the budget to get on their own. But I also need mature, responsible members who are engaged in our community, demonstrate an appropriate level of professionalism, and are responsive to our follow up requests. I like to think most roadtesters are professional. I surely do not think these 4 delinquent roadtesters represent the RoadTest group.

 

But going forward, I will have to modify my approach in selection somewhat. And I probably will not hand out all the kits if I don't feel I have enough roadtesters who are knowledgeable about the product, and are mature, professional and reliable. If you were in doubt that I am very serious about people completing their reviews, I hope this discussion makes my position very clear. I apologize to all my loyal and responsbile roadtesters who do complete their reviews. But this is a community and I have to communicate my concerns as well as be open to new ideas and feedback: it's a two-way street.

 

If you can't finish the review, contact me and tell me or my colleague danzima why. If you need a bit more time, that's fine if you need to do more testing. (Needing more time to finish your Differential Equations homework or finishing your digital electronics lab is not a reason for needing more time.) Communicate and keep us in the loop; you will find in your career that developing communication skills is as important as honing those engineering skills. Even if you received a non-working product, you are still required to post a review. Put it out to the members: "I took these readings and I believe it's faulty. Help me troubleshoot it." There are plenty of eager members who are more than happy to help.

 

I want everyone to benefit from a Roadtest. I think completed roadtests are a great place to learn. I think they are a fantastic vehicle for the new engineer who is trying to shine in their first job interview. Read our e-book on IoT careers to learn more shining in a job interview: https://www.element14.com/community/community/publications/ebooks?ICID=hp-iotcareerebook-rotational#?ICID=ebooks-downloa…

 

But you can't reap the benefits of the roadtest program if you don't do your reviews.

 

Sincerely,

 

Randall Scasny

RoadTest Program Manager

  • Sign in to reply
  • Cancel
  • shabaz
    shabaz over 7 years ago

    Incidentally, if the particular RoadTests  are for equipment we may likely have, or are low-cost (I still have $200 Project14 prize budget to use up) I'd be happy to do a quick review if it increases the chance the manufacturer will be happy for future RoadTests too, otherwise it is unlikely they will want to do it again I guess : (

    • Cancel
    • Vote Up +5 Vote Down
    • Sign in to reply
    • Cancel
  • rscasny
    rscasny over 7 years ago in reply to Fred27

    Thanks.

     

    No, we are trying to see how we can get all the applicants involved in the Azure Sphere board.

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • Cancel
  • Fred27
    Fred27 over 7 years ago in reply to rscasny

    They all sound like good ideas. I don't think there would be any harm suggesting some criteria that might help get you selected though. "Preference given to members who have watched and commented on the onboarding webinar", "Preference given to members who have already written a blog about a development board". Something like that. They can all be at your discretion, but a hint at some expected prior effort.

     

    I've also been wondering if there's any way experienced road testers could mentor those who want to be selected. However, if the problem is a lack of effort rather than a lack of skills on the part of the missing road tests then I don't suppose there's much that can be done.

     

     

    I notice that the Azure Sphere dates have been pushed back a bit. I hope that doesn't mean that of the 359 applicants there weren't 50 good ones. image

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • Cancel
  • rscasny
    rscasny over 7 years ago

    Hi All.

     

    I'd like to thank everyone who has participated in this discussion. It's help me clarify the problem and think about solutions.

     

    Change Idea #1: I used to send a standard availability email when I notify the roadtest finalists wether they are new roadtesters or experience. I will start sending out a separate email for new roadtesters that spells out the responsibilities of a roadtester and the consequences of not doing a review.

     

    Change Idea #2-- I am thinking that I should have an onboarding webinar for new roadtesters. It may be a way to build relationships with new people and they can hear from me and what I expect.

     

    Change Idea #3--I have had some instances when a member was not available because he was doing another roadtest. I am considering setting up later due dates for these people instead of choosing someone else who wrote a below average application.

     

    Change Idea #4--If I got 5 kits to hand out and I honestly feel I don't have 5 reliable roadtesters, I may have to select less than 5 and reserve the other kits for a project.

    • Cancel
    • Vote Up +12 Vote Down
    • Sign in to reply
    • Cancel
  • balearicdynamics
    balearicdynamics over 7 years ago

    Hi Randall,

     

    I am so sorry to read this. The thing that leaves me really surprised is that there are many people like this than expected. I am the first that I missed some road testò this has been due to some my personal problems, but I know this is an excuse. And I had the opportunity to make other road test after this debacle and I appreciated this very much.

    I suppose what you need is a solution or at least a proposal. The idea may be that there should be a road test preview, before the deadline. I mean, after sending the first email recall in the mid of the road test period, if you have no answer or there is not draft already written by the roadtester, you can at least suspend him and do something before the expected period ends. This does not solve the problem that one piece of hardware has been tossed out but at least there is something that can be done respect the customer/producer involved in the roadtesting.

     

    About the value and importance of road tests, I have the intention to mention the roadtesting opportunity as a great free resource for makers in one of the chapters of the book I am writing, I have already sent you a message about this. take a look and let me know if it is worth to have a contribution by you.

     

    Enrico

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • Cancel
  • robogary
    robogary over 7 years ago

    Thanks for the message, it reinforces that integrity does really count still.

    There will always be extenuating circumstances for some Road Testers, ......and always some pinocchios,......... hang in there, keep the faith for the 99%'ers.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • ciorga
    ciorga over 7 years ago

    Hi Randall,

    I like what you wrote in this message.   This issue was what made me stop applying to roadtests (specifically the issue that happened with the R&S FPC1500 spectrum analyzer roadtest).  I may start applying again.

    Best Wishes,

    Cosmin

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Cancel
  • Jan Cumps
    Jan Cumps over 7 years ago in reply to Jan Cumps

    ... I’d also tone down the legal section of a road test conditiond. You won’t sue  anyone anyways ...

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • Fred27
    Fred27 over 7 years ago

    shabaz  wrote:

    Even really skilled engineers can have difficulty communicating information (partially stereotype, but partially true) , so Project14, the RoadTests, and other activity writing could be great ways to get an edge when job-hunting.

    I agree that things like road tests and Project 14 are really helpful with expanding skills that you can use in your job (or to get a new job). Some stereotypical engineers might need these skills more than others, but we can all benefit to some degree. It shows that you can research and understand a topic or piece of equipment, and then pass on that knowledge to help others.

     

    I'm a software developer, so electronics and embedded development isn't directly related to my job. However, I've done presentations to my colleagues on these sort of subjects - often at lunchtime with pizza provided. (I even ended up repeating one of these presentations on stage at Microsoft's UK HQ at a hackathon. Nerve-wracking stuff!) I've done others that are a little closer to work topics too. It definitely helps you when you want to get ideas across to management or prove you're the guy to promote. They fit well on your CV as the extra stuff that proves you have a bit more to you that just the skills they listed in the job spec.

     

    I'll give you an example. Right now I'm wondering whether my C# web developer colleagues who are familiar with Azure would be interested in finding out more about Azure Sphere. They are unlikely to have even heard of it. If I road test one, then that might form the basic of a presentation. Should I decide to change jobs, I'm very likely to be discussing Azure in a job interview. Having published an article on an aspect that the other candidates have never heard of - that's bound to go down well.

     

    Having links to things like road tests that you have done outside work is definitely a good thing. Even if you don't intend to show these to anyone outside the E14 community then you've built a valuable skill that will help you a lot. To any new member who's reading this then I'd say that it's really worth going for a road test and it's really worth putting some effort in - before you start as well as after you're selected.

     

    Anyway, getting back on topic...

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Cancel
  • Jan Cumps
    Jan Cumps over 7 years ago

    This is not too different from dealing with anyone new in other circumstances.

    At my job, I hire contractors without meeting them in person too - and there's no 100% guarantee of satisfaction (also not when you interview staff on location).

     

    I admire Randall's effort to get new reviewers. Kudos for not taking the easy path. It's the best way to keep things healthy and to grow the community. Saying that, it's not easy. There's no path to success.

    The only thing I can advise is: take the risk. Allow for failure. Assign low risk items to as many new reviewers as you can.

     

    Settled reviewers aren't saints either. I've seen lousy reviews and no-shows from settled members.

    • Cancel
    • Vote Up +5 Vote Down
    • Sign in to reply
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube