4 ms·
I think that blaming remote work to mask people/team problems that existed in person is unwise. If your team isn't comfortable being legitimate and honest durin
by alexbanks 6y ago
I think that blaming remote work to mask people/team problems that existed in person is unwise. If your team isn't comfortable being legitimate and honest during requirement analysis, is it worth having? If, in person, the process breaks down into "What the team lead can notice about the team's body language/behavior during requirement analysis", I would probably suggest that there needs to be a fundamental rethinking of the purpose of that meeting. And this is why, I think, the problems being blamed on remote work are usually much larger/harder problems that can get swept under the in person rug.
- MattGaiser 6y agoI don't see it as a fundamental problem with remote work, but remote work requires that many things work a lot better than they on average do. You can try and fix everything from team dynamics and documentation or drag everyone into the office and have the problems kind of be fixed by default. You run into this issue with documentation too. A lot of the "go chat with X" really should be "go read Y on the wiki." But fixing that, especially after long periods of neglect, is a project likely to fail.
- alexbanks 6y agoYeah, I guess the whole point of this whole conversation is that in the pandemic-world, you can't "just" do what you're describing.