The Remote Pop-In (2021)
twos.dev
twos.dev
Regardless how crappy Teams is at certain things, the people that decide "we're using Teams" often barely use it themselves.
Teams itself has some limitations that are easy to improve upon. They have no way of doing a huddle/pop-in-style room. They screw up the presence signaling in a way that discourages pop-ins: if you join a call with someone your and the other participants' status is set to busy/unavailable. From other peoples' perspective this isn't very inviting, and doesn't indicate that the conversation is public. Teams also limits who can share screens to only 1 person at a time.
Just schedule a regular meeting, and attend it - then advertise widely that you are available at that time and that anyone is welcome.
It's a great way to foster skip-level interactions, give help to someone who needs it, and just chat. It's really fun when a few people come in at once. Sometimes nobody shows up, and that's fine, too.
Give it a try!
Maker's schedule and all that. http://paulgraham.com/makersschedule.html
I personally do not have fun in these kinds of meetings. Even if they were held in person. My goal at the end of the day is to finish my work quickly and efficiently and try to get out a little early while meeting my obligations. Typically these chats eat up an hour or more and I end up working longer to make up for it.
They are extremely useful for helping newer engineers and answering questions but the "fun" chats tend to be just time consuming noise. It's entirely possible I have a different/maligned view of my relationship with my job but I just don't like giving any more than I have to for something that consumes 40-60 hours a week of my life.
Interesting, I would never have expected anyone to feel the need of recreating this particular piece of office life in a remote setting.
That being said this suggestion is hilarious. I would imagine people are auto-muted in the restroom channel so it seems like the ideal place to sit yourself if you're required in zoom all day. It's totally valid. I often get my best thinking done in the bathroom.
There’s also a physical warmth you get when being near someone. Being physically close to a fellow primate who is part of your clan and who you trust not to kill you must trigger something that video calls do not.
I have no training at all in any of this and this could be complete pseudish nonsense. I would be interested to read more informed opinions about this sort of thing.
I agree with you, having a common 'thing' to focus on together is great. I absolutely HATE video calls as well, but I can sit in a discord call for hours if there is something to focus on. Playing a game with someone, or people watching a video together, etc.
Which is why it's really sad that Discord doesn't scale for enterprise usage. No enterprise SSO, no way to search through or organize an ever-growing list of voice channels with an ever-growing number of people in them, no way to force the employees you invite to use their real names as their usernames so user management becomes difficult. We would have easily made the decision to throw Discord $10+/user/month if they would have decided to address the enterprise market. Shame.
I personally don't like all the "fun" calls extroverts seem to want to have all the time. But for short huddles I've often gotten unblocked 10x quicker by simply seeing if someone had 5 minutes to talk through something 1-on-1. Then I have their undivided attention and I don't have to wait for them to get around to me on Slack or email which understandably take a back seat.
Both this assumption and the gp's assumption are just that: assumptions. It's fascinating how a few years of half-hearted attempts with status quo management all too eager to revert to at-location is used as a way to support this.
It's still way too early to make such a bold statement.
It's everyone. Not 'especially' programmers. Everyone. Flip the tables and expect the other side to adapt to the context instead, and we'd be calling management terrible at communication. Software development seems fairly unique in expecting developers to bridge the gap instead of management, when such expectations are not put on several other fields. Regardless of the mental strain put on those professions.
Heck, it's stunning we have so many customer-facing type jobs in software development only to expect developers to adapt. The heck you getting paid for if you're not actually a mediator between two different contexts like, you know, almost every other field?
Now most meetings are bad, I’ll give you that. But a well-run meeting, with purpose, which doesn’t faff on and respects the participants’ time, is still a very effective way to get something done.
It is a fallacy that every meeting can be replaced with email. I hate email more than I hate even a mediocre meeting.
I view meetings as next to worthless as nothing is retained as nobody writes anything down (and I am not willing to pay attention enough to do it as a rank and file dev who won't be blamed for it).
Because a lot of people have a pathological need for social interaction. In my opinion this is extremely unhealthy, a person should not be dependent on other humans to be comfortable and happy, but society sees it as normal and even desirable.
Human interaction is fundamental to being a human, and people should be expected to desire it regularly.
I do, however, agree people shouldn't be dependent on their office for that. I have no desire to make friends with coworkers, unless it just happens to occur organically because we like each other.
It's a weakness that needs to be fixed, not something that should be encouraged.
My suspicion is a non trivial amount of introverted staff will just never have an “open door” so to speak, but then you miss out on valuable interactions for the broader organization or team even if locally for the person they’re uncomfortable or annoying.
Anyone can call anyone during office hours for any reason they would classically pop in.
Anyone receiving such a call is entitled to ignore it.
This has an additional advantage over the physical office: by declining the call you don’t get cognitively interrupted. With the popin the person starts talking about accounts API and the context switch has been forced on you.
Unless you dispense with politeness in the physical office, but that is a lot harder to do. Maybe impossible without some team building role play training.
The pop-in paradigm seems principally a matter of synchronisation/rendezvous.
Someone is "available" because they are "holding you in mind" but still receptive to engage or not engage without consequence. Fancy high-bandwidth tools, including smartphones and web-video don't solve it because they create a commitment of presence. In response/defence people erect barriers, away messages, out-of-office notes etc, working hours get out of sync and asynchronous exchanges fall apart.
IRC seems to find the best balance that approximates between a digital water-cooler where you can turn up and see who is up for a chat, and a notice board where you can leave a message "I called in, chat with me when you have time".
I think the Discord setup mentioned in the OP feels like a “place” because when you’re joined to one room, you’re crucially not in any of the others. You can do this with IRC but it’s not very natural. Honestly, I think the place where that interaction style would feel most natural is in a MUD.
At my last 3 jobs - it was common to slack or IRC "Got time for a zoom?" and on yes, type '/slack meeting talk.'
remote pop-ins happen all the time.
I would have no problem having an open channel on discord for example for the team to pop in and out but doing so forces my Bluetooth headphones into 'microphone' profile and dramatically lowers the audio quality.
Give me an option that allows me to have my music playing on full quality or an audiobook etc, then id happily leave a call open and muted.
I’m hoping that Bluetooth 5.2 and BLE audio fix this issue. It’s hard to find info on how the updated headset profile works in terms of bandwidth and latency of input and output.
I've been building a 3D visual collaboration platform that has some fairly obvious value in how you externalise/connect/recollect thoughts, but I'm really keen to explore if it can become a workplace where pop-ins and serendipitous social collisions come easily. For that to happen it needs to become something you can spend large chunk of your workday inside of, which is no easy task.
"When you are online and able to be disturbed, you join your office, alone."
In the office scenario, I as the interruptor take on the burden of finding out when someone is open to being interrupted (and it's not that hard). For example I can just say "I'll ask him the next time I see him" and wait until I see him go to the coffee machine or the bathroom. Or, if it's more urgent, I can take a peek in his office and see if he seems to be engrossed in thought or more relaxed.
Particularly, we had our morning standup using the URL and when we stayed around working together on something. Other people in the company would just be able to pop in and talk to use. It was super nice!
I did see two issues with this, though:
- Bluetooth headphones have worse audio when mic is on.
- I felt it used some cognitive overhead being in a video call.
I was shocked when I found out this was the case in 2020. Surely this would be a solved thing! So annoying especially for this exact use case.
Ok, I realize there's a context for it. Still can't help, but laugh at how low is a "high" mark for physical effort when in office.
There is one equivalent, and everyone is going to hate me suggesting it: call me. Pick up the phone and call me.
Yeah, Gen Zers, I said it. Use your telephone to send me an alert that says you want to speak to me with your voice. If I have time to chat, I'll answer. If not, leave me a store-and-forward recorded offline message, aka voicemail. If I have time I'll listen to it and call you back.
This is inferior to the pop-in for the interrupter, but superior for the interruptee. It gives us back control of whether we are interrupted (put your phone on silent if you really need to), it is universal and ubiquitous.
Obviously, because of phone spam, this doesn't work with normal telephones (unless you add all your coworkers to your contacts). But Slack/MS Teams/Discord/VoIP/etc can solve that for us. Just tell everyone in your office to call you, and leave a message if you're not there and you will get back to them as soon as you can. Put "Call Me" as your away message. Voice calls worked well enough for nearly a century as a remote working method; I think we can learn to do it again.
If you get one call a day, it’s fine.
Getting one slack message a day is also fine.
Getting 50 a day makes it impossible, because unless the messages are transcribed, you have to listen to each one to decide if you want to return the call.
…and if they are transcribed, well… now you’re using slack.
There’s definitely something to be said for a call that you can’t do over chat (for whatever reason; some people just don’t “text” they only talk).
…but, calling arbitrarily when you want something flat out doesn’t work.
Personal experience: people call for trivial reasons, you don’t answer and they don’t leave a message.
3 missed calls from your boss, no message left.
Just leave it because they didn’t leave a message? Probably not.
…but, the reality is, most people cbf leaving a message saying what they wanted. They want to talk now, or not at all. …and, I don’t think it’s ok to just ignore your missed calls.
So then the pressure is on you to track down each of those people and see what they wanted.
It’s a nightmare. (My solution: choose a different place to work. /shrug. Can’t change the culture in some places)
I don't see how either of those are true for phone calls.
1. It's ideal for the interrupter: they get to decide when they want your time. They want it now.
2. It's annoying for the interruptee, because you only have two options. Either you can pick up the phone now and force a hard context switch away what you were doing, or you can reject the call and spend more time later listening through voicemails. And unless you have voicemail transcriptions, you're at the complete mercy of the interrupter again.
Compare that to asynchronous text-based communication, where the interrupter can't forcefully take your time from you. They can only message you, and you can decide when to read it. Reading the message doesn't cede control of your time to them, and you can adjust the actual time of the call to accommodate whatever you're working on.
As a millennial I suppose I fall in between the two camps. When I was younger, social anxiety about taking up people’s valuable time with my silly questions made a phone call seem like a terrible burden to subject someone to, but with age and (remote work) experience, I’ve realised that conversations are indeed much higher bandwidth and often appreciated more than a letter or thread of back-and-forth clarifications. If I _had_ to stereotype by generation (sorry GP) I could say voice and video seem easier than reading and writing for boomers and Gen-Zs, but even that doesn’t sound right. It’s probably just a communication style thing. There’s a reason many of us struggle to read a book when we can watch some TV instead. As humans we communicate with our voice, face, and body. The main benefit of text is asynchronicity. The challenge is how to thread the needle of asynchronicity in an increasingly post-literate world.
Most people don't watch TV to obtain information, yet at the same time, videos can convey information better than a book would thanks to audio and video. Quality audio and video material far surpass books when they augment the original text-only format. Shoddy video material is still preferred over shoddy writing for reasons beyond conveying information.
And that's the real issue. People are using bad writing and asynchronous communication skills as a cop-out to push more, not realizing their other communication skills are just as poor. Sure, the guy waving his warms during a presentation feels more humane, but how much does it really add one week after? You're stuck only with the notes he left, the notes you made (probably none) and your own memory probably muddied along the way. It's the same for meetings or any kind of call. Taking notes takes far longer if you ask the one conveying information to slow down so you can keep up. Most people are awful at communication in any form, and half of the problem comes from them trying to blame the medium or believing they are better using a different medium or it's flat-out the medium's fault. Newsflash: it's probably you, not the medium.
It's most astounding this has to be told to developers of all people. The field moves fast, new information is thrown out at rapid pace, the work is mostly mentally straining and you're expected to know a lot. Surely, that alone would make enough people question whether fast-paced, transient communication is a great fit. Writing is easier to point at people and say "this doesn't make sense" without the answer being another call.
Consider a plot of fidelity vs latency. You want to talk to somebody - high-fidelity back-and-forth communications instantly. It's up in one corner of our plot.
Now consider voicemail. One-way, lots of "um, uh" wasted time, tedious menus to fetch and wade thru it, maybe tomorrow. It's down in the other corner of our plot.
Literally any other form of communication beats that. Text. Email. Hell, send a letter. But you try to leave me a voicemail, you're saying "Here, you type this email".
I never even set up my voicemail.
In my work circle a protocol has naturally established itself. If you call me, I assume you want something. Otherwise you wouldn’t have bothered calling me. So you don’t need to leave a message: I will see your missed call, and I will call you back.
Those quick replies you can send from your phone help. Customise them. I use two:
“Can’t pick up, call you back in 5.”
“I’m in a meeting, call you back as soon as it’s over.”
Hey! I’m working on X and I was wondering if you’d have time today to help me out.
I think I disagree with all the advice in your comment, but this part has me particularly baffled.
It would be nice if Slack had an away message that was sent back to the user when they message you, rather than a status that nobody ever reads.
So you reply to that with a link to https://no-hello.com/ every time, and they eventually catch on.
1. “Why not accomplish this with X?” We arrived at this solution organically, which was important for adoption: a Discord server meant for gaming hour turned into hangout rooms turned into offices. It may not be the best option, but best means nil if you can’t convince people to use it. For us and our existing culture, Discord was an easy and incremental jump to take. Take whatever path makes sense for your culture.
2. “Why not make this asynchronous?” Asynchrony should indeed be the default mode of communication, but synchrony has its uses; between nonverbal communication and round-trip-time it is simply obnoxiously higher bandwidth. It trades away efficiency (person-hours) for speed (hours). The fewer people involved the better the exchange rate, which is why this article focuses on 1:1 interactions. I wrote about this later in my article “Why Be Synchronous?” [1] but tldr; synchrony should be deployed similarly to tech debt.
“Hey, I told you not to call me on this wall. This is an unlisted wall!”