Read on Twitter
@SagerToothTiger just got a ton of backlash on her tweet about sending emails at 10 pm.
Here's why sending emails at 10 pm is ok
Here's why sending emails at 10 pm is ok
If your team is *remote* and *async* (it's probs both rn) you need to track your teammates' OUTPUT, not HOURS.
(^this should be true anyway, but that's another thread)
If done correctly, this switch will have a major impact on how your team works. In short, it provides freedom.
(^this should be true anyway, but that's another thread)
If done correctly, this switch will have a major impact on how your team works. In short, it provides freedom.
Freedom to...
-work during hours you are most productive
-sleep when you need sleep
-be with your kids when you want to be with your kids
and so on.
-work during hours you are most productive
-sleep when you need sleep
-be with your kids when you want to be with your kids
and so on.
I have teammates on the other side of the world ( @AsDivyansh, @calledRahul 
).
When I send an email to them at 10 pm, they receive it at their 8:30 am.
We don't make them work during ET hours. They can work when they want to, and they deliver value via OUTPUT (not hours)
).When I send an email to them at 10 pm, they receive it at their 8:30 am.
We don't make them work during ET hours. They can work when they want to, and they deliver value via OUTPUT (not hours)
Everyone on our team chooses when they work.
Sometimes they choose their hours based on time zone, sometimes it's based on when they're most productive, sometimes it's based around their kids' schedule, sometimes if baed on when they like to go to the gym.
Or some combination.
Sometimes they choose their hours based on time zone, sometimes it's based on when they're most productive, sometimes it's based around their kids' schedule, sometimes if baed on when they like to go to the gym.
Or some combination.
And for this reason, we are all aware that we need to draw our *own* boundaries between work and life.
We understand that emails, calls, pings, can (and do) come in at all hours of the day, and it is up to *the individual* to draw healthy boundaries between work and life.
We understand that emails, calls, pings, can (and do) come in at all hours of the day, and it is up to *the individual* to draw healthy boundaries between work and life.
And we explicitly ask each new teammate during their onboarding which hours of the day they want to be *synchronously available* to other members of the team.
Usually we aim for 3 hours of overlap with other teammates.
Usually we aim for 3 hours of overlap with other teammates.
Tl;dr
1) On async teams, track output instead of hours
2) Output can happen at any time of the day
3) This gives everyone FREEDOM to work and rest when they CHOOSE TO
4) With this freedom comes responsibility to protect your own time. No one will protect it for you.
1) On async teams, track output instead of hours
2) Output can happen at any time of the day
3) This gives everyone FREEDOM to work and rest when they CHOOSE TO
4) With this freedom comes responsibility to protect your own time. No one will protect it for you.
