Real Ways that Building an Emotionally Supportive, Remote-First Culture Pays Off
February, 2024
February, 2024
4-min read
Summary: Intentional, concrete strategies to bring emotional support, transparent communication, and compassionate leadership to a remote-first company can and do make a big difference in culture and turnover, especially during tough times.
Most of us 40-and-above tech workers are not in the habit of crying at work. It can feel unprofessional, perhaps showing “weakness” in an industry or in leadership roles where few admit self-doubt.Tech rock stars often project a swaggering “ask for forgiveness rather than permission” attitude that leaves no room for emotional vulnerability.
Indeed, ever since the Great Resignation there’s been a push by employers to move in the opposite direction; to “make employees happy” for the sake of productivity, essentially the business’ bottom line. At a deeper level, beyond simply keeping employees “happy” so they stay productive for the company’s sake, it’s been empirically demonstrated that the more supported people feel at work, the less likely they are to be burnt out and leave for other jobs. And apparently, the beneficial effects of this are even greater for remote work.
"Responding first with care rather than accusations led to stronger bonds among team-members and more honest discussion of challenges."
And yet, working remotely can make openness even harder than usual, as many of us experienced during the pandemic. The lack of in-person connection to others takes a toll. Similarly, remote work – and the aforementioned rock star culture - can make emotional vulnerability much harder. And I believe that lack of vulnerability can and does prevent teams from building the strong bonds that help employees feel connected and happy at work.
At Mutations, a remote-first company since its inception in 2016 that I helped to grow as Managing Director of Services & Strategy, our team made the intentional effort to hold space for emotional openness and vulnerability, and it felt more connected than many in-person jobs I’ve had. Crying, for example, wasn’t encouraged at Mutations. But it was supported and accepted, along with expressing other emotions, admitting vulnerability, and sharing personal mental health status. Our company culture was to accept everyone – staff and clients alike – for who they are on a given day.
So how did we create this culture? Here are some of the strategies my team and I employed to build a mutually supportive culture and workplace:
1.Our leadership team (and eventually, other teams) started every meeting by going around the virtual room and asking everyone to express how they’re feeling – both personally and about the business. It’s a meeting kickoff strategy our Exec Director shared with us from Sociocracy, a flexible non-violent practice of management and decision making.
When one member of our team was going through some painful life changes, he’d get to share that with us in general terms. This helped us all frame the context of his contributions in the meeting, and it increased our empathy and patience towards him. We were able to approach tough conversations about his work with compassion and empathy, rather than with anger and blame.
2. Any team interaction or conversation that did not go smoothly (perhaps leaving someone with hard feelings) was debriefed immediately. Someone on the leadership team (usually me or the Exec Director) would grab the involved people the same or next day and sync up to learn from what had happened.
For example, if an engineer shared harsh feedback in a sprint retrospective, such as “this project was managed poorly,” sometimes that feedback was taken personally. After a meeting like this, I would grab the involved parties via Slack and start a conversation to discuss any lingering hard feelings in a smaller group. It didn’t prevent conflict, but it made conflict seem less daunting.
Once the emotionally open culture carried over to client relationships, things really clicked.
3. We built out a culture of help-seeking and collaborative problem-solving on our project teams. One way we did this is by having tech leads and project managers ask developers to never struggle more than an hour with a problem without asking for help.
We built a client marketing site using an atomic design front-end framework, a new concept for some of our devs. To avoid spending many hours ($$$ on time and materials contracts) of unbillable time, we told devs to spend a maximum of one hour as soon as they were “stuck” on a problem. After that one hour, they were to Slack in the project channel to get help before continuing to bill on the project.
4. We always began our team interactions with trust and with the assumption of best intentions.
If and when a developer missed a deadline on a task or deliverable, the project manager would ask: “Is everything okay? Is there anything I can do to help you get your work done or take something off your plate?” Responding first with care rather than accusations led to stronger bonds among team-members and more honest discussion of challenges.
How did these strategies pay off?
Our team felt accepted and happy to come to work. We regularly did anonymous team morale surveys, and scores were high for 95% of the team.
Retention was strong – over 95% YOY – even during and after the pandemic. Especially given the higher salaries that the devs could have been making at Silicon Valley companies, our attrition rate was amazingly low. The team told me they loved our team’s communication, collaboration, and the flexible and supportive atmosphere.
Productivity was high. We hit a 85%-90% utilization rate for all of our devs. This utilization was based on their desired utilization, not based on the expectation of 40 billable hours/week. Which is in itself a strategy to prevent burnout!.
***
Have comments? I'd love to discuss. LinkedIn / Email me at liana at lianaris.com