Project JellyConnect
Mentorship connections that help teams problem solve and grow together.
Project JellyConnect connects teams with mentors and experienced support for troubleshooting, builds, piloting, and technical reports. When a build manual and YouTube are not enough, JellyConnect gets teams real guidance from people who have been there.
Nolan Note: If you write it down and track it, it is science, and science always wins!
Why It Matters
Not every team has an engineer on speed dial, and not every program has a coach who knows how to troubleshoot beyond the build manual. Some schools have a wonderful teacher sponsor who is required to be there for meetings, but they may have zero engineering background, and that is not their fault. When a team hits a real problem, the kind that is not in the instructions, it can stall progress fast.
Project JellyConnect exists so teams do not have to figure it out alone. It is mentorship that feels like someone just turned the lights on, guidance, confidence, and real help when it matters most.
Impact includes:
-
Faster troubleshooting and clearer next steps for teams
-
More confident students through mentorship and support
-
Stronger programs because support does not stop at the manual
How It Started
Project JellyConnect began when educators reached out and said the quiet part out loud, we are here for the kids, but we do not know how to help when something breaks or does not work. We connected those teams with experienced mentors, including veterans and community supporters, and the results were immediate.
Students stopped feeling stuck. Teachers stopped feeling alone. Teams started learning faster, improving faster, and believing in themselves more. After seeing how powerful that support was, we knew mentorship could not be a one time favor. It needed to become a full time SEAPERCH Foundation project.
What We Do
Project JellyConnect may include:
-
Connecting teams with mentors for troubleshooting and guidance
-
Support for builds, wiring, waterproofing, and performance improvements
-
Pilot and co pilot coaching, communication, and strategy support
-
Technical report and documentation guidance when teams need direction
-
Q and A support sessions, including Ask an Engineer Nights and team help meetups
-
Matching support based on what a team actually needs
Who We Serve
Project JellyConnect supports:
-
SeaPerch and STEM teams who need technical guidance
-
Educators and sponsors who want to support students but need support too
-
Students who learn best through real conversation, not just videos
Connected Projects
Project JellyConnect connects with:
-
Project JellyUnite for workshops, templates, and shared learning tools
-
Project JellyLaunch for new teams who need early support
-
Project JellyResponse for teams building service focused projects
Photos and Highlights
A few moments from Project JellyConnect. We are still building this gallery, so if you have photos from a Project JellyConnect event, workshop, or team activity, please email them to info@seaperchfoundation.org and include the project name and event date in the subject line.
Project JellyConnect
 |  |  |
|---|---|---|
 |  |  |
 |
By sending photos, you confirm you have permission to share them and that they may be used on our website and social media.
By sending photos, you confirm you have permission to share them and that they may be used on our website and social media.
Advice, Tips and Tricks From Around the World
This section is where teams share the small things that make a big difference, what worked, what surprised them, and what they wish they knew sooner. Tips are specific actions you can try right away. Tricks are small hacks that save time or reduce mistakes. Advice is the bigger direction that helps teams make good decisions over the whole season.
From Our Junior Board
Nolan, tip: Before you ask for help, do a 60 second baseline check, prop direction, loose connections, motor mount wiggle, tether snag, is your battery charged. The basics solve more than you want to admit.
Nolan, tip: Change one variable at a time. If you change five things, you will not know what fixed it, or what broke it.
Nolan, trick: Send a “help packet” in three parts, one photo of the full frame, one close up of the problem area, and one sentence describing what changed right before it started.
Nolan, advice: Tell mentors what you already tried. It saves time and keeps you from looping the same fix three times.
Brooklynn, tip: Ask one clear question first, then add details. “Our left motor stopped,” is easier to solve than a whole paragraph of panic.
Brooklynn, trick: Take one photo of the problem and one short video clip if it involves movement. A picture can save ten paragraphs.
Brooklynn, advice: If you feel stuck, take a breath and ask anyway. Getting help is not weakness, it is how teams grow.
Julian, tip: If a mentor shows you a fix, write the steps in your own words immediately. If you cannot explain it, you do not own it yet.
Julian, advice: Do the fix twice. Once proves it worked, twice proves you learned it.
From Around the World
SeaPerch mentors, tip: Include your division, your thruster layout, and what you want the ROV to do that it is not doing. Mentors troubleshoot faster with context.
Experienced teams, advice: Teams that ask questions early and often waste less time and learn faster.
Coach sponsors, advice: Build a culture where questions are normal. The best teams ask more questions, not fewer.