Approaching a new event

[windu34]

How do you guys first approach a new event? Make a binder? Watch videos? Build prototypes? Draw blueprints?

[Chris_L]

Depends what event. For builds I try to draw up some blueprints and do some research online about what could work best, then build a basic one that is a proof of concept. Then build the real thing. For studies I try to go broad and learn the basics of an event before delving more deeply into the details however I make sure to have a great cheat sheet by the time i get to competition.

[watermydoing14]

I usually start with the resources posted on soinc.org under each event like training handouts/powerpoints, etc. For studies, I read the rules and take note of the topics I need to study. I like to make a binder with handwritten notes. When I start studying, I take out a new sheet of paper and head the top with the overarching topic outlined on the rules sheet. For example, for anatomy, I have a tab in my binder for each body system and the heading for one of my notes sheets might be "I. Functions of the Integumentary System". Then I would do research on this topic. I start with the training handouts on soinc.org. I also do google searches on the topic. Textbooks can also be very helpful if you find one. Openstax has a bunch of free textbooks or you can buy your own.

For build events, start by reading the rules. I've found the most helpful thing to do is to work with an older member of your team that has experience on the event. They can help you get started and give you tips. If you don't have access to a mentor or older team member, go through the scioly.org forums and gather what knowledge you can. The key to builds is practice. The more you work on your build, the more you will learn about it, and the better you'll be able to compete with it. For builds I know that people always tell you to build detailed blueprints, but judge whether or not you actually need to based on the event you're doing. If it's something technical like bridges or wright stuff, you definitely need a detailed blueprint. If it's something like Mission Possible or Bungee, you need less of a detailed blueprint and more of a general plan. If there is a kit available for the event (e.g. Wright Stuff), then it would be a good idea to buy the kit, then once you get a better feel for the event, you can play with the design a little more.

[Fluorine]

To add to this:

For ID events (what I mainly do). I first go through all the possible “things” that can be tested in a general format. For each one I write general info like taxonomy, ecology, habitat (or anything else useful) and include some type of note to help me memorize what the "thing" looks like or if you can a picture. Then if we are allowed a binder. I put that sheet up front, and then print full info pages on everything else. I find this works really well, as I have the ability to answer questions quickly, but can fall back on my printed info for more detailed questions. If you cannot have a binder then I usually can memorize what all the “things” look like, and have minor notes to spark my memory. And then I fill my one page notes with everything that I cannot memorize (anatomy, vocab and more). Usually practice fills in the gaps of info I miss.

[samlan16]

For most of my (lab) events, I generally start by doing background research for about a month and then practice the actual lab components thereafter while revisiting my research occasionally. If any questions come up, I do more research outside of my designated practice time.