Chapter 1: Why Did You Agree to Do This?
Updated: Sep 10
Maya graduated last spring.
She had been on the robotics team for a few years, long enough to accumulate the usual assortment of team shirts, safety glasses, and opinions about mechanisms that no normal teenager should reasonably possess.
One fall afternoon, a few months after graduation, she stopped by the robotics lab.
This is something former students do. Sometimes they come to see the new robot. Sometimes they come because college has made them nostalgic for a room where somebody is always drilling something. Sometimes, I suspect, they just want to confirm that the team has survived without them.
We talked for a while about life. The robot. The new team. College. Classes. Dorm life. The usual questions.
Then she said she had decided to study mechanical engineering. I had to try really hard not to look overjoyed as she told me why.
Before joining robotics, engineering had seemed intimidating. It was something done by people who already knew how everything worked. People who understood machines and equations and could look at a pile of aluminum tubing and somehow see a robot hiding inside it.
She didn't think she was one of those people.
Then she joined an FRC team.
She learned to use tools.
She watched ideas fail.
She helped build things that didn't work, figured out why they didn't work, and helped build them again.
She discovered that the students who seemed to know everything mostly knew more because they had already broken more things.
She learned that engineering wasn't about walking into a room already knowing the answer. It was about being willing to walk into the room without one.
And somewhere in that process, engineering stopped being intimidating.
It became something she could do. Something she could talk fluently about. Something she could share with others.
Now, if you have been coaching FRC for any length of time, there is an enormous temptation at this point to tell you about the robot.
I understand. I have the same problem. Ask an FRC coach about a season and within thirty seconds we are explaining competition results. We will tell you about rankings. Awards. Playoff runs. That incredible match where everything finally worked. The alliance selection nobody expected. The robot that came back from something everyone was reasonably certain should have killed it. And, of course, the ever elusive Blue Banner.
If you've never encountered one, winning certain FIRST events and awards earns a team a large blue championship banner. Teams hang them proudly in their shops, schools, and practice spaces. As they should. A Blue Banner represents an enormous amount of work. Students designed, built, programmed, practiced, presented, strategized, repaired, fundraised, traveled, failed, adjusted, and tried again to earn it.
Winning one is wonderful.
But this is where a guide about FRC success has to be very careful. Because if I tell you the banner story first, I may accidentally teach you the wrong definition of success.
The most important thing that happened that season may not be hanging on the wall.
It may be Maya.
She walked into the robotics lab believing engineering was something other people did.
She walked out believing she could become an engineer.
That is not the consolation prize.
That is the point.
There will come a night when the intake doesn't intake, the code that “worked yesterday” has apparently reconsidered its life choices, two students disagree about something involving gear ratios, someone needs a purchase approved immediately, and you have just learned that a form you did not know existed was due three days ago. At that moment, it is remarkably easy to believe that your job is to get the robot working. And, temporarily, it is.
But the robot is not the final product.
The students are.
The robot is the project complicated enough to require them to communicate.
It is the problem difficult enough to make them fail.
It is the deadline real enough to make planning matter.
It is the machine dangerous enough that responsibility matters.
It is the competition exciting enough that they voluntarily spend hundreds of hours learning things you could never convince them to study from a worksheet.
It gives them a reason to learn CAD because something actually has to fit.
A reason to learn programming because something actually has to move.
A reason to understand electricity because magic smoke is both expensive and educational.
A reason to speak to adults because judges, sponsors, volunteers, engineers, and parents keep asking questions.
A reason to lead because eventually somebody has to make a decision.
And perhaps most importantly, it gives students repeated opportunities to discover:
I don't know how to do this.
Followed, eventually, by:
Wait. I think I can figure this out.
That transition is one of the most valuable things FRC can give a young person.
This guide is going to talk about winning. We will talk about building better robots, preparing for competition, surviving inspection, choosing strategy, organizing pits, developing drivers, scouting effectively, raising money, recruiting mentors, submitting awards, traveling with teenagers, and preventing Build Season from consuming every functioning adult in a twenty-mile radius.
Those things matter.
Competitive excellence matters.
Your students deserve the experience of setting difficult goals and learning how to pursue them well. There is nothing un-FIRST-like about wanting your robot to be excellent, your team to be prepared, and your season to end with more blue fabric than it began with.
But we need to agree on the definition of success before we go any farther.
Because otherwise all the systems in this book can become aimed at the wrong target.
A successful FRC program does not merely produce a better robot.
It produces students who are more capable than they were when they arrived.
More confident.
More curious.
More willing to solve difficult problems.
More comfortable saying, “I don't know, but I can learn.”
Some will become engineers.
Some won't.
That isn't the litmus test of success.
The test is whether participating in your team gave them opportunities to discover abilities, interests, resilience, leadership, friendships, and possibilities they did not know they had before they walked through your door.
Maya chose mechanical engineering.
Another student may discover programming.
Another may discover that they are remarkably good at project management.
Another may become the person who can stand in front of three judges and explain six weeks of chaos with astonishing confidence.
Another may simply discover that there is finally a place at school where being intensely interested in how things work is not merely tolerated but useful.
Yet another student may realize that actually, STEM isn't truly where their interest is.
Those are victories too.
Some of them will never appear in an awards database.
There will be no medal.
No trophy.
No Blue Banner.
Years later, one of those students may come back into your lab and tell you what the experience did for them. And suddenly you will remember why you agreed to do this.
Start there. We'll get to the robot and team soon enough.
Comments