Episode 30: The Magic of Meetups

On this episode of Distributed, we dig into the good, the bad, and the karaoke-filled history of Automattic meetups. Before the COVID-19 pandemic, our annual Grand Meetup brought the entire company together for a week. The time spent together — along with team-specific meetups scattered throughout the year — helped us strengthen relationships with our colleagues located around the world. Now, as companies and workers grapple with returning to the office, it’s a perfect chance to consider in-person time as an important complement to the autonomy and flexibility of distributed work.

We spoke with Automatticians about how to stay connected in a distributed work culture. You’ll hear from Toni Schneider, Automattic’s first CEO, Josepha Haden Chomphosy, Executive Director of the WordPress Project, and Nick Gernert, CEO of WordPress VIP, along with a wide range of Automatticians.

The full episode transcript is below and has been lightly edited for clarity.

More

Episode 29: Dylan Field, Figma Co-founder, Talks Design, Digital Economy, and Remote Culture with Host Connie Yang

Subscribe to Distributed at Pocket Casts, Apple Podcasts, Spotify, RSS, or wherever you like to listen.

Nearly ten years ago, Dylan Field and Evan Wallace turned a Thiel Fellowship into a solution to the ‘single source of truth’ problem for design systems. 

Their interest in design collaboration and WebGL laid the foundation for the origin story of Figma, today’s ubiquitous browser-based design tool — and rapidly-growing company.

“The more (we) pulled this thread, the more we learned there’s so much to do in terms of making design better, and in making it so more people can access design within the organization,” says Dylan of their early pursuis. (Spoiler: drone technology was a runner up in their technology explorations).  

The latest episode of the Distributed podcast pairs Dylan, Figma’s CEO and Co-founder, and guest host Connie Yang, Head of Payments Design at Stripe, with past design leadership posts at Coinbase and Facebook.  

Connie’s passion — uncovering the bits of magic surrounding us in everyday life — guides their friendly dialogue from design to remote culture and much more. Early in the show, Dylan shares what he’s learned about instilling culture in a rapidly-growing company, especially amid the changes brought on by the pandemic. “The main thing that changes once you go from in-person to remote is you can no longer rely on physical context to instill culture,” says Dylan. “It matters even more to elevate the role of design, and elevate anything you think is really important in that digital context.”

Dylan also builds on a recurring Distributed podcast theme over the past year, adding “It’s really important to be intentional about creating serendipitous moments.” Figma’s playful approach to collaboration influenced its recently-launched FigJam, a digital whiteboard that can help fill the need for serendipity.  

Dylan speaks with the unique authority of a tech leader who has not only prioritized design but, with his team and products, greatly influenced it in a way that seems to have happened just in time for distributed collaboration. 

“We’ve gone from a physical economy to a digital economy. I don’t think these are new trends or new things that happen but now, all of a sudden it happened all at once, and accelerated massively,” he says, echoing Matt’s May 2020 post Gradually, Then Suddenly

“I think that we’re seeing every part of the economy shape around design,” says Dylan, noting how Figma has even observed collaboration in the product, beyond design, on days when other workplace chat tools were down.

Why does it matter? Because now, Dylan says, “Design leads to winning.” 

Thank you to both of our guests for this latest episode of Distributed. We hope you enjoy it.

The full episode transcript is below.

More

Distributed FAQ: How Did P2 Become Automattic’s Signature Mode of Communication?

In Distributed FAQ, Matt Mullenweg addresses some of the most common issues companies, executives, and individuals face as they consider transitioning to a distributed model.


Q. Automattic is known for using internal blogs called P2s for most work-related conversations. How and why did that happen?

A. In Automattic’s early days, we collaborated a lot directly in the code, or on IRC (Internet Relay Chat), a Slack precursor. We quickly realized that it wasn’t great for asynchronous discussions, and when we tried email instead, it didn’t allow for the transparency that is the hallmark of open source (it also brought a lot of noise with it). Finally, we ditched email and moved to an internal blogging system. P2 is the evolution of the blog for the purpose of working within and across teams. It’s organized much like a Yammer or Facebook stream, but on the back end it still operates like a blog, allowing for archiving, advanced search, and rich media embeds. 

More

Distributed FAQ: How Does Crisis Management Work in a Remote Context?

In Distributed FAQ, Matt Mullenweg addresses some of the most common issues companies, executives, and individuals face as they consider transitioning to a distributed model.


Q. How do you tackle crises and tough situations in a remote setting, when it’s impossible to gather all the relevant parties in one room?

A. The number-one priority is communication. Communicating often and transparently is key. At Automattic, we have a company-wide Slack #announcements channel that will link to a P2 blog post for additional context. We advocate for a framework of radical candor. 

We’re a distributed company, but we deal with the same challenges as other companies, including security breaches, hacks, downtime, fraud, and employee issues. I believe that conversations that happen in written form can be very helpful — they’re archived, so we can refer back to them, and they facilitate learning. One person can share a written summary with their interlocutor so they come to a shared understanding.

While working distributed, you can de-escalate yourself easily. You can take a break. A micro-habit you may want to introduce is to take a mindful minute and breathe.

And one final guideline we’ve adopted over the years, after seeing it defuse tough, challenging moments: assume positive intent (lovingly dubbed API) in all communications. Take the extra moment to consider how you might have misinterpreted a colleague’s words, or how they may have misread yours.


For more on communication and chaos, listen to Matt’s conversation with Automattic’s Sonal Gupta.

On the Psychology of Remote Meetings

Anyone who’s spent a few minutes on Zoom (by now, who hasn’t?) must have intuitively grasped that remote meetings via videoconferencing come with distinct textures and dynamics compared to in-person conversations. But what is it that underpins these differences? Over at Google’s The Keyword blog, UX Researcher Zachary Yorke explores the scientific explanations for the way our face-to-face communication changes as soon as it switches from colocated to distributed.

Even minuscule details, like milliseconds in audio lag, can make a Zoom call feel radically different from a hallway chat:

When the sound from someone’s mouth doesn’t reach your ears until a half second later, you notice. That’s because we’re ingrained to avoid talking at the same time while minimizing silence between turns. A delay of five-tenths of a second (500 ms)—whether from laggy audio or fumbling for the unmute button—is more than double what we’re used to in-person. These delays mess with the fundamental turn-taking mechanics of our conversations. 

Read the rest of the post at The Keyword

Photo via Pexels

Written Communication Tip: Assume Positive Intent

It’s not news that 90% of communication is non-verbal, and that nuance and subtlety are lost over written messages. Be conscious of this.

With lots of our communication now written (when previously you might’ve popped over to someone’s desk) it’s good to head off the risks of such interaction with a wise interpretive principle through which to view your exchanges: Assume Positive Intent. 

The Memrise team

In a recent Zoom chat, Matt Mullenweg shared work-from-home advice with the team at Memrise. They’ve compiled Matt’s 10 top tips, including advice for teams who are likely communicating much more in written form than they’re used to. Read and listen to more best practices on the Memrise blog.

7 Remote Work Lessons for Managers During the Coronavirus

During this time of tremendous change, here is some timeless advice from leaders who have worked with their own distributed teams. For more, check out their individual Distributed podcast interviews.

1. Make time and space to listen

“As a manager, the best thing you can do is train yourself to hold space for yourself so you are not having a million things that you need to unload onto your employee, to keep making more room, to keep letting more things bubble up that can be resolved. Keep it with open-ended questions and to let advice maybe only come in at the very end.”

Leo Widrich, cofounder of Buffer 

2. Trust each other

“At distributed companies, you can’t tell really if someone doesn’t show up to work. I mean, you can eventually tell, but it’s much easier to disappear. The level of trust required is much higher. And so there is a portion of the [hiring] process that is earning that trust. We really believe that people can be successful and we’re looking to make people successful. There is no ‘prove it again’ after you get hired. I think that’s really important.”

Cate Huston, Automattic

3. Know your role as a manager

“I think part of my role is to explain why things aren’t impossible. And I see increasingly with a lot of projects we have done, the first response is, ‘That’s just impossible.’ …  I am happy when people say that. When I’m not happy is when people say, ‘Oh sure, we’ll do it,’ when I plainly know there is no way they can do it, it’s too hard. And so then I’m trying to figure out, ‘OK, so let’s see whether we can figure out how to do it.’”

Stephen Wolfram

4. Give yourself the structure you need

“When I got here, everyone was like, ‘It’s great because you can work in your pajamas if you want to.’ And for the first six months I did. I didn’t have a dedicated office area and I just sort of got up and started working whenever I felt like it, and finished working whenever I felt like it. And I found that that was not a good choice for me, especially in the work that I have to do. It ended up making me less resilient, more reactive, and also I had no concept of when work started and stopped.” 

Josepha Haden, Automattic  

5. Blog your experience 

“My wife will always say, ‘You’re staring off into space like you’re writing something.’ She just knows that it’s this thing where I’m collecting my thoughts….I think better and organize my thoughts better and share my ideas better when I write it, and it introduces a rigor to what I’m sharing. I love that push to accuracy and push to quality. It makes my thinking stronger.”

Anil Dash, Glitch

6. Rethink your meetings

“If you’ve taken three days to think about something and you say it in a meeting and people start just throwing stuff right back at you — in some ways you’re asking them to because you’re sitting at a table, what else are they going to do? But it seems unfair to them, in fact, for them to have to react to this thing that you have thought about for three days or three weeks or three months, for them to have 30 seconds to say something back seems unfair.”

Jason Fried, Basecamp

7. Consider what questions you’re asking

“An effective manager in a distributed work environment needs to develop the skill of asking precise and information-gathering questions to elicit this kind of information. Because even if the employee might not be able to produce this information on their own, or might know it but not necessarily know how to communicate it in a way that would be applicable and useful in a work environment.”
Lydia X. Z. Brown

For more insights, subscribe to Distributed on Apple Podcasts, Spotify, or wherever you like to listen.

Photo by Alexas Fotos / Pexels

Welcome to the Chaos

“Welcome to the Chaos.”

These are the words every new hire at Automattic sees on their first day, emblazoned across the company’s online handbook. They are designed not to instill fear, but to prepare the newly-minted Automattician for life in a fast-moving, globally-distributed company. Working at Automattic sometimes feels like chaos, but over 950 employees wouldn’t have it any other way.

Sonal Gupta is one of them. She describes the moment she first read those words. They gave her immediate comfort because they confirmed that yes, working in this environment can feel overwhelming, but she wasn’t alone. 

More