Actions
Forum Thread Details
  • Replies 24 replies
  • Subscribers 2564 subscribers
  • Views 1880 views
  • Users 0 members are here
Related

RoadTests: Project vs Unboxing vs Experiment vs Other

rscasny

Over the past few months, I have implemented some changes to the RoadTest program. Some of these changes had to do with things that needed to change in order to have the program work for all stakeholders. Of course, some of them have to do with things that would help me manage the program better (e.g., asking applicants to use their profile email address on applications or my asking supplemental questions.)

 

But one comment caught my attention last week. To paraphrase it, the commenter thought that RoadTests were more or less morphing into prototyping "big" projects. This has led some individuals not to apply because of a lack of time.

 

While creating a big project would be nice, it's definitely not required. After all, we give you 60 days to complete testing and write a review. Not a whole lot of time to create something totally new.

 

A RoadTest can be a combination of performing an unboxing (start up/installation), conducting some experiments or tests (e.g., verify a power supply's load regulation is in specs), building a prototype, or doing something else.

 

When I review the applications -- all of which get sent to the supplier -- I do provide some recommendations. Sometimes they go with my recommendations, sometimes they do not.

 

But I've observed the following things regarding applications:

 

  • We are looking for a concise plan of testing.
  • Is the project do-able? Some projects aren't in 60 days.
  • Does the RoadTester appear to be able to pull off the testing and write the review.
  • The plan isn't being re-hashed over multiple RoadTests.
  • The application sounds like the applicant took the time to study the product; we have had some RoadTesters that submitted applications that were irrelevant to the product being tested.
  • Long applications may get looked at, but the winners are a combination of long or short applications. The application should be only as long as need be to explain your testing plan. But 1 sentence applications are rarely taken seriously.

 

I encourage everyone who is interested to keep on applying for RoadTests. Since we are given a limited number of units, we can't get everyone to test all the time. But a good plan will rise to the top.

 

Randall Scasny

RoadTest Program Manager

Parents

  • I typically like to apply with a project-based proposal. For me the best way to really evaluate something is to play around with it for a reason, instead of just idly twiddling knobs. Having a project also means I have thought about the item to be tested, at least looked up some specs, and I actually have a need for it. I know that a project probably involves more time, but OTOH most of my project ideas are to see whether one can really do the project with the road test item - which means the goal is the evaluation of fitness, and not the finished project. In fact, for all road tests I have only one project which got finished for the road test, for all the other ones I did find out that it did not work out as imagined.

Reply

  • I typically like to apply with a project-based proposal. For me the best way to really evaluate something is to play around with it for a reason, instead of just idly twiddling knobs. Having a project also means I have thought about the item to be tested, at least looked up some specs, and I actually have a need for it. I know that a project probably involves more time, but OTOH most of my project ideas are to see whether one can really do the project with the road test item - which means the goal is the evaluation of fitness, and not the finished project. In fact, for all road tests I have only one project which got finished for the road test, for all the other ones I did find out that it did not work out as imagined.

Children
  • in reply to hlipka

    Hendrik,

     

    You make some great points.

     

    I agree that a project is a great way to really evaluate the product. At the same time, one may not have enough time to complete it given the time we give you for the roadtest review. But that's okay. The deliverable of the roadtest is the review, not the completed project. I think you could do a good review without completing the whole project. My concern is that there have been a few people who've told me that they are taking longer to complete the project and that's what was holding up the review -- or they just gave up.

     

    Remember, we need your help to review the product not just complete a new prototype. So, do the best given the finite period of time you're given. Explain why you think you could not complete it: too big of a concept or technical difficulties or a lack of documentation, et al.

     

    Randall Scasny

    RoadTest Program Manager