It’s one of the little things I miss about working in-person with other people.
Writing software can involve so many different tools. Before my current remote working times, one of the ways I picked up on efficient ways to use some of the tools involved was from seeing how coworkers navigated them, especially when they had a lot more practice with them.
A colleague and I would be looking at their screen together, working with a tool that I had an OK understanding of, when they’d use a feature or shortcut I didn’t even know about. It may have been muscle memory to them, but it would be brand new to me.
Wait, how did you just do that?
One of the most staggering things about ramping up at Google was the number of internal tools and systems that were brand new to me. I learned many of them by trying them out and following patterns of how I saw others using them, slowly over time building my familiarity with them until things became second nature. Even after I was comfortable, there would still be power-user techniques that I only picked up on from seeing a coworker do them on their screen.
What button was that again?
I’ve noticed that this discoverability is harder for me since I’ve been working remotely. It still happens as we share screens, record talks, and screenshot pages and buttons for each other, but it has never felt quite as natural. Maybe because there’s some inherent cognitive load to screen sharing, requiring at least a few mental cycles to even just keep up with what someone is doing. Add in any delays, sudden window changes, or small fonts, and it’s even trickier.
Maybe it’s that we often only share a single screen or window, with text blown up so we can all see in our browser windows or Zoom clients. I wonder if having the exact same monitor setup as the other person and having their monitors mirrored on mine would help, since I would have the full context of what they’re doing.
Sorry, do you mind zooming in a bit?
There may also be some natural barrier in my head to looking at a screen together remotely. It’s probably latent Zoom fatigue, but there’s a difference between a text chat back and forth and hopping on a call. Working in-person, it’s likely that a discussion would be us talking about it already, so maybe the jump to “can I come see what error you’re getting?” doesn’t have as much overhead to it.
I’ve actively worked to push against this barrier. When working with more junior engineers or interns, I would force myself to remove it completely for them, jumping straight into chats and debugging without hesitation. For my regular individual contributor work with others, though, I still feel it, and I always try to stay conscious of it.
Want to hop on a quick call?
I think about this discoverability a lot for junior engineers or new team members ramping up. There are so many things to learn, and reducing barriers to sharing that knowledge can only help. As we continue to move forward with widespread remote work, how do we better enable easy and casual collaboration?