Live data from Hacker News

The benefits of a more asynchronous workplace

doist.com

181–190 of 272 posts

Re: The benefits of a more asynchronous workplace

#181

Earlier quoted context omitted.

My manager _constantly_ will shout out, "does anyone know what X is working on?" It pisses me off to high hell that a manager has to ask his workers what another worker is working on. I honestly think that EVERYONE should be using a ticket tracking system and just put assignments in a person's queue. I don't see why this is such a big deal or looked down upon. It's so easy to see what everyone is working on, run repo…

A huge problem with ticketing systems is then management uses it to track all productivity. We had a ticketing system and one guy in our group had between 60% and 80% more tickets than the rest of us. So it would seem we were all slackers, however he took the tickets that took like 2 minutes to do (password resets, account unlocks, etc...), meanwhile i would get stuck troubleshooting a production performance issue th…

On the flip side... At my previous job, cause of the ticket tracking system, it was shown that I handled 40% of all tickets that came into our team of 7 people. And this wasn't 2 minute tickets either, these were projects also.

Sorry you had that experience, but to me the justification of those types of system are solid.

Re: The benefits of a more asynchronous workplace

#182

Earlier quoted context omitted.

I can't tell you how unburdening it is to read your response. Thank you for your honesty.

I can tell you, I'm in the same boat. I can't really do more than 4 -5 hours of actual coding on a typical day. I've done days with 7 - 12 hours of coding but those are outliers. Also by Thursday, I'm pretty burned out. I rarely get a lot done on Friday.

We all are, but we play this little game with our employers so that we don't get fired.

My take is that you can't shoehorn creative work into your desired time slots. Not if the result is supposed to have any quality.

I have found that sometimes I just need to stare away from the screen and forget what exactly I have written in order to obtain a fresh perspective and spot any problems.

No way to speed up this process, and what's worse is that if I try to log only the time during which I did "focused work", the result generally doesn't go over the mentioned 5h 15min daily.

Every person I ever asked about this is in the same situation.

Re: The benefits of a more asynchronous workplace

#183

Earlier quoted context omitted.

> As one of my ex CEOs put it: "If I don't see my employees stressing out at thier desks I get the impression they're not working." This really hits the nail on the head, in my experience this is accurate for employers that are anti-remote , they want to be able to see people "work". I've argued that that means they are essentially paying people to be there 8 hours a day, not that they're working 8 hours a day. You s…

It’s easy when work gets completed. I would hire anyone remotely or let them play games at work if work is done. It is more difficult when we think their work in average or has a lot of defects. Then, the contract is for them to put in the required hours with decent concentration, and they have fulfilled their part in a measurable way that satisfies the manager. And truth be told, if their work were perfect, they wou…

Then the junior developers never get the benefit/mentorship of the best senior developers, instead they get mentored by the senior devs with poor productivity. That seems like a recipe for more unproductive developers

Re: The benefits of a more asynchronous workplace

#184
post #144

Earlier quoted context omitted.

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

> (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. I don't get it - shouldn't one-on-ones and regular progress check-ins (be those standups, metrics (This is your #2), whatever) give you that information? None of those are easier when on-site. In fact, given today's move to…

> > (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site.

> I don't get it - shouldn't one-on-ones and regular progress check-ins (be those standups, metrics (This is your #2), whatever) give you that information? None of those are easier when on-site. In fact, given today's move towards open offices, any form of 1:1 collaboration is easier remotely where you don't have to fight for precious meeting room space.

This is not quite the case everywhere. We have agile 5-8 person offices and people are still supposed to walk out for longer phone calls occupying one of the smaller meeting rooms.

But I actually like that different teams can mix a lot easier.

Re: The benefits of a more asynchronous workplace

#185
post #144

I tried sharing these studies at my ex employers in Europe hoping they'd spare me the hellish 40 minute commute in stop/start traffic and they weren't interested at all. Management there only values "butt time in seats" and the ability to come over and interrupt you by tapping you on the shoulder whenever they need something. As one of my ex CEOs put it: "If I don't see my employees stressing out at thier desks I get…

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

I would like to suggest a tremendously simple (4) : Every day, each employee spends no more than 5 minutes reporting what they did the prior day, and what they are planning to work on that day. If they're blocked by anything, they can mention that and ask for assistance.

I just finished working on a fully remote contract that worked that way, every day at noon there was a conference call that never took longer than 15 minutes. It worked great. A couple manager types were on the call, and they'd share any developments on the contract side of things, feedback from the customer, things like that, but mostly they just listened and took note of potential issues and made sure they got resolved (so like if you mentioned a problem one day then didn't the next, they'd ask if it got dealt with).

Re: The benefits of a more asynchronous workplace

#186
post #144

I tried sharing these studies at my ex employers in Europe hoping they'd spare me the hellish 40 minute commute in stop/start traffic and they weren't interested at all. Management there only values "butt time in seats" and the ability to come over and interrupt you by tapping you on the shoulder whenever they need something. As one of my ex CEOs put it: "If I don't see my employees stressing out at thier desks I get…

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

Reminds me of an old adage about tech work and other skilled labors: If you give me a task that takes a normal perosn 8 hours, and I finish it in 30 minutes, you're paying me for the skill, knowledge and experience that allows me to do it in 30 minutes. I do not owe you another 7.5 hours of work. I owe you the job being done, not the hours it should take to do it.

Re: The benefits of a more asynchronous workplace

#187
post #144

Earlier quoted context omitted.

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

I would like to suggest a tremendously simple (4) : Every day, each employee spends no more than 5 minutes reporting what they did the prior day, and what they are planning to work on that day. If they're blocked by anything, they can mention that and ask for assistance. I just finished working on a fully remote contract that worked that way, every day at noon there was a conference call that never took longer than 1…

Making standups useful to everyone on mid-to-large teams (i.e. > 6:1 employee:manager ratio) is quite challenging, but yes, you raise a good point that this is viable, particularly for smaller teams.

Re: The benefits of a more asynchronous workplace

#188
post #144

Earlier quoted context omitted.

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

Reminds me of an old adage about tech work and other skilled labors: If you give me a task that takes a normal perosn 8 hours, and I finish it in 30 minutes, you're paying me for the skill, knowledge and experience that allows me to do it in 30 minutes. I do not owe you another 7.5 hours of work. I owe you the job being done, not the hours it should take to do it.

Isn't that one of the reasons Hacker News exists, to fill those other 7.5 hours?

Re: The benefits of a more asynchronous workplace

#189
post #144

Earlier quoted context omitted.

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

In the many jobs I've had I've never seen "things go side ways" because those tricky employees have finally found a way to not do any work! By and large the vast majority of workers have the capitalist cultural logic deeply ingrained in their psyche and personally feel value only when they produce meaningful work. Most people are not trying to get away with doing less, and, at least in my experience, feel the most sa…

Agree that 90% of people want to do effective work. The problem is that 6 people have 7 opinions about what effective means.

It's not about blame, it's about trying to ensure the team works together cohesively, and that individuals are unblocked.

Re: The benefits of a more asynchronous workplace

#190
post #144

Earlier quoted context omitted.

As someone who has gone to the dark side, there's an interesting tradeoff here. There's basically three scenarios: (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. (2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some w…

Reminds me of an old adage about tech work and other skilled labors: If you give me a task that takes a normal perosn 8 hours, and I finish it in 30 minutes, you're paying me for the skill, knowledge and experience that allows me to do it in 30 minutes. I do not owe you another 7.5 hours of work. I owe you the job being done, not the hours it should take to do it.

> I do not owe you another 7.5 hours of work.

Only if you are a contractor and you've fulfilled your contract. If you are a salaried employee I expect you to keep your hopper of tasks full so you aren't sitting around idle 95% of the day waiting for me to feed you 30 minute taskers

Post reply on HN