All posts

A 30-day check-in for remote collaboration

A drop in remote collaboration is usually weeks old by the time you notice. A 15-minute monthly check-in catches it early, without tracking anyone.

By the time you notice that collaboration on a remote team has dropped, it has usually been dropping for weeks. A handoff gets missed, a project stalls because nobody asked the obvious question, or someone you thought was happy hands in their notice.

There’s an easier way to find out: a short check-in, once a month, starting around day 30. It takes about fifteen minutes, it doesn’t need a survey tool, and it looks at the team, never at individuals.

Why attendance isn’t the signal

The tempting thing to measure is attendance: how many people came to the game, the coffee chat, the all-hands. It’s easy to count, and it tells you very little.

Attendance measures who showed up to something you organized, not whether people work well together. If your activities are truly optional, attendance should go up and down. And high attendance can mean people feel they have to be there, which is its own problem.

The better signals are in everyday work.

Six signals to check

Pick the same day each month and look back at the last few weeks. For each signal, you’re looking for a direction, not a score.

  1. Where questions get asked. Scroll the team’s main channel. Are people asking questions in the open, or has it gone quiet while private messages do the work? Open questions are one of the best signs a team feels safe.
  2. Who talks to whom across groups. Find a few conversations between people on different teams that weren’t forced by a ticket or a deadline. If you can’t, the bridges are weakening, which is one of the main reasons collaboration drops after the first month.
  3. How fast people get unstuck. When someone was blocked recently, did they ask for help within a day, or sit on it for a week?
  4. Whether anything non-work gets shared. A photo, a recommendation, a joke in a thread. Its absence is often the first sign of drift.
  5. Whether new people are part of the conversation. Are recent hires posting and answering in shared spaces, or only talking to their buddy? The second month of onboarding is where this is decided.
  6. Who’s consistently missing. Not which person, but which group: one time zone, one role, the part-timers. A pattern there usually points to a scheduling problem, not an attitude problem.

Three questions to ask the team

Signals tell you what’s happening. A few questions tell you why. Keep them short and optional. On a larger team, collect answers anonymously. On a small team, where anonymity doesn’t really work, ask in regular one-to-ones instead.

  • In the last month, who outside your immediate team did you work with or talk to?
  • When you got stuck recently, how easy was it to get help?
  • Is there anything that used to happen here that has stopped?

Read the answers for patterns. If three people mention that the Friday game quietly disappeared, that’s your answer.

What to try first when something slips

Each signal has a small, matching fix. Change one thing at a time, then check again next month.

  • Questions moved to private messages: have a lead ask a simple question in a shared channel. It shows that not knowing things is fine.
  • Few conversations across groups: set up optional fifteen-minute chats between people on different teams, every other week.
  • Nothing non-work being shared: start one weekly prompt in a shared space, with a question people can answer in a sentence.
  • New hires are quiet: do a second round of introductions, based on the work they’re actually doing now.
  • The same group is always missing: move or repeat the live moments for their hours, following the approach in team building across time zones.

Resist the urge to fix everything with a big event. A big event helps for a week. Small, regular changes are what move the signals.

Keep it light, and keep it about the team

Write down three lines after each check-in: what you saw, what you’ll try, and what changed since last month. After a few months, those notes show you trends no single check can.

And never use the check-in to rate individuals. The moment people suspect their participation is being tracked, they start performing it, and the signals stop meaning anything. Measure the team, not the person.

Where Teamopia fits

Teamopia’s engagement insights show where participation across the team could use a nudge, at the team level, so part of this check comes ready-made. Most of it, though, is just paying attention once a month, and that works with any tools.

Keep reading

Start this week. Keep it going all year.

Set up in a few minutes. Free for up to 10 people.