Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
This content was written exclusively for
by Samantha Lee, Digital Nomad Career Coach
and Community Advocate at GitLab
Educator to remote community advocate
Communication
Leadership
My training focused on diverse, in-person communication.
Now I apply these communication skills in a remote format.
Sharing with others on the same path to remote
Async is defined as things happening at different times.
Mark
Joseph
Samantha
Async teams typically have working hours that don’t necessarily overlap.
Today
Asynchronous communication
means you can’t expect immediate responses on Slack, Email, etc.
Remote works best with async communications, and it’s something to implement even if your company is starting/trying remote with everyone in the same time zone.
Remote work allows
for flexibility in working hours, time to support family and friends, and the option to optimize your efforts and skills.
A team entirely based in the US can builds their working hours around kids’ schedules, appointments, and when they feel most productive
A globally distributed team can work async based on their timezone
At GitLab, we use low context communication for clarity.
Low Context Communication
Be explicit and avoid confusion
Share direct, elaborate responses and notes
Include links whenever possible
Without body language, similar experience, or cultures, you end up with low context.
In these situations, written communication works best.
https://slack.com/
https://docs.google.com/
https://about.gitlab.com/
https://asana.com/
https://trello.com/
https://prezi.com/video/
Using low context lets a team jump right into the 'meat' of an issue or project, instead of getting caught up.
Create a space where anyone who needs to know can read, get caught up, and contribute to the discussion, like in a public issue on GitLab or a blog post with open comments.
becomes a means for
historical preservation
of resources for team
members and ensures
that information
is up-to-date.
Gitlab works with a handbook-first mindset, meaning we document as processes are improved, not after it’s all done.
means you update your handbook as processes are being improved, not after the fact.
If you must communicate synchronously,
consider how to document conversations
so that knowledge isn’t lost.
At GitLab, we all jump in to record notes when we aren’t speaking. Consider this option, or set a designated note taker.
Record questions and answers
Record and post the call
Remote work != limit team building
It is a powerful tool to strengthen team relationships
“I can never focus at home!”
“How do you work at home all day?”
“Do you ever feel isolated?”
Prioritizing team building on a remote team helps combat isolation
meant for
personal sharing:
#random, #dadjokes, #officetoday, #travel
https://about.gitlab.com/blog/2019/10/02/support-virtual-pizza-party/
https://about.gitlab.com/company/culture/all-remote/informal-communication/#coffee-chats
https://about.gitlab.com/company/culture/all-remote/informal-communication/#team-social-calls
https://about.gitlab.com/handbook/incentives/#visiting-grant
Check out these resources for a successful shift into remote work.
GitLab Communication handbook section and Remote Manifesto as a guide.
Embrace all-remote work, and demonstrate at the leadership level.
Adopt low context communication in your job application materials, and interview strategies.
Document your journey by writing LinkedIn articles or starting a blog.