Comments (5)
DevMynd has been doing (1), because we inadvertently did (2) for a while and found it didn't work for us. When I joined, everyone was in Chicago except for me in San Francisco, and I felt very out of touch due to missing out on the in-person conversations. That said, if we had been aware we were doing (2) perhaps we could have done better. :)
We switched to all working at home (or otherwise outside the office) on Wednesday, and it's been great for me because it moves so many more conversations into slack. Now that I've got more people in SF, keeping in touch with Chicago is less of an issue than it used to be...but they're still the home office.
from handbook.
Love that remote work is being discussed here! It's really exciting.
The only problem I see with the team choosing one day a week to WFH is that usually when I want to work from home it's for one of following reasons:
- I have one or several doctor's appointment(s) or some other scheduled obligation that makes working or being productive from home more convenient and/or feasible than going into the office.
- I'm struggling with my physical and/or mental health and going into the office is triggering moderate anxiety and stress, but I'd still really like to get some work done from home.
- I was/am triggered by something where I feel most safe and secure working from home.
Having the team choose a day to WFH means that my personal agency is stripped or rather discounted in the decision making process around working from home, and therefore the perk becomes much, much less desirable for me personally.
When it comes to living and working with mental illness it is important to remember that agency, in this specific situation; having the ability to say "I feel more safe and healthy working from home today" and feeling okay or even good about that decision, can be really empowering.
from handbook.
In the past, I had worked on a team wherein everybody on the team got to choose one day of the week to work remotely. The idea being that two people from the same team wouldn't be out at the same time. (I understand right now there is only one or a couple people on each team, but soon teams may consist of a few or more people each.) Im appreciating Julie's point though, that this eliminates her agency to dynamically decide to work remotely.
I'd like to add however, that I have no problem allowing everybody to create the remote work style/schedule as it fits to their lives. In other words, maybe scheduling a day for me would work, but allowing Julie the flexibility to decide dynamically is the best way.
from handbook.
This is interesting and is probably something we should learn from :)
https://18f.gsa.gov/2015/10/15/best-practices-for-distributed-teams/
from handbook.
This recent article by Martin Fowler also has some great insights into co-located vs remote-first teams and the spectrum of work environments in between:
http://martinfowler.com/articles/remote-or-co-located.html
@jessepollak, you said:
I've had the sense that we should change our policies around remote work ... I'm leaning towards [experimenting with a smaller number of individuals working remotely each day] because I think it better simulates what remote work actually is.
I think more clearly spelling out Clever's remote work goals will help you pick remote work simulations that'll be most helpful for your team. It sound like Clever's goal is to continue hiring co-located employees, but offering (even encouraging) your co-located employees to work remotely for limited stretches of time (e.g. going home early to answer emails, working from home on days when personal appointments make that more convenient, working from home for a stretch of time accommodate physical and/or mental health needs). Conversely, I think it's worth clarifying that your short-term goal is not to begin hiring satellite workers nor is your goal to shift to a remote-first work environment.
P.S. I'm suggesting clarification because as a fully remote employee at a company that works remote-first, simulation (1) is exactly "what remote work actually is" for me
from handbook.
Related Issues (20)
- Close the technical/non-technical divide HOT 8
- Add policies about on-call rotations and compensation
- Rubric for the Interview Process HOT 1
- Referrals HOT 1
- Pay increases and passing the 5-year mark HOT 1
- Cap on vacation accumulation HOT 3
- Matching nonprofit contributions HOT 1
- 83b elections and option expiration.
- Clarify technical interview circumstance and content
- Clarify Clef's involvement in local communities HOT 2
- Expand our Equal Opportunity Employment document
- Consider adding that repeated microagressions will count as harassment HOT 2
- Clarify drugs and alcohol policy
- Clarify Clef's offering of trans-inclusive health care
- Consider explicitly listing diversity & inclusivity goals HOT 4
- Use tags to preserve handbook history HOT 2
- Examples HOT 1
- Create PDF, HTML, MOBI release HOT 1
- Another resource that may be of interest HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from handbook.