Ok, so we all know and understand the benefits of async work for the employees. Given that good developers are dufficult to get (for below-FAANG compensation), it makes sense to consider offering this as a benefit.
But the big hairy mammoth in the room is that the company needs to put a lot of effort into making sure everyone does their part. A single person who is taking advantage of the benefits (slacking off) will quickly bring down productivity of the whole team. "They are not working much, why should I?" In the end it is easier to lead people that you see live.
I would be grateful for any hints on how to better organize work to make sure productivity stays high, if anyone has experience with this.
>A single person who is taking advantage of the benefits (slacking off) will quickly bring down productivity of the whole team
People are already doing this on-site. Whatever metrics you're using to prevent this kind of behavior should be largely independent from sync/async. There are also individual reasons why one would slack either sync or async. You give an async example. Plenty of school kids know the example of the projects where half the group doesn't do anything, even when they are together.
Good point. I guess it is the same as onsite... Team lead needs to know who is working on what and make sure that output velocity makes sense, or determine what the reason for poor performance is and try to fix it.
But the big hairy mammoth in the room is that the company needs to put a lot of effort into making sure everyone does their part. A single person who is taking advantage of the benefits (slacking off) will quickly bring down productivity of the whole team. "They are not working much, why should I?" In the end it is easier to lead people that you see live.
I would be grateful for any hints on how to better organize work to make sure productivity stays high, if anyone has experience with this.