The issue I often have with discussions of remote work vs. on-site, is how much confirmation bias tends to be incorporated into the conclusions made. After about 16 years of on-site work (at various jobs), I did almost 5 years of remote work (for a single company), having just recently returned to an in-office role (despite focusing on landing another remote position, the best opportunity wasn’t.) And, frankly, I fin…
The benefits of a more asynchronous workplace
41–50 of 272 posts
Re: The benefits of a more asynchronous workplace
#42Re: The benefits of a more asynchronous workplace
#43If you're in the i/o bound phase remoting is often hard. You need to talk to people, pull answers from them, communicate, coordinate, reach agreements and nail down development plans. You can't do anything anyway unless you agree on the next steps first.
Conversely if you're brain bound all you want is a laptop and being alone at home because it's way more efficient to focus on a problem when you can forget about everything else. You can't plan ahead anyway unless you dig down in the code and see for yourself first what will work and what needs to change.
These phases alternate in worklife, maybe based on projects, time of the month, the whatever happenstances take place in the progress of development. Usually when you're stuck in one phase you really need to spend time in the other phase for a while. This is normal.
This has consequences. People working remotely tend to maximise their time on what they're efficient at, i.e. brain bound programming. At the office it's easier to invite people to meetings through the week to get work done that way because you can't really be brain bound at the office anyway. Thus remote types and office types tend to inflate their favourite phase as much as possible.
This inflation happens because these two phases are inherently incompatible with each other, and crossing the gap to switch phases is tedious.
But if you only ever work i/o bound you begin to wonder how could people work remotely at all. After all, everything happens in the office anyway so maybe working from home could work if only we add enough meetings to keep the remote people more tightly in the loop... And people working steadily from home begin to fathom, in time, whether it's possible at all to work at the office as all you have is constant breaks, meetings, people coming to ask about stuff and you can't ultimately get any real work done.
Different things begin to become important for people who don't alternate. So there's a slight confirmation bias in how people flock to the position and environment that maximises the kind of work they're really good at. But the caveat is that in doing this that you could be comfort-siloing yourself. So natural and healthy alternating between phases is what keeps you open and able to adjust to changes in work life and work projects.
On the other hand, people who alternate too often begin to get nothing done. You need to allocate batches of time for both phases in some moderate proportion. How to balance that is more of an art than anything else.
Sounds familiar, anyone? This is a dynamic I've observed in my own work life over and over again.
Re: The benefits of a more asynchronous workplace
#44I 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…
David Graeber's book "Bullsh*t Jobs" is about that.
These companies main priority is not efficiency and productivity. If it was, they could hire less people to do the same work and that would foster unemployment.
They have a political and social role: hire as many people as possible. Keep them employed and busy and keep an eye on them.
Become too big to fail and you'll be rewarded with overbudgeted contracts (and even bailouts, sometimes).
Re: The benefits of a more asynchronous workplace
#45Anecdotal but I'm the opposite. I hate working from home and love having a team around me, sharing goals and ideas and hyping each other. Different strokes etc.
I will be cynical but this does not sound like some work is being done there. Reminds me of the guys of the gym who spend 90% time here just talking.
Re: The benefits of a more asynchronous workplace
#46Re: The benefits of a more asynchronous workplace
#47I 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…
It's then empirically obvious that I get more done and am happier.
If they don't like it, they can sack me. I earn more than twice minimum wage, ergo I can work half the year and get by.
It's never happened yet because it turns out actually people like people who get stuff done. Who knew?
Behind this monitor I'm looking out at the river, watching Winter roll in as I eat lunch. :)
Re: The benefits of a more asynchronous workplace
#48Except for the occasional visit to the office to give a few high fives and have some chit-chat I work remotely. Until recently we used Toggl to track work time and the guidance was to have "6h of focused work daily". I'm managing 5h 15min-ish, but only when working remotely. When I'm in the office that number organically drops to around 3h 40min. Only person really doing those hours(and above) is one guy who's not in…
I am, however, bad at time tracking by disposition, and haven't made a full system yet.
Re: The benefits of a more asynchronous workplace
#49Productivity depends on the phase of work. Simplisticly put there are two phases of mental work such as programming: i/o bound and brain bound. If you're in the i/o bound phase remoting is often hard. You need to talk to people, pull answers from them, communicate, coordinate, reach agreements and nail down development plans. You can't do anything anyway unless you agree on the next steps first. Conversely if you're…
Re: The benefits of a more asynchronous workplace
#50I 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…
If the only method for your manager to know what people are working on is to tap people on shoulders, then doing that isn’t a “bad behavior” for the manager, it’s necessary behavior.
Of cause a better solution is to have trust and plans. (Agile, scrum, waterfall, napkin sketches or whatever it doesn’t matter as long as people align during planning and have transparency into the plan). But in the absence you still need to have management in sync with what is going on.
Naturally the best pathway forwards is to look into changing your system to include all these value adding elements. But enabling remote work while management is critically dependent on physical presence to continue operation is not a good idea. And the solution is not just for managers to “give up the mindset” of knowing what’s going on below them. Trust is great when it works, and toxic when it doesn’t. The agile mantra of increasing trust is not just supposed to advocate blind trust. It’s about building a framework and working routine where we are validated in trusting each other.