5 ms·
Or… Just have optional office hours, Slack huddles and mob sessions every few days. Some of my engineers… - have a open huddle for a few hours a day where an
by jollofricepeas 3y ago
Or…
Just have optional office hours, Slack huddles and mob sessions every few days.
Some of my engineers…
- have a open huddle for a few hours a day where anyone can drop into their project while they work
- others make use of our scheduled themed mob sessions (ie. Maintenance Mondays, deployment Thursdays). have a problem, idea or just want to hangout then come by?
- ICs & seniors are required to host at least a weekly office hour to assist juniors or teach something of their choice.
The default doesn’t always have to be return to office for a physical meet.
There’s lots of other options.
- ramraj07 3y agoThere is absolutely something that gets lost in virtual meets. It’s not just for within team discussions. It’s also about discovering colleagues in other teams across the org. Tools like Donut help a bit but the magic is still lost.
- ahnberg 3y agoI think the biggest issue is people who claim it can't be done and that the only way to accomplish this is to physically meet. I feel like the biggest hinderance to making the most out of a remote option are the ones who prefer going to the office or explain all kinds of issues with "it's because we don't meet in person". One just have to embrace and apply the mindset that it is possible. Different, surely, but still possible! I'm not saying there is something WRONG with going to the office, it is lovely to hang out in person with lots of people, but it is very limiting in many ways as well. Just limiting in other ways than remote. You learn to deal with both, when you need to, though. The issue is mostly that people deal with the office-problems but don't care much about dealing with the remote-problems.
- jxramos 3y agothat's an interesting angle, I wonder if this pattern of defaulting to "because we don't meet in person" is that a giveaway for some lacking of communicating in writing I wonder. Just people who can't get an idea out effectively in textual form for complex ideas on a repeated basis and chalking it up to needing that in person outlet. That's curious, does being face to face elicit other modes of communication and ability to articulate and connect things. Maybe. But I suppose it could also be an opportunity to lean on the "see what I mean", "do you know what I'm saying" and allow body language and other social lubricant type bits and pieces to smooth glossing over when another doesn't follow or see what they mean.
- lostcolony 3y agoIt always struck me as strange that corporations rely on chance for people to connect and understand what other parts of the org are doing, to find synergies* and suchlike. That feels like something that absolutely can and should be operationalized* if the success of the company relies on it. Build in easy ways for people to join other teams for a quarter (or whatever), ensure that areas of effort are communicated horizontally and back down in minimally invasive, synchronous manners, have clear domain ownership such that it's easy to know who to reach out to, etc. It's absolutely bizarre to me to pin success on "employees chatting by the water cooler" or whatever the expectation by upper leadership is when they claim stuff around in person. Don't get me wrong, I like seeing coworkers in person now and again, but I explicitly want to do it just to meet them for socializing and team building; not working. *(buzzword) Bingo!
- jxramos 3y agolol, those mythical magic moments collaborating in the abstract, you never know where they're going to happen. It could be at the water cooler, or over that off color patch of carpet over there.
- lostcolony 3y agoHonestly, most of my work experience has been those mythical magic moments just led to a decrease in morale. As a remote worker I am not as invested in the company, and that's a feature, not a bug. I'm doing my job, I'm actively looking to do it well, but frustrations I can't control feel further from me. I remember distinctly overhearing our internal devops at one place (that was pretty fragmented) talk about how their mandate was to get people only 80% of the way there, that the teams were responsible for getting 100%, and it pissed me off no end, since one of the reasons my department was doing our own devops was that there was no way to take what the devops department was putting out, and leverage it to get to what we wanted (i.e., no path to go from the 80% they provided -> 100% of what we needed). We had tried numerous times to talk to them about it, but they wanted to decide things in isolation and tell us what to do, rather than listening to us. I tried figuring out who was in charge of that group and reaching out to them, and managed a meeting, and they heard and acknowledged the need and agreed change was necessary, then nothing happened with it. Etc. None of that helped my morale, and I ended up leaving that company, not because of that, but because of a number of places where I simply could not affect change. As a remote employee though? Don't care. As I said, that missing cultural buy in is a feature, not a bug, and it benefits everyone involved. I'm still raising concerns, still trying to reach out for solutions, but invariably when the business prevents me from fixing things I'm not stressing, and am so less likely to leave.
- oofta-boofta 3y ago> Tools like Donut help a bit but the magic is still lost. You can keep your magic, I'm gonna stay in my home office.