[Steven Smith]

Our team is just getting to the point this season where we have solid student buy-in on scouting, and as the students were iterating on their electronic scouting system last night, I had the following discussion with them. It is a simple point, but make sure you understand the WHY fully before locking in on the HOW. This also isn't directed specifically at you, but just a reminder to myself and other teams that are starting out scouting.

The purpose of scouting is not to collect data. The data is a means to an end. The best scouting application is the one that allows you to efficiently collect the bare minimum of data you need, and turn out a meaningful interpretation. We have been guilty, and many newer scouting teams are guilty of taking a lot of data without a clear plan on how to implement it. It turns the scout team into a "busy work" team that completes a massive data gathering exercise without any real results.

There are two different goals in scouting, the first being easier to execute.

First, scouting for playoff matches to generate a pick-list if you plan to seed in the top 12-15 and have a chance at being an alliance captain... or scouting for "complementary robots" and sell your strengths to someone that will be an alliance captain. In this scenario, simply having a list of the teams with quick notes on them in terms of their viability as a partner will suffice. At the end of qualification matches, you scratch off teams higher than you than you cannot pick, and you decide what key functions you need in your alliance. If at this point, you don't understand what score you will likely need to win an event, how many RCs that requires off the step, what is a reasonable number of stacks for an #1 seed or #20 seed at your event, etc... focus on watching match video, not on what scouting application to use.

Second, scouting for qualification matches to give your drive team advanced knowledge on their alliance members (to maximize team score) and opponents (this year, mainly focused on their ability to co-op). Make sure your drive team knows the difference between what a robot CAN do, and HAS done in previous matches. Ideally, provide them with a strategy such as ... this match Robot A can cap RCs reliably enough for us to not cap our own stacks. Instead of building 2 stacks of 5 with RCs, lets squeeze in a third stack of 5, without RCs, and allow Robot A to cap for us. Or perhaps, a warning to them that Robot A has the capability to cap, but they consistently knock over stacks . Their coach will likely propose a similar plan, but push back and execute your self-capped stacks to minimize risk.

As you start thinking through what information you plan to provide your drive team, or what decisions you need to make in alliance selection... it becomes more clear what data you need. I'd rather see our team scout with pencil/paper and a plan, than have the most elaborate system and not have a clear plan on how to implement.