Thread: Best Ways To Scout
View Single Post
  #11   Spotlight this post!  
Unread 13-03-2009, 14:08
Rich Kressly's Avatar
Rich Kressly Rich Kressly is offline
Robot/STEM troublemaker since 2001
no team (Formerly 103 & 1712. Now run U.P. Robotics (other programs))
Team Role: Mentor
  
Join Date: Oct 2001
Rookie Year: 2001
Location: Pennsburg, PA
Posts: 2,045
Rich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond reputeRich Kressly has a reputation beyond repute
Re: Best Ways To Scout
Asking this question is a LOT like asking, "What's the best robot design?"

I think it's more about meeting your team's needs and fitting the parameters and goals under which you operate. Once you have defined what your available resources (human and otherwise) will be at an event, have decided whether your team is best served by a high-tech, low-tech, or combination approach, and you decide whether your scouting effort will be single- or multiple-team, THEN you're ready to sit down and develop the detailed system that works for your team.

Developing/choosing the system BEFORE you consider parameters, goals, etc makes no sense to me because I never want to find out after the fact that it was "too much paper, too few people." Not that any system never needs analysis or improvements after the fact, but asking yourselves the right questions before investing deeply in any system should help a team prevent any huge mismatches that lead to poor outcomes.

.02 for what it's worth.
__________________
technology, innovation, and invention without a social conscience will only allow us to destroy ourselves in more creative ways
Last edited by Rich Kressly : 13-03-2009 at 17:02.