►
Description
Welcome to the Acceleration Content Series! Today’s tip is around how to use forcing functions to work remote-first.
Here at GitLab, as the world’s largest all-remote company, we feel that leaders should consider key forcing functions to ensure a commitment to remote-first practices.
Forcing Function 1 - Expire your Slack or Teams messages after 90 days
How to use forcing functions to work remote-first:
about.gitlab.com/company/culture/…rk-remote-first/
Download the GitLab Remote Playbook:
about.gitlab.com/resources/ebook-remote-playbook/
If you found this Acceleration content valuable, there’s several more forcing functions to share...subscribe to hear more tips.
A
Hello,
world
Michael,
a
bow
from
gitlab
and
the
acceleration
team
bringing
you
the
acceleration
content
series.
Today's
tip
is
around
helping
your
organization
to
embrace
remote
work
here
at
git
lab
is
the
world's
largest
our
remote
company.
We
feel
there
are
some
key
forcing
functions
that
leaders
should
consider
to
ensure
a
commitment
to
remote
first
practices.
A
Expire,
your
slack
or
teams
messages
after
90
days
when
working
synchronously
tools,
like
slack
and
Microsoft
teams,
enable
conversations
that
can
go
on
for
months.
This
equates
to
a
never-ending
stream
of
red
bubbles.
The
unread
notifications
that
really
take
its
toll
on
one's
mental
health,
not
to
mention
they
don't
allow
you
to
ever
really
find
that
flow
state,
letting
slack
beams
dictate
your
working
life
is
just
a
recipe
for
burnout.
A
Also,
you've
got
private
messages,
important
conversations
happening
in
private,
as
opposed
to
in
these
public
channels,
where
other
people
can
benefit
from
knowledge
and
information
sharing,
as
well
as
provide
input.
So
how
do
you
solve
for
this?
It's
simple.
Just!
Don't
subscribe
to
a
chat
plan
that
expires
messages
after
90
days,
make
it
90
days
or
less.
Your
teams
will
benefit,
and
as
soon
as
they've
realized
that
they
won't
be
able
to
query
a
message
thread
for
context
on
a
project
they're
not
going
to
use
that
tool
for
work.
A
Instead,
what
you'll
find
is
that
work
is
being
started,
documented
and
happening
in
places
where
you
want
that
work
to
end
up
and
live
for
us
here
at
git
lab.
That's
get
lab
the
product
in
our
issue
boards
and
things
like
that.
It's
just
a
much
more
inclusive
way
to
work.
It's
a
much
more
transparent
way
to
keep
the
work
out
in
the
open
and
it's
one
of
our
key,
forcing
functions
for
implementing
remote.
It
thanks
for
watching.
A
If
you
found
this
content,
valuable,
there's
several
more
forcing
functions
to
share,
subscribe,
to,
hear
more
accelaration
tips
and
click
on
the
links
in
the
description
below
to
access
get
labs.
Ebook.
The
remote
playbook,
along
with
other
best
practices
for
helping
to
ease
your
company's
transition
to
working
remote.