# Get Started Welcome to Tech Fleet user guide! This is the community manual that covers helpful information. This section describes the first steps when joining the Tech Fleet community. # What is Tech Fleet? Tech Fleet is a community-driven nonprofit focused on the mission to change the ways that we work. We offer professional development in teamwork, shared leadership, and collective decision making. ## Why We Exist
Why We Exist ### Technology and the Future Technology today is a result of the people who are already in control of decisions. Businesses prioritize features that may affect those who use it. Positions at tech industry companies are disappearing to make way for more automation. Over time, people who were already excluded from leadership are even more excluded. Our future will continue to evolve without the people who are already excluded. ### Changing How We Think About Leadership Technology products and features are a result of those in power today. When people hear "leadership," they think of one person who makes all the decisions. They think of someone with big ideas. They think of someone others ask for answers. This way of thinking about leadership is common everywhere. Both leaders and followers think this way. The person with power decides for the person without power. This thinking keeps the same type of person in leadership roles. People who have advantages get more chances to become leaders. People who went to fancy schools get more leadership opportunities. Many things stop other people from having a voice in leadership. Today's leadership cares about efficiency and logical decisions. People with power want to keep their power. People who already have power choose who they work with. Organizations that operate out of fear hold employees in control. The cycle continues. Our systems today keep some people in leadership and keep others out. People who serve leaders aren't involved in decisions that affect them. Organizations believe that workers should follow orders instead of finding new ways. ### We Believe in a Different World We believe in a world where: 1. We serve each others' growth together. 2. We share responsibility together. 3. We grow through practice. 4. We distribute power to everyone. 5. We give opportunity for the quiet voices to have a say. ### Community-Driven Change To lead the change we want to see in the world, we must do it together. We need all kinds of voices in the room. Since we started our community, our nonprofit has been guided by the people who belong here. The people who train in our programs make change happen. They work together as teams to solve problems. Together we help each other create new ideas and find the best ways to help the world. ### Serving Others' Growth There is a leadership style called "Servant Leadership." It talks about leaders serving employees, instead of employees serving leaders. But the word "servant" still suggests power dynamics. The leader still has power over the employee. This is different from shifting ownership and working as equals. We use the term "service leadership" because we all lead in service to each other's growth. No one is a servant. Every teammate is a leader to others. We don't do work for others. . We don't work for "masters" because there is no difference between "me" and "you." We train leaders who lead with the heart over anything. Teams that lead through service must find a way together.
## Our Mission Check out the information all about our mission, vision, and values here: {% content-ref url="/pages/AlELcGl0bayj7W9liBhB" %} [Mission and Values](/about-us/about-our-org/mission-and-values) {% endcontent-ref %} ## What We Offer
What We Offer ### People-First Leadership Development We train leaders to put people at the center of everything. We help them take ownership. People-first leadership means helping others grow. It means sharing power with the group. It means letting go of controlling results. It means giving others space to challenge how things are done. Teams that work together and help each other grow create the best new ideas. Together, people-first leaders can change the world. ### Team-based Practice and Experiences Everything today focuses too much on theory. People can learn systems and frameworks. But this comes at the cost of helping others grow in organizations. When we change the story to putting people first, teams explore and decide together. They find the ways they want to move forward. ### Working Together as a Community The voices of our community work together to decide our future. We are the change, together. Our organization prioritizes involvement and collaboration with those in our community. We work alongside them to drive change and evolve our impact in this world. There are many ways community members can get involved in the future of our mission and programs.
## Who We Work With ### People who have never been leaders before Historically excluded individuals must drive our future. We think it's important to develop leaders who have never had experience leading. Our organization trains first-time leaders to lead with the heart. ### People who are already leaders Those who hold power today can see another way forward. Their choice to distribute ownership comes with letting go of fear. Our organization trains people who are already leaders to shift their mindset. ## How We Carry Out Our Mission
How We Carry Out Our Mission ### Cross-Functional Teamwork with Nonprofit Clients Our training programs focus on practice and decision making. Our classes fill the gap between school and the real-world. Members can pursue real project work with mission-driven organizations. Teams get together across functions and train how to iterate on value. We practice continuous discovery and team-based problem solving to make a real impact. ### Service Leadership Communities who Practice Together Our members live what they train. They're not just part of a class, they're building a growing ecosystem that they drive. They work together to practice service leadership, help others practice it, and drive its standards forward. ### Tools and Resources for Leadership Development Leaderful Labs provides ways to guide in people-first leadership while practicing. We offer way to receive personalized guidance, measure progress, and tell the story. Our resources are built for people who've never done teamwork before and want to practice. Through this, our tools provide ways for people to build their confidence. ### Cohort-based Class Training Our org offers Learning Labs that provide theory-based education from practitioners. These are lab-based and provide ways for people to practice and actively learn in groups. Our members receive benefits that help them gain advantage in leadership growth. These cohorts serve everyone, from career changers to new graduates to executives.
## Tech Fleet Website Visit Tech Fleet's information website for basic information about Tech Fleet that can also be found in the following user guide. {% embed url="" %} Visit Tech Fleet's information website for basic information about Tech Fleet that can also be found in the following user guide. {% endembed %} ## The Tech Fleet Community You are not alone. Tech Fleet's community is full of new grads, career changers, and industry experts pitching in to help you break into tech. Our online community is hosted in Discord today. Outside of [projects ](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training)there are [masterclasses](/training-openings/current-and-upcoming-program-openings/masterclass-openings), social groups, communities of practice, educational talks, peer learning, support groups, and mentoring to get involved in. The more you're involved in the community the more you will get out of Tech Fleet. [Join Tech Fleet Discord](/resources/quick-links/join-tech-fleet-discord) today, and watch our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) beforehand. Be sure to read our [policies](/policies/community-collective-agreement) before you do! ## How to get the most out of this guide For **new members**, this space will be helpful during your first days with the community, to better learn about who we are and how we work. For **returning** **members**, this space will act as a user guide to learn how to navigate Tech Fleet throughout your membership with the community. ## Are You New? Book a Community Onboarding Call {% content-ref url="/pages/mDk0wxIFhawsGgpeAG0Q" %} [Book a Community Onboarding Call](/join-the-community/onboarding-to-tech-fleet/book-a-community-onboarding-call) {% endcontent-ref %} # Tech Fleet FAQ Here are some quick answers to your most common questions about Tech Fleet
What is Tech Fleet? Tech Fleet is a nonprofit training organization focusing on developing shared leadership, cross-functional teamwork, and collective decision making. We are a nonprofit with 501(c)(3) public charity status. EIN 92-1962909. We offer professional development training programs based on real-world practice, and support 1. [Projects ](/project-portal/project-success-handbook)- You can [build team experience training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) on Tech Fleet teams. You will work with a cross-functional team to solve business problems with clients. The community works with other nonprofit clients and builds open source software for the public good. Hundreds of people have gone through our programs and are now working in tech careers. 2. [Masterclasses ](/masterclass-portal/masterclass-openings)- You can register for Masterclasses in Tech Fleet to gain industry-focused training. We offer live cohorts for masterclasses. Different people teach different subjects throughout the year. Check out the Masterclass Hub for more information and current training.
Where can I see project work? Check out the new project dashboard for all the details about live and upcoming project training, and the work involved.
What should I do first? Check out the [First Steps in Tech Fleet](/start-here/get-started/first-steps-in-the-tech-fleet-community) page
What are Tech Fleet's rules and regulations? Our rules and regulations live in the form of our Policies and bylaws. \ \ **The Tech Fleet community expects that ALL Tech Fleet network activities, events, in-person forums, and digital forums abide by the Code of Conduct. We have a zero tolerance policy against harassment or anything in violation of our code of conduct of any kind.**\ \ We hold ourselves and our community to the highest professional standards. We have a strict [Code of Conduct and Anti-Harassment Policy](/community-code-of-conduct/code-of-conduct-and-anti-harassment-policy), a strict [Slack and Discord Policy](/policies/tech-fleets-policies/slack-and-discord-policy), and other [Policies](/policies/tech-fleets-policies) all must read, agree, and live by. \ \ Our [nonprofit bylaws](/policies/tech-fleets-policies/tech-fleet-bylaws) can be found here.\ \ Go to [Safe Space page](/community-code-of-conduct/safe-space) for instructions how to report or request to talk. If you are being harassed, or witness someone else being harassed or otherwise uncomfortable, or if you think anyone is in violation of Tech Fleet's [Code of Conduct](/community-code-of-conduct/code-of-conduct-and-anti-harassment-policy) for ANY other reason, or just want a safe space with someone to talk to, the community is here to help. Please report a Code of Conduct concern or send an email to . We protect and support whomever reports. Read through all [Policies](/policies/tech-fleets-policies) and ensure you always abide by them, and help report violations.
Does Tech Fleet use Discord or Slack? Tech Fleet just migrated to Discord as of September 2024. We no longer use Slack as a community. Check out [The Great Discord Migration video tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for everything you need to know about Tech Fleet Discord.
How can I join projects? There are 4 ways to participate in projects. Read about applying here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) **As an observer** anyone can participate without applying. You can join any team meeting that's happening, and watch the apprenticeship teams in action. A lot of members start with observing as it helps to build confidence and helps to learn the Tech Fleet framework. [Check out the Observer Portal](/observer-portal/observer-handbook). **As a teammmate** you must apply. You are a member of an agile, cross-functional team working for 8 weeks with a client. You're paired up with other apprentices and with leads who help guide the progress. Together you fail forward and learn how to work in an Agile environment. Learn more in the [Teammate Handbook](/team-portal/new-teammate-handbook).\ \ **As a mentor** you can sign up to guide in specific subject matter areas you know well. Right now, the process for project mentors is new and in pilot. If you are interested in mentoring, seek the @Mentors role in Discord through the #join-projects and the #mentors-get-ready channel. More information about Discord will be added to this guide soon. If you are interested in mentoring right now, email and express your interest! We're happy to place you on live projects
What can I apply to right now? Check our [Current and Upcoming Programs](/training-openings/current-and-upcoming-program-openings) page for the full list of live and upcoming opportunities. Join our mailing list to get alerted when we open new programs for you to apply to.
Is this school? NO! School holds your hand and gives you prompts for success. Tech Fleet's meant for you to prepare for the real-world expectations in the industry along with your peers. Apprenticeship teams in Tech Fleet are modeled based on the industry teams for in-house and agency roles. Teams are in an environment where they are accountable for the work and able to fail safely, trying new things and learning how to do the work for the first time. It is, however, the "deep end of the pool" and one should mentally prepare for this kind of environment. Tech Fleet helps you truly get ready for the convoluted real-world of product life.
What kind of company is Tech Fleet? Tech Fleet is a community-led nonprofit with 501(c)(3) public charity status. Check out our [website ](https://techfleet.org)for more information. Community members, [Guilds](/guild-portal/guild-handbook), nonprofit officers, and the Board of Directors carry out our mission to create fair access to tech careers through our programs. Read about our [organization structure](/about-us/about-our-org) in the guide for more.
What career paths are available in Tech Fleet? We open roles based on client demand and project needs, so each program that opens has different roles. We serve the following career paths in our programs: 1. UX Research 2. UX Design 3. UX Writing 4. Project Management 5. Product Strategy / Management 6. Web Development 7. Blockchain Development Read the section about [supported roles](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training) in the user guide
Is there a Pets channel? YES #pets-of-tech-fleet in [Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials). (And now, a #plants-of-tech-fleet channel too!)
Does Tech Fleet cost anything to join the community? 1. Project training does not cost anything to join the training 2. Masterclasses require a small fee to register, usually $50.00 USD per person. Anyone can join the community and join project trainings at no cost. The only things we charge for in Tech Fleet will be masterclasses, which have a small fee to join ($50 or country equivalent). These classes are not required to complete other Tech Fleet programs (like team project work). In the future we will seek revenue from public support and offer services like one-on-one career coaching or other ways to help that require fees to participate. Otherwise, we will always remain inclusive in who we serve (the unemployed and underemployed) and seek to cut down costs for community contributors as much as possible.
Can I apply to different job functions on training programs? Yes! Apply to as many positions as you'd like, but be prepared to pick one as your top priority if you're asked to choose. A lot of programs require time and energy and it's best to dedicate focus on one at a time, although you can choose to be a part of multiple programs at once. Check out the details of applying to project training here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) Check out the details of applying to volunteer work for our nonprofit organization here: \ [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams)
Can I apply to multiple programs at once? Yes! Apply to as many training programs as you'd like, but be prepared for the time and energy commitment. A lot of programs require time and energy and it's best to dedicate focus on one at a time, although you can choose to be a part of multiple programs at once. Check out the details of applying to project training here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) Check out the details of applying to volunteer work for our nonprofit organization here: \ [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams)
Can I be on multiple project teams at a time? Generally, no, we limit our members to being on one project team at a time so they can focus their energy on learning and contributing within their team. If someone is on two projects for less than 3 weeks it's generally ok to be on multiple projects, but otherwise, we limit it to ensure fairness in people joining opportunities. Check out the details of applying to project training here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) Check out the details of applying to volunteer work for our nonprofit organization here: \ [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams)
Do I need a resume and portfolio to qualify? **No!** Tech Fleet's one of the only orgs in existence that provide ways for people with 0 experience to get into teamwork for the first time and train in agile. You should [build an agile mindset and a service leadership mindset](/agile-training-portal/agile-training-in-tech-fleet) through our different agile training options before getting into project training or volunteering. It's possible to do so without any experience or any schooling. Check out the details of applying to project training here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) Check out the details of applying to volunteer work for our nonprofit organization here: \ [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams)
How can I observe what it's like before I apply? Anyone in the world is welcome to observe any project meeting, and watch the teams work. This helps build confidence, and helps you understand what the cross-functional work looks like in Tech Fleet. Read more about [life on projects](/project-portal/project-success-handbook), and read the [observer handbook](/observer-portal/observer-handbook) for all the details. Check out [Observers in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/getting-on-projects-in-tech-fleet-discord/observers-in-tech-fleet-discord) for information on how to use Tech Fleet Discord as an observer.
What ways can I receive support in Tech Fleet? You can get support in a variety of ways in Tech Fleet. Check out [How to Get Technical Support](/resources/the-great-tech-fleet-discord-migration-video-tutorials/get-technical-support-in-tech-fleet-discord) for more.
What's the application process in Tech Fleet programs? You can apply to two kinds of teamwork: 1. Project training teams with other nonprofit clients 2. Volunteer teams with Tech Fleet as a client Our project training application and team-building process is similar to the normal hiring process. Tech Fleet [project coordinators](/project-coordinator-portal/project-coordinator-handbook) open applications after agreeing to scope with clients, and then open applications for short periods of time. The leads on the project who get chosen will hire apprentices who've applied. Check out the details of applying to project training here: [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) Check out the details of applying to volunteer work for our nonprofit organization here: \ [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams)
# Start With the Community Collective Agreement ## Welcome To the Mission **As a community,** [**we are the change that tech needs for the future**](/policies/community-collective-agreement/community-core-values/tech-fleets-mission-and-values)**.** As a member, you are a part of this change with us. Welcome! When joining our community, all members agree to abide by our [policies ](/policies/tech-fleets-policies)and our [community collective agreement](/policies/community-collective-agreement). ## Community Policies {% content-ref url="/pages/kUi0se4NXaallJiY1x6r" %} [Community Collective Agreement](/policies/community-collective-agreement) {% endcontent-ref %} {% content-ref url="/pages/vZ2YLBIsK53JVKSxcHvH" %} [Tech Fleet's Policies](/policies/tech-fleets-policies) {% endcontent-ref %} # First Steps in the Tech Fleet Community Here are your steps to get involved in Tech Fleet
  1. Read the user guide to get a sense of Tech Fleet and how it works including
  1. Book an onboarding call with the community to hear from alumni, answer your questions, and learn about the first steps.
  1. Join Discord and engage with the community when you're ready to start engaging with the community
  1. Be an Observer to watch Tech Fleet apprenticeship teams work in Agile to learn the ropes before applying
  1. Train in Servant Leadership and Agile through our community-driven masterclasses.
  1. Apply to projects as a lead or apprentice, and be sure you've read the handbooks beforehand
# How to Get Discord Roles in Tech Fleet In Tech Fleet Discord, you can only see the channels you have access to. This is based on your role in Discord. You can manage your own roles based on what you want to do. Learn how to manage roles through the Great Discord Migration Tutorial videos: {% content-ref url="/pages/jmAmxGk1X2LaZ10DVqDT" %} [Using Roles for Alerts, Notifications, and Channel Access](/resources/the-great-tech-fleet-discord-migration-video-tutorials/using-roles-for-alerts-notifications-and-channel-access) {% endcontent-ref %} ## Masterclass Role This role enables Discord channels for masterclass alerts and guidance. Go here to learn how to get the role: {% content-ref url="/pages/M9iDU7PAV2RponzeTLIV" %} [Masterclasses in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/masterclasses-in-tech-fleet-discord) {% endcontent-ref %} ## Projects Role This role enables Discord channels for project alerts and guidance. Go here to learn how to get the role: {% content-ref url="/pages/KbUFqf2JKFRF4XJINFn7" %} [Getting on Projects in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/getting-on-projects-in-tech-fleet-discord) {% endcontent-ref %} ## Observers Role This role enables Discord channels for project alerts and guidance. Go here to learn how to get the role: {% content-ref url="/pages/at0TIpdlHZ0ho8EFUSS5" %} [Observer Role in Discord](/observer-portal/observer-handbook/daily-expectations-of-tech-fleet-observers/observer-role-in-discord) {% endcontent-ref %} ## Project Training Teammate Role This role enables Discord channels for project alerts and guidance. Go here to learn how to get the "Projects" role: {% content-ref url="/pages/ViSHLM5RSLtZxrTJRnzm" %} [Project Training Teammates In Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/getting-on-projects-in-tech-fleet-discord/project-training-teammates-in-tech-fleet-discord) {% endcontent-ref %} # How to Become a Teammate on Project Training You can train as a teammate in our apprenticeships to build cross-functional team experience. Check out how to prepare below.
Train in Agile and Servant Leadership Read about it all here/pages/RBKNeOCSQOqxEHOuvu5i
Observe ProjectsRead about it all here/pages/BbMR0StqCuWcosa5T8xj
Read the Project Success HandbookRead all about it here
Read the Teammate HandbookRead all about it here/pages/a2A9YzBut11QBik2J35T
Get the Projects Role in DiscordRead all about it here/pages/zgwfXoV29CR5GeJmRizy
Apply to ProjectsRead about it all here/pages/WzQRzvLgbqZr9FE3JCuo
# How to Become a Nonprofit Volunteer for Our Community You can make change in this community as a volunteer for our nonprofit. Check out how to prepare below.
Train in Agile and Servant Leadership Read about it all here/pages/RBKNeOCSQOqxEHOuvu5i
Observe ProjectsRead about it all here/pages/BbMR0StqCuWcosa5T8xj
Read the Project Success HandbookRead all about it here
Read the Teammate HandbookRead all about it here/pages/a2A9YzBut11QBik2J35T
Get the Projects Role in DiscordRead all about it here/pages/zgwfXoV29CR5GeJmRizy
Become a Volunteer for Tech FleetRead about it all here/pages/WzQRzvLgbqZr9FE3JCuo
# How to Register for Masterclasses
Join Tech Fleet DiscordRead all about it here/pages/r1AtQqGrigmkVJWyaqDM
Get the Masterclasses Role in DiscordRead all about it here/pages/M9iDU7PAV2RponzeTLIV
Register for MasterclassesRead about it all here/pages/x1RYKCUPJJO7oQIsGOnC
# About Our Org Everything to know about who we are and how we operate # Hello World Nice to meet you! We're a nonprofit on a mission to be the change that the work world needs for the future. ## About our Organization Tech Fleet is a Delaware nonprofit with 501(c)3 public charity status. Community members are accountable for our success and our future. Our Board of Directors and community members work together to make change in collaboration. ## Our Origin Story The professional work world is built on dynamics of single decision making. People who are making decisions don't always include the people who are affected. Employers may want prior experience before gaining jobs, and people may not be able to gain advantage doing that. Leaders and teams may act without making decisions with the people they serve. People who work for companies may never get the chance to be the key decision makers. We see a lack of collective ownership and collective decision making all over the professional world. And yet, the people doing the work are the best judges of what to do and how to do it, because they are in the day-to-day. We envision a different world, one where: 1. We lead together; 2. We decide together based on lived experiences; 3. We share ownership together; 4. We foster environments to empower others. When we started, our community was focused on creating opportunity for people to transition into the tech industry. We offered opportunities for experience-building teamwork and practice. As we grew, and as the world changed, we realized our mission is much larger. Not only should we be advocating for the people who haven't landed in the work world, but we should be advocating for people in the workforce too. We are changing cultures in the work world. We are advocating for a different kind of leadership, one that's human-centered. Today, we are building the future leaders of tomorrow that support others' growth. We do it through practice, common mindsets, collaboration, and collective decision making. Anyone with the willingness and the mindset can grow in our community. ## Head to the Next Lesson # Mission and Values This page outlines our goals as an org, and the principles we abide by within the community. ## Our Mission Statement ***We are the change that tech needs for the future.*** We’re a community-driven organization working together to remove barriers to access, take responsibility, orient around service, practice continuous improvement, and collaborate. We build technology with nonprofit partners that makes a positive difference. ## Our Values ### Service We work together to support the success and growth in our community. Everyone plays a part. We're all in service to each other to be the change. Together, we move our mission forward. We must amplify voices of those who have been unseen and unheard in the tech industry. ### Responsibility We are all responsible for the future of tech. Anyone who is willing to put in the commitment and to come with a learner’s mind is welcome to join. Steward leadership is the heart of everything our community does. Our members guide and support each other. ### Community As a distributed organization, those we serve have power to shape our future. We all contribute to the plans, processes, and projects that make up Tech Fleet. Members are invited to lead, design, and vote on our operations and direction. Everyone has something to offer. ### Continuous Improvement We teach with Agile philosophies in mind and in practice. We are constantly looking for ways to deliver more value to ourselves, our teams, our clients, and our community. Over the years, Tech Fleet has evolved at the helm of our community members. Our collective voices drive the change. ## Head to the Next Lesson # We Live by the Collective Agreement ## Our Collective Agreement Community members in Tech Fleet live by the Collective Agreement, which outlines our operating procedures and expectations for community membership. {% content-ref url="/pages/kUi0se4NXaallJiY1x6r" %} [Community Collective Agreement](/policies/community-collective-agreement) {% endcontent-ref %} ## Head to the Next Section # Tech Fleet's Roadmap This page shows Tech fleet's nonprofit roadmap across our nonprofit programs: 1. Community and Career Development Program - helping people gain experience on real Agile teams through cross-functional team project training. 2. Extension and Outreach Program - helping people master industry skills through educational training masterclasses and resources. ### Roadmap {% embed url="" %} ### Task Tracking {% embed url="" %} # Current and Upcoming Program Openings Find our current project and class openings here. # Project Training Openings See our current and upcoming openings! # Project Training to Apply To Now The following dashboard shows the projects you can apply to right now. ## Project Training You Can Apply To Now Here are Tech Fleet's Current Openings for project training: {% embed url="" fullWidth="false" %} Credit: Tech Fleet; this is the embedded version of the project dashboard showing current openings {% endembed %} ## How Project Training Applications Work Read more about how applications in Tech Fleet project training work on the Project Portal {% content-ref url="/pages/WzQRzvLgbqZr9FE3JCuo" %} [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) {% endcontent-ref %} ## Head to the next lesson # Upcoming Project Training The following dashboard shows the projects you can apply to right now. ## Project Training That's Launching or Opening Soon Here are Tech Fleet's projects that you can apply to apply to soon. {% embed url="" %} Credit: Tech Fleet; showing the projects that are opening soon at {% endembed %} ## How Project Training Applications Work Read more about how applications in Tech Fleet project training work on the Project Portal {% content-ref url="/pages/WzQRzvLgbqZr9FE3JCuo" %} [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) {% endcontent-ref %} ## Head to the next lesson # Live Project Training Phases in Tech Fleet The following dashboard shows the live projects in Tech Fleet. ## Project Training That is Live Right Now Here are live training projects in Tech Fleet: {% embed url="" %} Credit: Tech Fleet; showing the live projects going on in Tech Fleet at {% endembed %} ## How Project Training Applications Work Read more about how applications in Tech Fleet project training work on the Project Portal {% content-ref url="/pages/WzQRzvLgbqZr9FE3JCuo" %} [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) {% endcontent-ref %} ## Head to the next lesson # All Live and Upcoming Training Projects In One Place Here's a large version of the project dashboard to show you all current, live, and upcoming projects in Tech Fleet. ## All Project Training {% embed url="" %} Credit: Tech Fleet; showing the full project dashboard at {% endembed %} ## Head to the Next Lesson # Masterclass Openings This page shows the link to current and upcoming masterclasses in Tech Fleet. ## Masterclass Dashboard Here's the Masterclass Dashboard! Check out our masterclass cohorts for different industry topics. {% embed url="" %} This embedded block shows the Masterclass Dashboard for Tech Fleet masterclasses. Go here for the full page: {% endembed %} ## Masterclass Timeline Here's a view showing when masterclasses start and stop! Click on each one for more details. {% embed url="" %} This embedded block shows the Masterclass Dashboard for Tech Fleet masterclasses. Go here for the full page: {% endembed %} ## Head to the next lesson # Volunteer Project Openings This page shows all of the current volunteer projects under our community that you can apply to. ## Read the Teammate Handbook First! There are three types of projects to get involved in: 1. Project training with other nonprofit clients 2. Volunteer internal projects for Tech Fleet 3. Ongoing volunteer positions for Tech Fleet Read the Teammate Handbook to learn about this before you decide which things to apply to! {% content-ref url="/pages/LB0VQGEWHxQ2e3dJrWrR" %} [NEW Teammate Handbook](/team-portal/new-teammate-handbook) {% endcontent-ref %} ## Volunteer Projects for Our Community {% embed url="" %} # Application Forms Here are the application forms for Tech Fleet project training. ## Project Training Applications Complete the General Application and Project Phase Application to Apply to Training Projects
General Application/files/DLUeap9tvNrStA77eXTqhttps://form.fillout.com/t/tH3XB2zsRYus
Project Phase Application/files/mArsC56Cj7nOS7xEvTXYhttps://form.fillout.com/t/e88iPX3BrWus
## Volunteer Project Applications
Cover image
Volunteer Project Team Application/files/sdDvWt4wlwsFjc8Ha6jt
## Update your General Application Go here to update your General Application answers if you previously submitted it: {% content-ref url="/pages/wN9D4kMZtYAqLqwQiYfP" %} [Updating the General Application](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training/updating-the-general-application) {% endcontent-ref %} ## Check Our Openings Be sure you check which projects are open and which ones you want to join before you apply. {% content-ref url="/pages/g8GXUcCoPPIaYd77Bwd2" %} [Current and Upcoming Program Openings](/training-openings/current-and-upcoming-program-openings) {% endcontent-ref %} ## How Applications Work Read more about how applications in Tech Fleet project training work on the Project Portal {% content-ref url="/pages/WzQRzvLgbqZr9FE3JCuo" %} [Applying to Tech Fleet Project Training](/team-portal/new-teammate-handbook/project-training-teams/applying-to-tech-fleet-project-training) {% endcontent-ref %} {% content-ref url="/pages/lfJHBaRB16tPulU4nTW5" %} [Apply to Volunteer Teams](/team-portal/new-teammate-handbook/volunteering-teams/apply-to-volunteer-teams) {% endcontent-ref %} ## Head to the next lesson # How to Join Tech Fleet Discord After you do an onboarding call, [join the Tech Fleet Discord](/resources/quick-links/join-tech-fleet-discord) through the sign up form. Here are the steps: 1. Go to 2. Click "Join Discord" 3. Fill out the form 4. You will receive an email with the Discord invite link 5. Onboard to Discord: 1. Verify your phone number 2. Onboard flow 3. Account preferences setup Check out the [Discord video tutorial series](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for videos on how to join! # Onboarding to Tech Fleet # Book a Community Onboarding Call If you're new to the community, we offer weekly onboarding calls. All members are required to join at least one! Schedule on the calendar below. ## Head to this page to book an onboarding call with Tech Fleet's community {% embed url="" %} Tech Fleet Community Events Calendar on Luma {% endembed %} # Join our Mailing List Get alerted when we open new project or class opportunities, and other important news coming from our organization. {% embed url="" %} Click here to join our mailing list {% endembed %} # Onboarding Videos These videos are produced by the Tech Fleet Video Production Guild ## Introduction Video {% embed url="" %} Welcome to Tech Fleet, a nonprofit on a mission to create fair access to tech careers. {% endembed %} ## How to Get Started on Projects {% embed url="" %} Get started building real team experience in Tech Fleet with 5 easy steps. {% endembed %} ## Discord Tutorials {% content-ref url="/pages/gTdasq0C2MFwzC0JgbSF" %} [The Great Tech Fleet Discord Migration Video Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) {% endcontent-ref %} ## Story from Tech Fleet alum Kathryn Potter {% embed url="" %} Testimonial from Tech Fleet alumni Kathryn Potter, who went through Tech Fleet as a UX Design Lead. {% endembed %} ## Story from Tech Fleet alum Ben Shimazu {% embed url="" %} Testimonial from Tech Fleet alumni Ben Shimazu, who went through Tech Fleet as a UX Design Lead. {% endembed %} # Information Website Check out our information website for more information about our org! ## [Click here to go to the Tech Fleet information website](https://techfleet.org) # Community Happenings Here are some of the things happening around the community. Check out the [Tech Fleet web calendar](/resources/quick-links/tech-fleet-web-calendar) for event info. ### Onboarding Calls We hold onboarding calls for new members every week. During these calls you can learn about Tech Fleet and how to get started. [Book one here!](/join-the-community/onboarding-to-tech-fleet/book-a-community-onboarding-call) ### ☕️ Community Chats Every week, the community members host community chats welcome to all. Check out the [Tech Fleet web calendar](/resources/quick-links/tech-fleet-web-calendar) for days and times. ### ☕️ Open office hours Once a week, Tech Fleet hosts a coffee chat for whoever is open and interested, Bring your questions! ### 🤝 Community Buddy system We are in this to help each other, and you can't go it alone! Request a buddy in #buddy-up channel within Discord to pair up. ### :postal\_horn: Tech Fleet Talks Every so often, the community hosts educational talks covering different topics. Stay tuned in #events channel in Discord for the latest updates. # Brand Guide This guide details how to write and produce visuals in the style of Tech Fleet's brand. # Brand Guide Introduction This is an introduction to the Tech Fleet Brand Guide ## Get It All in One Document {% file src="/files/a8h3mGT2ijbkECz573jz" %} {% file src="/files/X1W995LCw593nr2jv8hw" %} ## Introduction Welcome to the Tech Fleet Brand Guide. This document helps us speak, write, and design with one clear voice. We are building a world where everyone can lead through service, teams are empowered to make decisions together, and people grow together without judgment. To do that, we need to communicate in a way that is welcoming, caring, and informative. This guide is for everyone who creates content for Tech Fleet. Whether you are writing a social media post, designing a web page, or sending an email to a partner, these guidelines will help you stay on brand and ensure our content is accessible to everyone. ## Purpose This guide ensures that Tech Fleet looks and sounds the same everywhere. Consistency builds trust. When we use the same voice, colors, and rules, people know what to expect from us. It helps us show the world that we are a reliable, caring, and inclusive community. ## Who This Guide Is For This guide is for internal teams, volunteers, board members, and external partners. If you are creating anything that represents Tech Fleet, this guide is for you. ## How to Apply the Guidelines Read through the sections to understand our core identity, our voice, and our visual rules. When you write or design, keep this guide open. Use it as a checklist to make sure your work matches our standards. ## Sections of the Brand Guide {% content-ref url="/pages/Rj4tH8ZjDqw5oPxhBHpz" %} [Brand Foundations](/resources/brand-guide/brand-foundations) {% endcontent-ref %} {% content-ref url="/pages/s03WLXJs1dnFKHoCrILc" %} [Brand Identity](/resources/brand-guide/brand-identity) {% endcontent-ref %} {% content-ref url="/pages/djGLNFOdB8m2l5T6spVC" %} [Editorial Style Guide](/resources/brand-guide/editorial-style-guide) {% endcontent-ref %} {% content-ref url="/pages/iY8Y1JJRdS28DOcq5MI8" %} [Brand Visuals](/resources/brand-guide/brand-visuals) {% endcontent-ref %} # Brand Foundations This page covers the basic high-level principles of the Tech Fleet Brand. # Design Principles On this page, learn about the values we portray in our brand. ## Design Principles Our design principles guide how we build products, create content, and shape experiences. They act as a filter for decision-making. When you are unsure if a design or piece of content is right for Tech Fleet, measure it against these six philosophies. ## Minimalist We believe in removing the unnecessary so the essential can speak. Minimalism in our design means reducing cognitive load, avoiding decorative clutter, and giving content room to breathe. How to apply it: * Use white space generously. * Limit the number of colors and fonts on a single screen. * If an element does not serve a clear purpose, remove it. | Do This | Not This | | --------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | Use a single, clear call-to-action button on a page. | Clutter the page with five different buttons competing for attention. | | Group related information into one clean card with plenty of padding. | Put a heavy border around every single paragraph of text. | | Use a solid color background behind text for easy reading. | Place text over a busy, high-contrast photograph. | | Show only the three most important features on the homepage. | List all 25 features on the homepage in a dense grid. | | Use a simple, two-color icon to represent a concept. | Use a highly detailed, multi-colored illustration that looks like a photograph. | ## Universal We design for everyone, not just the average person. When we build for people with the widest range of abilities, backgrounds, and contexts, we create experiences that work better for all. Accessibility is a civil right, not an afterthought. Every person who interacts with Tech Fleet deserves a full, dignified experience, regardless of how they see, hear, move, or think.This principle goes beyond technical compliance. It means designing with empathy from the start, not retrofitting it at the end. It means asking: who might we be leaving out, and how do we bring them in? How to apply it: * Always meet WCAG 2.2 AA standards as the baseline. * Ensure high color contrast for people with low vision. * Support keyboard navigation for people who cannot use a mouse. Write descriptive alt text for people using screen readers. * Never rely on color alone to convey meaning. * Provide captions, transcripts, and audio descriptions for all media. * Design layouts that reflow cleanly on small screens and at high zoom levels. * Test your work with real assistive technology, not just automated checkers. | Do This | Not This | | ------------------------------------------------------------------------------ | ------------------------------------------------------------------- | | Use an icon and a text label together to indicate an error state. | Use only a red outline to indicate an error state. | | Ensure all text has a contrast ratio of at least 4.5:1 against its background. | Use light gray text on a white background because it looks "clean." | | Write descriptive alt text like "A woman smiling while typing on a laptop." | Write alt text like "Image 45" or leave the alt text field blank. | | Make sure every interactive element can be reached using the Tab key. | Build custom dropdowns that only work with a mouse click. | | Provide captions and a written transcript for all video content. | Post a video with only auto-generated, unedited captions. | ## Intuitive Our experiences should feel familiar and require no explanation. We respect established mental models and design patterns so people can focus on their goals, not on figuring out how our interface works. How to apply it: * Use standard icons (like a magnifying glass for search). * Place navigation where people expect it. * Use Gestalt principles to build visual relationships and help people interpret your experiences correctly. * Keep workflows linear and predictable. | Do This | Not This | | --------------------------------------------------------------------- | --------------------------------------------------------------------- | | Put the main navigation menu at the top or left side of the screen. | Hide the main navigation inside a custom, unconventional interaction. | | Use a magnifying glass icon for the search bar. | Use a pair of binoculars or a radar dish icon for the search bar. | | Make links look like links (e.g., underlined or a distinct color). | Make links the exact same color and style as regular body text. | | Put the "Next" button on the right and the "Back" button on the left. | Put the "Next" button on the left and the "Back" button on the right. | | Group form fields logically (e.g., First Name, Last Name, Email). | Mix form fields randomly (e.g., Email, City, First Name, Zip Code). | ## Purpose-Driven Every design decision must solve a specific problem for the people using our products. We do not design for design's sake; we design to empower teams and facilitate learning. How to apply it: * Before adding a feature or a visual element, ask: "What user need does this serve?" If the answer is unclear, do not add it. | Do This | Not This | | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | Add a progress bar to a multi-step form so people know how much is left. | Add a complex animation to a form just because it looks cool. | | Use a chart to make complex data easier to understand at a glance. | Use a chart when a simple sentence would explain the data better. | | Include a tooltip only if the term is highly technical and needs definition. | Put tooltips on common words just to add interactivity to the page. | | Design a dashboard that highlights the user's next required action. | Design a dashboard that shows every possible metric, even irrelevant ones. | | Use an illustration to explain a difficult concept visually. | Add random illustrations to a page just to fill empty space. | ## Intentional We are deliberate in our choices. From the words we use to the spacing between elements, nothing is accidental. Intentional design builds trust and shows that we care about the details. How to apply it: * Align elements to a strict grid. * Use a defined type scale. * Ensure consistent padding and margins across all screens. | Do This | Not This | | ----------------------------------------------------------- | -------------------------------------------------------------------------------- | | Use a consistent 16px margin between all cards in a layout. | Eyeball the spacing, resulting in 14px, 18px, and 15px margins. | | Stick strictly to the defined H1, H2, and H3 font sizes. | Manually adjust font sizes on every page so they look slightly different. | | Align all text to the left for easier reading. | Center-align long paragraphs of text, making them hard to read. | | Use the exact brand HEX codes for all colors. | Pick colors from a color picker that look "close enough" to the brand colors. | | Ensure all buttons on a page are the exact same height. | Have buttons of varying heights depending on the length of the text inside them. | ## Welcoming Our design must feel like an open door. We want people to feel safe, supported, and encouraged when they interact with Tech Fleet How to apply it: * Use warm, conversational copy. * Choose imagery that reflects our diverse community. * Avoid harsh, aggressive colors or intimidating error messages. | Do This | Not This | | ----------------------------------------------------------------------------- | --------------------------------------------------------------------- | | Use soft, rounded corners on UI cards to feel approachable. | Use sharp, aggressive angles that feel corporate and cold. | | Write error messages that offer a clear solution and apologize for the issue. | Write error messages in all caps that blame the user for the mistake. | | Feature photos of real community members collaborating and smiling. | Feature photos of empty, sterile office buildings. | | Use our primary blue and green colors to create a calm, inviting interface. | Use stark black and neon red as the primary interface colors. | | Include a friendly welcome message on the dashboard for new users. | Drop new users into a blank dashboard with no instructions | # Reading Level Standards This page covers how writing for the Tech Fleet Brand should adhere to reading level requirements for full accessibility. ## Reading Level **Always aim for a 7th grade reading level.** We want our writing to be easy for everyone to understand. This makes our content accessible to people from different backgrounds, those who speak English as a second language, and people with cognitive or learning differences. If you are not sure what grade level your writing is, use the [Hemingway Editor](https://hemingwayapp.com/). Paste your text into the app, and it will tell you the reading level. It will also highlight sentences that are too hard to read. Rewrite those sentences until the reading level drops to grade 7 or below. ## Examples | Do This | Not This | | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | "We help teams learn how to work together." | "We facilitate the optimization of collaborative methodologies within cross-functional paradigms." | | "Sign up for the newsletter to get updates." | "Subscribe to our digital publication to receive periodic notifications regarding organizational developments." | | "This guide shows you how to use our logo." | "This documentation delineates the parameters for appropriate brand mark utilization." | | "If you have questions, ask in the Slack channel." | "Should inquiries arise, please direct them to the designated communication platform." | | "We believe everyone can be a leader." | "Our core philosophy posits that leadership potential is universally distributed among all constituents." | # Accessibility Guidelines Here's a page that outlines how you ## Accessibility Policy Tech Fleet upholds its Accessibility Policy throughout its brand materials online and in-person. Read more about what we prioritize, why, and how: {% embed url="" %} ## WCAG 2 Standards We must uphold accessibility standards across our brand offerings. It's important to adhere to WCAG guidelines so that we're offering the best experience we possibly can within the Tech Fleet Brand. Learn more here: {% embed url="" %} # Brand Identity # Brand Statements Our brand identity is the foundation of everything we do. It defines who we are, what we stand for, and why we exist. ## Core Identity ### Mission Statement Our mission is to build environments of empowered teams. We are building a world where everyone can lead through service, teams are empowered to make decisions together, and people grow together without judgment. ### Vision Statement We envision a world where we can work together with shared power and autonomy. ### Core Values #### Service We work together to support our collective growth, learning, and sustainability as a community. Everyone plays a part. We amplify voices of those who have been unseen and unheard in the work world. #### Responsibility We are all responsible for the future of work tech. Anyone willing to put in the commitment and to come with a learner's mind is welcome to join. Service leadership is the heart of everything our community does. #### Community As a distributed organization, those we serve have power to shape our future. We all contribute to the plans, processes, and projects that make up Tech Fleet. Everyone has something to offer. #### Continuous Improvement We are constantly looking for ways to deliver more value to ourselves, our teams, our clients, and our community. We choose to look for opportunities to learn and grow, instead of seeing mistakes as failures. ## Brand Positioning ### Target Audiences We serve four main audiences who want to learn a better way of working and leading: 1. **Recent Graduates and Career Changers:** People who face barriers to qualifying for new careers and are stuck in the experience trap. They need real-world practice to build skills and portfolios. 2. **Senior Contributors:** Experienced professionals who want to grow into leadership positions. They want to make a bigger impact and contribute to the development of emerging talent. 3. **Middle Managers:** Current people managers who aim to strengthen their leadership abilities. They need to learn how to lead diverse, distributed teams in modern work environments. 4. **Executives:** Executive leaders who recognize the need for leadership at all levels. They want to grow as leaders and create cultures of empowered teams in their organizations. ### Positioning Statements For recent graduates and career changers who face barriers to qualifying for new careers, Tech Fleet is a nonprofit workforce readiness platform that bridges the experience gap through real teamwork and collective decision making with real-world results. Unlike theory-based academic programs or passive online courses, Tech Fleet provides spaces to grow in practical leadership skills through inclusive, team-based learning. For experienced professionals who want to remain relevant for their entire career, Tech Fleet is a leadership development platform that enables senior professionals to grow in leadership and contribute to the development of emerging tech talent. Unlike consulting or traditional volunteer programs, Tech Fleet provides structured paths to developing as a leader through real team-based collaboration and collective decision making. ### The Problem We Solve The world of work is leaving people behind. Many entry-level jobs ask for three to five years of experience, creating an "experience trap." At the same time, the skills companies want are changing. Human-centered skills like teamwork and communication are in high demand, but traditional leadership training is outdated and authoritarian. Furthermore, people from historically excluded backgrounds face massive barriers to leadership. ### Our Unique Value Proposition Tech Fleet is a nonprofit workforce development organization that bridges the experience gap through real teamwork and collective decision making. We provide hands-on, practice-based learning through real teamwork, real practice, and real clients. We remove barriers to leadership development for historically excluded groups while teaching service leadership and empowered team principles. ### Brand Promise We promise to provide a lifelong system for learning, practicing, and growing as a service leader. We promise to offer real-world experience, human-centered skills, professional networks, and career advancement in a safe, inclusive environment. # Brand Personality This page covers Tech Fleet's Brand personality ## The "Outfit" Metaphor If Tech Fleet were a person, they would wear a bright yellow cardigan, jeans, comfortable shoes, and cute socks. We are approachable, practical, and a little bit bright and cheerful. ## Brand Archetype: The Sage Our brand archetype is The Sage. * Definition and Core Motivation: The Sage seeks truth, shares wisdom, and empowers others through knowledge. * The Sage's Goal: To understand the world and share that understanding to help others grow. * The Sage's Fear: Being misinformed, misleading others, or acting out of ignorance. * Brand Examples: TED, BBC, Harvard University, National Geographic. * How the Sage Manifests in Tech Fleet: We act as a mentor and philosopher. We provide clear, factual, and empathetic guidance without arrogance. We share our knowledge openly to help others succeed. ## What We Are vs. What We Are Not We are thought leaders and experts. We are not influencers, attention-seekers, performers, or win-at-all-costs players. We praise behavior, not identity. | Do This | Not This | | ----------------------------------------------------- | ------------------------------------------ | | "Here is a guide on how to run a great team meeting." | "Watch me run the best team meeting ever!" | | "You did a great job leading that meeting." | "You are a natural leader." | | "We learned a lot from this project failure." | "We never fail, we only win." | # Editorial Style Guide This section covers how to write editorial style for the Tech Fleet Brand. # Voice and Tone This section covers how to portray the proper voice and tone with the Tech Fleet Brand. ## Voice Principles Our voice is how we sound. It reflects our personality and our values. Our tone changes depending on who we are talking to and what the situation is. Our voice must always reflect our commitment to inclusion and equity. * Center mission, vision, and values: Everything we write should reflect our core beliefs. * Match natural language: Speak in a way that our audience understands. Avoid sounding like a robot or a textbook. ## Core Voice Traits ### Welcoming We are inclusive, kind, accessible, open, and friendly. We make sure everyone feels like they belong, regardless of their background or abilities. | Do This | Not This | | --------------------------------------------------- | --------------------------------------------------------- | | "Welcome to the team! We are so glad you are here." | "You have been added to the system." | | "Let's figure this out together." | "You need to fix this." | | "Hi everyone, thanks for joining the call today." | "Attention all attendees, the meeting will now commence." | | "We'd love to hear your thoughts on this." | "Submit your feedback via the portal." | | "Come as you are, we are happy to have you." | "Ensure you meet all prerequisites before participating." | ### Caring We are actively concerned with welfare, non-judgemental, compassionate, and thoughtful. We recognize that people have different needs and we accommodate them. | Do This | Not This | | ---------------------------------------------------------------------- | ------------------------------------------------------------- | | "It looks like you are having trouble with this task. How can I help?" | "Why haven't you finished this yet?" | | "We know this is a hard topic to learn. Take your time." | "This is easy, you should know this by now." | | "Take a break if you need one, your health comes first." | "Push through the pain, we have a deadline." | | "I understand why that was frustrating for you." | "You shouldn't be upset about that." | | "Let me know if you need any accommodations for the meeting." | "Everyone must have their cameras on for the entire meeting." | ### Informative We are useful, enlightening, instructional, and clear. We provide information in a way that is easy to perceive and understand for everyone. | Do This | Not This | | ------------------------------------------------------------------------------------- | -------------------------------------------------- | | "To join a project, first fill out this form. Then, wait for an email from our team." | "Just sign up online." | | "Agile means we build things in small steps so we can learn as we go." | "We use Agile methodologies to optimize delivery." | | "The meeting starts at 2:00 pm EST. Here is the Zoom link." | "See you at the meeting later." | | "If you forget your password, click 'Reset Password' on the login screen." | "Contact support if you can't log in." | | "This document explains our three-year strategy and how we will achieve it." | "Here is the strategy doc." | ## Tone Variations * Formal vs. Informal: Use informal language and slang only in chat or non-official contexts. * Client and Partner Communications: When talking to clients, funders, or partners, our tone should feel professional and respectful, while still being welcoming and caring. * Community Contexts: In our community spaces, the tone can be more relaxed and conversational. | Context | Do This | Not This | | ------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------- | | Slack Chat | "Hey everyone! Who is ready for the weekend?" | "Greetings colleagues. I trust you are prepared for the weekend." | | Partner Email | "Thank you for partnering with us. We are excited to start this project." | "Thanks for the cash! Let's go!" | | Website Copy | "Learn how to lead through service." | "Wanna be a boss? Click here." | | Error Message | "We couldn't find that page. Let's get you back home." | "404 Error: Page Not Found." | | Event Invite | "Join us for a workshop on team building." | "You are hereby summoned to attend a mandatory training session." | ## Humor and Emotion * Memes and GIFs: They must always reflect our core values and never put anyone down. * Punctuation and Emojis: Use exclamation points and emojis in moderation. They can add warmth, but too many can look unprofessional and can be confusing for screen readers. | Do This | Not This | | ------------------------------------------------ | ---------------------------------------------------------- | | "Great job on the presentation today! 🌟" | "GREAT JOB ON THE PRESENTATION TODAY!!!!!!! 🎉🎉🎉🎉🎉" | | "We are so excited to announce our new project." | "OMG WE ARE SO EXCITED ABOUT THIS NEW PROJECT!!!!!" | | "Thanks for your help with this." | "Thanks for your help with this. 🤪" | | "Welcome to the community! 👋" | "Welcome to the community! 🚀🔥💯🙌" | | "That was a funny moment in the meeting." | \[Posting a meme that makes fun of a specific team member] | # Editorial Writing This section covers the mechanics of how we write. It ensures our writing is clear, consistent, and respectful of all people. ## General Writing Principles * Active Voice: Use active voice instead of passive voice. It makes sentences clearer and more direct. * Plain Language: Avoid complex sentences and obscure words. Write so that a 7th grader can understand. This is a key part of our accessibility commitment. * Handling Jargon: Avoid slang and jargon. If you must use a technical term, explain what it means the first time you use it. | Do This | Not This | | ------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | "The team finished the project." | "The project was finished by the team." | | "We use psychological safety, which means creating a space where it is safe to take risks." | "We leverage psychological safety paradigms." | | "Our volunteers built this website." | "This website was built by our volunteers." | | "Please send us your feedback." | "Feedback should be submitted to us." | | "We will review your application next week." | "Your application will be reviewed by us next week." | ## Grammar and Mechanics * Baseline Style: We generally follow AP Style for news and press releases, but prioritize clarity and our specific brand rules above all. * Capitalization: Use sentence case for headlines and titles. Only capitalize the first word and proper nouns. * Proofreading: Always proofread your work and ask a peer to review it before publishing. | Do This | Not This | | --------------------------------------------- | --------------------------------------------- | | "How to build an empowered team" | "How To Build An Empowered Team" | | "Welcome to our new website" | "Welcome To Our New Website" | | "Meet the board of directors" | "Meet The Board Of Directors" | | "Five ways to improve your leadership skills" | "Five Ways To Improve Your Leadership Skills" | | "Join our upcoming learning lab" | "Join Our Upcoming Learning Lab" | ## Tech Fleet Specific Terminology * Brand Name: Always spell it as two words: "Tech Fleet". Never write "TechFleet". * Team Practices: Capitalize "Team Practices" when referring to our specific framework (Service Leadership, Psychological Safety, Collective Decision Making, Empowerment, Shared Ownership, Continuous Improvement, Agility). | Do This | Not This | | ----------------------------------------- | ---------------------------------------- | | "Welcome to Tech Fleet." | "Welcome to TechFleet." | | "We teach the seven Team Practices." | "We teach the seven team practices." | | "Tech Fleet is a nonprofit organization." | "Techfleet is a nonprofit organization." | | "Our Team Practices guide how we work." | "Our team practices guide how we work." | | "Thank you for supporting Tech Fleet." | "Thank you for supporting Tech-Fleet." | ## Inclusive Language and Accessibility We are committed to building a world where people grow together without judgment. Our language must reflect that. Accessibility is a civil right, and our language must respect all individuals. * Race and Ethnicity: Capitalize "Black". Do not capitalize "white". "BIPOC" is acceptable, but specify the exact group when possible. * Gender and Sexuality: We prefer the acronym "2SLBGTAI+". Words like "Queer" or "gay" are acceptable in celebratory or self-identifying contexts. Avoid gendered language. Use the singular "they" and "their" instead of "he/she". Avoid calling adult women "girls". * Disability and Neurodiversity: Avoid victimizing language. Capitalize "Deaf" when referring to the identity or community. Do not capitalize "blind"; prefer "person with vision impairment". Never use ableist words. * Age: Avoid age-related adjectives unless you are stating someone's age directly. * Systemic Terms: Use terms like "historically excluded" carefully and thoughtfully. * User Terminology: Say "people who use the product" or "people who use the services" instead of "users". Say "constituents" instead of "clients" or "beneficiaries" when talking about the nonprofits we serve. | Do This | Not This | | ------------------------------------------- | --------------------------------------------- | | "Welcome, everyone." | "Welcome, guys." | | "The student left their book on the table." | "The student left his/her book on the table." | | "Person with a disability" | "Suffers from a disability" | | "That is a wild idea." | "That is a crazy idea." | | "People who use our website" | "Our users" | # Interface Copywriting Because we build digital products and experiences, we need rules for how we write interface copy. Our UX content must meet WCAG 2.1 AA and WCAG 2.2 AA standards. Here are the guidelines. ## UX Writing Principles * Clarity and Conciseness: Interface text must be short and easy to understand instantly. * Scannability: People don't read web pages; they scan them. Use short paragraphs, bullet points, and clear headings. * Plain Language: Writing should be presented in the most plain language you can use, at a 7th grade reading level. See [Reading Level](/resources/brand-guide/brand-foundations/reading-level-standards) requirements. ## Interface Elements * Buttons and CTAs: Use action-oriented verbs. Tell the person exactly what will happen when they click. * Form Labels: Keep labels short. Use helper text below the field if more explanation is needed. Form labels, instructions, and error messages must be programmatically associated with the right field. | Do This | Not This | | -------------------- | ------------ | | "Submit Application" | "Submit" | | "Create Account" | "Go" | | "Download PDF" | "Click Here" | | "Save Profile" | "Save" | | "Join Project" | "Join" | ## System States and Messages * Error Messages: Be empathetic, clear, and actionable. Don't blame the person. Tell them what went wrong and how to fix it. * Success Messages: Be celebratory but appropriate. Confirm that the action was successful. * Empty States: When a page has no data yet, use the space to encourage action. Tell the person what they can do next. | Do This | Not This | | --------------------------------------------------------------------------------------- | ------------------------ | | "We couldn't find an account with that email. Please check the spelling and try again." | "Invalid email address." | | "Your application was sent! We will email you within two days." | "Success." | | "You don't have any projects yet. Click 'Find a Project' to get started." | "No projects found." | | "That password is too short. It must be at least 8 characters." | "Password error." | | "Your profile has been updated." | "Update complete." | ## Accessibility in UX Content * Alt Text: Always write descriptive Alt Text for images, charts, and icons so screen readers can describe them to people with vision impairments. * Meaningful Links: Never use "click here" as link text. The link text should describe where the link goes. * Media: Provide captions for all pre-recorded video, live captions for live events, audio descriptions for video where meaning depends on visuals, and transcripts for podcasts and audio-only content. | Do This | Not This | | -------------------------------------------------------------------------- | ---------------------------------- | | "Read our Three-Year Strategy" | "Click here to read our strategy." | | Alt text: "A group of four people smiling and looking at a laptop screen." | Alt text: "Image of people." | | "Download the Annual Report PDF" | "Download" | | Alt text: "Bar chart showing a 20% increase in volunteer signups." | Alt text: "Chart." | | "View the event schedule" | "More info" | ## UX Components To ensure our digital products are intuitive and consistent, use these specific rules for common interface components. ### Action Labels (Buttons and Links) * Always use the "Verb + Noun" formula for primary actions (e.g., "Save profile", "Create project"). * Keep labels to three words or fewer. * Do not use vague labels like "Submit", "Go", or "Click here". | Do This | Not This | | --------------------- | -------- | | "Join project" | "Submit" | | "Upload resume" | "Upload" | | "Cancel subscription" | "Cancel" | | "Send message" | "Send" | | "View dashboard" | "View" | ### Date and Time Formatting * Write dates as Month Day, Year (e.g., January 15, 2026). * Do not use ordinal numbers (e.g., 15th). * Write times using a 12-hour clock with am/pm (e.g., 2:30 pm). * Include the time zone if the event is distributed (e.g., 2:30 pm EST). | Do This | Not This | | --------------------------------------------------- | --------------------------------------- | | "The meeting is on March 4, 2026 at 1:00 pm EST." | "The meeting is on March 4th at 13:00." | | "Applications close on November 30, 2026." | "Applications close on 11/30/26." | | "Join us at 9:00 am PST." | "Join us at 9 AM." | | "The event runs from October 1 to October 5, 2026." | "The event runs from Oct 1st-5th." | | "Office hours are at 4:30 pm GMT." | "Office hours are at 16:30." | ### Tooltips * Tooltips should only provide highly contextual, supplementary information. They must never contain essential information required to complete a task, as they are difficult to access on mobile devices and for some screen reader users. * Keep tooltip copy under 100 characters. Do not include links or formatted text inside a tooltip. | Do This | Not This | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | "Your public profile URL." | "This is the URL that other people will see when they view your profile. You can change it later in your account settings by clicking here." | | "Only visible to you." | "This information is private and will not be shared with anyone else on the platform." | | "Must include a special character." | "Your password needs to be strong, so make sure you include at least one special character like an exclamation point or a question mark." | | "Used for account recovery." | "We need your phone number just in case you forget your password and need us to send you a text message to recover your account." | | "Optional field." | "You do not have to fill this out if you do not want to, it is completely up to you." | ### Modals and Confirmation Dialogs * The modal title should clearly state the action being taken or the decision required. * The body text should explain the consequences of the action. * The primary button must match the action described in the title. Never use "OK" or "Yes" for destructive actions. | Do This | Not This | | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | Title: Delete project? Body: This will permanently remove all files. This action cannot be undone. Buttons: Cancel / Delete project | Title: Are you sure? Body: Do you want to do this? Buttons: No / Yes | | Title: Leave team? Body: You will no longer have access to the team's files or chat. Buttons: Cancel / Leave team | Title: Warning Body: You are about to leave the team. Buttons: Cancel / OK | | Title: Publish article? Body: This article will be visible to everyone on the website. Buttons: Cancel / Publish article | Title: Confirm Body: Ready to publish? Buttons: No / Yes | | Title: Discard changes? Body: Any unsaved edits will be lost. Buttons: Keep editing / Discard changes | Title: Unsaved changes Body: You have unsaved changes. Buttons: Cancel / OK | | Title: Remove user? Body: This person will no longer be able to log in. Buttons: Cancel / Remove user | Title: Are you sure? Body: Do you really want to remove this user? Buttons: No / Yes | # Channel-Specific Guidelines Different platforms require different approaches, but our core identity remains the same. Use these guidelines to adapt our voice and visuals to specific channels. ## Social Media Social media is where we act as The Sage, sharing knowledge and building community. * LinkedIn: This is our primary professional channel. The tone should be informative and encouraging. Focus on thought leadership, sharing articles, and celebrating community milestones. Use professional formatting with clear paragraph breaks. * Instagram and Blue Sky: These channels allow for a slightly more casual, welcoming tone. Use them for behind-the-scenes community highlights, quick tips, and event announcements. * Hashtag Strategy: Use 3 to 5 relevant hashtags per post. Always use CamelCase for accessibility (e.g., #TechFleetCommunity, not #techfleetcommunity) so screen readers can parse the words correctly. * Community Engagement: When responding to comments, always be welcoming and caring. If a comment is negative, respond professionally, acknowledge the concern, and move the conversation to a private channel if necessary. Never argue publicly. | Do This | Not This | | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | "Thanks for sharing your perspective! We'd love to hear more about your experience. Feel free to DM us." | "You are wrong about how our program works." | | "Check out our latest article on #ServiceLeadership." | "Check out our latest article on #serviceleadership." | | "Congratulations to the team on a successful launch! 🎉" | "The team launched a project." | | "We appreciate your feedback and will look into this issue." | "That's not our fault, contact support." | | "Join us for a live Q\&A session tomorrow at 2 pm EST." | "Q\&A tomorrow." | ## Email Communications Emails are personal and direct. They should always feel like they are coming from a helpful mentor. * Newsletters: Keep the layout clean and minimalist. Use clear H2 headings for different sections so readers can scan the content. Always include a clear, single call-to-action per section. * Transactional Emails: System emails (like password resets or application confirmations) must be extremely clear and intuitive. Do not use jargon. Tell the person exactly what happened and what they need to do next. * Signatures: All official Tech Fleet emails should use the standard signature template, which includes your name, pronouns, role, and a link to the Tech Fleet website. | Do This | Not This | | -------------------------------------------------------------------------------------- | --------------------------------------------------------- | | "Your application has been received. We will review it and email you within 48 hours." | "System update: Application status changed to pending." | | "Hi \[Name], here is your monthly Tech Fleet update." | "Newsletter Vol. 45" | | "Click the button below to reset your password." | "To initiate the password recovery protocol, click here." | | "Include your pronouns in your email signature." | "Leave your pronouns out of your email signature." | | "Use a clear, descriptive subject line like 'Action Required: Update your profile'." | "Use a vague subject line like 'Important Update'." | ## Presentations and Slide Decks Presentations are visual aids, not teleprompters. They must be accessible and purposeful. * Slide Density: Apply our minimalist principle. Never put more than three bullet points or one core idea on a single slide. If you have more to say, put it in the speaker notes. * Data Visualization: When showing charts or graphs, ensure the data is easy to read. Do not rely on color alone to differentiate data points; use patterns or direct labels. * Templates: Always use the official Tech Fleet slide deck template to ensure consistent typography and logo placement. * Downloads: Coming soon | Do This | Not This | | -------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Use a large, clear chart with direct text labels on the data points. | Use a complex pie chart with a separate color-coded legend that is hard to read. | | Put three short bullet points on a slide. | Put a full paragraph of text on a slide and read it word-for-word. | | Use high-contrast colors for text on slides. | Use light gray text on a white background. | | Include alt text for all images in the presentation file. | Leave the alt text fields blank. | # Brand Visuals # Color Palette ## Color Palette | Color Name | HEX | RGB | Usage | | ---------------- | ------- | ------------------ | ------------------------------------------------------------------------------ | | Deep Space Navy | #01061E | rgb(1, 6, 30) | Primary background color for dark mode sections and hero areas. | | Tech Fleet Blue | #0056A7 | rgb(0, 86, 167) | Primary brand color. Used for primary buttons, links, and active states. | | Action Blue | #1863DC | rgb(24, 99, 220) | Secondary blue used for hover states or secondary accents. | | Growth Green | #56A045 | rgb(86, 160, 69) | Success states, confirmation messages, and secondary brand accents. | | Alert Orange | #EB4F26 | rgb(235, 79, 38) | Error states, warnings, and destructive actions. | | Pure White | #FFFFFF | rgb(255, 255, 255) | Primary background color for light mode sections and text on dark backgrounds. | | Off-White | #F4F4F4 | rgb(244, 244, 244) | Secondary background color for cards or alternating page sections. | | Dark Gray (Text) | #212121 | rgb(33, 33, 33) | Primary body text color on light backgrounds. Ensures WCAG 4.5:1 contrast. | | Medium Gray | #757575 | rgb(117, 117, 117) | Secondary text, placeholder text, and disabled states. | # Grid and Spacing ## The 4px Spacing System Every margin, padding, and spacing value must be a multiple of 4px. Do not use arbitrary values like 10px or 15px. | Name | Value (px) | Value (rem) | Common Usage | | -------- | ---------- | ----------- | ----------------------------------------------------------- | | space-1 | 4px | 0.25rem | Tiny adjustments, spacing inside small components. | | space-2 | 8px | 0.5rem | Spacing between an icon and text, or inside a button. | | space-3 | 12px | 0.75rem | Padding inside small cards or alerts. | | space-4 | 16px | 1rem | Standard margin between paragraphs or form fields. | | space-6 | 24px | 1.5rem | Padding inside standard content cards. | | space-8 | 32px | 2rem | Spacing between distinct sections within a container. | | space-12 | 48px | 3rem | Margin between major page components. | | space-16 | 64px | 4rem | Padding between major page sections (e.g., above a footer). | ## The 12-Column Layout Grid Our layout grid adapts to the screen size while maintaining a 12-column structure. | Size | Gutters | Outer Margins | Max Container Widt | | ------------- | ------- | ------------- | ------------------ | | Above 1400px | 32px | 48px | 1440px | | 1024 - 1399px | 24px | 32px | 1399px | | 768 - 1023px | 16px | 24px | 1023px | | Below 768px | 16px | 12px | 768px | # Iconography Tech Fleet uses Feather Icons (feathericons.com) for all UI iconography. Feather provides a clean, minimalist, and welcoming aesthetic that perfectly matches our design principles. Icon Specifications: * Library: [Feather Icons](https://feathericons.com/) * Stroke Weight: Strictly 2px. Do not alter the stroke weight. * Corners & Caps: Round (default in Feather). * Size: * Standard UI icons should be rendered at 24x24px. * Micro icons (inside buttons or tooltips) should be 16x16px. * Color: Icons should inherit the color of the text they accompany, or use [Tech Fleet Blue](/resources/brand-guide/brand-visuals/color-palette) (#0056A7) when acting as standalone interactive elements. # Illustrations ## Illustration Style Our illustrations are one of the most distinctive parts of our visual identity. They are hand-drawn in feel, technical in precision, and warm in character. Every illustration we use must feel like it belongs to the same family. The three examples below define the rules. ## The Two Illustration Families We use two distinct but complementary illustration styles. Both must always feel like they belong to the same brand. ### Family 1: The Sketch-Fill Style (used for icons and UI illustrations) This style is seen in the partnership icon (three abstract human figures connected by arrows) and the world map illustration.
It has the following characteristics: * Line quality: The outlines are hand-drawn in character, slightly organic and imperfect, never perfectly geometric. The stroke feels like a confident pen or brush stroke rather than a ruler-drawn line. * Fill technique: Shapes are filled with parallel diagonal hatching lines rather than solid color fills. The hatching runs at approximately 45 degrees and is evenly spaced. This gives the illustration a hand-crafted, sketch-book quality. * Stroke weight: Outlines use a medium-weight stroke (approximately 2px to 3px at standard display size). The hatching lines inside shapes are thinner (approximately 1px to 1.5px). * Color: This family uses a single flat color for both the outlines and the hatching. There is no shading, no gradients, and no secondary colors within a single illustration. The primary color for this family is Tech Fleet Blue (#0056A7) or Action Blue (#1863DC) on white backgrounds. * Transparency and layering: Shapes may overlap. Where they overlap, the hatching of the shape on top simply continues over the shape below, creating a layered, stacked effect. * Human figures: When representing people, use simple, abstract silhouette-style figures. The figures are rounded and friendly, not detailed or realistic. They have no facial features. They communicate role and relationship through posture and proximity, not detail. * Motion and connection: Use simple curved arrows to show relationships, collaboration, and flow between figures or concepts. Arrows should match the hand-drawn quality of the outlines.Family ### The Engraving Style (used for hero and section illustrations) This style is seen in the planet illustration (a large circular planet with a habitat dome, satellite dish, and rocket ship on its surface).
It has the following characteristics: * Line quality: This style uses a fine, precise engraving or etching technique. Lines are closely spaced, parallel, and used to build up form, texture, and volume. The overall effect resembles a vintage scientific illustration or a woodcut print. * Texture and form: Volume is created entirely through the density and direction of parallel lines, not through color shading. Areas of shadow have more closely spaced lines. Areas of light have more widely spaced lines or no lines at all. * Stroke weight: All lines are fine and consistent, approximately 1px to 1.5px at standard display size. There is no variation in stroke weight within a single illustration. * Color: This family uses a single flat color for all linework on a white or transparent background.. Use any primary brand color for these. * Subject matter: This style is reserved for larger, more conceptual illustrations that represent the world, the mission, or the journey. Subjects include planets, celestial bodies, spacecraft, habitats, and other space-exploration metaphors that speak to exploration, discovery, and building something new. * Scale and detail: These illustrations are highly detailed and are designed to be viewed at large sizes. Do not use them at small sizes where the fine linework will become illegible. ## When to Use Each Family | Context | Illustration Family | Example Use | | ----------------------------------------------------------- | --------------------- | -------------------------------------- | | UI icons, feature explanations, small diagrams | Family 1: Sketch-Fill | Partnership icon, career path diagrams | | Hero sections, section backgrounds, large visual statements | Family 2: Engraving | Planet illustration, world map | | Social media graphics | Family 1: Sketch-Fill | Post illustrations | | Email headers | Family 1: Sketch-Fill | Newsletter headers | | Landing page hero | Family 2: Engraving | Homepage hero | ## What Not to Do | Do This | Not This | | ----------------------------------------------------------------- | ------------------------------------------------------------------- | | Use a single flat color per illustration. | Use gradients, shadows, or multiple colors within one illustration. | | Keep human figures abstract and silhouette-based. | Draw realistic human faces or detailed anatomy. | | Use hatching to fill shapes in Family 1 illustrations. | Use solid color fills in a Family 1 illustration. | | Use fine engraving lines to build form in Family 2 illustrations. | Use bold outlines or flat fills in a Family 2 illustration. | | Keep the hand-drawn, organic quality of the linework. | Use perfectly geometric, computer-drawn lines that feel mechanical. | # Logo Use the following logo without a wordmark: ## PNG {% file src="/files/zC8jEOGtiwvdx7EZyf9k" %} ## SVG {% file src="/files/h0Aue3ffshtYk90jTNXv" %} ## Color Variants You may use the [primary brand colors](/resources/brand-guide/brand-visuals/color-palette) with the logo to suit your needs. # Photography Our photography must reflect the reality of our community: universal, collaborative, and focused on growth. ## Example
## Photography Specifications: * Subject Matter: Show real people engaged in real work. We prefer candid shots of collaboration (e.g., looking at a screen together, talking in a group) over posed shots of people staring directly into the camera. * Saturation: Photography can be in black and white or full color. * Lighting: Prefer natural, bright lighting. Avoid dark, moody, or heavily artificial studio lighting. * Composition: Keep compositions clean and minimalist. Ensure the subject is the clear focal point and the background is not distracting. * All kinds of identities and backgrounds: Imagery must reflect the universality of the world we are building. Ensure representation across race, gender, age, and ability without tokenizing. * Treatments: Do not use heavy color overlays, extreme filters, or duotones. Keep the colors natural and authentic. # Typography ## Font Family * Headings: Futura PT Bold for all headings to convey strength and forward momentum * Paragraph: Poppins Regular for all body text to ensure maximum legibility and a welcoming, geometric feel. ## Font Downloads
Font FamilyWeights UsedDownload URL
Futura PTBold
PoppinsRegular
## Font Sizes and Spacing * All font sizes are responsive, using rem units (assuming a 16px base). * All text uses a strict 1.2em letter spacing. * Use 110% line height across the board.
TextText
ElementFamilyWeightSize (rem)Size (px)Line HeightLetter Spacing
Display (Hero)Futura PTBold (700)4.0rem64px110%1.2em
H1 (Page Title)Futura PTBold (700)3.0rem48px110%1.2em
H2 (Section)Futura PTBold (700)2.25rem36px110%1.2em
H3 (Subsection)Futura PTBold (700)1.5rem24px110%1.2em
H4 (Card Title)Futura PTMedium (500)1.25rem20px110%1.2em
Body LargePoppinsRegular (400)1.125rem18px110%1.2em
Body StandardPoppinsRegular (400)1.0rem16px110%1.2em
Body SmallPoppinsRegular (400)0.875rem14px110%1.2em
Caption/MicroPoppinsRegular (400)0.75rem12px110%1.2em
# Community Glossary This is a community-contributed glossary of common product terms, and how they’re defined. # How to Get Technical Support {% embed url="" %} You can receive technical support in a couple of ways: 1. **Chat with the TF Discord Community:** Go into Tech Fleet Discord and head to the #support-general channel. Type in that channel what you'd like support from the community. 2. **Create a TF Discord support ticket:** In Tech Fleet Discord, head to the #create-a-ticket channel and click on the button "Create Ticket". A new private channel will be created for you and a moderator in Tech Fleet Discord. You can type whatever you need in that channel. It's all private! 3. **Email us:** Email and type your support request in the email. Someone will get back to you usually within 72 hours (but this is not guaranteed). For a faster response, create a support ticket in Tech Fleet Discord (see #2 on this list). # Join the Tech Fleet Figma Educational Space This page goes over how to add yourself to Tech Fleet's educational space for access to project deliverables in Figma. ## ## What is Figma? Figma is a tool that product people and UX people use. With this tool, you can make mockups, high fidelity designs, or digital working spaces. Tech Fleet uses this tool for project work. All project team trainees should have a Figma account to be able to use Figma (the design tool) and Figjam (the whiteboard tool) during project work. ## Steps to Verify In order to verify yourself on Figma education, Figma must verify you. You must submit a form to request to be added to the Figma education account. 1. This process takes 7 to 10 business days. 2. We need to submit your request after you complete this form. 3. You will receive an email from Figma once they verify you. Here's the form to fill out: {% embed url="" %} {% endembed %} # The Great Tech Fleet Discord Migration Video Tutorials This page covers everything you need to know about Discord migration for Tech Fleet community! # Discord FAQ TL;DR version of everything you need to know about Discord migration! ## What is happening with Tech Fleet community? Tech Fleet is migrating from Slack to Discord! \ \ Growth and Development Guild has led the charge. Tech Fleet has carefully configured Discord to make it easy to use, and more elegant than Slack. We've worked for the past year to configure, test, and validate the features and setup. #### Check out the videos here: {% content-ref url="/pages/ZsGRudRhH7zDwbRQ32uI" %} [Discord Basics](/resources/the-great-tech-fleet-discord-migration-video-tutorials/discord-basics) {% endcontent-ref %} ## Why is this happening? In short: we're doing this to better serve our community members. Discord offers way more features that are better for a community experience than the Free version of Slack. We've "hit our limits" as a community in Slack. Discord offers more personalized and powerful capabilities that community members can use. #### Check out the videos here: {% content-ref url="/pages/ZsGRudRhH7zDwbRQ32uI" %} [Discord Basics](/resources/the-great-tech-fleet-discord-migration-video-tutorials/discord-basics) {% endcontent-ref %} ## What's going to happen in Slack? Slack will be "decommissioned" for community use. We will keep it up in September 2024. After which, we're going to remove all members and channels. Slack will be the official company tool for Tech Fleet. The Board of Directors and employees of the nonprofit will use Slack from now on. The community will use Discord from now on. #### Check out the videos here: {% content-ref url="/pages/ZsGRudRhH7zDwbRQ32uI" %} [Discord Basics](/resources/the-great-tech-fleet-discord-migration-video-tutorials/discord-basics) {% endcontent-ref %} ## How long will Tech Fleet Slack be around? For the community, Slack for Tech Fleet will be around for the month of September 2024. For the employees and Tech Fleet board of directors, Slack will be used as a community chat tool forever more. #### Check out the videos here: {% content-ref url="/pages/ZsGRudRhH7zDwbRQ32uI" %} [Discord Basics](/resources/the-great-tech-fleet-discord-migration-video-tutorials/discord-basics) {% endcontent-ref %} ## What do I need to know about Discord? 1. Discord has amazing features, more features than Slack, to help us manage the community in better ways 2. Discord has better security features than Slack 3. Discord has more elegant meeting and chatting abilities compared to Slack #### Check out the videos here: {% content-ref url="/pages/rUh6Bm9hM88VbzWaWJlZ" %} [Security Protocol in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/security-protocol-in-tech-fleet-discord) {% endcontent-ref %} {% content-ref url="/pages/ZsGRudRhH7zDwbRQ32uI" %} [Discord Basics](/resources/the-great-tech-fleet-discord-migration-video-tutorials/discord-basics) {% endcontent-ref %} ## How do I get support in Tech Fleet? Several ways! 1. Get guidance in your career with our guidance channels 2. Get technical support with our support ticket system 3. Get a community buddy and receive some help from peers #### Check out the videos here: {% content-ref url="/pages/MobHKJDYfiHtJxbzqovf" %} [Getting Career Guidance in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/getting-career-guidance-in-tech-fleet-discord) {% endcontent-ref %} {% content-ref url="/pages/9gRxnNoc506J1tclGj5n" %} [Get Technical Support in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/get-technical-support-in-tech-fleet-discord) {% endcontent-ref %} {% content-ref url="/pages/kVJtFZ77FpnRNZ7zvf4u" %} [Get a Tech Fleet Buddy](/resources/the-great-tech-fleet-discord-migration-video-tutorials/get-a-tech-fleet-buddy) {% endcontent-ref %} ## How do I join Tech Fleet Discord? 1. Go to 2. Fill out the form 3. Receive an email after you submit the form 4. Click on the Discord invite link in the email 5. Login to Discord 6. Verify your mobile phone number 7. Onboard to Discord #### Check out the videos here: {% content-ref url="/pages/RtasHebSBVrFVTwip0Q7" %} [Sign Up Process for Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/sign-up-process-for-tech-fleet-discord) {% endcontent-ref %} {% content-ref url="/pages/rUh6Bm9hM88VbzWaWJlZ" %} [Security Protocol in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/security-protocol-in-tech-fleet-discord) {% endcontent-ref %} ## How do I chat and interact in Discord? 1. Type messages in channels where you have the permission. 2. Join live stream video and voice channels to chat it up with your community peers. 3. Create threads for replies to messages. 4. Tag people or roles to alert them when you send messages. 5. Create, mark, or edit events in Discord. #### Check out the videos here: {% content-ref url="/pages/uuMLg2YViJBeKc1wEl3X" %} [Managing Events in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/managing-events-in-tech-fleet-discord) {% endcontent-ref %} {% content-ref url="/pages/jmAmxGk1X2LaZ10DVqDT" %} [Using Roles for Alerts, Notifications, and Channel Access](/resources/the-great-tech-fleet-discord-migration-video-tutorials/using-roles-for-alerts-notifications-and-channel-access) {% endcontent-ref %} {% content-ref url="/pages/tKaHmssX9RdAfmQnhOka" %} [Basic Chatting Abilities in Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/basic-chatting-abilities-in-discord) {% endcontent-ref %} ## How do I get ready for project work? You must get new Roles in Discord to get ready for project work as an observer, apprentice, co-lead, or mentor. Without these roles you will not see any channels related to projects. This is by design, so that you don't see notifications for them if you don't want to. This process is straight forward. Learn more about it in the videos below. #### Check out the videos here: {% content-ref url="/pages/KbUFqf2JKFRF4XJINFn7" %} [Getting on Projects in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/getting-on-projects-in-tech-fleet-discord) {% endcontent-ref %} ## How do I get ready for classes? You must get new Roles in Discord to get ready for masterclass work. Without these roles you will not see any channels related to masterclasses. This is by design, so that you don't see notifications for them if you don't want to. This process is straight forward. Learn more about it in the videos below. #### Check out the videos here: {% content-ref url="/pages/M9iDU7PAV2RponzeTLIV" %} [Masterclasses in Tech Fleet Discord](/resources/the-great-tech-fleet-discord-migration-video-tutorials/masterclasses-in-tech-fleet-discord) {% endcontent-ref %} # Discord Basics This section covers what Discord is, why it's good for the community, what's happening with Slack, and the features of Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Introduction to The Great Tech Fleet Migration **TL;DR:** Tech Fleet's migrating from Slack to Discord! #### Here's a video: {% embed url="" %} Introducing the Great Tech Fleet Migration! {% endembed %} #### Here's the text version:
Introduction to The Great Tech Fleet Migration **Tech Fleet’s got some exciting news!** Join us in celebrating Tech Fleet's 4th anniversary with the launch of our new Discord community! After four years on Slack, we’re excited to bring you a more personalized experience on Discord. We know you have questions, but don’t fear! In this video series, Tech Fleet’s Growth and Development Guild will guide you through everything you need to know to thrive on Discord. **Here are the basics** Soon, all Tech Fleet Slack members will receive instructions on how to transfer and onboard to Discord. Get ready for an exciting new chapter! **What's happening?** Tech Fleet's community is migrating from Slack to Discord! Discord is an online community platform. It's specialized for online communities and offers fantastic features that we currently lack in Slack. This includes: 1. Alerts and notifications 2. Read-only channels 3. Automated messages 4. Live streams 5. Dedicated apprentice, lead, and observer channels 6. Progressive disclosure info 7. Member permissions 8. Custom integrations 9. Security bots 10. Support ticket system Overall, it's a richer experience than Slack **Why are we doing this?** We're migrating to Discord to better support our community and offer you a better experience online! With Discord, Tech Fleet can better support your growth and success. We can do it in ways that you'd expect from a mature online community. We can fulfil our commitment to creating fair access to tech careers using improved tools in Discord. This series covers the following topics: 1. Features we're using 2. How to join 3. Security protocols 4. How to start interacting 5. How to receive support 6. How to start observing projects 7. How to start joining masterclasses 8. How to start joining as an apprentice, lead, or mentor on projects.
## What's Happening with Tech Fleet Slack? **TL;DR:** Slack will be used for the Board of Directors, and the Community will use Discord from now on! #### Here's a video: {% embed url="" %} What's Happening with Tech Fleet Slack? {% endembed %} #### Here's the text version:
What's Happening with Tech Fleet Slack? Here’s a quick summary of what to expect with Tech Fleet’s Slack and Discord communities moving forward. Discord will be the official community forum for all contributors in the Tech Fleet community. In Discord you can chat, apply for projects, sign up for masterclasses, get help, shadow meetings, and more. Tech Fleet Slack will stop being used by community members. It will become the official company tool for the Tech Fleet Professional Association, a nonprofit with public charity status in the U.S. All full-time employees, board members, and independent contractors will be granted access to Tech Fleet Slack for company use. All apprentices, leads, observers, mentors, clients, and partners will use Tech Fleet Discord. Members of the Tech Fleet community will primarily use Discord instead of Slack. If you need to communicate with Tech Fleet's company side, you can do so through the Discord support portals. We understand this is a big change, so we'll keep the Slack community open for a while after the official migration to assist any members who need help during the transition.
## Key Features in Tech Fleet Discord **TL;DR:** So. Many. Great. Features. So. Much. Better. Than. Slack. #### Here's a video: {% embed url="" %} Key features in Tech Fleet Discord {% endembed %} #### Here's the text version:
Key Features in Tech Fleet Discord If you’re new to Discord you may be asking yourself: Why Discord? What can Discord do? We’re going to cover the features and abilities that make Discord such a powerful online community tool. Here’s an overview of new abilities in Discord for Tech Fleet community members: **Engagement** 1. Discord is built specifically with online communities in mind. In Tech Fleet’s Discord you’ll have everything you need to interact with the community and get involved in work. 2. Discord lets you assign roles to personalize your experience. Once you choose your roles, you'll automatically get alerts and access to new channels related to those roles. 3. Project teams have more control over permissions in their channels. For instance, only leads can post in announcement channels on Discord, keeping communication clear and concise. Teams can adjust these permissions anytime by submitting a support ticket in the Tech Fleet Discord. 4. Discord syncs with events on Tech Fleet’s calendar, making it easy for anyone who wants to engage with projects to stay updated and plan ahead. 5. Some channels are open for everyone, while smaller teams like moderators and guilds have private channels for collaborative work. This keeps communication clean, allowing everyone to focus on important messages like announcements and project postings. 6. In Discord, anyone can join a video chat via live streams. Project teams have dedicated live stream channels, and the community hangout channel is open for everyone. These live stream rooms are perfect for brainstorms, discussions, or online activities. No need for third-party links—just jump in and start collaborating! **Support and Security** 1. Discord allows any community member to create a support ticket if they need help. This ensures members can get assistance from a real person—either a moderator or guild member in Tech Fleet. 2. Unlike Slack, everyone in the Tech Fleet Discord has signed up for Tech Fleet and agreed to our community policies. That means no more spam or random people hanging around! 3. Also unlike Slack, Tech Fleet Discord members are not allowed to direct message each other. This enhances security, protects members from unwanted messages, and prevents the sharing of malicious files and links that could compromise online safety. 4. Tech Fleet Discord uses moderator bots to monitor activity and content in channels. These bots block inappropriate words, links, images, and files, enhancing online security and protecting the server from threats like hacking. 5. Tech Fleet’s Discord bots also assist by responding to questions and common concerns on behalf of moderators. This ensures members get the help they need promptly, without waiting for a human response. Overall, Discord provides a more holistic, safe, secure, and interactive experience than Slack could for our community. We're able to evolve with new experiences and new support! In the other videos, check out the details of how to get started in Discord and how to get the most out of Discord in the Tech Fleet community.
## Setting Default Channels in Discord {% embed url="" %} How to set default channels in Discord {% endembed %} ## Head to the next lesson: # Sign Up Process for Tech Fleet Discord This page covers all you need to know before, during, and after signing up to Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Verified Phone Numbers Required on Discord Accounts **TL;DR:** you must have a verified mobile phone number to use Tech Fleet Discord. If you don't, you can email us to get in another way. #### Here's a video: {% embed url="" %} Verified phone numbers required on Discord Accounts {% endembed %} #### Here's the text version:
Verified Phone Numbers Required on Discord Accounts **Tech Fleet Discord requires all members to sign up with a verified mobile phone number.** Why? It's for everyone's protection in the community. This is a feature that Slack doesn't offer, and leads to bad actors in Slack. This setup is the highest level of security in Discord. It prevents some bad actors in the world from trying to join Tech Fleet Discord for the purposes of scamming or spamming members. Without this, members could invite malicious bots that may hack our new community or other kinds of bad things, or may impersonate others in Discord to try to scam members of the community. We don't want this to happen at all. We're committed to providing a safe, secure, and inclusive forum to help you break into Tech. We've enabled Discord's built-in feature to verify members with phone numbers to prevent these security and safety issues.  **Here's how it works:** When you register for an account, or sign in, after receiving the Discord invite link, Discord is going to ask you to enter a phone number for your account. This phone number must be unique, and can't be used on other Discord accounts. Enter the phone number you want to use for your Discord account. You cannot use a virtual phone or landline phone. Discord requires a real mobile phone for this.  If you don't have a mobile phone, contact Tech Fleet at info at tech fleet dot org and we may be able to help you get into Discord other ways.  After you enter the phone number, Discord will ask you to enter a code you receive on the mobile phone number. Enter the code you receive in the prompt. If you receive an error that another account is using the phone number, this happens! Don't worry. You can resolve this! First, try logging into the other account with the phone number you've already associated. This may be from an old account you made a while ago on Discord and didn't remember. IF you are able to remember the password, login to the old account and use that account for Tech Fleet Discord. Alternatively, if you don't want to use the old account, you can remove the account from Discord. Login to the old account, and then remove it from the settings of Discord before you proceed.  **Please note:** If you remove a Discord account, it may take up to 15 days for the account to be fully removed from Discord's records. You may need to wait 15 days or more in order to create a new Discord account with the same phone number you had on the old account.  If you need assistance from Discord, or this doesn't resolve your issue, you should create a support ticket with Discord the company. Discord can help you resolve this issue on their support team.  Go to the Discord support form online using the link we just gave you and create a new support request with Discord. Let Discord support know you have seen the error about the duplicate account with the same phone number. Ask them to help you resolve this issue, and they will help resolve it on their tech support. **And remember:** Tech Fleet is only an email away. Contact our team at info at tech fleet dot org to chat with someone outside of Discord for assistance or conversation. We're here for it!
## How to Sign Up to Tech Fleet Discord **TL;DR:** Fill out the new form to get into Tech Fleet Discord on [techfleet.org/join](https://techfleet.org/join) or [Join Tech Fleet Discord](/resources/quick-links/join-tech-fleet-discord). Then you will receive an email with a Discord invite link. #### Here's a video: {% embed url="" %} How to sign up to Tech Fleet Discord {% endembed %} #### Here's the text version:
How to sign up to Tech Fleet Discord **Getting into Tech Fleet Discord is easy!** Before joining Tech Fleet’s Discord community, everyone must agree to Tech Fleet’s policies and procedures through the new sign up form we've created. You must complete this form to access the Discord community link. After you submit the form, we will email you a Discord invite link that only you can access. **Here are the steps to receive your Tech Fleet Discord invite link:** 1. Go to the Tech Fleet website, tech fleet dot org. 2. Click on the Join Discord button. 3. This will take you to tech fleet dot org back slash join. Alternatively, you can get to this page from the Tech Fleet User Guide. Click on the Join Discord menu item in the user guide. Click on the link within that page to be taken to the Tech Fleet sign up form. 4. Fill out your basic information. This includes your certifying that you're over eighteen years of age, your first name, last name, your email, and your Discord username. You do not need a Discord username before you join Tech Fleet Discord. Please note: we're committed to keeping you safe and secure. This includes your data. Your data is securely stored. Tech Fleet does not share your information with third-parties. Tech Fleet does not use this information for marketing unless you opt in to marketing on our newsletter. Tech Fleet will send communications to your email you provide related to transactional actions you do in Tech Fleet. Please review our privacy policy for information on how your data is protected and secured. You can find the link to this policy on the footer of our website, or in the Sign up form for Tech Fleet that we cover in this video. 5. In the form, read and agree to all Tech Fleet’s policies. By joining, you agree to abide by all policies. Read each policy carefully before joining Tech Fleet. Violations of Tech Fleet's policies can result in removal from Tech Fleet. 6. We expect the Tech Fleet community to read through our user guide before joining the Discord. We're going to ask you basic questions about the Tech Fleet community before you join the Discord. The purpose of this is to encourage everyone to read through the user guide before joining. This provides basic information that's important to know before you join. While we won't prevent you from joining if you get these answers wrong, it's important to know these answers so that you have the best experience possible. You will receive an email with your scores after you submit, so that you know what the real answers are. 7. When you're ready, submit the form. 8. After submitting the form, you will receive an email with an invite link to Discord. The email we send the link to will be the same email you filled out on the form. 9. Click the invite link in the email to start the Discord onboarding process. You need to login to an existing account or register for a new account on Discord in order to get into the community. 10. If you get stuck in this process at any time, Tech Fleet is here to help! Email us at info at tech fleet dot org for support getting into Discord. Check out the next sections in this series to learn how to finish Discord onboarding in Tech Fleet Discord, and how to customize your experience in Discord.
## Onboarding Flow in Tech Fleet Discord **TL;DR:** When you first join Tech Fleet Discord, go through the Onboarding flow to customize your experience / alerts / channels, and agree to the rules. #### Here's a video: {% embed url="" %} Onboarding flow in Tech Fleet Discord {% endembed %} #### Here's the text version:
Onboarding Flow in Tech Fleet Discord Discord has a feature called "onboarding" which allows communities to configure members' preferences when they join. This is valuable because it makes it easier for members to see only the channels and alerts that they care about, and nothing more. For the first time in Tech Fleet's history, you will get personalized alerts based on your onboarding selection! Here are the steps for onboarding in Tech Fleet Discord: **Intro page:** Click through on this page to get to the onboarding questions. **Question 1:** Have you read and agreed to the Tech Fleet Policies? You should have done so on the sign up form! Choose yes if you have done so. Choose no if you haven't, and a Tech Fleet Moderator can help you after onboarding. **Question 2:** What kinds of career topics do you want to receive support for? Your answers here unlock channels and alerts based on what areas you want to focus on. You can change this later. Choose all that apply. **Question 3:** What kinds of activities you want to do in Tech Fleet? Your answers here unlock channels and alerts based on what areas you want to focus on. You can change this later. Choose all that apply. **Post Onboarding** After you're done onboarding, you will be asked to agree to the Tech Fleet Rules before you can interact. Read and agree to all of the rules for our community. It's crucial that all members abide by the rules and policies for the safety and success of our members. You will be able to check out the most common first tasks in Tech Fleet Discord on the Server Guide. This provides important links and access to channels that are good to read before you jump into the community further.
## Head to the next lesson: # Common Channels in Tech Fleet Discord Here's a page describing all of the relevant channels in Tech Fleet Discord and how to utilize them.
"Start Here" Channels **channel-guide** - Channel Guide has a description about all of the channels in Discord. **safety-check** - Safety Check channel covers important information about how to secure yourself on Discord communities. All community members must read through this channel and turn off their Direct Message settings in Tech Fleet Discord. **about-us** - About Us channel covers information about Tech Fleet as an organization. ⁠ **user-guide** - User guide channel has links to the Tech Fleet user guide. ⁠**rules** - Rules channel covers Tech Fleet's policy information and links to our policies that every community contributor agrees to by interacting with the community in all scenarios. ⁠ **official-links** - Official links channel provides official links for Tech Fleet. Always use this channel and DO NOT click on random links online for Tech Fleet, as they might not be the official links. ⁠👋 **welcome** - Welcome channel shows the people who join the Discord community. **⁠introduce-yourself** - Introduce Yourself channel is where you can post introductions if you are new to Tech Fleet Discord.
"Live Stream" Channels **⁠tech-fleet-stage** - Tech Fleet Stage is where Tech Fleet public events will be hosted, like talks or working sessions. ⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **hangout** - Hangout channel is a voice channel for anyone in the Tech Fleet community to join and hang out with others at any time. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
"Announcements" Channels ⁠**announcements** - Announcements channel shares general announcements from Tech Fleet guilds and leadership. This channel is read-only for most of the community. **⁠project-openings** - Project Openings channel is visible if you have the @Projects role (this role can be obtained through the ⁠project-role channel). It shows openings for new projects. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **⁠masterclass-openings** - Masterclass Openings channel is visible if you have the @Masterclasses role (this role can be obtained through the ⁠masterclass-role channel). It shows openings for new masterclasses. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **mentor-openings** - Mentor Openings channel is visible if you have the @Mentors role. It shows openings for new group mentorship. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
"Project Alerts" Channels **calling-all-observers** - channel dedicated to alerting Observers when meetings are about to happen. Only people with the @Observers role can see this. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **calling-all-apprentices** - channel dedicated to alerting apprentices. Only people with the @Apprentices role can see this. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **calling-all-leads** - channel dedicated to alerting co-leads. Only people with the @Leads role can see this. SSee our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **calling-all-mentors** - channel dedicated to alerting mentors. Only people with the @Mentors role can see this. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
"Community" Channels **general** - General channel hosts general chat in Tech Fleet Discord. **⁠lgbtqia-space** - LGBTQIA+ channel is dedicated to those who identify with the LGBTQIA+ community, along with its allies and supporters. ⁠ ⁠**kudos** - Kudos channel is the place where anyone in Tech Fleet Discord can post recognition of other peers in the Tech Fleet community based on working together. **personal-project-help** - Personal Project Help is a channel where anyone can post to receive feedback, research, or other help with work they are doing outside of Tech Fleet. ⁠ **portfolio-review** - Portfolio Review channel lets you post your portfolio case studies and ask for others in the Tech Fleet Community to review and give you feedback. **⁠pets-of-tech-fleet** - Pets of Tech Fleet is the channel where you post pictures of your pets and spread the pet love. **⁠ideas-and-feedback** - Ideas and Feedback Channel is where Guild members will post to receive feedback about pertinent work they're doing. ⁠
"Guidance" Channels **⁠guidance-general** - General Guidance channel provides an opportunity for any Tech Fleet community contributor to post or respond to things to provide guidance to peers in the community. Any community contributor can access this. ⁠portfolio-job-guidance - Portfolio Guidance channel provides opportunities for people to get or give guidance about Portfolios. In order to receive access to this channel, you must first go to the ⁠job-help-roles channel and assign yourself the @Portfolio Help role, then you will receive access to this channel. ⁠ ⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **portfolio-job-guidance** - Job Help Guidance channel provides opportunities for people to get or give guidance about Job Search. In order to receive access to this channel, you must first go to the ⁠job-help-roles channel and assign yourself the @Job Search Help role, then you will receive access to this channel. ⁠ux-guidance - UX Design Guidance channel provides opportunities for people to get or give guidance about UX Design. In order to receive access to this channel, you must first go to the ⁠career-path-roles channel and assign yourself the @UX Design role, then you will receive access to this channel. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **ux-guidance** - UX Research Guidance channel provides opportunities for people to get or give guidance about UX Research. In order to receive access to this channel, you must first go to the ⁠career-path-roles channel and assign yourself the @UX Research role, then you will receive access to this channel. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **⁠product-strategy-guidance** - Product Strategy Guidance channel provides opportunities for people to get or give guidance about Product Strategy. In order to receive access to this channel, you must first go to the ⁠career-path-roles channel and assign yourself the @Product Strategy role, then you will receive access to this channel. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **⁠project-management-guidance** - Project Management Guidance channel provides opportunities for people to get or give guidance about Project Management. In order to receive access to this channel, you must first go to the ⁠career-path-roles channel and assign yourself the @Project Management role, then you will receive access to this channel. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **technical-guidance** - Development Guidance channel provides opportunities for people to get or give guidance about UX Design. In order to receive access to this channel, you must first go to the ⁠career-path-roles channel and assign yourself the @Front-End Development , @Back-End Development , or @Blockchain Development roles, then you will receive access to this channel. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **buddy-up** - observer guidance channel offers help for observers. In order to see this, you must have the @BuddyUp role. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **apprentice-guidance** - observer guidance channel offers help for observers. In order to see this, you must have the @Observers role and the @Projects role. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **lead-guidance** - observer guidance channel offers help for observers. In order to see this, you must have the @Observers role and the @Projects role. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. **mentor-guidance** - observer guidance channel offers help for observers. In order to see this, you must have the @Observers role and the @Projects role. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
"Projects" Channels ⁠**project-role** - Join Projects channel allows you to see information about how to start joining projects, and lets you assign yourself the @Projects role to receive access to other role channels and obtain the @Observers , @Apprentices, @Leads , or @Mentors roles. ⁠observers-get-ready - Get Ready Observers channel is dedicated to community contributors who want to start observing teams in Tech Fleet. Within the channel, you can access important information and links from the User Guide, and assign yourself the @Observers role which grants you access to observer channels and project team channels. In order to view this channel, you must first go to ⁠project-role channel and assign yourself the @Projects role, then you will be granted access to this channel to assign yourself the observer role. ⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. apprentices-get-ready - Get Ready Apprentices channel is dedicated to community contributors who want to start apprenticing on teams in Tech Fleet. Within the channel, you can access important information and links from the User Guide, and assign yourself the @Apprentices role which grants you access to apprentice channels. Once you apply and are selected for a project, you will be added to additional appropriate project team channels. In order to view this channel, you must first go to ⁠project-role channel and assign yourself the @Projects role, then you will be granted access to this channel to assign yourself the apprentice role. ⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. leads-get-ready - Get Ready Leads channel is dedicated to community contributors who want to start co-leading on teams in Tech Fleet. Within the channel, you can access important information and links from the User Guide, and assign yourself the @Leads role which grants you access to leads channels. Once you apply and are selected for a project, you will be added to additional appropriate project team channels as a lead. In order to view this channel, you must first go to ⁠project-role channel and assign yourself the @Projects role, then you will be granted access to this channel to assign yourself the lead role. ⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions. ⁠mentors-get-ready - Get Ready Mentors channel is dedicated to community contributors who want to start mentoring on teams in Tech Fleet. Within the channel, you can access important information and links from the User Guide, and assign yourself the @Mentors role which grants you access to related mentoring channels to see mentoring opportunities. In order to view this channel, you must first go to ⁠mentors-get-ready channel and assign yourself the @Mentors role, then you will receive access to mentor-related channels.⁠See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
"Masterclasses" Channels masterclass-role - Join Masterclasses channel allows you to view information about how to start joining masterclasses, and assign yourself the @Masterclasses role which grants you access to masterclass-related channels. See our [Discord Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) for instructions.
⁠ # Security Protocol in Tech Fleet Discord This page covers the important facets of security protocol that all Tech Fleet Discord members must follow. Read this information carefully, and treat it as highest priority. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Security Account Settings in Tech Fleet Discord **TL;DR:** set these security settings to prevent bad things from happening to your Discord account. Check the video or text below to learn more. #### Here's a video: {% embed url="" %} Security account settings in Tech Fleet Discord {% endembed %} #### Here's the text version:
Security Account Settings in Tech Fleet Discord Before you interact with Tech Fleet, you should set up your account to be the most secure in Discord. Here's how to do it. Here's are the steps to secure your Discord account in Tech Fleet's server: 1. Click on your Profile picture on the bottom left of Discord 2. Pull up your profile settings 3. Go to "Privacy and Safety" options. 4. Go to the "User Settings" tab. 5. Block all DM messages from friends. 6. Block all DM messages from others. 7. Filter all DM messages. 8. Toggle off the "Allow direct messages from other server members" option 9. Toggle off the "Allow access to age-restricted servers" option 10. Toggle off the "Allow access to age-restricted commands from apps in Direct Messages" option 11. Go to the "Server Settings" tab and select "Tech Fleet" from the server selection dropdown 12. Toggle off "Direct Messages" option  Additionally, follow Tech Fleet Policies for security. All Tech Fleet members are expected to follow the Discord Policy for community safety standards. Direct messages to members about non-Tech Fleet issues, solicitation, and other forms of spamming are against the rules in Tech Fleet. Do not do this, or you are at risk of being removed from our community. Read more about this in the Tech Fleet Policies found in the user guide.
## Securely Direct Messaging in Tech Fleet Discord **TL;DR:** DO NOT accept friend requests from strangers. DO NOT message randos. Follow the proper protocol to safely message people privately. Check the video or text below to learn more. #### Here's a video: {% embed url="" %} Securely Direct Messaging in Tech Fleet Discord {% endembed %} #### Here's the text version:
Securely Direct Messaging in Tech Fleet Discord Do not accept friend requests, and do not direct message people in Discord, without following the proper steps. Be proactive and careful online when interacting with links or files. Unlike Slack, you should never accept a friend request, or direct message someone in Discord without following protocol described in this video. People can send some really malicious files, links, or messages in DM. A lot of hacks happen this way. It's a security concern for keeping you all safe online in Tech Fleet forums.   Please report any suspicious messages or friend requests you receive to a moderator using the Tech Fleet Discord ticket system.   It's not that we don't want you to have friends! We do! We promise! It's that we'd like to protect you all and Tech Fleet from online harm. Only you can prevent this, by following these guidelines and not interacting with links, files, or messages sent to you. Please use public threads in Discord to message people individually. Right-click a message and select "Create Thread". Everyone has permissions in public channels. We hope this will be what you need to break out further conversations with your peers in the online community. [See Basic Interation section for instructions.](/resources/the-great-tech-fleet-discord-migration-video-tutorials/basic-chatting-abilities-in-discord) If you need a private chat, go to Create a Ticket channel under the Support menu in Tech Fleet Discord. Create a support ticket and a Tech Fleet mod will discuss your needs. [See Get Support section for instructions.](/resources/the-great-tech-fleet-discord-migration-video-tutorials/get-technical-support-in-tech-fleet-discord) If you ever receive a friend request from someone you don't know, or think you know, IGNORE IT. REPORT IT. ALWAYS ASSUME A RANDOM DM OR FRIEND REQUEST IN DISCORD IS A SCAM. Here's how to securely direct message people in Discord 1. In a public channel, YOU tell THEM to DM YOU. Tell them "Friend request and DM me". Wait for the other user to request you as a friend. 2. Click on their profile pic from the general channel. 3. Check your friendship request in Discord from within the same public channel (by clicking on the other person's profile picture to see your pending request) to ensure your friend request ties back to the same person. It's best to do this so that you can be sure the friend requests you see tie back to the real person. After all, someone may be impersonating that person and trying to message you! 4. Once the friend request is accepted in discord, you can direct message with the person. 5. Go to your direct messages with the new friend, and wave to your new verified friend. 6. Now you can chat safely in a direct message!  WE REPEAT: DO NOT ACCEPT FRIEND REQUESTS IF YOU DID NOT FOLLOW THIS PROTOCOL. IF YOU SEE A RANDOM FRIEND REQUEST IN DISCORD, IT IS PROBABLY A SCAMMER. REPORT ALL SCAMMERS TO TECH FLEET MODERATORS. IGNORE THE REQUEST. DO NOT INTERACT WITH THE MESSAGE OR THE PERSON. Thanks for following security procedures for the Tech Fleet Community. Your community members appreciate your diligence and attention to these important ways in keeping us all safe online. If you have any questions, please email Tech Fleet at info at tech fleet dot org, or Create a support ticket in Tech Fleet Discord to speak with a moderator.
## Sharing Links in Tech Fleet Discord **TL;DR:** Bots are set up to block any link that's shared, for the purposes of security. You can share links in special channels. Check the video or text below to learn more. #### Here's a video: {% embed url="" %} Sharing links in Tech Fleet Discord {% endembed %} #### Here's the text version:
Sharing Links in Tech Fleet Discord **Be proactive and careful online when interacting with links or files** In order to properly send links in Discord, use the Link Sharing channels. These are set up in Tech Fleet Discord. People can send some really malicious things when sending you links, files, or messages. A lot of hacks happen this way. This is a big security concern in Tech Fleet forums. Here's the good news: Tech Fleet Discord is configured to help prevent this as much as possible. Unlike Slack, Tech Fleet Discord has bots that will block links from being sent in channels if they are not officially whitelisted, or sent in official "link sharing" channels. This is set up for the security of the community. If you send a link that's not whitelisted, or in a community channel, it will be deleted and you will receive a warning. You may not be able to talk for 2 minutes if you attempt to send the link again. **Send links in the "Link Sharing" channels of Discord** You can also send links in the Portfolio Help channel. Additionally, each project has their own link sharing channel, and the community has a dedicated "Link Sharing" channel as well. We're doing this for you. Your protection online in our community is very important. It is better for everyone in the community that you don't send random links to websites. You never know what's behind that website that looks trustworthy!
## Head to the next lesson: # Basic Chatting Abilities in Discord {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Sending Chat Messages in Tech Fleet Discord **TL;DR:** You can chat in channels where you have the permission, but not all channels. It's best to make a thread when having conversations with people. Learn how below. #### Here's a video: {% embed url="" %} Sending chat messages in Tech Fleet Discord {% endembed %} #### Here's the text version:
Sending Chat Messages in Tech Fleet Discord Here's everything you need to know about sending messages in Tech Fleet Discord. **To type into channels** Your account must be verified as a human. Discord takes care of this for you, but you need to do one thing. You will go through the onboarding steps when you join. Then you must go into one of the community channels to take the last step and click on a button. This ensures that you are human, and not a bot. Once you do this, voila! Channels open for you to type. You can type in any channel that has the permission to type!  **To alert others in a Discord message** You can do what's called "tagging" them, or tagging an entire role of people. You can't tag entire groups in every channel, but you can do this in some channels. To tag people or groups, simply type the "at" symbol in the chat. Start typing the user's username you want to tag. Select the user, or the role, and hit enter on your keyboard. Then, when you send the message, whomever gets tagged will see a channel notification on their Discord. This allows them to get a heads up when you want to get their attention. **Some channels are Read-Only** These read-only channels are meant for guilds or moderators to type in. If a channel is read-only, the text box will look like one of these two things, and you won't be able to type in it. If you don't run your own Discord server, ignore the message that says "Follow". However, you may be able to make a thread from any message you see in a read-only channel. Follow the next steps to make threads. **Creating Threads** If you want to reply to people in messages, it's best to make a thread. Threads are a great way to keep channel messages between your peers in the community clean. To make a thread in Discord, hover over or right-click the message, and select "Create Thread". A new thread will be created. Provide a name for the thread, and type your message to begin the thread. Be sure you tag your buddies in the thread, or tag "Community" so that anyone can see the thread contents. Otherwise, you may be talking in the thread that no one else notices! That's the basic gist of how to message in Tech Fleet Discord. Get out there and chat with your community peers!
## Live Stream Channels in Tech Fleet Discord **TL;DR:** Live streams are video and voice calls that are instantaneous in Discord. You don't need any third-party meeting tools to talk with friends! Learn how below. #### Here's a video: {% embed url="" %} Live stream channels in Tech Fleet Discord {% endembed %} #### Here's the text version:
Live Stream Channels in Tech Fleet Discord With Tech Fleet Discord, anyone can hang out with any member on a special channel that's built in Discord. Discord has a great way for anyone to do audio or video chats live. It's called Live Stream channels. You don't need to schedule a calendar invite to meet with your pals in Discord. Learn how to use video Live Stream channels in this handy lesson. Let's go!   **Live Stream Category** You will see a menu category in Tech Fleet Discord for Live Streams. This has two channels in it: Tech Fleet Stage channel is a live stream where Tech Fleet will host events. Only the people who are leading the event can speak in this channel. This helps us moderate events better. Hangout is an open live stream channel that anyone in the community can join at any time. If you want to hang with people over voice or video, you only need to get into this channel, and wait for others to join! You can start an activity, or you can invite friends to the live stream who are already in the Tech Fleet community. **Here's how to join the Hangout live stream** Click on the Hangout channel. You will be added to the live stream. The channel has its own chat, and you can turn on your video if you choose. Change the "Activity" n the channel so that you can let others know the purpose of you joining the live stream. If you want others to join you in the live stream, then they can see your activity.  Change the Channel Purpose by clicking on the pencil icon under the Hangout channel name in the menu. Type your meeting purpose. Click Set Status. This lets others can see what you wrote, and will be able to see what you're trying to meet about in the live stream. **Joining a Stage Live Stream** If you want to join a Tech Fleet Stage for an event, you click on it, and if there is an event happening, you will be let into the event when it starts. Otherwise, if there is no event happening, you will be placed in the "waiting room". **Talking in Live Streams** In order to talk in a live stream, you need to "Undeafen" yourself and you need to "Unmute" yourself. "Deafen" feature silences others so that you don't hear anyone talking. Mute feature silences your mic, so that no one can hear you talking.  To Undeafen yourself, click on the headphones icon.  To unmute yourself, click on the microphone icon. After this, you should be able to talk in the live stream and you should be able to hear others in the live stream.  Disconnect from live streams at any time by clicking on the Phone icon on the bottom left side of the Discord menu. **Live Streams for Project Teams** Each project team has their own sets of live stream channels that team mates can use at any time to call a meeting. You must have the Observers role or the role to be on the project team in order to access the live streams for project teams. Learn how in the other videos within this series, Getting Ready to Observe, Apprentice, or Co-Lead. It's as easy as that! Go hang with your community buddies in Tech Fleet Discord!
## Head to the next lesson: # Get a Tech Fleet Buddy {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Buddy Up in Tech Fleet Discord TL;DR: The community offers a decentralized buddy system where anyone can pair up with someone who's interested from the community. You can use the buddy system to get help while starting, or to give back to others by helping them. #### Here's a video: {% embed url="" %} Buddy Up in Tech Fleet Discord {% endembed %} #### Here's the text version:
Buddy Up in Tech Fleet Discord With Tech Fleet, you're only a message away from getting help. We're a community-driven nonprofit. This means everyone in the community pitches in to the success of the mission. If you ever get stuck and want some help from someone else in the community, we have a decentralized buddy system in place. Anyone in the community that has the Buddy Up role can receive access to a channel to request buddies and accept someone else's request for a buddy. Attention all Buddies: please follow the video we put together for properly direct messaging people in Discord. Your security is at stake! Follow these instructions to use the Buddy system in Tech Fleet. **Step 1:** Get the Buddy Up role. There are two ways to get this role. The first way is to check off that you need to buddy up with someone while you are going through Tech Fleet onboarding. The second way is to go to the Channels and Roles menu item. Head to the Customize tab. Then scroll down to the section that asks you about the activities you want to do. Find the "I want to buddy up with someone" and check it off. By following one of these two things, you will obtain the Buddy Up role. **Step 2:** Head into the Buddy Up channel and find a buddy! This can be found under the Guidance menu category. **Step 3:** Post your request for a buddy in this channel. Tell the buddies of the community who you are, what your goals are, what kind of help you want, and what kind of buddy you're looking for, and how you'd like to proceed with your Tech Fleet buddy. **Step 4:** Create a thread to your original post so that others can reply to your post. Do this by right-clicking the message and select "Create Thread". Then give your thread a name, and be sure you tag the Buddy Up role in a message within that thread so that others can see it. Follow the video about Discord Chats to learn more about messaging in Discord. **Step 5:** Wait for someone from the community to respond. **Step 6:** Once you have a buddy, start buddying up! Start chatting with your new buddy. Use the Hangout channel to meet your buddy on a live stream if you'd like. We encourage you to give back to other buddies in the community just like others give back to you. Be a buddy, take a buddy! With this, we help each other succeed in Tech Fleet community, and the cycle continues.
## Head to the next lesson: # Managing Events in Tech Fleet Discord This page covers how to create events, get alerts for events, see events, and edit events. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Managing Events in Tech Fleet Discord TL;DR: Events are synced with the Tech Fleet Web Calendar in Discord. Only people with the proper roles can edit or create events. You can get alerts for events too. #### Here's a video: {% embed url="" %} Managing events in Tech Fleet Discord {% endembed %} #### Here's the text version:
Managing Events in Tech Fleet Discord
## Head to the next lesson: # Get Technical Support in Tech Fleet Discord This page covers how you can get technical support in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Getting Technical Support in Tech Fleet Discord **TL;DR:** go to the support general channel, or create a ticket channel. #### Here's a video: {% embed url="" %} Getting Technical Support in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Technical Support in Tech Fleet Discord Tech Fleet's got some exciting new ways to provide support to our community! Now, members in Tech Fleet Discord can create a support ticket to speak directly with a moderator. **Here's how to Get Tech Support** 1. Go to the "Support" menu category in Tech Fleet's Discord. You can find this on the left-hand side at the bottom of the channel list. 2. Go to the "Create a Ticket" channel. 3. To start a new ticket, click on the "Create Ticket" button within that channel. 4. A new private channel will be created with you and the Tech Fleet Guilds. You can chat with a moderator from the Tech Fleet Guilds about anything! 5. Simply go to the new channel that was made, and type your details in your support ticket. 6. When you're finished, you can close the ticket, or a moderator might close the ticket for you. Simply click on the "Close" button in the ticket's channel. Anytime you have a question or need assistance, Tech Fleet is here to speak to you one-on-one. We don't have this ability in Slack, so it's exciting to offer this level of support to our community members.
## Head to the next lesson: # Using Roles for Alerts, Notifications, and Channel Access This page covers how to customize your Tech Fleet Discord experience through roles, alert settings, and default channels. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Using Roles to Customize your Experience in Tech Fleet Discord TL;DR: Learn how Discord Roles affect your alerts, notifications, and channel access and learn how to customize the experience you want in Discord. #### Here's a video: {% embed url="" %} Using Roles to Customize your Experience in Tech Fleet Discord {% endembed %} #### Here's the text version:
Using Roles to Customize your Experience in Tech Fleet Discord Discord allows for some pretty powerful customization for each person. Let's go over some basics about how you can personalize the channels and alerts you receive in Tech Fleet's Discord. In this video, we'll cover how Discord handles permissions, and how you can set up your own custom experience.  **What are roles?** Roles are a new concept in Discord. We don't have this in Slack. This is one of the great new features we now have as a community!  Think of roles in Discord like different hats at a party. Each hat signifies a specific responsibility or privilege. Some hats give you access to exclusive areas, while others let you know about events, and send you alerts when people message your role. Some let you do things that others can't do. Just like you might wear a chef's hat to help with cooking or a host's hat to greet guests, Discord roles assign various duties and permissions to keep everything running smoothly. Best of all, you only see what you want to see in Discord with the power of roles. Roles in Tech Fleet Discord are the "hats" associated with your account. They let you access channels and alerts that match your interests. This helps you stay connected, updated, and achieve your goals in the community. Roles help everyone focus on the things they want to do and cut down on clutter for all. They will allow you to gain access to channels and see the alerts in those channels. If you don't have the roles, you won't see the channels and won't see the alerts. Life is much easier in Discord with roles! **How can you obtain roles in Discord?** There are two ways to get roles in Discord: 1. A moderator in Tech Fleet discord will give you a role 2. You can assign yourself certain roles. To obtain project team roles for a Tech Fleet team, or to obtain masterclass roles, a moderator must assign you the role. Watch the other videos for details about this. To obtain access to guidance channels, or to prepare for projects and masterclasses, you can assign yourself roles to gain access. Learn how in this video **Let’s learn how to assign yourself roles to gain access**  First: When you enter Discord, during the onboarding flow, you will be asked questions about what content you want to see. By selecting the topics 📍 that interest you, you will automatically be assigned roles related to that topic. These roles grant you access to specific channels that align with your goals in Tech Fleet. It's as simple as that! If you want to change your roles, you can do so at any time. After you join, you can head to the Channels and Roles section of Discord to edit your selection.  Once in the Channels and Roles section, head to the "Customize" tab, and simply select any role you want to assign yourself related to alerts, notifications, and channel access.  You can also go to the "Browse Channels" section to mark off which channels you want to see by default. Checking off channels here makes your channels show up all the time in Discord. It's good to do this when you enter Discord so that you can customize your own experience. In the next video, learn how to get access to the guidance channels, project channels, and masterclass channels in Tech Fleet Discord. Each role opens up new opportunities, so dive in and explore!
## Head to the next lesson: # Getting Career Guidance in Tech Fleet Discord This page covers how to receive roles and alerts for career area guidance in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Getting Career Guidance Roles in Tech Fleet Discord TL;DR: To get guidance, you have to get the roles for guidance based on the area you want. Learn how below. #### Here's a video: {% embed url="" %} Getting Career Guidance Roles in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Career Guidance Roles in Tech Fleet Discord  **First:** A reminder about what Roles are. Roles in Discord are like hats: if you wear the hat, you have access to special channels or special abilities. This means that you can control what you see and what you do in Tech Fleet Discord. **Next:** How do you receive access to the career guidance channels in Discord? There are two ways to do so! 1. The first way is to select your guidance areas you want to receive during the Onboarding Flow when you join. 2. The second way is to go to special channels to grant yourself access to areas for career guidance. Tech Fleet Discord offers channels that are dedicated to guidance about job help, guidance about portfolios, or guidance about career areas in tech. We support U.X., product management, project management, development, and solutions architecture careers. We've got channels dedicated to each topic. But! You won't see these channels until you "wear the hat", and get yourself the role for them! We do this so that you don't see notifications for things that don't interest you in Discord. **Finally:** Let's learn how to assign yourself the roles for career guidance after onboarding in Tech Fleet Discord! Head to the "GET GUIDANCE" channel category on the Tech Fleet Discord menu. You should see three channels: 1. "Guidance General", 2. "Career Path Roles", 3. and "Job Help Roles". In the Guidance General channel, you can receive general help about anything related to the community. This is open to everyone. In the Career Path Roles channel, you can assign yourself roles to receive access and alerts to receive help for different career areas. In the Job Help Roles channel, you can assign yourself roles to receive access and alerts to receive portfolio help.  To assign yourself a role in one of these channels, simply head to the channel and click the emoji associated with each role. You'll see instructions about each role. Each one is associated with a channel that you can gain access to. **Let's go through an example** Let's say you want to get help with your portfolio. 1. Step 1: Head to the Job Help Roles channel 2. Step 2: Find the emoji associated with the portfolio help channel. 3. Step 3: Click on the emoji 4. Step 4: You should now see the Portfolio Job Guidance channel! 5. Step 5: Repeat the process for any other areas of guidance you want to receive. And that's all you have to do! With Discord, you have the power to control what you see and do. Check out the other videos in this series to learn how to get ready to observe, apprentice, or lead in Tech Fleet with the same kinds of roles.
## Head to the next lesson: # Getting on Projects in Tech Fleet Discord This section covers information about how to obtain the Discord Roles you need to start being involved in projects within Tech Fleet Discord # Observers in Tech Fleet Discord This page covers everything you need to know to be able to get the Observer capabilities in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Get Ready to Observe Projects in Tech Fleet Discord **TL;DR:** First, get the Projects role, then get the Observers role, through the project-role channel and the observers-get-ready channel. #### Here's a video: {% embed url="" %} Getting Ready to Observe Projects in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Ready to Observe Projects in Tech Fleet Discord Learn how to get ready to start observing projects in Tech Fleet Discord. In order to do this, you need the Observers role in Tech Fleet Discord.  **First:** Here's a reminder about what Roles are. Roles in Discord are like hats: if you wear the hat, you have access to special channels or special abilities. This means that you can control what you see and what you do in Tech Fleet Discord. **Next:** What does it mean to be an Observer in Tech Fleet? Let's start with the breakdown of project teams in Tech Fleet. Tech Fleet has four different ways for you to be involved on projects: 1. One: You can be an Observer 2. Two: You can be an Apprentice 3. Three: You can be a Co-lead 4. Four: You can be a Group Mentor Observers watch project teams work Apprentices work alongside co-leads and own work as servant leaders Co-leads guide apprentices and contribute to work as servant leaders Group mentors offer mentorship to teams in subjects they know   **Next:** Here's everything you need to know about Observers in Tech Fleet: An observer is anyone in the world who wants to watch how project teams work. Because there's no better way to learn how Agile operations work than to watch Agile teams in action! Tech Fleet highly recommends this as the first step to interacting with the community, and a first step to joining projects. We offer this for anyone in the community. The Tech Fleet project calendar is open for anyone to view. Meetings on that calendar are open for any Observers to join. **Finally:** How does someone start observing projects in Tech Fleet? 1. Step 1: Obtain the "Projects" role in Tech Fleet Discord. This role opens up channels for you to further decide how you want to be involved on projects. To get the Projects role, go to the Projects category. 1. Head into the Project Role channel. 2. In this channel you will see instructions. Read the instructions. These instructions have you go into the Tech Fleet user guide. 3. We know what you're thinking. Do I really need to read the user guide? Really YES! You will greatly benefit from the lessons in the user guide. In fact, they are crucial to applying to projects in Tech Fleet. 4. [PROJECT PORTAL](/project-portal/project-success-handbook) - Go to the section in the user guide about Life in Tech Fleet. Read all the sections to start understanding what it's like on project training and in the community 5. After you do this, and follow the instructions on this channel, click on the emoji at the bottom of the channel. When you click on this emoji you will receive the Projects role. You're now ready to obtain the Observers role! 2. Step 2: Obtain the Observers role in Tech Fleet Discord. This role opens up access to channels that you can utilize while observing project teams. To get the Observer role, go to the Projects category, and head into the Observers Get Ready channel. BUT! Be sure you have the Projects role first! Otherwise, you won't see this channel. 1.  In this channel you will see information, a link to the Observer Handbook, and instructions on how to obtain the Observer role. Read the observer handbook. Read it all carefully. It tells you exactly how observing works, what to do, and what you can expect. 2. [Observer Handbook](/observer-portal/observer-handbook) - After you're done reading the Observer Handbook and the user guide, come back into the Observers Get Ready channel. 3. Click on the eyes emoji. Once you do, you will receive the Observers role. 4. This grants you access to new channels and new abilities in Discord! Hooray! **Observer Role Abilities** The first new ability it gives you is access to all of the project team channels in Tech Fleet. Each project has an Observers channel where you and other observers can chat with teams. Best of all: there is a Calling All Observers channel in Discord. You can find this under the Alerts menu category. Only Observers and project teams see this channel. This gives you alerts each day about new meetings that are coming up to observe! Check this channel every day when you're observing, and be sure to check the Tech Fleet Web Calendar outside of Discord to see all of the project team meetings.  That's it for now! Check out the other videos in this part of the series. You can learn how to get ready to apprentice, how to get ready to lead, and how to get ready to join masterclasses!
**Here's the sections of the Guide you need to read:** [PROJECT PORTAL](/project-portal/project-success-handbook) [Agile Handbook](/agile-training-portal/agile-handbook) [Observer Handbook](/observer-portal/observer-handbook) ## Head to the next lesson: # Project Training Teammates In Tech Fleet Discord This page covers everything you need to know to be able to get the Projects capabilities in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Get Ready to Join Project Training in Tech Fleet Discord **TL;DR:** First, get the Projects role and then you will receive access to the project channels. #### Here's a video: {% embed url="" %} Getting Ready to Apprentice in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Ready to Apprentice in Tech Fleet Discord Learn how to get ready to be an apprentice on projects in Tech Fleet Discord. In order to do this, you need the Apprentices role in Tech Fleet Discord.  **First:** Here's a reminder about what Roles are. Roles in Discord are like hats: if you wear the hat, you have access to special channels or special abilities. This means that you can control what you see and what you do in Tech Fleet Discord. Next: What does it mean to be an Apprentice in Tech Fleet? Let's start with the breakdown of project teams in Tech Fleet. Tech Fleet has four different ways for you to be involved on projects: 1. One: You can be an Observer 2. Two: You can be an Apprentice 3. Three: You can be a Co-lead 4. Four: You can be a Group Mentor Observers watch project teams work Apprentices work alongside co-leads and own work as servant leaders Co-leads guide apprentices and contribute to work as servant leaders Group mentors offer mentorship to teams in subjects they know **Next:** Here's everything you need to know about Apprentices in Tech Fleet: An apprentice is a member of team project training in Tech Fleet. You work alongside peers that are other apprentices, co-leads, and mentors. You work on a client project. Apprentices must apply to projects in order to join. Projects are eleven weeks, and we open new projects to apply to every month. Please note: having the Apprentices role does not mean you're on a team yet. It means you can see the alerts to apply to openings for projects as an apprentice. It also means you get channels for guidance as someone who is applying as an apprentice, or actively apprenticing. You still need to apply to a project and be selected by a co-lead. Getting the Apprentices Role is the next step towards joining a team. Tech Fleet highly recommends Observing as the first step to interacting with the community, and a first step to joining projects. We offer this for anyone in the community. Check out the other video we've made, Getting Ready to Observe. It tells you what you need to do in Discord to start observing projects. **Finally:** How does someone start being an apprentice on projects in Tech Fleet? 1. Step 1: Obtain the "Projects" role in Tech Fleet Discord. This role opens up channels for you to further decide how you want to be involved on projects. 1. To get the Projects role, go to the Projects category. 2. Head into the Project Role channel. 3. In this channel you will see instructions. Read the instructions. These instructions have you go into the Tech Fleet user guide. 4. We know what you're thinking. Do I really need to read the user guide? Really YES! You will greatly benefit from the lessons in the user guide. In fact, they are crucial to applying to projects in Tech Fleet. 5. [PROJECT PORTAL](/project-portal/project-success-handbook) - Go to the section in the user guide about Life in Tech Fleet. Read all the sections to start understanding what it's like on project training and in the community. 6. After you do this, follow the instructions on this channel, click on the emoji at the bottom of the channel. When you click on this emoji you will receive the Projects role. 7. This grants you access to new channels: Observers Get Ready, Leads Get Ready, Apprentices Get Ready, and Mentors Get Ready. You're now ready to obtain the Apprentices role in the Apprentices Get Ready channel! 2. Step 2: Obtain the Apprentices role in Tech Fleet Discord. This role opens up access to channels that you can utilize while applying to projects as an apprentice. 1. To get the Apprentices role, go to the Projects category, and head into the Apprentices Get Ready channel. BUT! Be sure you have the Projects role first! Otherwise, you won't see this channel. 2. In this channel you will see information, a link to the Apprentice Handbook, a link to the Agile Handbook, and instructions on how to obtain the Apprentice role. Read the Apprentice handbook. Read the Agile handbook. Read it all carefully. It tells you exactly how apprenticing works, what to do, and what you can expect. 3. After you're done reading the Handbooks in the user guide, come back into the Apprentices Get Ready channel. 4. Click on the leaf emoji. Once you do, you will receive the Apprentices role. 3. Step 3: You have access to new abilities with the Apprentices role! This grants you access to new channels and new abilities as someone applying for Apprentice in Discord! Yay! **Apprentice Role Capabilities** The Projects role grants you access to Project Opening alerts. Only people with the Projects role see this channel. You will see alerts whenever projects are open to apply in the Project Openings channel. There is a Calling All Apprentices channel in Discord. You can find this under the Alerts menu category. This gives you alerts that only Apprentices with the Apprentices role can see. Having the Apprentices role grants you access to the Apprentice Guidance channel. You can find this under the Guidance channel. Only apprentices, co-leads, mentors, and guild members can see and chat in this channel. You can use this channel to obtain any guidance as an Apprentice! Simply post your questions in that channel, and we got you. That's it for now! Check out the other videos in this part of the series. You can learn how to get ready to observe, how to get ready to lead, and how to get ready to join masterclasses!
**Here's the sections of the Guide you need to read:** [PROJECT PORTAL](/project-portal/project-success-handbook) [Observer Handbook](/observer-portal/observer-handbook) [Agile Handbook](/agile-training-portal/agile-handbook) [Project Success Handbook](/project-portal/project-success-handbook) [NEW Teammate Handbook](/team-portal/new-teammate-handbook) ## Head to the next lesson: # Mentors in Tech Fleet Discord This page covers everything you need to know to be able to get the Mentor capabilities in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Getting Ready to Mentor on Projects in Tech Fleet Discord **TL;DR:** First, get the Projects role, then get the Mentors role, through the project-role channel and the mentors-get-ready channel. #### Here's a video: {% embed url="" %} Getting Ready to Mentor in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Ready to Mentor on Projects in Tech Fleet Discord  Learn how to get ready to be a group project mentor on projects in Tech Fleet Discord! In order to do this, you need the Mentors role in Tech Fleet Discord. **First:** Here's a reminder about what Roles are. Roles in Discord are like hats: if you wear the hat, you have access to special channels or special abilities. This means that you can control what you see and what you do in Tech Fleet Discord.  **Next:** What does it mean to be a Group Project Mentor in Tech Fleet?  Let's start with the breakdown of project teams in Tech Fleet. Tech Fleet has four different ways for you to be involved on projects: 1. One: You can be an Observer 2. Two: You can be an Apprentice 3. Three: You can be a Co-lead 4. Four: You can be a Group Mentor Observers watch project teams work. Apprentices work alongside co-leads and own work as servant leaders. Co-leads guide apprentices and own work as servant leaders. Group mentors offer mentorship to teams in subjects they know within a group setting. **Next:** Here's what you need to know about Mentors in Tech Fleet: A group project mentor gives at least one hour a week to mentor a project. They can choose the project they mentor. It's based on who requests a mentor from active projects. Projects are eleven weeks, and we open new projects to apply to every month. Please note: having the Mentors role does not mean you're on a team yet. It means you can see the alerts to openings for projects as a mentor. It also means you get channels for guidance as someone who is mentoring projects. You still need to respond to the need for a mentor on a project and be selected by a Project Coordinator. Getting the Mentors Role is the next step towards joining a team. Learn the entire process in this video. Tech Fleet highly recommends Observing as the first step to interacting with the community, and a first step to joining projects. We offer this for anyone in the community. Check out the other video we've made, Getting Ready to Observe. It tells you what you need to do in Discord to start observing projects. **Finally:** How does someone start being a Mentor on projects in Tech Fleet? 1. Step 1: Obtain the "Projects" role in Tech Fleet Discord. This role opens up channels for you to further decide how you want to be involved on projects. 2. To get the Projects role: 1. Go to the Projects category. 2. Head into the Project Role channel. 3. In this channel you will see instructions. Read the instructions. These instructions have you go into the Tech Fleet user guide. 4. We know what you're thinking. Do I really need to read the user guide? Really? YES! You will greatly benefit from the lessons in the user guide. In fact, they are crucial to applying to projects in Tech Fleet. 5. [PROJECT PORTAL](/project-portal/project-success-handbook) - Go to the section in the user guide about Life in Tech Fleet. Read all the sections to start understanding what it's like on project training and in the community. 6. After you do this, follow the instructions on this channel, click on the emoji at the bottom of the channel. When you click on this emoji you will receive the Projects role. 7. This grants you access to new channels: Observers Get Ready, Leads Get Ready, Apprentices Get Ready, and Mentors Get Ready. You're now ready to obtain the Apprentices role in the Mentors Get Ready channel! 3. Step 2: Obtain the Mentors role in Tech Fleet Discord. This role opens up access to channels that you can utilize while mentoring. 4. To get the Mentors role: 1. Go to the Projects category, and head into the Mentors Get Ready channel. BUT! Be sure you have the Projects role first! Otherwise, you won't see this channel. 2. In this channel you will see information: a link to Life in Tech Fleet, a link to the Agile Handbook, a link to the Apprentice Handbook, and instructions on how to obtain the Leads role. Read all of the handbooks. Read it all carefully. It tells you exactly how projects works, what to do, and what you can expect. 3. After you're done reading the Handbooks in the user guide, come back into the Mentors Get Ready channel. 4. Click on the leaf emoji. Once you do, you will receive the Mentors role. 5. Step 3: You have access to new abilities with the Mentors role! This grants you access to new channels and new abilities as someone trying to mentor projects in Discord! Yay! First: The Mentors role grants you access to Mentor Openings. This is a channel that only mentors see. Teams can post mentoring needs in this channel. If you're interested in mentoring a team, reply in a thread to any message, and the project coordinator will set you up. Secondly: there is a Mentor Guidance channel in Discord. You can find this under the Get Guidance menu category. This gives you alerts that only leads with the Mentors role can see. Use this channel to receive guidance as a mentor any time. That's it for now! Check out the other videos in this part of the series. You can learn how to get ready to observe, how to get ready to apprentice, and how to get ready to join masterclasses!
## Head to the next lesson: # Masterclasses in Tech Fleet Discord This page covers everything you need to know to be able to get the Masterclass capabilities in Tech Fleet Discord. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## Getting Into Masterclasses in Tech Fleet Discord **TL;DR:** Get the Masterclasses role through the masterclass-role channel. #### Here's a video: {% embed url="" %} Getting Into Masterclasses in Tech Fleet Discord {% endembed %} #### Here's the text version:
Getting Into Masterclasses in Tech Fleet Discord If you'd like to start taking classes in Tech Fleet, you're in luck! Tech Fleet offers industry-focused masterclasses that are taught by different instructors throughout the year. You can take these classes at any time, and level up your learning. Most of the masterclasses in Tech Fleet focus on topics that you are expected to know in the industry, but were probably not taught in your prior training. This is a key gap in the industry. A lot of areas that people are expected to know don't get taught except on the job. And then....there was Tech Fleet Professional Association! The organization built on the mission to change the face of Tech by giving newbies a chance to succeed. Tech Fleet's made up of superheroes trying to give back to the world, and to people like you. You don't need prior education or experience to get into Tech Fleet Masterclasses. We teach you everything from the ground up. Masterclasses are either free, or require a small fee to register. Usually this is 50 dollars per class. Proceeds go to sustaining operations in Tech Fleet. Tech Fleet tries to keep prices as affordable as possible for anyone in the world. Anyone should get the chance to receive industry-focused education. To get started, you need to get the Masterclasses role in Tech Fleet Discord. You can obtain this one of two ways: 1. The first way: during onboarding in Tech Fleet Discord, check off that you'd like to get into Masterclasses. 2. The second way: after you join Tech Fleet Discord, head to the Masterclass Role channel. Assign yourself the Masterclasses role by clicking on the book emoji at the bottom of the page. Once you have the Masterclasses role, you will gain access to other channels in Tech Fleet Discord that are related to Masterclasses. Check out the Masterclass Openings channel under the Announcements category for alerts about when new masterclasses are open. You can see these alerts and get links to register when they open. Check out the Masterclass Hub under the Masterclasses category to receive a link to the Masterclass Dashboard. This Dashboard, hosted online, gives you all the key information you need to know about masterclasses, like time frames, requirements, skills, syllabus links, and registration links. Once you register for a Masterclass, your instructor is going to get you into the class channels with other kinds of roles that only moderators grant you once you register. Typically, you will receive an email with instructions after you register. Look out for that if you're registering for a class! And that's it! Go get some real world education in Tech Fleet!
# Quick Links # Join Tech Fleet Discord All Tech Fleet members must agree to our policies before joining the community. Fill out the form below to do so. {% hint style="info" %} Email Tech Fleet for tech support outside of Discord: {% endhint %} ## **Steps to Join Tech Fleet Discord** 1. Fill out the form on to agree to our policies. 2. After you submit, you will receive an email to the address you specify in the form. 3. Click on the Discord invite link in the email. 4. Login and onboard to Tech Fleet Discord. ## Discord Sign Up Form Click on this to be redirected to Tech Fleet's website where you can sign up for a Discord invite link: {% embed url="" %} techfleet.org/join {% endembed %} ## Don't Forget to Watch Our Video Tutorial Series on Discord {% content-ref url="/pages/OIs1OkCbT9ZAKJwMlliE" %} [Broken mention](broken://pages/OIs1OkCbT9ZAKJwMlliE) {% endcontent-ref %} # Figma Community Templates from Tech Fleet Tech Fleet maintains open source templates for workshops that Agile teams can run. ## Figma Community Template Repository from Tech Fleet Tech Fleet maintains open source product development templates for anyone in the world to be able to use for their Agile team work. {% embed url="" %} Tech Fleet maintains open source templates for workshops that Agile teams can run. Credit: . {% endembed %} Head to Tech Fleet's community page in Figma for all templates: 1. [Working Agreements workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/working-agreements) 2. [Agile Team vision workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/agile-teams-vision) 3. [Team RACI chart workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts) 4. [Project roadmap workshop](broken://pages/a7rLakbW5PEx99fKbQ5p) 5. [Sprint retrospective workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-retro-boards) 6. [Sprint planning workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items) 7. [Sprint Demo presentation template](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-demo-presentations) 8. [Agile maturity measurement workshop](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/agile-team-maturity-measurement) 9. And more # Tech Fleet Web Calendar This page embeds the web calendar for project meetings and community meetings happening throughout Tech Fleet {% embed url="" %} # Tech Fleet's Project Repository on Notion This page shows a link to the Tech Fleet Notion Repository where all teams hold their project work, decisions, recordings, and deliverables. ## Active Tech Fleet Project Spaces Tech Fleet teams use [Notion ](/resources/quick-links/tools-used-in-tech-fleet-programs)to hold project work. Each project and each phase has its own space where teams document their progress. ### Each notion space includes: 1. Phase scope information 2. Team information 3. Hand-off documents 4. Meeting summaries 5. Deliverables 6. Recordings ## Go here for the Tech Fleet Project Notion Space {% embed url="" %} Tech Fleet's page for active project team spaces {% endembed %} # Join our Mailing List! Get alerted when we open new project or class opportunities, and other important news coming from our organization. {% embed url="" %} Click here to join our mailing list {% endembed %} # Common Links This page gives you access to common links for the Tech Fleet community ## Discord Migration Video Tutorials {% content-ref url="/pages/OIs1OkCbT9ZAKJwMlliE" %} [Broken mention](broken://pages/OIs1OkCbT9ZAKJwMlliE) {% endcontent-ref %} ## Our Policies and Guidelines {% content-ref url="/pages/98muUxDmEI0hpAt8mjD0" %} [Policies](/policies/community-collective-agreement) {% endcontent-ref %} ## Email Us - We're only an email away for general inquiries for [Code of Conduct Concerns](/community-code-of-conduct/code-of-conduct-and-anti-harassment-policy) and other safe space conversations. {% content-ref url="/pages/20eork4n7yoNyKmDkdOS" %} [Safe Space](/community-code-of-conduct/safe-space) {% endcontent-ref %} ## Information website The website has information about who we are and what we do. This space has much more detail. {% embed url="" %} ## Tech Fleet project repository The Notion project repository shows all of the active, archived projects, as well as the Tech Fleet Guild workspaces. Check out the work that project teams deliver in Tech Fleet programs. {% embed url="" %} ## Youtube Channel Check out our YouTube channel for community videos that get posted publicly. {% embed url="" %} ## LinkedIn Catch Tech Fleet on LinkedIn for social media updates {% embed url="" %} ## Medium Articles Read our articles that have been written by contributors in the community {% embed url="" %} ## Mailing List Join the Tech Fleet mailing list to get the latest updates and news from around the community {% embed url="" %} ## Discord Discord community is where Tech Fleet operates today. {% content-ref url="/pages/OIs1OkCbT9ZAKJwMlliE" %} [Broken mention](broken://pages/OIs1OkCbT9ZAKJwMlliE) {% endcontent-ref %} ## Tech Fleet Video Onboarding Series This series covers the basic topics about Tech Fleet to help new people build context. {% content-ref url="/pages/ei2I3PT7w1Ne0zfw6u6I" %} [Broken mention](broken://pages/ei2I3PT7w1Ne0zfw6u6I) {% endcontent-ref %} ## Litepaper The litepaper is a living document hosted on Medium that shares the founder's vision for the future of Tech Fleet {% embed url="" %} # Tools Used in Tech Fleet Programs ## Discord (We Changed from Slack) Discord is our main community hub online. Watch Our Video Tutorial Series on Discord {% content-ref url="/pages/gTdasq0C2MFwzC0JgbSF" %} [The Great Tech Fleet Discord Migration Video Tutorials](/resources/the-great-tech-fleet-discord-migration-video-tutorials) {% endcontent-ref %} ## Training Templates Tech Fleet's guilds have prepared training templates that are based on group work to complete the entire project lifecycle, from intake to delivery. See all of our training templates here on our website: {% embed url="" %} ## Notion Notion is used for Tech Fleet project repositories, where teams document their work for historical purposes. The Project Coordinator will create a project page for the team that's based on a template we use for every project. Check out the template here: {% embed url="" %} * Have all members sign-up for Notion with the same email they use when they signed up for Tech Fleet * Instruct to watch youtube tutorials to understand the basics [Notion App: Full Notion Tutorial for Beginners in 2022! \[A-Z Guide\] ✨💻](https://www.youtube.com/watch?v=IrIAmq80VEE\&ab_channel=ProductiveDude) * Customize the Tech Fleet project workspace as you like to best fit the needs of the project. ## Google Meet Google Meet is Tech Fleet's video meeting tool. With it, recordings and notes can be managed. Sometimes teams add meetings using [Discord streaming channels instead of Google Meet](/resources/the-great-tech-fleet-discord-migration-video-tutorials/basic-chatting-abilities-in-discord). All meeting links, whether Google Meet or otherwise, should show on Tech Fleet Calendar events. The Project Coordinator will share a Google log in for the team so that they can use the Tech Fleet Zoom account (Video recording storage and transcription for each project). #### Storing, documenting, and rewatching recordings * Record meetings that are important for the team (and observers) * Document recordings in Notion and share links on appropriate Slack channels * Please make sure that you are sharing a link that is open to anyone with that link as appropriate ## Lettucemeet For scheduling team meetings and establishing availabilities {% embed url="" %} ## Figma Figma's the main design tool Tech Fleet teams use on projects. * Figma - a prototyping tool used by teams to make pixel-perfect designs * FigJam - a digital whiteboarding tool great for brainstorming / group work / UX research / UX design / sprint planning / retros / workshops ## Google Tech Fleet uses Google for shared calendars and meeting scheduling. The same email shared by the Project Coordinator allows for the team to have a dedicated email for scheduling research sessions and a focused calendar for the team. * When creating meetings for the team use the same project prefix everywhere. Examples: “#Project-Design” on Slack, “Project-Design Working Session”, “Project-Sprint Planning” * This makes it easier for team members and shadowers to find the meetings * Login to the team email * Add all team members to the respective google calendar * Add a zoom meeting to the invite with the Google Meet link on the invite * Invite so that meetings appear on the Tech Fleet Google Calendar * Create agendas before all meetings. This ensures the meeting stays on track when they need to {% embed url="" %} ## Gitbook You're in it! Gitbook is where Tech Fleet's user guide lives. The community maintains this wiki space. {% embed url="" %} # NEW Teammate Handbook Welcome to the new and improved handbook for cross-functional teamwork. Learn everything you need to know about being a teammate on all different kinds of teams in our community training ecosystem. # Start the Teammate Handbook Here # Introduction to the Teammate Handbook ## Video Version Here's a video version of this page: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Introduction This community is here to make change in the world. We are the change that the work world needs for the future. In order to be the change, we need to lead the change. We seek to make different kinds of work cultures. We seek to change who gets to be in leadership. We seek to build teams that are empowered to solve problems together. We need to teach people how to own the stake in the work together and decide through collective voices. We are building a culture of empowered teams all over this community. This doesn't just happen through project training, but in every team-based interaction we have. Every kinds of teams should follow the same principles and live the same philosophies to empower each other to succeed. You've learned about [what makes strong teams](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams). You've learned how to operate in the [agile ways of work](/agile-training-portal/agile-handbook/agile-philosophies/agile-ways-of-work). You've learned how to [finish the project outcomes as a team](/project-portal/project-success-handbook). Now learn how to be different kinds of teammates, and learn about the different kinds of teams that you can get involved in within our community ecosystem. This handbook teaches you the rigors of all kinds of empowered teamwork that happens in this community: project training, volunteer work, and class work. By the end of the handbook you will know how to get involved in the different kinds of empowered teams that our community offers on your way to your own growth. ## Head to the Next Lesson # Read the Other Handbooks Before Reading the Teammate Handbook ## Read These Handbooks First Before you become a teammate in project training, volunteer work, or classes, you should read the other handbooks our community has generated first: ### Agile Handbook The Agile Handbook covers everything about the Agile Ways of Work compared to the Waterfall Ways of Work. Leanr how Agile teams build things, how they treat each other as teammates, how they operate, and how they deliver iterative value to the world. {% content-ref url="/pages/KQKcYjQiAbU5Dk5Apfqo" %} [Agile Handbook](/agile-training-portal/agile-handbook) {% endcontent-ref %} ### Project Success Handbook The Project Success Handbook is for any kind of team-based problem solving in the world! It covers operations of project-based teamwork. Learn the different parts of the project lifecycle, how they work, what kinds of work they involve, and how to use the workshop templates we've made in the community to deliver the milestones as a team. {% content-ref url="/pages/DENW3PkiAIeFJyXIONMj" %} [Project Success Handbook](/project-portal/project-success-handbook) {% endcontent-ref %} ### Observer Handbook People in our community start getting involved by watching real agile teams operate. We call them Observers, and we've kept all community team meetings open for them to observe from day 1. Learn about the basics of observing, the benefits of observing, what to expect while observing, and how to observe. {% content-ref url="/pages/BbMR0StqCuWcosa5T8xj" %} [Observer Handbook](/observer-portal/observer-handbook) {% endcontent-ref %} ## Head to the Next Lesson # Who Should Read the Teammate Handbook? ## All Community Members Should Read This Handbook!
If you want to get involved in team-based problem solving of any kind, this handbook is for you. It will provide valuable information about the different kinds of teamwork we do in this community and how to get involved. It's essential reading for all kinds of teammates: project trainees, volunteers, and classmates. ## Head to the Next Lesson # What Happened to "Co-Leads" and "Apprentices"? Read about the changes we made in our efforts to build a cross-functional teamwork culture and find out what happened to "co-leads" and "apprentices" titles. ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Building an Agile Culture Our community doesn't just teach agile and cross-functional teamwork. We live it. Everything members do should be cross-functional and should follow the [agile philosophies](/agile-training-portal/agile-handbook/agile-philosophies/agile-ways-of-work). We started building an agile cross-functional team culture in 2024. Our training programs built ways for people to model behavior of agile teammates. Our training templates and agile coaching offers ways for people to be coached in agile cross-functional teamwork for the first time. This helps people build experience and do it together with peers. Our culture of agility is a practice that always evolves. Our community itself is driven by the principles of interacting with individuals, delivering working results, collaborating with others, and responding to change. We collectively live the ways of agile the same way we teach them. Being a teammate in our community means that you live the agile ways of life too. Everything you do in peer-to-peer work should be guided in the principles of agility and cross-functional teamwork. What we noticed on our project training was the opposite of Agile. We noticed team dynamics of people "managing" others. Co-leads were expected to tell people what to do, how to work, what to work on, and whether they were doing it right. This creates a dynamic that hinders empowerment. It provides a way for people to stay with the old dynamics of "authoritarian boss and employee". What agile teams really should be doing is providing a forum for collective ownership and shared leadership. Decisions should be made together. People should be viewed as peers, not subordinates. Teams should provide the space for others to speak out, try new things, and fail in order to learn together. We needed to respond to change to build a culture where empowered teamwork is at the heart of everything we do. ## What Changed in 2025 Our journey as a community-driven ecosystem brought us to a new path of how we look at teamwork. We measured impact in our project training, and found the dynamic between "co-leads" and "apprentices" to be hindering. They behaved as bosses and employees no matter how much agile materials they read, or how much they learned about cross-functional teamwork. We decided to experiment with a new dynamic on teams all across the community. We changed our project training so that there are only "teammates" instead of "co-leads and apprentices". Teammates learn how to behave as a cross-functional team through agile coaching and training templates (see more in the [Agile Handbook](/agile-training-portal/agile-handbook) and [cross-functional team dynamics](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork)). They use RACI charts when they prioritize work to self-commit, instead of being assigned work. They span across functions so that the team feels ownership in a shared outcome that's not focused on one single person. This changed everything on our project training. Teams became more cross-functional and more agile in nature ([read the full report here](https://tech-fleet-community-dao.notion.site/Research-Report-The-Difference-in-Agile-Maturity-Levels-of-Training-Teams-After-One-Quarter-of-Agi-2561a3bddce580079bcceebde28eb3cd?source=copy_link)). Cross-functional teamwork improved a whopping 20% on project training teams. This dynamic needs to happen for every single kind of group in our community. Everything that we do should provide dynamics of empowered cross-functional teams. Our focus is to form team dynamics like this everywhere: in Tech Fleet's volunteer work, on the board of directors, in agile coaching communities of practice, in classes, you name it. The same things project trainees experience shouldn't just be in the training: it should be a practice and a way of life for members of our community. This means any time you join a team, whether it be as a volunteer, a board member, a contributor, or a project trainee, you are a "teammate". Your title is not as important as the activities you commit to as a part of a group. You are a part of the shared outcome on the team. You have as much of a voice as anyone else on the team. You live the principles of cross-functional team dynamics. ## Head to the Next Lesson # Contents of the Teammate Handbook ## Table of Contents The Teammate Handbook covers the following subjects: 1. [Introduction and basic information](/team-portal/new-teammate-handbook/start-the-teammate-handbook-here/introduction-to-the-teammate-handbook) — we cover information about the change from "co-lead" and "apprentice" to "teammate", audiences for this handbook, and the types of teamwork you can get involved in. 2. [Teammate FAQ](/team-portal/new-teammate-handbook/teammate-faq) — frequently asked questions related to all kinds of teams in our community. 3. [Cross-functional Teamwork for Teammates](/team-portal/new-teammate-handbook/expectations-for-teammates/what-does-it-mean-to-be-a-cross-functional-teammate) — information about cross-functionality and the dynamics of teammates without titles or departments. 4. [Expectations for Teammates](/team-portal/new-teammate-handbook/expectations-for-teammates) — basic expectation setting for the definitions of teamwork, how to prepare for teamwork, what leadership looks like, and how to bring yourself as a teammate in this community. 5. [Daily Life for Teammates](broken://pages/LEtvA7XDLP2wbhXNYV7c) — detailed information about project trainees, volunteers, and classmates involving teamwork. 6. [Start Joining Teams](/team-portal/new-teammate-handbook/start-joining-teams-today) — the ways to take the next steps in the community after you read this handbook. ## Head to the Next Lesson # Our Approach to Learning Tech Fleet's approach to learning is based on Agile coaching principles. Teammates experience the rigors and challenges of self-organized teamwork as servant leaders to each other. Learn more below. ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Leveling Up in Agile is Not About Your Skills or Experience You may have a perception in your head that if only you had more experience and more skills, you can join teams and immediately start producing work. You may think that expert Agile teams in the world are very experienced in what they do. This is a false perception. Expert Agile teams are experts in navigating uncertainty, experts in pivoting, and experts in supporting growth of others. They are not necessarily experts in hard skills. They progress through product development by being of service to each other as they manage risks and build a working process together. Yes, we're all here to make a living. We're all here trying to deliver results. We want to ship products. We want to have job security. We've got to make management happy if we want to stay working at a company. But Agile teamwork is not really about producing work itself. Any one person with skills and experience can perform work. Not all teams can perform work efficiently. They may be in a continuous [storm of conflict](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/the-four-stages-of-team-growth). To work as a unified [Agile team](/agile-training-portal/agile-handbook), teams must look past the skills and tight deadlines. They must look past seeking perfect outcomes. They must provide environments for experimentation, risk taking, learning, and personal growth. They must help each other build [psychological safety, service leadership, self-organization, and continuous improvement.](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams) ## Agile Teams Help Each Other Grow Teams that are Agile have the following foundations of active listening, empathy, understanding, learning, and support. They make their own calls about how to prioritize work. Agile teams don't try to control outcomes or prevent failure. They play out scenarios and respond to change. They collaborate and build working results quickly so that they can learn how to change their plans. The team decides how to work, and when to prioritize, and what to deliver. This requires a whole lot of [foundational Agile culture and mindsets](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams). Expert Agile teams provide the space for others to disagree and hear people out. They support each other in failing "fast" together, adjusting their work, and looking in reflection. They never judge or blame each other. The more a team provides these, the more a team produces strong end-results. The faster they will ship their product. The stronger that product will become at market. Read more in the Agile Handbook: {% content-ref url="/pages/atGAqiM1zNOtTP3Ai9UO" %} [Agile Teamwork](/agile-training-portal/agile-handbook/agile-teamwork) {% endcontent-ref %} ## Tech Fleet's Learning Environment Tech Fleet project training, volunteer work, and class training offer environments to fail forward with teams and gives you the same experience as you’d get on an agency or in-house teams. Tech Fleet works with actual nonprofit clients, giving you a true-to-life experience of what it's like building services and products in the world. Peers learn from other peers. No one is the "expert" or the "boss", and everybody is learning together. Agile coaches guide the teams in the ways of agile work. When we can get them, community contributors join projects as mentors for subject matter expertise. You don’t need any experience to get into a project training or volunteer work. After all, this is why we exist! To open doors for people without experience. ## Service Leadership Service leadership is crucial for successful Agile teams. All peers are service leaders to each other. Being a Service leader means you're not telling people what to do or giving them the answer, or preventing them from failing. You are their guide and empowering them to find the answer on their own. You act in support of others' success and growth. Everyone shares leadership on agile teams. No one is the "boss". No one is above anyone else on the team. All teammates should jump right into the work and own work outcomes as early as possible. We want to avoid team dynamics where people direct others or hold power over others; rather, all on the team are a part of the team's success, and all teammates have great ideas and perspective. Everyone should be providing a [psychologically safe ](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams)environment to empower the team. ## Learning by Doing In school you’re taught how to deliver a perfect, finished end result. In practice product teams rarely see the opportunity for a "perfect end result" and achieve things through quick, continuous delivery of things, a bit at a time. Apprentices and leads learn to work on the most important things each week through their own determination. They demo to clients and feedback to adjust plans each week. In Tech Fleet it's about progress over perfection. How far can the team progress in 8 weeks?\ \ Tech Fleet project training allows you to build mixed sets of skills from different roles as you contribute. Projects allow you to work with cross-functional team members with different roles across Research, Design, Business Strategy, Development, and other roles. You can pitch in to any area you want during a project, whether it’s part of your role or not. This allows people to get exposed to new career paths and try them out while they’re learning their craft. ## Team Structure We have a fully cross-functional structure on teams. People who are teammates have no titles, but they agree to whatever work they want to do across functions.\ \ On the team you are one collective team doing work together, and roles matter less when progressing as a whole. You will experience different things on different Tech Fleet projects, as it should be in the real world on Agile teams who fit Agile to their context. ## Head to the Next Lesson # Types of Teamwork in the Community ## Project Training Teammates Teammates who are a part of apprenticeship trainings work together across functions to solve problems with nonprofits. Our training programs for team-based problem solving are built around cross-functional teamwork. Learn all about this teamwork here: {% content-ref url="/pages/XUYSqVisRgZ76styGwQf" %} [Project Training Teams](/team-portal/new-teammate-handbook/project-training-teams) {% endcontent-ref %} ## Volunteer Teammates Community members can get involved in our [company](/about-us/about-our-org) (which is a nonprofit with 501(c)(3) public charity status) as nonprofit volunteers. People in our community can serve as nonprofit volunteers to work on teams and contribute to change. This happens outside of our project training, but offers the same kind of agile cross-functional teamwork experience. Volunteers operate off of the central roadmap that the Tech Fleet board of directors puts together. Learn all about this teamwork here: {% content-ref url="/pages/stwAcUgiuLAXQXcIZrTP" %} [Volunteering Teams](/team-portal/new-teammate-handbook/volunteering-teams) {% endcontent-ref %} ## Class-based Teammates People in our community can join class-based training, and these are also built around cross-functional teamwork. Classes are practical and lab-based, offering chances to build real experience while also learning the theory of teamwork and agile. {% content-ref url="/pages/kO2YMnaroOAEFvjOdYfY" %} [Masterclass Openings](/training-openings/current-and-upcoming-program-openings/masterclass-openings) {% endcontent-ref %} ## Head to the Next Lesson # The Process of Becoming a Teammate ## Steps to Become a Teammate in the Community Here's the process for gettin involved in a teammate capacity within our community: 1. Read the user guide 2. Read the handbooks 3. Join community onboarding 4. Join Discord 5. Start observing 6. Join teamwork 1. Project training 2. Volunteer work 3. Class-based training
### Read the User Guide and the Handbooks We do mean all of it! The user guide was built by the community for the community. It has valuable resources for everyone to understand every component of our community-driven ecosystem. [Start here](/) to get started with the user guide and explore the areas of teamwork. ### Join Community Onboarding We host community onboarding calls every week to invite new members aboard. Hear the basics about our community, why we exist, how we started, and how you can get going (just like in this handbook!) [RSVP for a community onboarding call here](/join-the-community/onboarding-to-tech-fleet). ### Join Discord We make it easy for people to get started with our online community in Discord. We've made a lot of video tutorials for people to learn how to operate with our community in Discord, so [learn more in the tutorials we've made](/resources/the-great-tech-fleet-discord-migration-video-tutorials). When you are ready, [join Discord for Tech Fleet here](/resources/quick-links/join-tech-fleet-discord). ### Observe Teams Everyone starts in this community by watching teams work so that they understand how to be a teammate in the real world. We recommend being an observer for one entire sprint, or two weeks, while you watch one project or many project teams. Learn more in the [Observer Handbook](/observer-portal/observer-handbook). ### Joining Teamwork After you've completed the previous steps, read this handbook to learn how to participate in the different types of teamwork that this offers. ## Head to the Next Lesson # Teammate FAQ Here are some frequently asked questions about teamwork in our community. ## Frequently Asked Questions
What kinds of teams can I join? There are three different kinds of teams you can join: 1. [Project training](/team-portal/new-teammate-handbook/project-training-teams) — This is our "apprenticeship training program. You are a teammate working alongside people in different functions to solve problems for a nonprofit. 2. [Volunteering for our organization](/team-portal/new-teammate-handbook/volunteering-teams) — This is where you sign up to volunteer for our nonprofit organization, working alongside peers and board of directors members to do project-based teamwork. 3. [Class training](broken://pages/vwTX7QKcCv0ZYX8MASSR) — This is where you join cohort-based classes to train in different topics, some of which also offer team-based work environments.
Why does Tech Fleet focus on teamwork dynamics over skills? We believe that empowered [team success has nothing to do with your skills](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/prioritizing-growth-over-skills). It has everything to do with your team's dynamics of collective decision making, growth support, and healthy risk taking. All [great agile teams](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams) make room for experimentation, learning, belonging, and shared ownership. Without these things, the work is not likely to happen at all! Teams will [storm](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/the-four-stages-of-team-growth) longer, and will work less efficiently. No one single person makes or breaks the success of an empowered team. The team moves together, or not at all. This is the reason we focus so much on these dynamics. Empowered teams need much more than a lot of skills.
How many project-based teams can I join at the same time? We encourage you to commit to only what you can handle at any given time. Only you can decide this. We ask that you commit to one single project training at a time, and you can be a volunteer at the same time you are participating in project training and class training.
What’s the weekly time commitment as a teammate? 1. **As a project trainee** — While there is no minimum requirement, we expect apprenticeship trainees commit to 15 to 20 hours weekly to project training. This is flexible and something you manage with your team. No one will prevent you from working less with your team, or working more. This is a decision for you the team to make together. 2. **As a nonprofit volunteer for Tech Fleet** — We cannot legally require you to work specific hours or hold a specific schedule if you are volunteering for our org. We make scheduling work around you and your scheduling commitments. You can contribute to as little as 1 hour a week as a nonprofit volunteer for Tech Fleet. The choice is yours! 3. **As a classmate** — We hold live classes and also make recordings available for classmates to experience the classes asynchronously. This helps classmates cater to their own schedules in and outside of the community.
What kinds of clients do you work with? For project training we partner with other nonprofits who have already obtained a 501(c)(3) public charity status. None of them should require a non disclosure agreement or confidentiality agreement to work with us. These are the conditions they agree to when they partner with our organization. They know that they are a client because they offer you, the trainee, the opportunity to work directly with real businesses as a teammate. For volunteer work, Tech Fleet is the client! We are a nonprofit with 501(c)(3) public charity status.
Are teams led by experts in our community? Not at all! We offer coaching on project training in several areas like agile coaching, strategy coaching, and customer experience coaching. These coaches are NOT always very experienced ([after all, it has nothing to do with skills and experience to succeed in teamwork](/team-portal/new-teammate-handbook/start-the-teammate-handbook-here/what-happened-to-co-leads-and-apprentices)). They are peers in our community who may also be practitioners. They may be doing their own training in Tech Fleet (like the Agile Coaching Residency) where they are learning how to coach others themselves. We are a peer-to-peer training ecosystem, and we've learned that peer-led learning offers opportunities to form the dynamics where everyone is learning from each other. No one is providing answers. No one is preventing failure. Those things are crucial for [building team ownership and self-organization](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization). We may, however, offer opportunities for experienced people to work alongside teams as teammates. But even when we do, they themselves are not the people who provide answers. They have no hierarchy above the team. They ARE the team! They work alongside anyone else as a cross-functional teammate. The dynamic of an "expert teaching the people who don't know" leads to people who are not empowered to fail fast and grow continuously. Failure and mistakes should be looked at as amazing things for teammates. They provide opportunity for learning and improvement ([see continuous improvement practice here](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/continuous-improvement)).
Am I considered a volunteer when I join projects? When you are in project training, you are a trainee. When you sign up as a nonprofit volunteer for Tech Fleet, you are considered a nonprofit volunteer. Although these two seem similar, or the same, they are not. Trainees are expected to receive a training service, and as part of their training, they work on teams. HOWEVER, they are NOT expected to **perform expert work or timely work with clients.** This is not an agency. This is not a job. It's a training called an apprenticeship. Trainees are held to expectations that they are in training, and should not be beholden to schedules, timelines, or work capacity. Nor should volunteers be held to rigors that employees get held to when they are paid. See more here: [Training Versus Volunteering](/team-portal/new-teammate-handbook/expectations-for-teammates/training-versus-volunteering)
Do I get paid as a teammate? Right now we don't offer paid roles for any project training. The nonprofit volunteer roles are unpaid. But they all come with valuable experience to gain.
Do I have to pay to be a teammate? 1. Project training is free to join and participate in 2. Volunteer training is free to join 3. Class training requires a registration fee per class, which is described on the syllabus of each class. Normally our classes run at a low cost of $50.00 per student.
## Head to the Next Lesson # Expectations for Teammates # Training Versus Volunteering Learn about how Tech Fleet defines its apprenticeship training below. ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Definition of Apprenticeship Training When you are participating in Tech Fleet project training, you are a **trainee** learning how to work in an Agile cross-functional team environment. You are NOT a volunteer! Volunteers hold different set of expectations from trainees. Project training in Tech Fleet are meant to be a safe environment to learn how to do something for the first time. People training on teams should not expect to carry out perfect work, like in the real world jobs. This is not a job, this is an apprenticeship training. While we work with real nonprofit clients, the work we do is not fast or expert-focused as our teams are built of people who are learning to do this for the first time. Clients who partner with Tech Fleet do not expect expert-facing work to be produced. They work with Tech Fleet to give back to [Tech Fleet's mission](/about-us/about-our-org/mission-and-values) and provide opportunity for first-time learners in training. ## Project Trainees * Project training is not considered volunteer work, it's considered an educational service; * During the project training, contributors work with the guidance of coaches; * There is no requirement for specific schedules or hours worked each week for trainees, although there are expectations for teammates to spend time on teams in order to get the most out of training; * The training in projects, even though it includes actual operation of Tech Fleet or its clients, is similar to that which would be given in a vocational school; * The training is for the sole benefit of community members, not clients; * The trainees do not displace regular employees; * The trainees are not entitled to a job at the conclusion of the training period; * Tech Fleet, clients, and the trainees understand that the trainees are not entitled to wages for the time spent training; Read more here: {% embed url="" %} ## Volunteers * Volunteers of Tech Fleet are volunteer workers for Tech Fleet Professional Association, a nonprofit with public charity 501(c)(3) status; * Volunteers are not paid for their work; * Volunteers may not receive training by doing collaborative work while volunteering; * Volunteers work with a volunteer coordinator to join volunteer teams; * Volunteers do not hold specific schedules or required hourly commitments; * Volunteers and Tech Fleet can both end a term of volunteering at any time; * Volunteers may be expected to hold higher levels of experience to join a volunteer team, depending on the volunteer role; * Volunteers may be working alone or in a team; Read more here: {% embed url="" %} ## How to Put Tech Fleet Training on Resumes When providing your Tech Fleet experience on resumes, it's important to list Tech Fleet as the organization under which you trained. You can showcase the kinds of team functions you did and the nonprofit clients you partnered with in your training. ### Format 1. Organization: Tech Fleet Professional Association 2. Title: Apprentice or Co-Lead 3. Position: List whatever team function you did 1. UX Design 2. UX Research 3. UX Writing 4. Project Management 5. Product Management 6. Development 7. Agile Coach / Scrum Master ### Example **Company:** Tech Fleet Apprenticeship Training **Title:** UX Design Apprentice **From:** March - May, 2025 **Summary** * Apprenticeship training for an Agile cross-functional team * Worked with Science 2 People, a nonprofit on the mission to create fair access to public health information, to help them built a product experience. * Daily tasks: (list the tasks that are described here under [Team Functions](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training)) * Performing Scrum work in two-week sprints * Participating in Sprint Demos, Sprint Retros, and Sprint Planning * Operating cross-functionally with other departments to carry out work * Creating and maintaining prototypes * Creating and maintaining design systems * Creating and maintaining UI kits * Turning requirements into reality * Creating and maintaining personas and journey maps * Leading design thinking activities * Leading rapid ideation sessions ## Head to the Next Lesson # Do These Things Before you Join Teams ## Observing Before Joining Teams Community members start engaging in the community by watching other teams work. This helps people see cross-functional teams in action, making decisions and dealing with real-world constraints. Before you join project training and volunteer work, we highly encourage you to become an observer. {% content-ref url="/pages/BbMR0StqCuWcosa5T8xj" %} [Observer Handbook](/observer-portal/observer-handbook) {% endcontent-ref %} ## Getting Discord Roles for Teammate Work Our community in Discord is set up based on Discord Roles. These allow you to control what you see and what you get notified by based on what you want to do in the community. We've put together a lot of tutorials for community members to learn how to get the proper permissions and roles in our Discord. Check out the tutorials below to add yourself to new project-related roles. {% content-ref url="/pages/2UZgAcBqMu2NcffNSf7A" %} [How to Get Discord Roles in Tech Fleet](/start-here/get-started/how-to-get-discord-roles-in-tech-fleet) {% endcontent-ref %} ## Head to the Next Lesson # Code of Conduct for Teammates ## Code of Conduct for Teammates When you [join the Tech Fleet community](/join-the-community/how-to-join-tech-fleet-discord), you agree to our policies. **The Tech Fleet community expects that ALL network activities, events, in-person forums, and digital forums abide by the Code of Conduct and the Community Collective Agreement. We have a zero tolerance policy against harassment or anything in violation of our code of conduct of any kind.** Teammates must abide by our code of conduct in every interaction: training, volunteer work, community interactions, classes, events, and more. Whenever there are moments that violate code of conduct, members are encouraged to use Safe Space to report safely. Read through our Policies before you start your project or working with Tech Fleet. {% content-ref url="/pages/kUi0se4NXaallJiY1x6r" %} [Community Collective Agreement](/policies/community-collective-agreement) {% endcontent-ref %} {% content-ref url="/pages/5gNVfKLwO7lINb57Qv0r" %} [Code of Conduct and Anti-Harassment Policy](/community-code-of-conduct/code-of-conduct-and-anti-harassment-policy) {% endcontent-ref %} {% content-ref url="/pages/20eork4n7yoNyKmDkdOS" %} [Safe Space](/community-code-of-conduct/safe-space) {% endcontent-ref %} ## Upholding Community Values as Teammates Every member of this community is expected uphold our values and principles at every step. Find more information on these pages in our user guide. {% content-ref url="/pages/AlELcGl0bayj7W9liBhB" %} [Mission and Values](/about-us/about-our-org/mission-and-values) {% endcontent-ref %} {% content-ref url="/pages/QaMFLUHP9hihj5p4tPyO" %} [Working with Different Working Styles](/team-portal/new-teammate-handbook/expectations-for-teammates/working-with-different-working-styles) {% endcontent-ref %} ## Head to the Next Lesson # What Does It Mean to Be a Cross-Functional Teammate? ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Defining “Cross-Functional Teammate”
A ["Cross-functional" team](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork) means: 1. Teammates perform work across different functions 2. The team has no "departments" or "silos" of isolated work; they all work together 3. Teammates all get involved in the work together according to their agreed upon [RACI responsibilities](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts). This is quite different from other teams. On waterfall teams, everyone is "siloed" to a specific function and only does work in that function. Agile teams who are cross-functional are a "heist team": they all get together from different backgrounds and share responsibilities across different types of work together. They work toward a shared outcome together. [Learn more about cross-functional teamwork in the Agile Handbook](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork). ## Benefits of Cross-Functional Teamwork
Cross-functional teamwork has the following benefits: 1. **It fosters environments where people feel deeper ownership in the outcomes —** Giving teammates a voice and abilities to decide how they want to proceed is powerful. It encourages people to make decisions that avoid "perfection mindset" and the ability to form judgments on their own. 2. **It allows people to grow —** You don't need to be experienced to try new kinds of work if your team provides opportunities for you to do so. This is why having a "department" is limiting: it creates a sentiment that people who are in the department are dedicated to that kind of work, and anyone else is "trespassing" into the work that others should be doing. This is a false sentiment, and creates a lack of empowerment on teams. When a team decides how they want to get involved in work, the power transfers to each teammate who takes on that work. 3. **It prevents "silos" of work and is less risky —** If someone leaves the team or is added to the team, the work can continue seamlessly, and the team that self-organizes can best decide together how they want to proceed without waiting for a "boss" to tell them what to do or how to move. When teams are compartmentalized to a specific function, everyone else has to rely on that function to do their work and it creates a single point of failure on the team. When teammates share responsibility, they can always progress. ## How Cross-Functional Teams Function Without Titles or Departments Cross-functional teams, who have no "job titles" or "departments", float across responsibilities ([see more here in the Agile Handbook](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team)). Whenever prioritizing work, the team gets together to organize their priorities. They all decide what they will commit to together, and each teammate decides how they want to be responsible, accountable, consulted, or informed in the work. Agile teams use a deliverable called a RACI Chart to document these work assignments. No one tells a person what work to do, or what not to do, on a team that organizes themselves. Teammates should build a deep sense of ownership in the work outcomes so that they feel ready and willing to take on new kinds of work while being supported. When teams are setup in this way, it really doesn't matter what a teammate labels themselves for their job title. They can call themselves a project manager but commit to all different kinds of work as a teammate. It matters what the shared team outcomes are each week, and which activities teammates commit themselves to. With this dynamic in action, a researcher by nature gets involved in product work, or project management work. Project managers get involved in design work. Product people get involved in research work. Developers get involved in project management work. Everyone is like a bee contributing to a larger beehive. They have functions they are familiar with and functions they are less familiar with. No matter what, a teammate should be encouraged to take on new kinds of work together with others [for the opportunities to grow](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/prioritizing-growth-over-skills). This is why we the community changed out project training to have no titles. ## Cross-functional Outputs Here are the items that teams produce to perform cross-functionally: 1. [RACI Chart](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts) 2. [Team Process Map](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/agile-team-process) 3. [Project Plan](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/project-phase-roadmaps) 4. [Sprint Goals](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items) ## Head to the Next Lesson # Commitment vs. Job Function vs. People on Teams A duty is a chunk of responsibilities. One person can play many duties under a single function. Agile teams get together to build agreement of what duties people will carry out on each team. ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Roles and Jobs and Teams...Oh My! What's a role? Isn't that a job position? NO! 1. A role is a set of duties. 2. A job is a person's title. 3. A duty is a "commitment" of activities that a person carries out. 4. A job function is your title, what you call yourself. This means: 1. One person has one function on a team. 2. One function has many duties on a team. 3. One person has many duties on a team.

One person has one function on a team. One function has many duties. So, one person can play many duties on teams. Credit: Tech Fleet

Credit: https://giphy.com/gifs/no-ji6zzUZwNIuLS

## How Agile Team Duties Work Agile teams each operate differently because they [self-organize](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization) and agree to their process. Each sprint, they get together to build agreement of what duties people will play on each team through something called a [RACI chart](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts). Different companies and different work environments require different people to do different duties. You may find yourself in a UX design position but expected to play a Scrum Master duty, or a Business Analyst duty. This is common! Take a look at job title descriptions and the daily responsibilities to understand what duties they expect you to play. ## Tech Fleet Duties and Functions This chart shows the breakdown of responsibilities between cross-functional team positions on Tech Fleet project training. This is modeled after industry standard norms so that people get the real industry training they need.

A breakdown of team positions and roles that people play on Tech Fleet teams. Credit: Tech Fleet

1. **Product Strategy function** == Scrum Master duties + Business Analyst duties + Product Owner duties + Product Manager duties + UX Research duties 2. **UX Design function** == UX design duties + UX Research duties 3. **UX Research function** == UX research duties + UX Research duties 4. **UX Writing function** == UX writing duties + UX Research duties 5. **Project Management function** == Scrum Master duties + Project Manager duties 6. **Development function** == Front-end developer duties + Back-end developer duties + QA duties 7. **Solution Architecture position** == Information Security duties + Solutions architect duties ## Everyone Operates Across Functions on Tech Fleet Projects You should not stick to only your job responsibilities when you are on an Agile team. All strong agile teams are "cross-functional", meaning, they all work together across their different roles and functions. Product people do research with UX researchers; UX researchers collaborate in UX design activities with UX designers; UX designers collaborate in product requirements with the Product strategy team. The more collaborative a team is across functions, the more decision making prowess it has on its own. No one should tell them what to do or how to work or how not to work. They need to make their own collective decision. Learn more about cross-functional teams in the Agile Handbook: {% content-ref url="/pages/PWky0mqusNrryCjpBEEE" %} [Cross-Functional Agile Teamwork](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork) {% endcontent-ref %} ## Tech Fleet Team Role Dashboard Tech Fleet maintains training materials to help people understand what kinds of responsibilities are needed for different cross-functional roles. Here's the [Role Dashboard](https://airtable.com/appMDxpNsGN2qyS8N/shrCcRn4L2wKVBDUL) showing the details. This includes the expectations about daily tasks, tools, skills, and deliverables necessary to carry out a role (i.e. a set of responsibilities). {% embed url="" %} Credit: {% endembed %} ## Tech Fleet Team Positions Dashboard Here's the [Tech Fleet Position Dashboard](https://airtable.com/appMDxpNsGN2qyS8N/shroOCNmDNFu7QpTM) showing all of the information you need to know about different team positions in Tech Fleet training. This includes the expectations about roles, daily tasks, tools, skills, and deliverables necessary to carry out a position on a team. {% embed url="" %} ## Learn More about Team Functions in These Sections of the User Guide {% content-ref url="/pages/mJ4CsUHj7WkyVriUe2YM" %} [Project Management Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/project-management-function) {% endcontent-ref %} {% content-ref url="/pages/1MWMoalwVaD0Jakjw18Z" %} [Product Strategy Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/product-strategy-function) {% endcontent-ref %} {% content-ref url="/pages/hOpMfjWUlpOZHs3DE11W" %} [UX Research Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-research-function) {% endcontent-ref %} {% content-ref url="/pages/1pwZTrgZ3yc4wbM75e6g" %} [UX Design Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-design-function) {% endcontent-ref %} {% content-ref url="/pages/EjMKbZzxl71hYz1KOn2b" %} [UX Writing Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-writing-function) {% endcontent-ref %} {% content-ref url="/pages/STFILp2Bkc14170YjOm4" %} [Development Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/development-function) {% endcontent-ref %} {% content-ref url="/pages/FHzWnqQeyKBOmDmwdhBU" %} [Solutions Architecture Function](/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/solutions-architecture-function) {% endcontent-ref %} ## Head to the Next Lesson # Sharing Leadership with Teammates ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Everyone Shares Leadership on Agile Teams
Everyone leads on an agile cross-functional team. Yes, even the interns. Even the people who have 0 experience. This is very intentional! Everyone is in service to everyone else's growth. Read about [cross-functional teamwork here](/team-portal/new-teammate-handbook/expectations-for-teammates/what-does-it-mean-to-be-a-cross-functional-teammate) to learn about team empowerment in decision making. A self-organized team who is empowered to take the reins of ownership should not have a single leader, or even a group of leaders. Everyone should lead. When there's a dynamic of "leader" and "follower", it creates an imbalance of power and ownership.   People wait to be told what to do. People making decisions themselves may take the team in a direction that's not the best way forward. People may not speak up about important concerns because they fear punishment from a leader in charge. Decision making should be shared together in the entire group. Ownership should be handed to the people who are considered the least experienced so that they can grow. Cross-functional agile teams create environments where everyone shares leadership. Everyone makes decisions together; everyone owns work; everyone shares responsibility; everyone supports each others' growth. [Read more about this in the Agile Handbook](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/leadership-on-agile-teams). A lot of people are conditioned to think that something is "right" or "wrong". We seek perfection in decisions, and this creates a fear of making the wrong choice. Agile teamwork removes this notion of "the wrong choice" because teams encourage failure. This means, no one has to make the "right choices" in order to lead! You can get it wrong. You can try and fail, and adjust. This is how team structure of empowered teams operate. They foster senses of belonging, growth, and collective decision making so that they all can feel the deep ownership in the outcomes. This is how people share leadership on agile teams. On a shared leadership team, no team in our community should have single leaders telling everyone what to do, or assigning work. People transfer ownership to their teammates. Teammates decide what work to lead (or be ["accountable for"](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts)) and how to get involved (with the [RACI Chart](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts)). # Case Study Creation for Teammates ## Video Version Here's a video version: {% embed url="" %} Credit: Tech Fleet {% endembed %} ## Telling the Story of Your Experience Teammates involved in project training, volunteer work, and class training should tell the story of their experience through case studies. Everyone tells the same kind of case study: the story of the problems, the decisions made as a team, and the outcomes of progress made as a team. ## Great Case Studies Have The Following ### A Story Arc Everyone loves a great story. There are different ways to tell it, but it should start with some kind of problem and show how it progressed. Try to avoid describing “multiple events” like if you were describing how it all happened. Take the readers there. Envelop them into the story itself, relive the story through the case study with them. There are way to structure a story called “Arcs”, and this template focuses on the arc that depicts three parts: problem, journey, progress. ### Measurable Concrete Outcomes You may have heard the phrase “Do the work with the end in mind”. While visuals can be key to showing how the work happened, it’s not enough to add a lot of pictures of your interface designs or produced results. Showing how you measured success, or how you would measure success, is the most important part of showing the work. You can do this in a lot of ways. If you were not in the position to actually measure change, you should show how you would measure change so that readers can see your thought process. Doing this will highlight the potential impact of your decisions as a team. ### A Focus on the Why Focusing on the reasoning and “why” behind your design decisions in a UX case study is crucial because it reveals your problem-solving mindset and critical thinking skills. Employers and stakeholders aren't just interested in what you designed. They want to understand the logic, research, and trade-offs that guided each choice. By articulating the “why,” you demonstrate that your design isn’t arbitrary or based on trends, but grounded in user needs, business goals, and usability principles. This level of insight differentiates you from others who simply showcase visuals, highlighting your ability to think strategically and collaborate effectively within cross-functional teams. ### User Audience Perspectives This will ground your work in real human needs and context. UX is not a creative field. UX is an applied science field. We follow the scientific method to test hypotheses. Our product decisions are hypotheses, and we need to show how we tested them. We need to show the data that helped us form the hypotheses. All adjacent roles should follow this structure too. Product owners, business analysts, product designers, UX designers, UX researchers: you also need to showcase user perspective about the problems you are solving. Whatever title you are after, your case study should tell the story about the current state, and how you strategized to make the current state different. ### Conflict to Resolve The conflict you resolve could be the user pain points, conflict within the team, or both. Your audiences don’t want to see that you did this work alone. They want to see how your team pulled together to tackle the conflict. They want to see how you progressed through adversity and changing winds. This is an understated strength of teamwork when people face conflict and resolve it to grow together. Discuss in your case study how you grew through the conflict, and how your team and outcomes grew through the conflict. ### Collaboration that's Cross-Functional UX and product work often happens in a team, and sometimes teams isolate themselves based on a department. Employers value designers who can collaborate effectively and contribute to a shared vision, not just produce individual work in a vacuum. Employers who run agile teams want to see your cross-functional collaboration skills meaning how you worked together as a unified team across all kinds of work functions to accomplish an outcome. This is easier said than done. It relies on you to understand the overarching project plan and the work that others did. It relies on you as a teammate getting involved in other work functions so you can tell the story of the context. Showcasing how you worked within a team highlights your communication skills, adaptability, and ability to integrate diverse perspectives into your design process. ## Case Study Outcomes Your case study should: 1. Help readers make informed decisions about your ability to work with others 2. Showcase your collaboration and team skills 3. Showcase your approach to problem-solving 4. Showcase the ways you think 5. Showcase your ability to take a lot of information and condense it
## Case Study Creation Training Template Here's a template that provides a way for you to build the components of a story-driven case study that's based on the problem-solving outcomes and measuring success: {% embed url="" %}
# Resolving Conflict as a Teammate Teammates who serve each others' growth on agile teams resolve conflict through collaboration like everything else. Read the Agile Handbook to learn about how service leaders resolve conflict together: {% content-ref url="/pages/aGoehaYoGSktMV7iqUzt" %} [Resolving Team Conflict as Service Leaders](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/resolving-team-conflict-as-service-leaders) {% endcontent-ref %} {% content-ref url="/pages/B1Y1q3cJY6dSvVukfFjU" %} [The Process for Resolving Conflicts](/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/the-process-for-resolving-conflicts) {% endcontent-ref %} ## Head to the Next Lesson --- [Next Page](/llms-full.txt/1)