🫂Working with Different Working Styles
Video Version
Here's a video version:
Overview
We live our mission and values everyday, and you should too as a community member. We are a community of learning and growing individuals working towards access to quality leadership development and teamwork development. Be conscious of how you are communicating with others. Keep your interactions with teammates professional. We take code of conduct seriously, and encourage community members to report any violations of code of conduct through the processes we have in place. You can learn more about this in Safe Space section of this guide.
Being You and Respecting Others
Tech Fleet team members come from all over the globe. They bring different lived experiences and perspectives. It is important that we recognize and respect everyone’s way of life. Every member of our community should feel a sense of belonging. Everyone should feel free to challenge decisions, speak out, and communicate their boundaries in their team environment. Using ‘they’ when a team member has not explicitly defined how they want to be identified is one example of building a healthy work environment. Likewise, you should feel comfortable communicating your personal preferences, whether it be name, identity, working boundaries, or anything else.
Structure your meetings and tasks in such a way that every team member is able to play to their strengths and lean on the team for help with the things they want to improve. One way to do this is by communicating directly and clearly as much as possible, avoiding innuendos, sarcasm, and implied/unspoken statements if there is any risk of being misunderstood. Your team will benefit greatly learning about your unique strengths and challenges and how accommodations can improve the team's output as a whole.
Everyone excels in different kinds of working environments. Some of us enjoy working collaboratively in a synchronous environment, discussing thoughts and ideas in real time. Some of us feel more productive doing the thinking on our own and sharing our thoughts in Slack or through a comment within a document. It is up to the collective team to discuss needs and desires, make compromises, and ultimately determine what a working environment looks for them.
Asynchronous Working
In the perfect world, everyone will know exactly what they need to do at any given time and provide their deliverables in a timely manner, without ever having jumped on a call. Unfortunately, that’s not the world we live in, but that doesn’t mean it’s impossible to work outside of a call. Async working requires planning and delegation, but is a great way to maximize the amount of time and attention a task is given. Teams should decide what level of async working they feel comfortable with and ensure that is the default for the duration of the project.
Synchronous Working
Some discussion can’t be hashed out over Slack and need to be addressed synchronously. You might find yourself discussing something asynchronously with team members, yet after two or three exchanges back and forth, no decision has been made. In this situation, a synchronous session may be warranted. Sync sessions can also manifest in the form of sprint planning, weekly team sessions, and client demos.
Last updated