As the title says, this thread is for the community to discuss what makes an optimal drive team.
I find that the biggest error people make with drive teams is allocation of responsibility, mainly concerning the coach. There are many teams that are indecisive during the game and I attribute this mainly to communication delay as well as general driver experience.
In VEX, being active and always having a goal in mind is key to winning a game such as Gateway that has constantly shifting circumstances.
Responsibilities/Characteristics:
Main driver (drives chassis)
-second-to-second decisions
-loud, commanding, concise but clear communication
-quick decision making
-technical skill, understanding capabilities of robot
-understand the game
Operator
-mainly staying focused, listening attentively to main driver
-able to take orders
-understand personality and really know the driver
-do not lose any time coordinating when chassis/arm have to work together
Coach
-looking at opponents
-counting score
-looking at time
-match loading
-gate lifting,
-only makes decisions when absolutely necessary, usually as reaction to opponent actions
-understanding of game and other robots (scouting)
-quick analysis of circumstances to change strategy quickly
My optimal drive team, based on the responsibilities and characteristics above, aims to delete any communication delay during the match. Indecision is a big killer and every second wasted switching directions or waiting for your operator to raise the arm when you want to score is precious. In this way, the coach should not make many decisions, but allow the driver to control the match and eliminate that delay.
Similarly, driver and operator need to be synchronized perfectly. Not only should they both understand the game to the deepest degree, they need to understand how the other would react to certain situations (especially the operator) by understanding personalities and getting a lot of experience and practice together. This way, the driver and operator mimic the synchronization of robot subsystems of a single driver, but spread the mental load of controlling multiple subsystems at once over two people.
Thought I would share my own view on drive teams and am curious how other teams organize their drive teams.