00:02you mentioned sync versus async we try
00:05to look at it as sync complementing
00:08async there are there are two tools in a
00:11toolbox sometimes you need the
00:13synchronous tools sometimes you need the
00:15asynchronous tool but we've been very
00:19intentional about weaving asynchronous
00:21workflows into the culture at get lab
00:24and and to create massive Tailwinds
00:27around around this to really Galvanize
00:29people to learn to do things very
00:31differently maybe even counter to what
00:33has got them to a certain point in their
00:37the best way to do that is to integrate
00:39it into your values and operating
00:41principles it really can't it it's
00:43non-optional if you look at the gitlab
00:45values page you'll find an operating
00:47principle of bias toward asynchronous
00:49communication and we actually bundle
00:51that within our diversity inclusion and
00:53belonging value not our results or
00:55efficiency value and the core reason for
00:58that is if you are thoughtful and
01:00deliberate enough to move a piece of
01:01work forward without commandeering 30 or
01:0450 minutes of someone's day you are
01:06fundamentally being more respectful of
01:09their time and so for us async is about
01:12the work for sure but it's also about
01:14showing respect to other people now what
01:18do you need to do something like this
01:20it's it's quite difficult to stand it up
01:22and I think that's why you're seeing a
01:24lot of organizations who have quote gone
01:27essentially copy and paste the office
01:29environment into the virtual environment
01:32and not really take advantage of what's
01:34possible when you are globally
01:36distributed the core reason that I have
01:38found is that most management
01:41philosophies prioritize the speed of
01:44knowledge transfer as in how fast can
01:47person a tap person be on the shoulder
01:49and transfer something from one brain to
01:52the other but to do this well your
01:55management has to optimize for the speed
01:57of knowledge retrieval
01:59how fast can person a and person B seek
02:03and find information on Parallel tracks
02:06without needing each other to be online
02:09or awake or fully brought up to speed
02:11and this really gets at the heart of
02:14building infrastructure Building Systems
02:17that optimize for that and it's a
02:19completely different way of thinking
02:21from the the co-located Norms of getting
02:24people together such that knowledge is
02:26always in physical proximity to each
02:31other when you're working across the
02:33globe you can't assume that someone's
02:34available that they're online that
02:36they're in the same time zone that
02:37they're not on PTO so now we're seeing
02:40companies scramble to build systems
02:43Knowledge Management Systems so that
02:46that information isn't just in someone's
02:49head that's how you scale knowledge in a
02:51global space you did ask a bit about
02:53meetings so at gitlab all meetings are
02:55optional and we're very intentional
02:57about what a synchronous meeting has to
03:00have before it can even be accepted on a
03:03all work meetings have to have an agenda
03:05No Agenda No Agenda this is again being
03:08respectful of someone's time so that
03:10even if they can't make the synchronous
03:12meeting there's an agenda there from the
03:14start they can input their questions
03:15they can input a loom for example they
03:19actually can contribute to the meeting
03:20without physically being there and also
03:23this is how we scale information even
03:25after that meeting happens the agenda is
03:27still there we can go back we can
03:29reference it we can see what decisions
03:30were made if there's anything crucial
03:32that the entire organization needs to
03:34know we can document that in the
03:36handbook and that's how we enable
03:38meetings to be optional we also document
03:41what good meetings look like and what
03:44things shouldn't necessarily be in
03:46meetings be a meeting organizations ask
03:48me all the time how do we reduce
03:50meetings and my friends at levels Health
03:52have this concept of memos over meetings
03:54which I really like instead of the term
03:56asynchronous which feels very big and
03:58weighty and nerdy at times but things
04:02like fyi's status update dates and
04:04recurring meetings are the low-hanging
04:05fruit so if you're listening to this and
04:07you're like where do I start status
04:09updates fyis recurring meetings those
04:12are usually the first that can go