# Tips for Teammates ## **Address Blockers Proactively** It's understandable that team members may express their concerns or encounter blockers, as we are all learning. Including learning to work with each other. Nevertheless, it's important to avoid dwelling on the obstacles that are impeding progress. When someone brings up a blocker, work together, as a team to provide potential solutions on how to overcome it. By doing so, we can move ahead swiftly and efficiently. ## **Get Comfortable Being Uncomfortable** Are you nervous you don’t have enough skill? Perfect, then you’re in the right place! This is the story for every project, it's working through the ambiguity and what you don't know. Listen…you’re never going to be 100% ready, and that’s okay! You have to start BEFORE you’re ready because that’s how you learn. Welcome to the edge of your comfort zone. You will need to learn a lot on the job. With that in mind, if anyone wants to learn at Tech Fleet, they have to take the initiative to use their resources to find the answers themselves – same goes for leads. It’s okay to not have all the answers all the time. **Lean into your pain by asking questions** and stay vocal. Don't be afraid to make mistakes on camera because it makes you human, and your team will see that. Set the right example on how you would approach the project because your team will look to you for guidance and behavior. **Getting comfortable being uncomfortable** has a true meaning here. Like anything at Tech Fleet, you get what you put into it. And I mean this in the best way possible. The best (and simplest) way to be prepared is just to **take it seriously**: **Care** about the project **Care** about your team **Care** about your client **Care** for yourself ## Build Partnerships Build partnerships, build trust with your teammates, and uplift the people you're working with. ## **Over Communicate** One of the main aspects of being a peer leader is managing the nuances in communication cross-functionally. ## Consider scheduling project time for Case Studies Scheduling dedicated time for [case studies](/team-portal/new-teammate-handbook/expectations-for-teammates/case-study-creation-for-teammates.md) within the 8-week project timeline can greatly benefit the team by increasing the likelihood of producing portfolio pieces. Since the whole team will still be active this could also make it easier to take screenshots or share specific documents. These case studies could also be incorporated into [handoff documents](/team-portal/new-teammate-handbook/project-training-teams/being-on-project-training/hand-off-and-case-study-creation.md) for future phases, providing valuable context and insights for the next team. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.techfleet.org/team-portal/new-teammate-handbook/expectations-for-teammates/tips-for-teammates.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.