Team Culture Training Module
Our motto is a behavior standard
“Everyone has a place here”
This is not just a slogan. It means our shop, meetings, pit, travel, outreach, Discord, drive team, awards work, and mentor conversations should help people belong.
Open Door
Interest and hard work should matter more than prior experience.
Shared Growth
Students should be allowed to learn, practice, fail, and improve.
Team Responsibility
A welcoming team is built by everyone, not only mentors or leaders.
Inclusion is part of how 5041 defines success
Mission
Grow every season by learning technical and professional skills while staying open to students who want to join.
Vision
Create an inclusive space where all students can engage with STEM and enjoy learning for its own sake.
Values
Practice FIRST values, Gracious Professionalism, Coopertition, inclusion, and STEM for all.
Key idea: We are not only building robots. We are building people, trust, and future teammates.
Students voices matter
What students need from the team
Safety
- Respectful language
- No bullying or harassment
- Clear ways to ask for help
Belonging
- People are invited in
- Roles are explained
- Questions are treated as normal
Purpose
- Everyone has useful work
- Strengths are noticed
- Growth matters more than status
When people feel safe, they ask better questions, take useful risks, and stay involved longer.
How to make space for different team members
New Members
Explain acronyms, tools, roles, and why the team does things a certain way.
Quiet Members
Invite ideas without forcing someone to perform in front of the whole group.
Younger Members
Give real jobs with support instead of only cleanup or watching.
Experienced Members
Ask them to teach, document, and make room instead of taking over.
Inclusive communication is specific and respectful
Helpful
- “Want me to show you how this works?”
- “What part do you want to try?”
- “Let’s test that idea.”
- “Can you explain your reasoning?”
- “I made that mistake too.”
Harmful
- “Just let me do it.”
- “Everyone knows that.”
- “That’s a dumb question.”
- “You are not a build person.”
- Jokes that target identity, ability, or background.
Safe teams make failure useful
Normalize
Everyone starts somewhere. Mistakes are expected in design, coding, wiring, awards, and outreach.
Repair
Fix the part, fix the process, and fix the relationship if someone was embarrassed or dismissed.
Document
Turn lessons learned into checklists, CAD notes, code comments, pit notes, and mentor reminders.
Belonging means access to real work
A team can accidentally exclude people by:
- Letting the same students use every tool.
- Assuming quiet students are not interested.
- Not explaining inside jokes or acronyms.
- Making business, safety, media, or outreach seem less important than robot work.
- Only asking friends to help with high-visibility tasks.
A team creates access by:
- Rotating practice opportunities.
- Pairing new and experienced members.
- Explaining the “why” behind decisions.
- Respecting all team roles as team success.
- Keeping documentation useful for the next person.
Professional conflict keeps people safe
Pause
Stop escalating. Keep your voice controlled and focus on the issue, not the person.
Clarify
Ask what happened, what is needed, and what decision has to be made next.
Escalate
If someone feels unsafe, threatened, excluded, or targeted, bring in a mentor immediately.
5041 expectation: Students should maintain a professional attitude and find diplomatic solutions.