Coaching FLL - Tips and Traps

[timdavid]

A few years ago, I prepared a document intended to contain information helpful to new FLL coaches. The document has a few Minnesota-specific references, but overall most of the information should be applicable to coaches in any region.

The document, titled "Coaching FLL - Tips and Traps", is attached to this post. Please read it and let me know what parts you like or dislike. If people find the document useful, I will try to update it and find a more permanent place on the web where it can reside.

Thanks,
Tim

[andycivil]

This is perfect! I'm a new coach and am looking for any resources that might help. Thank you soo much.

[jklawrence]

Thanks Tim, this is superb! I can't comment fully because I've only read half - I hit brain overload. There are loads of great ideas and I want to give them thought before I try to digest the rest.

The advice on handouts is great - I will probably tacklet that first. Thanks for the example. Thanks also for all the links to great resources.

[Roosevelt Robotics]

timdavid,

Thanks for the coaching tips. Very helpful. May I share this on our robotics website at school?

Randy

[timdavid]

Originally Posted by Roosevelt Robotics

timdavid,

Thanks for the coaching tips. Very helpful. May I share this on our robotics website at school?

Randy

Glad you like it. Yes, please feel free to share it on your robotics website.
Tim

[timdavid]

Originally Posted by jklawrence

Thanks Tim, this is superb! I can't comment fully because I've only read half - I hit brain overload. There are loads of great ideas and I want to give them thought before I try to digest the rest.

The advice on handouts is great - I will probably tacklet that first. Thanks for the example. Thanks also for all the links to great resources.

You're welcome! I'm happy to hear you finding some useful ideas.

I noticed that the Coaches' Handbook for this year briefly mentions bringing a one page summary about the robot to the teams' technical judging session. This is on page 47 of the handbook, in a section titled 'Robot Design'.

Just to clarify - this is strictly an optional practice for most teams. Some regions require a more formal "Robot Design Executive Summary". Your tournament directors should be able to tell you if this is required in your region.

Another clarification - the summary or handout should be prepared by the kids, not the coach. As a coach, I'll help the kids with the mechanics of getting a picture of their robot onto the computer, and with some simple formatting issues, but the kids are responsible for the content on the handout or summary.

I like having the team prepare a handout about the robot for two main reasons. First, it helps the team members think about the main features of their robot and programming, and prepares them for discussing these things with the judges. Second, it gives the judges something to remember the team by, and also gives the judges ideas for possible areas for questions.