|
|
|
|
|
by ergothus
2437 days ago
|
|
> (1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site. I don't get it - shouldn't one-on-ones and regular progress check-ins (be those standups, metrics (This is your #2), whatever) give you that information? None of those are easier when on-site. In fact, given today's move towards open offices, any form of 1:1 collaboration is easier remotely where you don't have to fight for precious meeting room space. I think the core problem is that you're trying to prove "everyone is working" when we should be interested in "the work is getting done". Seeing that everyone is working doesn't actually mean progress is getting made. If you have to take steps to answer that question anyway, the first question is fairly pointless. |
|
Also had managers that were basically invisible but kept a great crap umbrella for us. Loved them too. Ended up working a ton and getting enormous amounts of work done because trust and autonomy are huge.
I think the worst situations are when managers are too insecure to be honest with direct reports. That’s decidedly uncool and super ineffective.
Also, it seems managers get so overloaded that 1 on 1s and stand ups end up being mostly a waste of time because it’s too hard to remember all the little details.
So remote or in office isn’t really the issue. In my view, remote is superior due to productivity, flexibility and happiness, but it does require everyone to do regular video chats and pair programming.
Ironically, the in office folks have the hardest time with this because they feel they need to get up from their desk and find an overly booked conference room as you mentioned.
Simple solutions are context dependent, but could be along the lines of a) work remote if you have the discipline, b) asynchronous slack based standups, c) report status as you go in your tickets, d) every day or two peers and managers sync up 1 on 1 or in person depending on their preference, e) have clear goals as a company and a team, f) have good technical product people writing 1-3 day user story tickets including completed designs if it’s ui work, g) have good tech leads writing 1-3 day technical improvement task tickets, h) vote as a team on contentious technical decisions, then disagree and commit, i) generally chill out a bit and let work be enjoyable.
At least that’s a start...