> There is almost always value in seeing what happens right before the problem, and I almost always have questions I want to ask them about it, and it's so much

> There is almost always value in seeing what happens right before the problem, and I almost always have questions I want to ask them about it, and it's so much faster just to do it with screensharing and voice. This is a pretty good counterpoint to my site! I think that for some, voice is just the preferred medium of communication and that should also be taken into account when possible. Of course, I'd argue that a little bit of context of what the problem is related to could still be helpful, not to have to waste a bunch of time trying to find some Jira ticket that had some relevant info from like 2 weeks back during the call. For others, text will probably reign supreme, though I also enjoy things like huddles that Slack introduced, to make informal "meetings" a bit more organic: https://slack.com/help/articles/4402059015315-Use-huddles-in-Slack https://slack.com/help/articles/4402059015315-Use-huddles-in...