Preface: About the Human, the AI, and the Trail of Broken Things

Before we get too far into this book/blog/whatever form this thing will eventually take... Let's refer to it as a "FRC Success Guide" for now at least. That sounds a little pretentious for my taste but let's roll with it for now. There something you should know about how this FRC Success Guide was written.

A substantial amount of the actual writing was produced with the help of AI. Kind of appropriate that a robot helps write a guide about running a robotics team. Eh?.. no.. ok.

There. We have survived the disclosure.

AI helped organize ideas, research topics, compare sources, turn rough notes into readable prose, and occasionally find a more dignified way to describe situations that, at the time, mostly involved staring at a robot and saying words unsuitable for an educational publication.

But this guide was not created by asking an artificial intelligence, “How do you run an FRC team?” and then wandering away while it produced several hundred pages of extremely confident nonsense.

Every section begins with, is prompted by, or is reviewed through the perspective of a real-life-flesh-and-blood FRC coach. Imagine an awkward wave on the other side of the keyboard.. Hi!!!!

More specifically, I am a coach who was once exactly where you may be now.

I did not begin this journey knowing how FIRST Robotics Competition worked.

I did not understand all the deadlines for grants, or fees, when the robot should be ready.

I did not understand how competitions really functioned.

I did not know what inspectors were going to ask for, what judges were looking for, how much time travel planning would consume, how difficult it would be to keep students meaningfully involved during Build Season, or meaningfully involved at all for that matter. Especially when the majority of the action happens January - April.

I learned.

Sometimes because another mentor explained something.

Sometimes because the FRC community shared an idea.

Sometimes because FIRST provided exactly the resource I needed.

And sometimes because we made a terrible decision and were kind enough to document the consequences for future generations.

We had success along the way.

There were awards, competition victories, great robots, memorable matches, students taking on leadership roles, community recognition, and all the other things that make coaches stand a little taller when somebody asks, “So, how's the robotics team doing?”

But behind those successes was a trail of failures.

• Missed opportunities.

• Bad planning.

• Poor communication.

• Mechanisms that should never have escaped the whiteboard.

• Mechanisms that we couldn't design if we tried.

• Things ordered too late.

• Things ordered twice.

• Things nobody ordered because everyone assumed we had. I once had to order a part and deliver it to the hotel to put on the robot the very next morning before competition.

• Students who were not prepared because the adults had not created a system to prepare them.

• Adults who were exhausted because we had built a system that depended on exhausted adults.

• Competition lessons learned approximately 2.5 minutes after they would have been useful.

• And, naturally, robots that worked perfectly yesterday...

This FRC Success Guide grew out of those experiences.

It also grew out of the experiences of other teams.

FRC has an enormous community of coaches, mentors, students, volunteers, engineers, parents, alumni, and professional robot whisperers who have been documenting what works—and what very much does not—for decades. Team blogs, Chief Delphi discussions, mentor resources, presentations, conversations in pits, and stories exchanged while waiting for matches all contain lessons worth preserving.

Many of the stories in this guide draw inspiration from those kinds of experiences.

That brings us to the characters.

The People in These Stories Are Not Real. Mostly... But the lessons are.

Throughout this guide, you will meet fictional students, coaches, mentors, parents, programmers, drive-team members, and other inhabitants of the FRC ecosystem.

Their names are fictional.

Their teams are fictional.

The specific events described are often fictionalized.

But the lessons usually are not.

Many stories are composites inspired by things I experienced personally, situations other mentors have described, lessons documented by teams, or patterns that occur so frequently in FRC that somewhere in the world they are probably happening again while you read this sentence. Details may be changed. Several real incidents may become one fictional incident.

One spectacularly complicated real incident may be divided among several fictional people so that no single character appears to possess an unreasonable concentration of bad judgment.

These stories should therefore be read as allegories based on the accumulated experience of running an FRC team, not as historical accounts of identifiable people.

If you recognize yourself in one of them, that does not necessarily mean the story is about you.

It may simply mean you have coached FRC. Our condolences.

The fictional team exists because failure is one of the best teachers in this program, but real students should not have to become permanent literary monuments to something they did when they were sixteen. A student can forget to charge the batteries without having that event preserved under their legal name for generations.

The lesson matters.

The embarrassment usually does not.

Why Use AI at All?

Because writing a guide like this requires bringing together an absurd amount of information. I'm sure you've tasted from the firehose of information.

FIRST publishes rules, policies, training materials, calendars, manuals, award criteria, safety resources, and administrative guidance. Technical organizations publish documentation. Teams publish resources. Mentors discuss problems. Chief Delphi contains decades of accumulated community knowledge, several brilliant ideas, several arguments that may still be occurring, and enough information about robot construction to occupy a person until the heat death of the universe.

AI is useful for helping sort through all of that. It can help organize research, identify questions, compare explanations, restructure drafts, and transform the sentence:

“Tell them not to wait until competition morning to discover their driver's laptop hasn't updated since October” into something resembling a paragraph. More importantly, it can help me, as the flesh and blood FRC Coach, share this information in a more digestible way.

What AI cannot do is have experience.

• It has never stood in a pit while students frantically diagnose a robot with six minutes until the next match.

• It has never called a parent because a student decided to wander out of reach.

• It has never watched a freshman discover that the part they designed in CAD actually fits.

• It has never sat in the stands during alliance selection wondering whether the team's season was about to continue.

• It has never watched a graduating senior come back and say that robotics changed what they believed they were capable of doing.

• Those experiences belong to people.

AI can help describe them.

It cannot replace them.

That distinction matters.

This Is Also Not the Rulebook

There is another distinction that matters even more.

This guide is not an official FIRST publication.

When this book/blog/thing explains an FRC rule, policy, deadline, eligibility requirement, award criterion, inspection requirement, or technical standard, the goal is to verify that information against the best available source.

• But FIRST changes.

• Games change every year.

• Policies change.

• Control systems change.

• Award structures change.

• Deadlines move.

• Procedures evolve.

• And occasionally FIRST releases a Team Update capable of making something you understood perfectly well on Tuesday considerably more interesting by Wednesday.

So throughout this guide, remember:

FIRST is the authority. This FRC Success Guide is attempting to be the translator.

If anything in these pages conflicts with the current Game Manual, Team Updates, official FIRST policies, the FIRST Q&A, or another applicable official source, the official source wins. Every time. No dramatic appeal.

No citing page 147 of this FRC Success Guide to an inspector.

No saying, “But ChatGPT told me…”

Please do not make a Lead Robot Inspector endure that.

They have suffered enough.

Community knowledge is enormously valuable, but it is not the rulebook either.

Chief Delphi, team resources, veteran mentors, and books or guides like this one can explain how teams interpret a challenge, organize themselves, avoid common problems, and make better decisions.

They tell you what people have learned.

FIRST tells you what is required.

Knowing the difference is one of the first skills a successful FRC coach needs.

About the Word “Success”

You will see the word success frequently in this FRC Success Guide.

It needs some explanation.

Success can absolutely mean winning.

This is a competition.

Winning an event is exciting.

Winning an award is meaningful.

Building a robot that performs well is worth celebrating.

Playing deep into the playoffs is fun.

Blue Banners look terrific on walls.

We are not going to spend the next several hundred pages pretending nobody is keeping score.

But winning is only one kind of success.

Sometimes success is having a something that moves with code for the first time.

Sometimes success is getting inspected before your first match.

Sometimes it is arriving at competition with batteries that are actually charged.

Sometimes it is a student making their first CAD model.

Sometimes it is your programming team learning how version control works before learning why version control exists.

Sometimes success is a sophomore confidently explaining your robot to a seasoned engineer after spending September afraid to speak in front of strangers.

And sometimes success does not reveal itself until years later, when a former student walks back into your lab and tells you that the experience changed what they thought they could become.

Those successes are harder to put in a trophy case.

They are also the reason the trophy case exists.

This guide will help you build better systems.

Better teams.

Maybe even help build a robot before inspection at competition.

Possibly fewer emergencies.

But the purpose is not to create a perfectly optimized competition organization that happens to contain teenagers.

The purpose is to create an environment where students can learn difficult things, attempt ambitious projects, make mistakes safely, work with adults who believe in them, become responsible for something larger than themselves, and discover that problems that once looked impossible can be solved.

The robot gives us an excuse to do all of that.

An expensive, complicated, 120-pound-ish excuse with motors.

Welcome to FRC.