3 ms·
Many assumptions in your statement. You probably can't evaluate your productivity by yourself and record profits come at specific context, specific time and bas
by fgblanch 4y ago
Many assumptions in your statement. You probably can't evaluate your productivity by yourself and record profits come at specific context, specific time and based on a historic inertia and multi-year strategy.
This is not about fighting any tyranny, this is about running companies, and the same way there are costs associated to work in an office for you, there are costs associated with employees working remotely (and not only economic), but you don't see them.
- rzz3 4y agoIt’s fairly easy for most people to compare their own productivity before and after working from home. Mine is significantly greater. The number of hours I’ve spent working has drastically increased due to losing my 2 hour commute, and the focus I’ve been able to achieve at home is like nothing I’ve ever seen at an office.
- fgblanch 4y agoHow you know it was not anecdotical due to switching workspaces and it is not regressing to normal?
- txcwpalpha 4y agoPersonal productivity isn't the same as organizational productivity. This is one of the key things at the heart of the WFH discussion. It's entirely possible that you personally wrote more lines of code, but the team still fell behind in products shipped. This could be due to many different factors. One easily identifiable one is that while good employees might be more productive WFH, poor performers are even more poor when WFH, and it becomes much more difficult to actively manage/coach/mentor poor performers when they are remote. There's many more metrics too, like attrition, or poor onboarding experience for new hires, or inability to coordinate across teams (sure you're producing more personal output, but is it the right output?) Organizations are more than individuals working in isolation. They're coordinated masses of people that have to work together, and what is best for one person's personal productivity may not be best for the organization's overall productivity.
- asdff 4y agoCommunication is great for organizations, but I don't understand what you are getting in person that you don't get over zoom talking about whatever you need to talk about. It's not like the entire org is talking to eachother at once in person. At best you talk to like a handful of people a day, probably a good amount of that talk has nothing to do with work. Meanwhile with zoom I've been having so many more directed meetings with key people. Like before, we would sit in this in person meeting and say something like "it would be nice to get Steve's input on this, if he were here in this meeting" and now with zoom we can actually get steve in the meeting. We meet with people from around the world who might have relevant input. If your issue with wfh is team isolation, just have more meetings and get better at communicating. The issue is not the venue, its the event.
- refurb 4y agoI work with a bunch of people who are super busy and they would say productive. But little of their work drives the company forward. 6 people that are paddling a boat in different directions goes nowhere.
- jbluepolarbear 4y agoMany assumptions in your statement: people are fully capable with self evaluation of their own productivity and companies aren’t bringing people back because of some cost associated with remote work. Apple, in this case, is making people come back to justify their super expensive and ridiculous new campus.
- amf12 4y ago> Apple, in this case, is making people come back to justify their super expensive and ridiculous new campus. Needs sources. Otherwise it's just speculation.
- jbluepolarbear 4y agoNeed counter sources; otherwise it’s just speculation. Goes both ways.
- darth_avocado 4y agoI can, because I go into office twice a week now. The days I am least productive are the ones I go in, because I lose more than the two hours of door to door commute every day. It is the fact that I lose my most productive hours of the day in waking up, getting ready, fixing a breakfast, getting myself to the office and having to small talk with people before FINALLY I can work.
- fgblanch 4y agoThen you are accepting that what drags your productivity down is commuting, not actually working from an office. Remote working may be a solution to your problem but comes with associated costs you may be not counting (misunderstandings, wrong team member mental models, alignment calls, longer on boarding times, suboptimal knowledge sharing, less serendipity/synergies in general). Another solution to your commuting problem is find a job that is closer to your place
- Apocryphon 4y ago> Another solution to your commuting problem is find a job that is closer to your place A solution that may depend on first resolving the housing crises in many tech hub cities.
- dismantlethesun 4y agoI agree. However I still support work from home because it’s not up to me as an employee to fight for something that benefits the company at my own expense. Commuting, finding an apartment closer to work, living in a place that you dislike, buying lunch or making it in advance, and a whole mess of other things are expenses that fall directly on an employee. On the other hand suboptimal knowledge sharing, misunderstandings, less serendipity, etc. are not only hard to measure but are strictly of benefit to the employer. If WFM means slightly less productivity per dollar spent in exchange for employee happiness , then so be it. The company can absorb the expense just like it does when it pays for on site cafeterias, overtime, and bonuses or extra vacation to mitigate burnout.
- asdff 4y ago
- deleted 4y ago[deleted]
- ronaldo7 4y ago
- falcolas 4y ago> You probably can't evaluate your productivity by yourself I’m going to go out on a bit of a limb here, and say if you can’t evaluate your own productivity, you aren’t trying. If you are running any kind of scrum, or you are tracking estimates on tickets, you can create a velocity for yourself. You can track that velocity over time - weeks, months, years. You can track the velocity of your peers, or at least your entire team and compare your velocity to that. You can look at how many features you implement. You can look at how many code reviews you do and compare that against how many code reviews your peers are doing. And finally, you can calibrate your own measurements against your bosses feedback on your performance. There’s a lot of data to be tracked, and so I really do believe that if you don’t know your own productivity in relation to your past productivity, or to your peers productivity, it’s because you are not collecting the data, not because there’s no data to collect.