I'm an employer. Quick background: We're a small Django consultancy/web app development company based in the UK. 7 people, all remote, split as three developers, one frontend dev, one designer, one sales, one administrator. I'm a developer/managing director. Our experience with remote working has been largely very positive. - It keeps our overheads very low. I think that when we remove our staff wage bill, our operat…
"- I think it's easy to 'hide' from the team if a developer is having a problem (either with their code, or their motivation). It's easy to coast through an unproductive day and there is often a delay in the other team members realising that a project is falling behind schedule." I understand the code part of this problem. I think it's good to have a set estimate on how long the item should take so that as soon as yo…
I believe set estimates are not the best way to approach this problem because how do you estimate it? If you are in new territory then what seems trivial to one person may require some research and extra understanding by another. Also when you set a deadline it becomes more of a target for the individual action and instills a time wasting mentality.
It's especially difficult when a new employer enters the company as they feel under pressure that this is the expected deadline. One of the most helpful things Jon has done to elevate this situation when it arises is allow honest conversations without any fear which come from I guess a personal understanding/experience.
I also don't believe this problem is specific to remote working, it's simply a managerial problem within the industry as I am willing to openly admit this (having a problem and not speaking up) also happened at my previous job but the openness didn't exist hence a lot of dodging and ducking was performed until the task at hand was accomplished.