Hacker News new | past | comments | ask | show | jobs | submit login

> scruple's boss should have told him that right at the interview stage, before a job offer is made.

Well, this is awkward. I don't think you even read my original post. I literally said that I transitioned from on-site to part-time remote to full-time remote. I've been with this company for many years, it's gone exceptionally well until very recently.

> Maybe say that he expects scruple to turn up in the office for a few days every month.

We've had the working agreement ever since I went full-time remote, back when I was on a different team, that I am unequivocally full-time remote with no obligations to turn up in the office. *editing this to add: If that needs to change because of new team dynamics, that's fine, but it's going to be awfully hard on my colleague in Mexico.

> Or whenever a major decision needs to be made and scruple is out of the loop.

Major decisions should NEVER be made in isolation or with team members who aren't even sure what is being tabled. Why do we need to play "catch up the other 3 team members" when we're having a discussion about a major decision? Oh, because another team member keeps having side conversations with product people or customers and not relaying the information back to the rest of their team? Hmm, sounds like a personnel problem to me -- and not with the "out of the loop" team members, either.

> Or have regular one-on-one meetings over video-conference with everyone in the team to remain connected, making up for his physical absence.

Myself, my other full-time remote colleague, and my other 2 team members who are on-site meet every single working day. We scrum, we go our agile rituals, we pair remotely, etc... We meet with our product people over video conference twice a week. We meet with our managers infrequently but I personally talk to my manager over the phone at least once a week.

> Whatever the details are, scruple's boss should have told me he'll need to make an extra effort to make up for his remote work, and both sides can then decide whether to go ahead with the job.

You're totally off base here.




> I literally said that I transitioned

Sorry for getting that detail wrong. I re-read your original post to make sure I didn't miss anything else.

Since you now say that you agreed ahead of time that you had no obligation to turn up in the office (that information wasn't there in the original post), I now agree with you that your manager was wrong. (This is something I've seen happen over and over again with managers — they say yes without thinking things through.)

If people are deliberately withholding information from you, as you said you suspected in your original post, that's obviously a bad thing.

Regarding my suggestion to have regular meetings, you're already doing it, so that's good.


Speaking as a manager here, what am I supposed to do when a valuable on-site employee approaches me and asks if they can transition to full-time remote?

If I say yes, I get skewered later when people on both sides aren't adapting to the new situation.

If I say no, them I'm a do-nothing windbag who can't feel like anything is getting done unless I can physically see the people typing and clicking.

If remote work is the minority situation, you're going to see challenges. Even if it's the norm, there are decisions that are time-sensitive and you're going to sometimes be dropped (same as if you were on PTO that week; you're just more exposed to it as a remote worker in a predominantly co-located team).

I have teams all around the world; even with that, we still bother to move desks to put squads all together in the same location. If you agree with the latter practice, I think you have to give some nod that co-location matters, even if only a little bit.


Why not do as I suggested above, which is to answer "Can I work remotely?" with "You can do anything you want as long as it doesn't hurt your work."

That way, you're setting clear expectations ahead of time.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: