Live data from Hacker News

Amazon Announces RTO for Employees

cnbc.com

81–90 of 90 posts

Re: Amazon Announces RTO for Employees

#81
post #76

Earlier quoted context omitted.

I have deep collaborative conversations via DM all the time. If anything it's better because it's written.

I've done the same in chat rooms where everyone on the team can read if they want to, even if the conversation is limited to me and another individual.

Yeah I think there's a place for both honestly. The place I work at encourages using a channel. But when it's deep and freeform, I think DMs is better. Sartre's Look and all that.

Re: Amazon Announces RTO for Employees

#82
post #6

There are a lot of companies making remote work work for them, and for a lot of people's lifestyles it's a huge boon. My personal experience has been that WFH has lead to an absolute grinding halt in productivity that requires any form of collaboration. A lot of people will often not respond to Slack for several hours and any video conferencing is usually scheduled for later in the week, instead of in 20 minutes. I k…

> A lot of people will often not respond to Slack for several hours

Fire them.

One hard rule I have for my team is not being responsive on IM for extended periods is treated the same as not showing up for work.

If people need to be taught how to work remotely, or anywhere for that matter, then the company has the wrong people, or maybe interns who need such training.

Re: Amazon Announces RTO for Employees

#83
post #74
post #72

Earlier quoted context omitted.

"So you're saying that your ability to get work done is dependent on forcing time with your co-workers on your schedule instead of theirs? This would be rude even if in the office. I've had the complete opposite experience of being able to get co-workers to respond in chat and jump onto meetings when needed." I'm saying on average, everyone's ability to get stuff done is higher if everyone can interrupt everyone.

A very works on my system take. If you interrupt me it takes me hours to get back on speed.

What do you work on and what % of the day do you work on tasks that complex?

Hours is an incredibly long time. I'm not against people blocking off specific time when dealing with an especially gnarly bug or planning out a major feature, but for day-to-day tasks the cost of an interruption is usually a "right, where was I" once it's over.

Re: Amazon Announces RTO for Employees

#84
post #79
post #72

Earlier quoted context omitted.

"So you're saying that your ability to get work done is dependent on forcing time with your co-workers on your schedule instead of theirs? This would be rude even if in the office. I've had the complete opposite experience of being able to get co-workers to respond in chat and jump onto meetings when needed." I'm saying on average, everyone's ability to get stuff done is higher if everyone can interrupt everyone.

> I'm saying on average, everyone's ability to get stuff done is higher if everyone can interrupt everyone. There's no actual evidence of that being true though. It's very much your personal take on it as you've said. I'm also hesitant to ask that if your work relies so much on being able to interrupt your coworkers at a moments notice is that evidence of other issues. Not having power to make decisions on the direct…

I agree that there's no good data to back this up, it seems really hard to collect. Unless you have a rock solid idea on how to measure productivity? The rest of your post is essentially "I hesitate to ask, but are you bad at your job?"

No, it's more that when you're venturing outside your usual territory it can be so much quicker to ask your teammates who are area owners.

If I'm modifying widget X that John built, and I encounter something non-obvious, I can spend an hour figuring out why that was, or I can ask John sitting next to me, and he can usually unblock me in about 30 seconds.

When I help people get up to speed in code I've written I usually say something along the lines of "if you get stuck and you've spent 5 minutes trying to figure it out, please ask me about it".

Re: Amazon Announces RTO for Employees

#85
post #82
post #6

There are a lot of companies making remote work work for them, and for a lot of people's lifestyles it's a huge boon. My personal experience has been that WFH has lead to an absolute grinding halt in productivity that requires any form of collaboration. A lot of people will often not respond to Slack for several hours and any video conferencing is usually scheduled for later in the week, instead of in 20 minutes. I k…

> A lot of people will often not respond to Slack for several hours Fire them. One hard rule I have for my team is not being responsive on IM for extended periods is treated the same as not showing up for work. If people need to be taught how to work remotely, or anywhere for that matter, then the company has the wrong people, or maybe interns who need such training.

So no one can do any sort of deep work in your team. Should definitely mention that in interviews for potential candidates to spot red flags.

Re: Amazon Announces RTO for Employees

#87
post #6

There are a lot of companies making remote work work for them, and for a lot of people's lifestyles it's a huge boon. My personal experience has been that WFH has lead to an absolute grinding halt in productivity that requires any form of collaboration. A lot of people will often not respond to Slack for several hours and any video conferencing is usually scheduled for later in the week, instead of in 20 minutes. I k…

Yea, let's interrupt our developers every 20 minutes because the PM needs a question answered.

'Hey, how are you?'

And then nothing.

OMG he takes forever to reply on Slack.

Re: Amazon Announces RTO for Employees

#88
post #78

Earlier quoted context omitted.

People who don't work don't work, it doesn't really matter where they are.

That seems false on the face of it. There are people (on HN, even!) who say they're more productive from an office, specifically without the distraction of children. These are people that "don't work" from home, so by your logic, they also wouldn't work from an office. Yet that doesn't seem to be true.

Thats if you take what a small number people say at face value and then apply that to everyone.

We can each only work with anecdotal evidence. In my working life I've not been able to observe a lot of people switching between in office and WFH. But those I have observed either got on with things in either location or carried on not really doing much, regardless of kids.

It would be cool to see some actual evidence... of anything really.

Re: Amazon Announces RTO for Employees

#89
post #84
post #79

Earlier quoted context omitted.

> I'm saying on average, everyone's ability to get stuff done is higher if everyone can interrupt everyone. There's no actual evidence of that being true though. It's very much your personal take on it as you've said. I'm also hesitant to ask that if your work relies so much on being able to interrupt your coworkers at a moments notice is that evidence of other issues. Not having power to make decisions on the direct…

I agree that there's no good data to back this up, it seems really hard to collect. Unless you have a rock solid idea on how to measure productivity? The rest of your post is essentially "I hesitate to ask, but are you bad at your job?" No, it's more that when you're venturing outside your usual territory it can be so much quicker to ask your teammates who are area owners. If I'm modifying widget X that John built, a…

So coming back, your main problem still seems to be the unresponsiveness of your teammates when you can't force them to respond by being directly in front of them? If you're teammates are really that bad at responding then perhaps they are "bad at their job". Just about every job description usually has something about ability to communicate included in it.

So basically trying to fix one problem with another one. Can't please everyone 100% of the time.

Re: Amazon Announces RTO for Employees

#90
post #82

Earlier quoted context omitted.

> A lot of people will often not respond to Slack for several hours Fire them. One hard rule I have for my team is not being responsive on IM for extended periods is treated the same as not showing up for work. If people need to be taught how to work remotely, or anywhere for that matter, then the company has the wrong people, or maybe interns who need such training.

So no one can do any sort of deep work in your team. Should definitely mention that in interviews for potential candidates to spot red flags.

If “deep work” means can’t function as a team member and communicate in a timely and professional manner, like we all did when working in an office was more common, yes I let them know.
Post reply on HN