惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
L
LINUX DO - 最新话题
P
Proofpoint News Feed
Cyberwarzone
Cyberwarzone
Know Your Adversary
Know Your Adversary
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
L
Lohrmann on Cybersecurity
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Security Latest
Security Latest
T
The Exploit Database - CXSecurity.com
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
P
Privacy & Cybersecurity Law Blog
K
Kaspersky official blog
The Last Watchdog
The Last Watchdog
Webroot Blog
Webroot Blog
Scott Helme
Scott Helme
T
Threat Research - Cisco Blogs
C
Cyber Attacks, Cyber Crime and Cyber Security
WordPress大学
WordPress大学
L
LINUX DO - 热门话题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - Franky
V
Visual Studio Blog
O
OpenAI News
AI
AI
Hacker News: Ask HN
Hacker News: Ask HN
V2EX - 技术
V2EX - 技术
GbyAI
GbyAI
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Simon Willison's Weblog
Simon Willison's Weblog
S
Schneier on Security
Spread Privacy
Spread Privacy
Y
Y Combinator Blog
I
InfoQ
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
Threatpost
C
Cybersecurity and Infrastructure Security Agency CISA
F
Fortinet All Blogs
C
CERT Recently Published Vulnerability Notes
T
The Blog of Author Tim Ferriss
C
Check Point Blog
Apple Machine Learning Research
Apple Machine Learning Research
有赞技术团队
有赞技术团队
人人都是产品经理
人人都是产品经理
N
News and Events Feed by Topic
Project Zero
Project Zero
小众软件
小众软件
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
B
Blog
G
Google Developers Blog

Max Stoiber's Essays

Save polish for where it matters How I get things done How I run gratitude circles How to present to executives Message me whenever How I manage my todos as a CEO How to run recurring virtual meetings efficiently How to have great taste How to be great at storytelling How we make brainstorming work How do you invent the future? Being unreasonably responsive has made my projects more successful Why I'm vigorous about giving feedback How to ship faster How to be better at making decisions How I tend to my digital garden David Cain: Do Quests, Not Goals Deliberate practice beats every other form of training, even via transfer learning Why I don't compliment people for their talent How can you slow down life? (which is perceptually half over by 23) 1:1s are for personal connection, not project updates Developer tools startups are playing on hard mode Developer tools are different than tools for any other profession You probably don't need GraphQL Why I Love Tailwind Margin considered harmful I am joining Gatsby Why I Write CSS in JavaScript Tech Choices I Regret at Spectrum Streaming Server-Side Rendering and Caching
How we foster deeper connections in our remote team
Max Stoiber · 2024-08-14 · via Max Stoiber's Essays

I believe that:

  1. Teams that have deeper personal connections perform better.

  2. Remote teams generally have shallower personal connections.

At Stellate, we knew from the start that we were going to build a remote team.1 So, we asked ourselves: How can we foster deeper connections in our remote team?

Sue Odio and I tried many ideas, and we eventually settled into this rhythm:

Offsites: Every four months

We ended up settling into a rhythm of three company-wide offsites per year (so one every four months), with 1-2 additional team offsites per year on an as-needed basis to work on a specific topic.

This rhythm felt like a good fit:

  1. The few times that we went longer than four months without an offsite, I noticed how much more disconnected we felt the next time

  2. The few times that we went shorter than four months until the next offsite, I thought it felt “unnecessary” as the personal connections were still strong

When teams had specific projects to work on (e.g., onboarding a new manager or figuring out our product process), they would additionally schedule departmental offsites on an as-needed basis. In practice, we never needed more than one of those per year.

Game meetings: Every two weeks

Every two weeks on a Friday, we would get together for our no-work connection meeting. Usually, we would hang out for a bit and then play some virtual games together. Every now and then, team members would also self-organize and play other “actual” games like Minecraft.

Some of our favorite virtual games

These are all the games we played many times in these connection meetings; none require much (if any) instruction and can be played in people’s browsers.

  1. Codenames

  2. Jackbox Games, especially Drawful (although Draw Battle below is equally fun)

  3. Make it Meme

  4. Gartic Phone

  5. Draw Battle

Fun once but not multiple times: Death by AI

Checkin questions: Every day

As a remote company, watercooler conversations are difficult to come by. Sue Odio introduced check-in questions as a standard part of our recurring meetings to get some of that connection energy back.

For the first 10% of the meeting (e.g., 3 mins of a 30-min meeting), we go around the room and everybody answers a random icebreaker question.

Learnings:

  • Personal, yet not too-personal, questions work best.

  • Work-related questions generally don’t work well because they aren’t safe for people to answer.

  • Instead of phrasing questions as extremes (“your favorite,” “the worst,” etc.), phrase them as “one of.”

    • Asking for a single response (“your favorite”) makes the question more difficult to answer, and people tend to go “Phew my favorite hmm I have to think about that…”

    • For example, instead of asking “Who is your favorite sports player?” ask “Who is a sports player that you love?”

Examples:

  • Great (a bit more personal): “Which of your teachers left an impression on you?”

  • Great (a bit less personal): “What is a food you could eat every day?”

  • Too extreme: “Who is your favorite sports player?”

  • Too personal: “What’s one of your big regrets?”

  • Too work-oriented: “What do you think about working at this company?”


  1. If I were to found another startup, I’d be in-person in a room until we have PMF and only hire remote team members once we scale. The communication/collaboration overhead of remote work is deadly for nascent, early-stage startups who have to iterate quickly; Stellate survived this stage by pure luck of the funding environment, but it was unnecessary additional risk.↩