Tag: Podcast

Many tools on the market can help remote and distributed teams channel their creativity. But instead of forcing teams to use a small set of company-sanctioned tools for the team’s unique problems, it’s helpful (and empowering) to give employees the freedom to use the tools and processes that work best for them.  

In the seventh episode of the “Remotely Possible” podcast, I spoke with Sabeen Malik, Vice President of Global Government Affairs and Public Policy at Rapid7, to discuss building trust and enabling innovation on distributed teams. Here’s an excerpt from our conversation, including the three elements of trust and how to strike the right balance of synchronous and asynchronous communication when problem-solving.

Introducing Sabeen and Her Remote Cybersecurity Team

Rapid7 is a cybersecurity provider with solutions spanning detection and response, vulnerability management, and application security. Sabeen is building her team and currently works with five people in the U.S. and U.K. She is used to working with remote-first teams, partly due to her previous role at Thumbtack.

“Thumbtack very much is built around this idea [of] remote first,” she said. “Even pre-pandemic, the idea was to think about this model and how are we going to think about remote-first work in an environment where so many more tools were available for folks to work not only across time zones, but across different operational capacities, and what does that look like to bring that all together.”

Why Trust is Essential for a Healthy Distributed Team Culture

Sabeen recognizes that many teams use video calls to tackle challenges. She encourages companies to establish clear rules and expectations about when cameras can be on or off as a way to help employees process information in their preferred mode.

“I personally don’t feel like I need to see everybody when I’m doing what I need to do, which a lot of times is discussing concepts and information and deliverables,“ she said. “At the same time, I have found there is a little bit of a difference between consistently building trust in teams and having video on and off and everyone understanding what the rules are as to why someone may turn their video off and what the norms are around that.”

Trust is vital for enabling an effective distributed team that achieves the innate advantages of remote work. Sabeen encourages leaders to consider what trust means to them and their organization.

“It’s important to think about ‘what is trust at the end of the day?’ and ‘what are we actually looking for?’,” she said. “Thinking about how do you continue to use the tools and yourself, in terms of your ideas, to build it.” 

Sabeen shared her own perspectives on the three critical elements of trust. “I think about three elements: competency, integrity, and goodwill. For a team that has a lot of external stakeholders, trust is built by meeting them where they build trust. Internally, it’s more about how do you share with your teams the ideas around each one of those as a norm-setting behavior.”

Over the course of our conversation, Sabeen rejected the notion that in-person teams are more collaborative or innovative because of serendipitous encounters.

“[The idea] that you’re just sitting randomly and someone comes into a booth or someone stops by your workstation, and you have this amazing idea… I think that’s a little bit lionized or this mental model that I’m not sure most folks are operating that way,” she explained. “I think it has to be a little more structured than assuming it’s going to happen just because you all happen to be in the same space, and it’ll randomly happen.” 

When facing a challenge, Sabeen says that leaders should assess if they are explaining the problem well enough or if people need a change in time and space to let creativity flow. Innovation often comes down to allowing people time to think through challenges and work with their preferred tools.

“One of the things I’m doing more is asking folks the best ways that they think about creative ideas and how do they capture those,” she said. “If you’re at the early stages of a problem or a strategy, I tend to find that synchronous work tends to work better. What you’re truly trying to do is collect ideas and then shape ideas so everyone understands the end goal of executing on something. And then in terms of how and why and what the things are that are related to the execution, asynchronous tends to work a lot better.”

For more of Sabeen’s insights into building trust on remote teams, including a more detailed explanation of the three elements of trust and the tools her team uses, listen to the Remotely Possible Podcast, Episode 7. Interested in sharing your distributed work experience with our listeners? Apply to be my guest for a future episode.

There are undeniable advantages of working with a global team that can keep your company running at all hours. But juggling time zones can quickly become a headache—or a significant source of burnout—without a flexible plan.

In the fourth episode of the “Remotely Possible” podcast, I spoke with Zach Rattner, Co-Founder & Chief Technology Officer at Yembo, to discuss how his global team keeps projects moving seamlessly without forcing a structure that frustrates them. Here’s an excerpt from our conversation, including how he builds connections with his remote team and the importance of asking for feedback.  

Introducing Zach and His Fully Remote Team

Yembo is a computer vision company providing estimation services for home services brands (primarily moving and property insurance companies). Its team of approximately 70 people is fully remote, spanning India, the Philippines, Ukraine, and the U.S. 

“If we’re starting a new product, it’s always an inconvenient time for somebody. We’ve had to put together processes and workflows so that people are able to be productive and make meaningful progress when it’s not business hours somewhere else,” Zach said. “I feel like the benefits way outweigh the cons and that you can make 24-hour progress without burning anybody out because everyone’s working an eight-hour day.”

Zach and his team have developed a strategy that empowers each department to decide how they work, focusing on flexibility.

“You should strive for harmony, not homogeneity. Things don’t have to be identical across different teams, but everyone needs to get along,” he said. “One-size-fits-all solutions compromise something in a way that leave things to be desired. Letting each department head figure out what their team needs to do has been a bit more impactful for us. [We’re] able to be flexible and nimble and adapting to the needs of folks on the team, as opposed to trying to impose a top-down organizational structure that makes nobody happy at the end of the day.” 

How To Build Connections And Stay Efficient When Working Remotely

Savvy remote work leaders understand that teams must come together occasionally for some work or at least to get to know each other. And there needs to be a budget for this.

“Shared experiences are what drive a team to gel. If you are remote and not careful about this, you don’t have shared experiences; everybody is a Slack interruption in your day, a little red blip that can show up in the corner,” Zach said. “We aim to go out of our way to make opportunities so that people can get to know each other, get to know each other’s strengths.”

Yembo hosts an annual company retreat, YemboCon, and quarterly executive offsites. If teams are facing a particular problem that’s easier to solve in-person, there is a process to request an offsite. The key, however, is that Zach prioritizes free time during all company offsites.

“The unstructured time is actually super productive,” he said. “You have a unique opportunity when you’re a remote company and you bring everyone together, so I’ve been focusing less on trying to pack the schedule with all these productive outcomes—work meetings and things like that. Leaving enough room in the schedule so people don’t feel overwhelmed. And not just making that OK, but encouraged.”

During day-to-day operations, Zach’s leadership team prioritizes clear communication across teams, ensuring everyone understands what they need to do when they first sign on for the day. Part of this involves using the right tools to assign work and communicate updates, and Zach shares his tech stack in the recording. 

“If someone’s on vacation, they shouldn’t have to go read 100 messages and scroll back to figure out what went on,” he said. “The end result should be somewhere that they can pick it up.” 

At the end of project planning meetings, to foster an environment of continuous improvement, Zach surveys his team to understand if they gained value from the meeting, asking:

• Did you get what you needed out of it? 
• Was it helpful? 
• What would we have done better?

For more of Zach’s insights into running an effective remote team, listen to the Remotely Possible Podcast, episode 4. You can also read his book Grow Up Fast: Lessons From An AI Startup to learn more about the challenges his team has overcome.

Interested in sharing your distributed work experience with our listeners? Apply to be my guest for a future episode.