We Don’t Simply Get Remote Jobs, We Join Remote Teams

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by ptero on Friday September 16, 2016 @06:04AM (#12512922)

I think RW supporting teams that do RW well (including both managers who know how to run it and techies) outperform local ones. However, RW makes it easier for slackers to slack off; it is difficult for less effective managers to detect, let alone handle it.

I think managing RW teams well (getting needed work and shielding members from most non-tech crap) is a pretty rare skill.

In any case, if you want to do X (work remotely) and your management sees this as a problem, not a solution, consider looking elsewhere.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by walljm on Friday September 16, 2016 @09:18AM (#12513739)

> However, RW makes it easier for slackers to slack off; it is difficult for less effective managers to detect, let alone handle it.

This is, I think, because most management techniques don't rely on any sort of objective measurement to determine effectiveness.

Using measurements can have its own dangers if done poorly, but subjective observations and feelings about how productive or effective a team or individual is can be even more dangerous.

I've been on the receiving end of subjective judgements that have ruined a good team.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by tbrownaw on Friday September 16, 2016 @09:41AM (#12513878)

There mostly isn't any sort of objective measurement of effectiveness (if there was, everyone would use it).

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by chrishynes on Friday September 16, 2016 @10:06AM (#12514067)

You can't go based on something purely objective like lines of code, but a good code review will tell you if someone is working or slacking.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by tbrownaw on Friday September 16, 2016 @10:34AM (#12514270)

And when I spend the day planning ahead, or helping other team members research things, or bug hunting, or...?

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by chrishynes on Friday September 16, 2016 @01:17PM (#12515574)

Those things should also produce artifacts that can be reviewed by someone knowledgeable in tech.

Besides, it's not a day by day review, it should be week or month. If you haven't produced any artifacts in a week or a month then...

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by marcosdumay on Friday September 16, 2016 @11:13AM (#12514544)

Well, you really shouldn't measure any kind of human productivity on a daily scale.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by ozim on Friday September 16, 2016 @12:07PM (#12514986)

Yeah, I spent last week clarifying stuff with business analyst and QA person. Cleaning up delivery with small changes. When my team mate wrote quite a lot of code that need bunch of fixes. How to measure productivity.

[ Parent | on HN ]

Re:We Don’t Simply Get Remote Jobs, We Join Remote Teams by r2dnb on Friday September 16, 2016 @06:18AM (#12512962)

>I think managing RW teams well (getting needed work and shielding members from most non-tech crap) is a pretty rare skill.

I can't agree more, here's an article elaborating on the topic :

http://read.reddy.today/read/3/remote-teams-are-the-future-b...

[ Parent | on HN ]