The Social Media, Blog & Open Alliance Path
The team’s public story — told consistently, in the right places, for the right audiences — is how judges discover you before the tournament, how sponsors decide to renew, and how the next great recruit finds out we exist.
Everything the Right Brain team produces — the portfolio, the presentation, the outreach events, the sponsor relationships — leaves a trail. This path is about making that trail visible, intentional, and consistent across every channel where someone might discover Ducktape Robotics for the first time.
Judges look up teams before they walk into the judging room. Sponsors Google the team before they write a check. Future recruits stumble onto an Instagram post and think — for the first time — “that looks like something I could do.” A team that is posting nothing is invisible to all three groups. A team that is posting the right things in the right places is doing outreach, building the portfolio’s documentation record, and telling its story simultaneously — three jobs done with one camera and a consistent weekly habit.
This path is different from the others in one important way: it never ends. The training phase is finite. The posting cadence runs for the entire season and beyond. That is by design. Consistent public storytelling is one of the highest-leverage things a Right Brain student on this team can own.
Where We Tell the Story
Four Channels, Four Different Audiences, One Consistent Voice
The discovery channel. Short-form visual content — robot progress, build moments, competition day energy, outreach events, team culture. The audience here does not know what FTC is yet. Keep it human, visual, and jargon-free.
Team Blog
Sponsors · Judges · Deep-Interest ReadersThe credibility channel. Longer posts with real depth — season recaps, design decisions, outreach reports, sponsor spotlights. A sponsor who reads three blog posts before emailing us is already half convinced. Judges who find the blog before the tournament arrive with context.
Open Alliance (Chief Delphi)
FTC Community · Other Teams · MentorsThe technical credibility channel. Weekly build updates posted to the Chief Delphi FTC Open Alliance forum — CAD progress, code decisions, failures, and what was learned. The audience here is other FTC teams and mentors worldwide. They notice quality and they reward it with engagement and help.
YouTube
All Audiences · Match ArchivesThe archive channel. Match footage, robot reveal videos, and the match-recap reel that serves as the capstone of this path. Video content has the longest shelf life of anything the team produces — a match reel from this season is still recruiting tool years from now.
The Foundation
Brand Voice — What Ducktape Robotics Sounds Like
One Team. One Voice. Across Every Channel.
Brand voice is the consistent personality that shows through in every post, every caption, every blog paragraph. It is what makes a team feel like a team rather than a rotating cast of random social media managers. Ducktape Robotics has a built-in personality to lean into: a name that is slightly absurd, self-aware, and memorable — paired with genuinely serious work in engineering, outreach, and competition.
That tension is the voice. Confident but not arrogant. Technical but accessible. Honest about failures — especially failures, because the Open Alliance explicitly requires sharing frustrating challenges alongside successful progress. Warm and community-oriented, because the Forgotten Coast is a specific place with a specific character, and the team belongs to it. A post from Ducktape Robotics should sound like it could only come from us — not from a template, not from an AI, not from a generic robotics team account.
Every student who posts on behalf of the team — Instagram, blog, or Open Alliance — reads the existing posts first, matches the voice, and runs the draft by the Social Media lead before publishing. One voice. Maintained consistently. That is what builds an audience.
Know the Difference
Four Content Types — What Goes Where and Why
| Content Type | Best Channel | Audience | What It Looks Like |
|---|---|---|---|
| Build moment | Recruits, parents, community | One strong photo, three sentences, no jargon. “We rebuilt the intake for the third time today. It works now. Here’s why the first two didn’t.” | |
| Open Alliance update | Chief Delphi | FTC community, other teams | 300–600 words. CAD screenshots or photos. Specific mechanical or code decision explained. At least one thing that went wrong. Links to GitHub or Onshape if relevant. |
| Blog post | Team website | Sponsors, judges, deep readers | 600–1,200 words. A real narrative with a beginning, middle, and end. Outreach recaps, design retrospectives, sponsor spotlights, or season milestone posts. |
| Match recap reel | YouTube + Instagram | All audiences | 60–90 seconds of match footage, scored to music, with title cards marking key moments. Narration optional. This is the most-watched content the team will produce. |
| Season recap | Blog + Open Alliance | Sponsors, future recruits, FTC community | The full season story — where we started, what we built, what broke, what we won, what we learned. Written once. Linked everywhere. Lives permanently on the site. |
The Left Brain Connection
The Best Content Comes From the Build Room
The Social Media lead cannot produce good Open Alliance updates from a distance. The most compelling Instagram posts are not posed photos — they are candid moments from build sessions where something real is happening. The blog posts that sponsors actually read are the ones that explain a specific design decision in plain language, not generic “we’re working hard” filler.
All of that requires being in the room. The Social Media lead needs to attend build sessions with a camera, ask Left Brain students to explain what they are working on in terms a non-engineer can understand, and develop the habit of capturing content in real time rather than trying to reconstruct it later. The Left Brain students, for their part, should expect to be photographed, asked questions, and occasionally quoted. That collaboration is what makes the public storytelling feel authentic — because it is.
The Five-Stage Journey
From Zero Presence to Consistent Weekly Storytelling
Study Teams That Do This Well — Then Define Our Voice
Before posting anything, spend time studying how strong FTC teams use each channel. Search Instagram for FTC teams with engaged followings — look at their captions, their photo quality, how they talk about failures, how they credit individual students. Browse the Chief Delphi FTC Open Alliance forum and read several build threads from teams that get strong engagement. Notice what the best posts have in common: specificity, honesty, personality, and a consistent point of view.
Then write a one-page brand voice document for Ducktape Robotics. What words do we use? What words do we avoid? What does our team care about that other teams do not talk about enough? What is the Forgotten Coast angle — how does where we are from shape what we post? This document becomes the editorial standard that every student writer on the team follows. Without it, the accounts drift toward whoever posted last.
Set Up the Channels and the Posting System
Get the infrastructure right before the season starts. Instagram account confirmed with a bio that says clearly who we are and links to the website. The Open Alliance build thread created on Chief Delphi with a strong first post that introduces the team, the season, and our goals. The GitHub repository public and linked. The Onshape CAD document shared publicly. The team registered on theopenalliance.org.
Then set up the posting system — not just the accounts. Who is responsible for each channel? What day of the week does the Open Alliance update go out? Who approves a blog post before it publishes? Who has the Instagram password? A content calendar with recurring weekly slots, assigned owners, and a simple approval process turns “we should post more” from a vague intention into a functioning habit. Build the system before the season and it will run itself. Wing it week to week and it will collapse by November.
Learn to Mine the Build Season for Content — Every Week
The hardest part of maintaining a posting cadence is not writing — it is finding something worth writing about every week. Build sessions that feel routine to the Left Brain team are rich with content for the Social Media lead who knows what to look for. A decision between two design options is a post. A failed prototype is a post — arguably the best kind, because it is exactly what the Open Alliance exists for. A new sponsor signing on is a post. A student’s first successful autonomous run is a post. An outreach event is three posts: before, during, and after.
The Social Media lead attends at least one build session per week with a specific content objective: find one thing worth documenting and document it properly. One strong photo. A three-sentence explanation from the student who built it. A note on what problem it solved or what problem it created. That thirty-minute investment, done consistently, produces enough raw material for all four channels without scrambling.
Write and Ship Eight Consecutive Weekly Open Alliance Updates
The capstone for the Open Alliance channel is eight consecutive weekly updates posted to the Chief Delphi FTC Open Alliance forum — one per week, every week, without missing. This is the discipline that earns the team a reputation in the broader FTC community, which in turn generates the engagement, the helpful comments, and the technical feedback that the Open Alliance exists to produce.
Each update follows a consistent structure: what the team worked on this week, what specific decision was made and why, what did not go as planned, and what is next. Include at least one photo or CAD screenshot per post. Write it in the team’s voice — not a dry engineering report, but not social media fluff either. The Chief Delphi audience is technically literate and appreciates specificity. They will call out vague updates and respond warmly to honest, detailed ones. Both reactions are valuable feedback.
Produce the Match-Recap Reel
The match-recap reel is the second half of the capstone — and the most visible piece of content the team will produce all season. It is sixty to ninety seconds of competition match footage, edited to music, with title cards marking key moments: a successful autonomous run, a scoring sequence, a close match, a gracious moment with a competing team. No narration required. Strong music selection, tight editing, and honest footage do the work.
Someone needs to be filming at competition day — not watching the matches, not driving, not talking to judges. Filming. Multiple angles if possible. The editing happens in the days immediately after the event, while the energy is still fresh and the footage is top of mind. Post it to YouTube first, then share it to Instagram as a reel. Tag the league, tag FIRST, tag any sponsors whose logos appear on the robot. This video will be the first thing the next great recruit sees when they find our account — make it worth finding.
What a Week Looks Like
The Sustainable Posting Cadence — Season-Long
| When | Channel | What Ships |
|---|---|---|
| During build | Camera roll | Raw photos and short video clips captured at the session — not posted yet, just collected. |
| Same day or next day | One post — best photo from the session with a two-to-three sentence caption in the team’s voice. No jargon. No hashtag spam. | |
| End of week | Open Alliance | Weekly build update — 300 to 600 words, one decision explained in detail, at least one failure or challenge acknowledged, one photo or CAD screenshot. |
| Every 2–3 weeks | Team blog | A longer post — outreach recap, design retrospective, sponsor spotlight, or milestone update. 600 to 1,200 words. Linked from Instagram and Open Alliance. |
| After each competition | All channels | Match recap post on Instagram same day. Full blog post within one week. Open Alliance update with competition observations and lessons learned. |
| End of season | Blog + Open Alliance | Full season recap — the permanent record of everything the team built, won, learned, and plans to carry forward. Linked everywhere. |
What Good Posts Look Like
Four Templates — Annotated and Ready to Adapt
“We rebuilt the intake for the third time this week.”
The Explanation (one or two sentences)“The compliant wheels we switched to are slower on pickup, but they stop jamming mid-match — which cost us two scoring runs at Meet 1. Reliability beats speed when the match is on the line.”
The Human Moment (optional but effective)“[Name] came up with the fix at 10pm on a Tuesday. It worked on the first test run.”
Why It WorksSpecific, honest, credits a student by name, explains the engineering trade-off in plain language. A parent, a sponsor, and a judge all find something interesting in it.
What the team worked on this week — specific subsystems, specific goals going in.
What Was Decided and Why (the main section)One specific engineering or programming decision explained in detail. What options were considered, what criteria were used to choose, what was built. CAD screenshot or photo here.
What Did Not Go WellOne honest paragraph about a failure, a delay, or a problem that is still unsolved. This is required by the Open Alliance ethos and it is the most-read part of any update.
Next WeekTwo or three sentences on what the team plans to tackle next. Gives readers a reason to come back.
Set the scene. Where were we, who was there, what were we there to do. Make it specific enough that someone who was not there can picture it.
What Happened (the middle)The event in narrative form — not a bullet list. What the students did, what the audience responded to, a quote from an organizer or participant, one moment that surprised the team.
The Impact NumbersAttendance count, age range of audience, organizations involved, any measurable outcomes. These go in the portfolio too — write them here first.
The CloseWhat comes next from this relationship. Is there a return visit? A partnership developing? A student from the event who wants to join the team? End on something forward-looking.
Designate one person whose only job at competition is filming. They do not drive, they do not talk to judges, they do not pit-crew. They film.
Shots to CaptureFull autonomous run from above if possible. Scoring sequences in TeleOp. A close match final thirty seconds. Team reaction after a good match. Team reaction after a hard match — honest is better than curated. A Gracious Professionalism moment with a competitor. Pit candids between matches.
Edit Structure (60–90 seconds)Open on the most exciting ten seconds you have. Title card: team name and event. Best autonomous clip. Two or three TeleOp scoring sequences. One human moment. Final score or result. Closing title card with website and Instagram handle.
MusicUse royalty-free music from YouTube Audio Library. Match the energy of the footage. Do not use copyrighted songs — the video will be muted on YouTube and you will lose the best part of it.
Keep These Open While You Work
Related pages and platforms:
🔗 Join Open Alliance — what the Open Alliance is, why we joined, and how to set up a build thread → 🌍 Outreach & Community Engagement Path — outreach events are content; both paths feed each other → 📋 Engineering Portfolio Path — blog posts and Open Alliance updates are portfolio documentation in a different format → 💬 Chief Delphi FTC Open Alliance Forum — where the weekly build updates live; read existing threads before posting your first → 🏗️ theopenalliance.org/ftc — official registration, team directory, and Open Alliance guidelines → 🎵 YouTube Audio Library — royalty-free music for match recap reels and any video content →Ready to Start Telling the Story?
Set up the channels. Write the brand voice guide. Attend the next build session with a camera and a specific question to ask. The first post is the hardest. After eight weeks of Open Alliance updates, it becomes as natural as showing up.
✉ Email the Coach Read: Join Open Alliance →The team that posts consistently — honest, specific, in their own voice — builds an audience that sponsors trust, recruits want to join, and judges already know by name before walking into the room. Visibility is not vanity. It is strategy.